I’ve generally been up front when starting new jobs that nothing impinges my ability to work on FLOSS software on my own time. Only one company put a restriction in for working on FLOSS software in the same technical space as my $DAYJOB.

The article mentioned there is a long history of forks in the open source Doom world. It seems the majority of the active developers just moved to the new repository.

I helped with the initial Aarch64 emulation support for qemu as well as working with others to make multi-threaded system emulation a thing. I maintain a number of subsystems but perhaps the biggest impact was implementing the cross compilation support that enabled the TCG testing to be run by anyone including eventually the CI system. This is greatly helped by being a paid gig for the last 12 years.

I’ve done a fair bit of other stuff over my many decades of using FLOSS including maintain a couple of moderately popular Emacs packages. I’ve got drive by patches in loads of projects as I like to fix things up as I go.

Was it before or after Oracle acquired Sun that the fork happened? I’m fairly sure it was Oracle that passed the project across to Apache and I have no idea why the Apache foundation accepted it.

I’ve long avoided npm but attacks on PyPi are a worry.

Sorry to hear that. Good luck finding a new gig without needing to interact with Teams again.

I used to update my tickets from Emacs org-mode where I kept my working set off knowledge. The org export functions dealt with whatever format Jira expects. Nowadays I’m mostly tracking stuff so my comments are generally never more than a “thanks”, 👍 or occasionally a link to the patch series or pull requests.

Jira is alright, not great, not terrible. You need something to track projects and break down work and say least being ubiquitous a lot of people are familiar with it.

Teams is a dumpster fire of excrement though.

Care needs to be taken with big orgs like the NHS to not try and boil the ocean with massive IT systems. Concentrating on open interoperability standards allows for smaller more flexible contracts and the ability to swap out components when needed.

Open source licences would be the ideal default although at a minimum the purchasing org should have a licence that allows them (or subcontractors) to make fixes without being tied to the original vendor.

FLOSS projects can only be sustainable if their are enough shared interests able to support it through contributions of all kinds. Fortunately the code is free so that constellation of support can change over time. It’s a shame this particular line of government funding is coming to an end but others can help.

I think the most useful thing for this is hosting repos that suffer from constant DMCA takedowns. Emulators, ad-blockers, site revancers etc.

These are all excellent ways someone can contribute to a project. Our project website has a repo anything can contribute to to make changes, even the blog entries are statically generated pages.

Can those handle the meta data for the track name, artist and release date. Assuming you want a portable playlist that can then find the track on the recipients preferred platform (streaming provider or self hosting). Given that a lot of tagging is trash maybe also included an audio fingerprint for validation?

Yep I’ve been a happy Antenna Pod user for years. A double tap of my headphones skips 30s forward, triple 10s back and makes skipping past the ads easy.

There is a very large corpus of FLOSS software out there serving everything from individual itches to whole industries. Any project that is important to someone’s bottom line is likely to have paid developers working on it but often alongside hobbyists.

The project I predominately work on is about 90% paid developers but from lots of different companies and organisations. Practically though the developers don’t care about the affiliation of the other developers they work with but the ideas and patches they bring to the project.

I don’t quite follow what this is. Is it a from scratch implementation of the vscode experience or a fork which has removed propriety and telemetry?

I work for a company that makes money supporting FLOSS. Our members pay fairly hefty membership fees because they have a vested interest in their chips being well supported by Linux and the wider ecosystem. That money funds common projects they all benefit from all well as numerous maintainers in projects keeping those projects ticking.

The engineers on the project I mostly work on are predominantly paid to work on it. We value our hobbyist itch scratchers (~10% off contributors) but it’s commercial money that keeps those patches reviewed and flowing.

My Organic maps has a download screen for the maps which regularly update outside of the app itself.

I think you underestimate how much storage those tiles take up compared to the vector map data.

The data updates are handled separately in app