Earlier quoted context omitted.
open-source /əʊp(ə)nˈsɔːs/ adjective denoting software for which the original source code is made freely available and may be redistributed and modified Adding community to this definition is a stretch. It really doesn't matter if in practice communities form around projects, there are far more open source repositories on GitHub that have zero outside contributions, those projects are still open source.
You could try that definition during the 16 - 22 time period and experience the backlash on HN and Twitter. It is also interesting most of these zealotry were gone by the time Fed raises Interest rate and Tech companies started laying off or delaying bonuses.
How ‘open’ should your open source be?
61–67 of 67 posts
Re: How ‘open’ should your open source be?
#62Earlier quoted context omitted.
Well I mean I started out essentially with my own fork, that has modifications that make sense to me. In doing so, I found a trivial optimization that it would be neat if it was backported. Although this would benefit everyone using the mainline project, this is of very low personal importance to me and my patience for navigating an obstacle course is fairly low, even if this is to the detriment of the wider develope…
The goal of the filter is probably to pass people for whom benefiting everyone who uses the project is important because in the long run that's more valuable to the team and more sustainable for the project.
Re: How ‘open’ should your open source be?
#63Earlier quoted context omitted.
Free Software as explicitly anti-corporate is not something Microsoft likes to remind itself of.
Free/Libre Software is not anti-corporate, it is pro-user's freedom to use, modify, sell and improve such software
If floss takes over the world there’s no place for corporate software.
But I think it’s a false dichotomy and we will be a pluralistic state (like we are now) where there’s free/libre software that’s really popular and also corporate software where no one wants to volunteer their time to build.
But I understand how Microsoft could think that GPL is a threat to them. Linux did kind of kill (is killing) their dream of every server in the world running windowsnt.
Re: How ‘open’ should your open source be?
#64> First, let’s take a look at how we got here. > Open source eats the world (and needs some Tums) > Early software was written by researchers and academics, and open by default—it couldn’t even be copyrighted until 1974. We didn’t even have the now-common phrase “open source” until Christine Peterson coined it in 1998. That same year, the OSI formed and established the aforementioned open source definition, which rem…
> I realise that this is intentionally a very highly-compressed version of history, but Author here. As you say, it's a highly-compressed version of history. Getting into the finer points of the evolution of open source wouldn't really have had any bearing on the rest of the article.
Also, this is your readme so it’s not like you have some editor pressuring you to cut down.
Re: How ‘open’ should your open source be?
#65broken on Firefox mobile. Mirror: https://archive.is/0bxwR
Re: How ‘open’ should your open source be?
#66Re: How ‘open’ should your open source be?
#67Earlier quoted context omitted.
Complex projects need to have extensive tests if they are to accept contributions from everyone. I don't mean just unit tests - also extensive integration tests run with sanitizers and static analyzers as well. Without this kind of tests, you accept a significant probability of frequent bugs popping up (especially if you allow contributions from people unfamiliar with the code). It's perfectly fine for authors to dec…
I don't understand how this is supposed to be a response to what I wrote.