Kinda frustratingly written by ai
Particularly frustratingly because it's so unnecessary in this case. It's not even that much text, just write it yourself. It would probably take less time.
What they don't tell you about maintaining an open source project
11–20 of 171 posts
Re: What they don't tell you about maintaining an open source project
#12This is actually nice and balanced, but the title is misleading. I feel like ALL I hear about maintaining an open source project is how hard it is and how people burn our. I almost never read a blogpost or comment declaring how rewarding it is. So, this was a nice (slightly) more balanced view.
Re: What they don't tell you about maintaining an open source project
#13Kinda frustratingly written by ai
No evidence of this
Re: What they don't tell you about maintaining an open source project
#14Kinda frustratingly written by ai
Just curious, how do you know / why do you think it's written by AI? The bullet points?
Re: What they don't tell you about maintaining an open source project
#15> maintaining kaneo means helping people debug their setups. and honestly? it's taught me more than i expected.
> people run kaneo on setups i never imagined:
> behind corporate proxies
> ...
> in kubernetes with custom networking
It's OP's project so they're welcome to support whoever they want but I definitely would not offer free support to customers who are obviously using the product commercially, especially in large enterprises.
It's FOSS, so they can use it for free if they want, but if they need custom support or features, they're a great user to tell, "Sure, I'm happy to help you with that if you purchase a $500/yr support contract." You'd be surprised how many customers like that don't care because they have a corporate card and that amount is too little to require approvals or much process.
Re: What they don't tell you about maintaining an open source project
#16I liked the humble, “lessons learned” tone of the post.
> every feature you add is a feature you maintain forever.
This.
Keeping a framework/app/SDK “pure” is very important, in my experience.
Re: What they don't tell you about maintaining an open source project
#17> maintaining kaneo means helping people debug their setups. and honestly? it's taught me more than i expected. > people run kaneo on setups i never imagined: > behind corporate proxies > ... > in kubernetes with custom networking It's OP's project so they're welcome to support whoever they want but I definitely would not offer free support to customers who are obviously using the product commercially, especially in…
But the company wants a proper invoice. And not every single developer is interested in founding a Limited and getting the tax office breathing down their neck every year.
Also, look at Gitea. People got paranoid and forked the project after the original author did exactly that.
Re: What they don't tell you about maintaining an open source project
#18This is why I like building outside plant. You put the fibre up on poles or pull through ducts, splice it, bring it into the building, hook it up to the equipment, make sure it's working and.... you're done. It works until something breaks, usually for a very clear reason (power outage, drunk driver, rodent, vine, lawnmower man, fibre seeking backhoe, dump truck, direct lightning strike, thermal cycling of a marginal splice, failure to seal a gasket properly resulting in water intrusion that stresses fibres when the water turns into ice, ...), but those become quite rare if you're done your job properly.
On the other hand, software is never done. Even simple features, like headphones, regress these days. (I missed a meeting today because my phone decided to send audio notifications into the black void of the heat death of the universe because I didn't unlock my phone after plugging the headphones into the USB-C port of my iPhone -- the audio didn't come out of the speaker, nor out of the bluetooth of the car I was driving. No sound worked until after the phone was unlocked.)
At least with open source software I can fix the bugs I care about, but the fun goes away once you have to deal with other people to get things merged.
Is there a community of software Luddites I can go live with where we build simple technology that works and works well?
Re: What they don't tell you about maintaining an open source project
#19Kinda frustratingly written by ai
Hmm, I didn't pick up anything reading it but going back it does have that vibe with the repeated bullet points and cadence.
I wouldn't be certain of it but I can definitely believe it.
Re: What they don't tell you about maintaining an open source project
#20> maintaining kaneo means helping people debug their setups. and honestly? it's taught me more than i expected. > people run kaneo on setups i never imagined: > behind corporate proxies > ... > in kubernetes with custom networking It's OP's project so they're welcome to support whoever they want but I definitely would not offer free support to customers who are obviously using the product commercially, especially in…
But the company wants a proper invoice. And not every single developer is interested in founding a Limited and getting the tax office breathing down their neck every year. Also, look at Gitea. People got paranoid and forked the project after the original author did exactly that.
> But the company wants a proper invoice. And not every single developer is interested in founding a Limited and getting the tax office breathing down their neck every year.
I feel like it shouldn't be poor form to say on this site - a site that predominantly has been about building tech companies and revenue streams - to get over it and charge them.