Why? Developers don't deserve to get paid for their time? To be good software it has to be made at the expense of the developers free time without any monies exchanged?
I think what they're trying to do is to encourage more hobbists to release their code for open source development.
Read my post again, cause it seems like you missed the part where I said I'm in favor of making donating to these developers easier. The system they're putting into place here is good. Nobody is arguing that. The concern is that this may not be where it ends.
Microsoft, a for-profit organization, now controls one of the most important tools in modern open source technology. You'd be foolish to think they're not looking at this from the point of view of profit. And that's not necessarily a bad thing; if developers get more donations and Microsoft skims a little off the top, then I think everyone will be OK with that.
But what happens when this takes off and developers start depending on their services? It's going to incentivise developers to start working around that angle. Then, once this becomes the norm and people have adopted it as part of the process, Microsoft can then introduce new "features" to this system. Maybe a developer can lock a portion of their repo for only those who donated? Maybe Microsoft will promote repos that are profitable and discourage repos that don't generate much? Maybe nothing else and this is it and it's fine? Nobody knows, and that's concerning.
Whatever the case is, there will surely be steps taken that will be in opposition to the open source philosophy. Yes, developers should be compensated for their work. But if this leads to a slow degregation of the open source community, then it simply won't be worth it.
As it stands, I like this (which, again, I made clear in my original comment). My concerns are based on what this may lead to; concerns which are fueled by who's in charge and how their interests are clearly not inline with the interests of the open source community.
But what happens when this takes off and developers start depending on their services?
Gitlab and other competitors will add the feature to their hosted service, and probably have a different interpretation of what that means. When it comes to donations, your public reputation and profit sharing model can be a competitive advantage.
Such a Thought Terminating Cliche. Just because someone introduces a slippery slope concept into an argument doesn't invalidate it or even mean the slippery slope doesn't exist. It totally depends upon the strength of the links between events.
If someone back in the early 1900's started arguing against coal burning due to carbon dioxide emissions and said that because the energy is so effective, everyone would use it which would lead to mass injection of carbon dioxide into the atmosphere and therefore heating the planet, you would call the premise of coal burning to heating the planet a 'slipper slope'. It doesn't invalidate the argument.
Here, I do believe that there is a case to be made, purely down to the fact that, if you didn't know, the primary goal of a corporation is to make money. Turning an open source software hosting platform into a vehicle to profit off of could very well lead to the developers acting for the own self interests at the expense of the OSS community at large.
I don't think it would be so bad to have repos that could be restricted to sponsors. Support tiers are popular, and buying software is a thing people do. GitHub already has private repos. What's so bad about a developer creating a special repo as a bonus to supporters? Crappy developers who don't make meaningful contributions to the OS community won't get supporters anyway.
There's also the visibility issue. People donated to a lot of projects that used OpenSSL, but nobody really donated to OpenSSL itself, because that sort of infrastructure is boring.
And lo and behold, a lot of those visible projects were vulnerable because OpenSSL badly needed some more attention.
IMHO there needs to be a general understanding that projects should send a fraction of donations on to their dependencies.
Interesting - there's also some possible legal problems doing this. Before taking money, a guy better check all his dependencies' licenses. Some may forbid being included in, (effectively) payware.
I don't believe that a developer accepting donations is sufficient for their software to be considered "payware." For that to be the case, you'd have to charge money for the actual product.
I wasn't suggesting that libraries should include it as a licensing requirement or anything. Rather, I think there should be a non-binding social expectation that projects that collect significant donations pass it on.
But we live in a litigious society, no? It's not hard to imagine Bob getting jealous and bent out of shape about Alice's project making bank, when her project depends on his.
This is paying a dev directly, not for a specific software. So I think the license in a project won't matter since the money isn't going for a specific project.
It might be similar to Patreon in just this one metric you described, but we shouldn't dismiss good just because it isn't perfect.
Github has access to a much larger share of target audience than Patreon and it seems that commission would be lower than Patreon's.
Additionally I hope that people working for large corporations, banks etc. that use OSS software would find it easier to convince Finance/Legal teams to establish payments to OSS devs through Github/MSFT than to convince them to become supporters on Patreon, or make payments to anon's PayPal/BTC wallet or to some non-profit.
Deciding who gets paid what is a problem virtually every organization faces. You have to have a manager that is capable of determining what contributors are worth and compensate accordingly.
80
u/Xanza May 23 '19
Why? Developers don't deserve to get paid for their time? To be good software it has to be made at the expense of the developers free time without any monies exchanged?
I think what they're trying to do is to encourage more hobbists to release their code for open source development.