3 ms·

> If somebody is a user and decides to write a pull request, they are already invested anything more is virtue signaling, no amount of which will guarantee that

> If somebody is a user and decides to write a pull request, they are already invested anything more is virtue signaling, no amount of which will guarantee that they will be there in years, which is an unreasonable stipulation for a project that could be obsolete yesterday. I'll believe that when they're replying to issues, labeling bug reports, etc. Hell, or even making PRs that maintain the code base! That would be an instant commit access. Writing new code is easy. Maintaining is tough, boring, etc. Again, if i even get a gut feeling that this is going to be work - i'd rather just fork my own damn project and give them my old one. I FOSS projects to let others use my work if it's of value to them. It's a thin line between having fun side projects and work. I think you misunderstand the type of projects i FOSS. If your arguments were common i'd be more inclined to just make projects private, as i'm that averse to wanting more work in life. I really, really like to keep the fun in my projects.

em-bee 3y ago
replying to issues, labeling bug reports, etc i do that on projects that i am interested in. because it sometimes is a good way to get into a project and show that i care about the project as a whole, not just getting my patch accepted. and why should i not care? i am using it myself. to call that virtue signaling as the grand parent comment does, is frankly insulting. however, caring about a project doesn't guarantee anything. a while ago i found a nice project that solved a problem i had. it had some bugs that i fixed to make it work for me. i shared the issues and fixes with the project, expecting to do more work later. but then my situation changed and this project is no longer a priority. i hope to get back to the it, but i can't say when that will be. i still care about the project, i just don't have time for it now.

em-bee 3y ago

replying to issues, labeling bug reports, etc i do that on projects that i am interested in. because it sometimes is a good way to get into a project and show that i care about the project as a whole, not just getting my patch accepted. and why should i not care? i am using it myself. to call that virtue signaling as the grand parent comment does, is frankly insulting. however, caring about a project doesn't guarantee anything. a while ago i found a nice project that solved a problem i had. it had some bugs that i fixed to make it work for me. i shared the issues and fixes with the project, expecting to do more work later. but then my situation changed and this project is no longer a priority. i hope to get back to the it, but i can't say when that will be. i still care about the project, i just don't have time for it now.