131–140 of 284 posts
This is the big fallacity here, although I'm not sure why "free" is in (scare) quotes. FOSS isn't necessarily volunteer free-time development; afaik for example vast majority of Linux development is done by salaried engineers as their day-job. That is the way things should be done imho.
Earlier quoted context omitted.
I'm working on precisely this problem. My current idea involves payment plans defined in code. See: github.com/openfare/openfare
Good luck! At least promise, if but a dull glimmer of hope...
The up-and-coming generation of developers have grown up exposed to millionaire content creators. They might start wondering about their cut.
Earlier quoted context omitted.
I know many people, including myself, who do a lot of volunteer work without being Marxists. The motivation is not money, but to provide a benefit to society or to the people in the immediate vicinity, i.e. to be helpful and to be appreciated.
Thank you for your generosity!
Earlier quoted context omitted.
I'd like to include my reasons: - It's a lot of fun - It's addictive Honestly I was a bit struck when a friend looked at my github and said it was a nice portfolio. The material view never hit me at all: my github is a product purely of what I've wasted/spent time on for fun, not to make a profile. :)
I'm not a fan of the trend I've seen where GitHub is treated as a portfolio- I once had a hiring manager I worked with tell me I should delete a few of my GitHub projects, as they made me appear "amateurish." I WAS an amateur! And I don't want to feel like I need to to hide random things I've tinkered with just to impress others. As a result, I know those who have multiple GitHub accts, one for fun personal stuff and…
That’s what I do. Even my “farting around” projects have a lot of polish. I write everything I do as if it will ship.
I find it establishes great work habits and personal integrity, and my GH ids (I have a personal one, and a couple of org ones) make outstanding portfolios[0].
Not to worry, though. My experience, is that potential employers never look at at GH portfolios. Instead, they rely on leetcode tests to evaluate applicants.
"Since companies steal Open Source software without a care in the world" If you don't want companies to use your code for free, don't publish it for free. If they violate the licence, presumably it is a case for the courts. People have different reasons for working on open source. Some want to make money from it, others don't. As an example, I don't know the full ElasticSearch story, but if Amazon's fork was legally…
> If you don't want companies to use your code for free, don't publish it for free. If they violate the licence, presumably it is a case for the courts. Good look to the OBS team in pursuing legal actions against ByteDance/CCP.
"Since companies steal Open Source software without a care in the world" If you don't want companies to use your code for free, don't publish it for free. If they violate the licence, presumably it is a case for the courts. People have different reasons for working on open source. Some want to make money from it, others don't. As an example, I don't know the full ElasticSearch story, but if Amazon's fork was legally…
>If you don't want companies to use your code for free, don't publish it for free. If they violate the licence, presumably it is a case for the courts. this is assuming you have the resources to : a) know the theft happened b) follow up in court.
Nitpicking from the main point, but logging companies are still destroying our planet/forests. They haven't learnt a single lesson. The most valuable woods come from very unsustainable exploitations far away (from my perspective, eg. Philippines/Canada), and as for the so-called "sustainable" local exploitations here in France they earn the label by destroying entire ecosystems and replanting between 3-6 species over the entire area after they've chopped everything down.
It's still ecocide on a wide scale.
The reasons you write open-source code: - training purposes to better yourself - as a showcase or to build up your reputation to get hired - because you have a niche need in your personal life that no one else already solved None of those reasons are invalidated by big corporations using open-source without paying back.
That does not work. After several years of hard work a prior open source project that grew to immense popularity got me employment a few times. It wasn’t the actual project, code, or capabilities that meant anything. The only thing appealing about that project was it’s popularity. Nobody ever looked at the code, except people interested in submitting pull requests. If you think a prospective employer will take the ti…
If you think nobody ever looks at your public code, you're wrong. It's just like wearing a bathing suit at the beach or pool: people look.
Earlier quoted context omitted.
> As an open source coder, I theoretically love the above The above is not open source, it's a pretty common free (gratis) for limited use, paid for other use commercial/proprietary license of the type tons of non-open-source software uses. (E.g., Visual Studio.)
It is most certainly Open Source, in that the source is open. In the case where a support contract is available, but not required, it is no less free than any other free software, but there is at least a chance that it might be bankrolled, as well as the projection that this is a professional project. Even where the support is required, it is my understanding of RHS that that won't impede on the title free, since the…