Pet peeve: People complaining about the way I maintain my open source projects under MIT license (particularly my decision to use stale bot, since I don't like seeing literal thousands of open issues across my repos).
Just fork it! No skin off my back. https://www.jeffgeerling.com/blog/2022/just-say-no
@geerlingguy There is a distinct difference between a timeout based stale bot and saying no to an issue. With the former you ensure I will probably never contribute to your things again, with the latter I am still happy to help
From a fellow opensource maintainer and contributor.
@darix fine by me!
I often post a PR to a project with zero expectations whatsoever.
The only reason I post it is so (a) I can incorporate that into my own documentation or fork, and (b) so others who use the project can benefit.
If anyone on the project ever decides to merge my code, that's just icing on the cake.
Aha Jeff’s making this stuff and giving it away for free. I’d imagine sometimes just in case someone else finds it interesting..
It’s not really up to Jeff to do anything. He could log out of GitHub and never log back in ever again, and that would be his choice. I’m sure if there’s a project you really need changed, you’ll be able to pay another dev to fork it and do whatever you are after…. Or reach out and offer to pay Jeff. Much love,no h8
Hi Darix,
Sorry I didn’t mean to offend. I actually hit the character limit. I’m really just trying to say that not all those who upload code to GitHub publically are necessarily planning to upkeep or maintain it for others nor do they really have to. I seriously applaud you if you have been maintaining projects off your own back for 25+ years just for the people!
You are doing gods work dude. Again I did not mean to offend and I’m sorry!
That’s fair enough of a take. I see what you’re getting at. Again I still think the open part of open source means I could create a project, make it public and then just start introducing bugs and breaking features people use on purpose just to piss people off. That’d be within my rights.. it’d also make me a dick of course 🤣
I just think anything on GitHub with an mit or other permissive license is up to the owner to just do whatever with.
@Nadsec @geerlingguy all of it is true. you can break shit as much as you want. And people do plenty of that. I have no problem with that TBH.
But bug closing bot just means it looks like your project has no issues, while the known issues list might be really long.
Guess how happy an user will be if they find out later "oh the project with no open bugs, that looked like well maintained, is just hiding the bugs with a stale timeout bot"
Appreciate you explaining further, what you’re saying checks out and I feel like I’ve learnt something! Cheers
I think in Jeff’s case he’s quite well known publically obviously. So I do think this is a bit of an edge case with a fella stuck between a rock and hard place. Anyways let’s agree to disagree or whatever it is we’re doing here 🤣 appreciate the insights! Open source is an ever evolving beast in and of itself.
Jeff Geerling
darix
Nad