Live data from Hacker News

My boundaries as an open source developer

joeldenning.com

11–20 of 251 posts

Re: My boundaries as an open source developer

#11

Is 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.

That wasn't my impression from reading it. The writeup actually seemed very reasonable to me. They perhaps sound like they're having a bit more trouble than many at handling the onslaught and saying no, but given that, this felt like a fine way to set things up.

So I'm curious: what in the writeup indicates a dislike of users?

Re: My boundaries as an open source developer

#12
post #5

Once 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.

I'm shocked that it doesn't. What would you do if you were being harassed?

Re: My boundaries as an open source developer

#13

Is 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.

Probably not. I think there is a difference between having guidelines for how to.contact you is not dislike if users.

Waking up at 4 am to reply to a poorly worded bug report with a demand you fix it immediately is exhausting and sucks your will to live

Re: My boundaries as an open source developer

#14

Archive - https://web.archive.org/web/20220105000136/https://joeldenni...

Are you expecting the author to delete it?

Archive links allow others to read the article if the site suffers a Hug of Death from hitting the front page of HN.

Re: My boundaries as an open source developer

#15

Is 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 got the opposite read regarding their mental health. This was a very clear and well thought out statement of reasonable boundaries, especially for someone volunteering their time. I admire them for it.

Re: My boundaries as an open source developer

#16

Is 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 didn't get that vibe.

Seems to me, that he wants to keep going on it, but isn't really a "people person," and wants to control his agenda.

I can respect that.

I managed an open-source project for a decade, that was designed to serve an ... interesting ... demographic.

I think many of the folks here, would have defecated masonry, if they got some of the contacts that I did.

But I'm a fairly tough old coot. I held my own. It wasn't pleasant, though, and I learned a great deal, about interacting with ... interesting ... people.

Re: My boundaries as an open source developer

#17
post #14

Earlier quoted context omitted.

Are you expecting the author to delete it?

Archive links allow others to read the article if the site suffers a Hug of Death from hitting the front page of HN.

Case in point, the link isn't loading for me right now. Seems to be hugged to death.

Re: My boundaries as an open source developer

#18
post #5

Once 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.

You can already turn on repository interaction limits limiting issues/PRs to collaborators. It needs to be re-enabled every 6 months https://docs.github.com/en/communities/moderating-comments-a...

Re: My boundaries as an open source developer

#19
post #5

Once 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.

You don't need to use github, especially when you don't want the public making issues.

Re: My boundaries as an open source developer

#20
post #5

Once 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.

It would be nice to make the "open source, but closed to contributions/collaborators" model like SQLite and others (lightstream, etc) follow more of a first class citizen on github.
Post reply on HN