nenolod

OFTC is run by the OFTC board (of which tomaw is a member) on behalf of Software in the Public Interest, who originally organized it for Debian.

Although we do not yet support recording the copyright lines in the package metadata, SPDX labels are used to provide linked data references to the license text. Copyright metadata itself will be included in apk3.

If all goes to plan it will be part of Alpine 3.15 as a release variant.

There is supervise-daemon(8) for this.

We are actually in the design phase for a declarative variant of Alpine using OSTree.

With musl we discovered that qemu does not always properly initialize structures when doing the syscall translation. Most likely this is a missing initialization.

TCG's uops are modelled after real ones. It is close enough.

The real takeaway from this is if you want to work on FOSS on your own time, without retribution from your manager, don't work at IBM.

As IBM is supposed to be a huge supporter of FOSS, this is a total disappointment.

It's not just about adding new architectures to LLVM and rustc, it's also about bootstrapping supported architectures on all architectures supported by a distribution.

This isn't fully done in Alpine yet, and took a long time to do in Debian.

George Varghese's Network Algorithmics is a good book for backend-oriented people to learn various fundamental CS algorithms.

It presents various CS topics from the perspective of backend optimization, so it's a good book for approaching theoretical CS from a background you already probably understand.

But, ultimately, the best asset for somebody with a CS background is not so much having immediate knowledge, but knowing where to acquire knowledge as necessary. If you have a general idea that for a specific scenario, you can acquire X knowledge in Y resource as you go along, then you're already doing quite well.

Trademark disputes are best solved with litigation, not product relicensing.

Amazon's behavior may feel exploitative, but it isn't. That would be like saying Red Hat is exploitative.

Part of the whole concept of free software is that you have freedom of choice with vendors (this is derived from "freedom 0"). Amazon is providing the software and its support as part of the Elasticsearch offering as a managed service. Elastic is a competing vendor, both as a managed service and in a traditional sense too.

Elastic made this decision because they wanted to be the exclusive vendor for Elasticsearch. That's fine, but it's not in the spirit of free software.

If anything, Elastic has exploited the third-party contributors who contributed to Elasticsearch under a CLA by promising to not do what they did and then blaming AWS for doing it anyway.

They share a similarity: the Floragunn litigation is unresolved (and clearly Floragunn continues to distribute their plugin). SCO, too, failed to resolve their litigation favorably to SCO.

Yeah? SCO sued a bunch of people too. They haven't won, though.

Incidentally, the fact that it is OK to use Apache-2 licensed components inside projects licensed as SSPL is probably a net negative for free software moving forward as there will be more of these companies which do this in the future. It doesn't end with Elastic.

I read that article and it is very redolent of what SCO argued back in the day. If they had actual proof, they would take legal action against the author of that plugin.

Amazon contributed code to Elasticsearch. They are certainly allowed to profit from their code contributions.

That activity is being driven in musl directly. 1.2 has introduced optimizations for arm, aarch64, x86 and x86_64. there's more to optimize, but some are already there.

The good news is that there is work in progress to untangle the mess with PyPI wheels and musl. But it is easy enough to just not use wheels.

If you don't mind using IRC, there's a lot of people willing to help you get started with this adventure in #alpine-devel on freenode.

We have started to extend musl with optimized routines like glibc does. But really, the performance difference is usually minimal.

On desktop, we support KDE, GNOME and Xfce, which are the big ones, but yes, we could use more work there.

It is hoped that the cloud images project will get Alpine available in all of the main platforms, we've done AWS already starting with 3.13.

What is it missing that makes you feel it is unrealistic?

this page really should be updated, at this point all you basically have to do is `apk add gcompat`.

The gcompat project, which provides a wine-like compatibility layer for glibc applications, is pretty close to having vscode working out of the box.

As someone who is writing an implementation, you are responsible by default for stewarding it.

As you are somebody who is responsible for stewarding the ActivityPub specification, I am seriously disappointed by this dismissive attitude.

It does work, but AP follows are asynchronous so it may take a minute for the relationship to update.

Actually, the behaviour of the Mastodon author promising a "safe space" in his paid, targeted advertising campaigns without any real plan for data security is the unethical behaviour. If you don't like that people can scrape the fediverse, fix the damn security.

fediverse.network contains fairly exhaustive lists of open registration instances for both pleroma and mastodon