It's a slippery slope. What about consultant developers that worked on the codebase of photoshop 10 years ago, whose code is still used in the current version? Do they deserve a percentage of the subscription? And architect who designed it?
This is the reason studios can do this, because the contract was very exceptional, and they want to make it similar to any other industry, where freelances and employees do not share any long term revenue
Can anyone access all and popular? I was curious to see the reactions but they are unreachable
They don't remove bugs, but it is easier to solve them without having to wait for some random guy to answer on stack overflow.
I don't know now (I haven't asked a question in ages) but to get a good answer on stack overflow it used to take weeks sometimes
GitHub issues are usually more useful
People isn't considering that documentation has greatly improved over time, languages and frameworks have become more abstract, user-friendly, modern code is mostly self explanatory, good documentation has become the priority of all open source projects, well documented open source languages and frameworks have become the norm.
Less people asking programming related questions can be explained by programming being an easier and less problematic experience nowadays, that is true.
They want to approve the whole environment, including os, even if virtualized or not
Why are you so aggressive? Lack of sleep? I was just asking
Even more "we'll decide if you are worthy to get my data"
Are you something else? What's your work schedule?
The fact that it is work that I don't want to do... Pretty much
I read it, and I read the messages from the devs. The communication issue I am trying to point is also highlighted in the comments: if the decision on merging a PR is uniquely dictated by financial benefits of IBM, ignoring the broader benefits of the community, the message is that red hat is looking for free labor and it is not really interested in anything else. Which is absolutely the case, as we all know, but writing it down after the recent events is another PR issue, as red hat justified controversial decisions on the lack of contributions from downstream.
The Italian dev tried to put it down as "we have to follow our service management processes that are messy, tedious and expensive" but he didn't address the problems in the original message. The contributor himself felt like they asked his contribution just to reject it because of purely financial reasons without any additional details. It is a new PR incident
Do you have examples? It should only happen in case of overfitting, i.e. too many identical image for the same subject