The G in GNU stands for GET after all!
GNU Hurd
Microkernels project. In development since 1990, with varying activity.
After years of stagnation, development picked up again in 2015 and 2016, with four releases during these two years.[18] Since then, no release was made, but distributions pick up snapshots to produce distribution releases. - Wikipedia
Wikipedia lists six distributions; amongst them Arch, Debian, Gentoo, Guix
When I see that it's GNU, I can trust in it's license, and that it's backed by an org - whether actively maintained and developed or not. My impression is that the sources are not accessible to me, personally, mainly because of legacy tech stack but also they're typically in C or C++ which is often less approachable, and often they're Linux-only or -focused.
The GNU label, (if confirmed by the project being on their official websites), gives projects an immediate boost in trustworthiness over random FOSS projects.
I suspect many don't enforce it via GitHub functionality, but do implicitly require or recommend reviews.
How many contributors do these projects have? All multiple active?
If the original contract was for software without source code, you'll have to negotiate. I don't think it's helpful to look for options and licenses before knowing what they are ready to do and share and what restrictions they would require for that.
They would be very well within their right to outright refuse. The vendor-lock-in may even have been an explicit business strategy. I assume they offer maintenance, at a higher price than you would cost?
What does this parallel work mean? Does the background agent work on the same codebase as you? Doesn't that cause conflicts and confusion?
I would rather not have my 20-60 work commits, possibly shifting solution design twice or three times, in the main project history, spanning days and sometimes weeks, invalidating earlier commits, and a hassle if not impossible to reasonably and efficiently document changes between them. And all those changes intertwined with my other work and my colleagues' changes.
The key insight from Charity Majors is that speed and safety are not trade-offs -- speed IS safety. “Ship a single changeset by a single dev at a time, making it easy to isolate the owner of any problem, preventing the blast radius from expanding, and making it easy to fix while the intended effects of the code are fresh in their mind.”
I really don't get how "develop in feature-flagged trunk" is supposed to come together with "single dev single changeset". Work evolves. Design evolves. Surely, multiple/many "single changesets" must come together to form new features and changes? This claim seems to assume issues are found before it's being changed again, and in a timely manner, even when it is behind a feature flag?
Were pull requests really "created for FOSS"? I feel like, maybe assume, pre-merge reviews have been a thing before that [and unrelated to PRs].
I feel like the article could have been structured a lot better, and made its point without a "it's like this" "but maybe not" digression. Feels like inflammatory bait into relativation. I guess I'll refrain from raising my other points and disagreements that I noted because by the end of the article, it wasn't really claiming it broadly anymore anyway.
Outside of the irritation, I found the arguments interesting. I'll keep it in mind, but I don't see my team implementing it like that or to a higher degree. For various reasons.
Despite the negative vote sum, I think it's an interesting alternative perspective. Even if I found it irritating to read, and even if people hate it, it's a good discussion in the comments. About how we work.
MoonRay GitHub Source Repository, Apache 2 license
I hope Microsoft leaves GitHub alone
I see no way of that happening. GitHub is a huge resource for Microsoft; in terms of market penetration, people platform, but especially now with GitHub Copilot and their push for AI. They can't let go of GitHub.
Are there docs / an overview of what it does and how?
I remember Google marks their generated videos in some way. Is this based on similar or same published papers and approaches?
Before publishing, that text really needed a self-review/read-through. So many obvious issues to spot. Numerous typos like 'techjnical ', issues like double words 'missing missing', and so on.