My boundaries as an open source developer
joeldenning.com
My boundaries as an open source developer
1–10 of 251 posts
Re: My boundaries as an open source developer
#2Re: My boundaries as an open source developer
#3I only have one rule: I only contact an open source developer if I believe resolving the problem would make the product better unless I am willing to offer them reasonable money to do it.
Re: My boundaries as an open source developer
#4[deleted]
Re: My boundaries as an open source developer
#5Once again I wish github would allow the ability to limit who could open issues and PRs in order to do development in the open with a trusted/vetted set of collaborators without being subject to every zero-effort bug report from users.
Re: My boundaries as an open source developer
#6Is this person OK? Doesn't seem it. I use single-spa. I'm now worrying about it's future with the sentiments and apparent dislike of users expressed here.
Re: My boundaries as an open source developer
#7Archive - https://web.archive.org/web/20220105000136/https://joeldenni...
Are you expecting the author to delete it?
Re: My boundaries as an open source developer
#8Once again I wish github would allow the ability to limit who could open issues and PRs in order to do development in the open with a trusted/vetted set of collaborators without being subject to every zero-effort bug report from users.
Bots that close or even delete issues where the issue template hasn't been filled in help a lot.
Re: My boundaries as an open source developer
#9Is this person OK? Doesn't seem it. I use single-spa. I'm now worrying about it's future with the sentiments and apparent dislike of users expressed here.
I don’t see a dislike of users, just a dislike of the stress that being an open source maintainer tends to place on people.
Re: My boundaries as an open source developer
#10I only have one rule: I only contact an open source developer if I believe resolving the problem would make the product better unless I am willing to offer them reasonable money to do it.
Doesn't (almost) every bug report/feature request meet this criterion?