Live data from Hacker News

What they don't tell you about maintaining an open source project

andrej.sh

81–90 of 171 posts

Re: What they don't tell you about maintaining an open source project

#81
post #78

Earlier quoted context omitted.

This is not as simple as it sounds. Just yesterday I had a call with the Delft university of technology in Netherland, they want me to add some features on the free version of my FOSS product [1] but they did not want to pay anything. Over the last month, I was in contact with a 800B publicly traded company for a 1.8k per year invoice, once we agreed on the general direction they kept adding expectations, first was t…

Universities are a special case. They generally don’t spend money because of the red tape. In much of corporate America expenses under $100 give or take don’t even require documentation, so a $50/month support subscription is easily purchased. Just need to find the person with the purchase card.

In my experience, having MIT and UCI as customers, US universities are much easier to deal with small to no process for simple cheap things. On the other hand, I was contacted by a well known engineering school in France (ENSEEIHT), they wanted support but were laughing at the idea to spend 20$ per month for the privilege, left the impression they wanted to use my time for way under minimum wage, same yesterday with a deutch school who wanted help but not willing to spend a dime, and some other universities who have deployed my software in prod but did not upgrade in the last 5 years. Even in China, I stumbled upon a fork maintained by the university of Shangai, of course they never reached out in the first place to ask for any kind of support, just took the code and went their own way. This kind of behavior haven't happen with US universities which are more likely to reach out and pay for support

Re: What they don't tell you about maintaining an open source project

#82
post #54

Earlier quoted context omitted.

[flagged]

Well not every country is Germany. Dunno what to tell you there. The second half of that also sounds unhinged.

You aren't wrong on either; Germany's tax law is insanely complex but also many people don't want to change the tax law as they can deduct a million and one things.

Re: What they don't tell you about maintaining an open source project

#83
post #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…

or you could do what tsx does? charge money to fix issues as an option https://github.com/privatenumber/tsx/issues/758 issues are fixed on priority basis for people willing to pay

Re: What they don't tell you about maintaining an open source project

#84
post #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…

This is not as simple as it sounds. Just yesterday I had a call with the Delft university of technology in Netherland, they want me to add some features on the free version of my FOSS product [1] but they did not want to pay anything. Over the last month, I was in contact with a 800B publicly traded company for a 1.8k per year invoice, once we agreed on the general direction they kept adding expectations, first was t…

It's actually pretty simple. For the former case, you do nothing. Tell the university to find someone to make the improvement, or do it for fun. In the latter case, you should be charging 5-10x that, for starters... You send a Statement of Work, and only do what's in that, and only after they pay.

Re: What they don't tell you about maintaining an open source project

#86
post #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…

This is not as simple as it sounds. Just yesterday I had a call with the Delft university of technology in Netherland, they want me to add some features on the free version of my FOSS product [1] but they did not want to pay anything. Over the last month, I was in contact with a 800B publicly traded company for a 1.8k per year invoice, once we agreed on the general direction they kept adding expectations, first was t…

I agree, it's not as simple as "$500 per year". In some cases it can be, but mostly it's not.

Firstly, you need to clearly define what is included, and even more so, what is not included. How many hours is $500? Who decides what us should bug? Can they get new features because they have support? How many installs does the support cover? And do on.

And if they start with things like "supplier agreements" etc, just walk away.

Yes, some companies have a threshold where managers can just "spend money". Some managers may even use that to support you. But taking any money changes the relationship you have with the user.

Right now, it's completely inside your control. Direction, Priorities, Scope, Pace, levels of effort etc. I'm a huge fan of getting paid, I write software for money, but make no mistake - taking money changes things.

Re: What they don't tell you about maintaining an open source project

#87

Kinda frustratingly written by ai

Just curious, how do you know / why do you think it's written by AI? The bullet points?

For me, it could be:

> it's not better. it's different

> automation isn't lazy. it's sustainable

> it's not about gatekeeping. it's about making debugging possible

This is everywhere in the article.

Re: What they don't tell you about maintaining an open source project

#88
post #20

Earlier quoted context omitted.

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

[flagged]

You should definitely charge enough to hire an accountant to handle the bureaucracy. This might be multiples of the payment for the technical bits but probably still cheaper than a hitman/woman.

Re: What they don't tell you about maintaining an open source project

#89

> someone opens an issue: "how do i install this?" Honestly, this is a GitHub thing. You wouldn't get that issue on sourcehut, bitbucket or self hosted. GitHub is the lowest common denominator for users.

You’re telling me all I have to do to stop all the noob questions is to switch off of GitHub?

Re: What they don't tell you about maintaining an open source project

#90
post #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…

This is not as simple as it sounds. Just yesterday I had a call with the Delft university of technology in Netherland, they want me to add some features on the free version of my FOSS product [1] but they did not want to pay anything. Over the last month, I was in contact with a 800B publicly traded company for a 1.8k per year invoice, once we agreed on the general direction they kept adding expectations, first was t…

fwiw the pricing page is buggy on mobile:

- the second 'start' button overlaps the list items

- tapping that button darkens the whole page but doesn't display anything new

- even before I get to that stage, it's not clear what you're selling at each price point

Post reply on HN