Live data from Hacker News

Open source projects should run office hours

simonwillison.net

211–220 of 279 posts

Re: Open source projects should run office hours

#211
I think it’s time to take open source to the next level.

There are armies of retired, under employed, and even just people bored at work, ready to start making an impact.

What are your ideas?

More Open source projects For hardware and physical items

Involve people of all skills, marketing, PR, event planning, who knows!

Re: Open source projects should run office hours

#212

Earlier quoted context omitted.

To me (non-native, Spain), I read "office hours" as the time when I was a teacher in university: you have a set period of time where you are marked as available in your office for student consultation. I'm pretty sure that's what "office hours" is supposed to mean, although in Spanish and Catalan the word used would literally translate as "consultation hours" (horas/hores de consulta).

The term "office hours" in American English can mean either of these concepts, but in the current context it clearly means the one you suggest ("horas de consulta").

[deleted]

Re: Open source projects should run office hours

#213
post #100

Earlier quoted context omitted.

You may have gotten this in reverse direction: it's rather that users of open-source software often desire support, and sometimes speak about it, and developers then tend to have hard time managing psychological boundaries with regards to answering that desire/expectation. Which is generally a nontrivial thing between people in any relation.

Interesting historical note, this is how Chef was born. Adam Jacobs of Chef was running a Puppet consulting company (hjksolutions). He ran into a bug (#1010) that he couldn’t solve and used up a ton of Luke’s time. Luke worked hard on it but couldn’t reproduce it and after devoting a week or two on it told Adam that he was the only one with this problem and would need to pay him as a consultant for any further effort…

User’s sense of entitlement is probably driven by many companies astroturfing FOSS.

People are getting used to the freemium model popular in software, apps, games, and the "free" model of gmail/youtube/facebook (where you pay with your privacy).

Re: Open source projects should run office hours

#214
post #170
post #167

Since about half of this thread is (reasonably) taking offense at the implication from the headline that this is yet another demand for free labor from open source maintainers, I'd like to emphasize this sentence: "I’d like to encourage more open source project maintainers to consider doing something similar" It's a matter of fact that many people (myself included) form opinions based on the headline without reading…

I re-titled it "Open source projects: consider running office hours" - if a bunch of different people all misinterpret something the same way that implies poor communication on my part.

No it doesn't imply that. Your article is crystal clear, and makes a valid point based on your personal experience. So, thanks for writing it, and don't bother too much for internet points !

Re: Open source projects should run office hours

#215

I have deep aversion to "Open source projects should run office hours" title. Maybe "Office hours may be a good idea for open source projects"? This would not suggest obligation. In general, fact that someone created or maintains or supports open source projects should not be considered to create any obligations beyond lack of malice and abuse. I am not obligated to support any bugs, create any features and it is per…

It's a clickbait title. That being said the real idea is the freemium consulting concept. Basically open source Devs give free consulting for a short time and then upselling to full on consulting for extended periods at full price.

In theory it could be a way to fund open source dev.

Re: Open source projects should run office hours

#216
post #206

I have deep aversion to "Open source projects should run office hours" title. Maybe "Office hours may be a good idea for open source projects"? This would not suggest obligation. In general, fact that someone created or maintains or supports open source projects should not be considered to create any obligations beyond lack of malice and abuse. I am not obligated to support any bugs, create any features and it is per…

The submission title appears to be editorialized. Original title is "Open source projects: consider running office hours" And the article talks about the purpose being for gathering feedback (think UX sessions), not for gratuitous support. Meaning that goal is for the project maintainer to draw benefits from others donating their time. Personally I think this a really clever idea

Actually, the submission title is referencing the original title of the article, but the author edited it and left a note at the bottom:

>Update 5th March 2021: The original headline of this piece was “Open source projects should run office hours”. This was being misinterpreted as yet another demand for free labor from open source maintainers, so I changed it to “Open source projects: consider running office hours”—less pithy, but it better reflects my actual message here.

Re: Open source projects should run office hours

#217
post #205

Sure if you want to kill open source. I'm working in the office during office hours.

Those office hours could be on the weekend if you wish, and nobody says that you have to have a longer time window to book than one or two hours a week. That's more than some lecturers.

Re: Open source projects should run office hours

#219
post #215

I have deep aversion to "Open source projects should run office hours" title. Maybe "Office hours may be a good idea for open source projects"? This would not suggest obligation. In general, fact that someone created or maintains or supports open source projects should not be considered to create any obligations beyond lack of malice and abuse. I am not obligated to support any bugs, create any features and it is per…

It's a clickbait title. That being said the real idea is the freemium consulting concept. Basically open source Devs give free consulting for a short time and then upselling to full on consulting for extended periods at full price. In theory it could be a way to fund open source dev.

It's actually not so much about free consulting where I help them, it's more the other way round: they help me figure out how to improve the software by showing me what they've built or talking about what they want to achieve.

It's more of a market research exercise than freemium consulting.

That's not to say it couldn't also turn into a profitable exercise through up-selling consultancy, but that's not the primary goal.

Re: Open source projects should run office hours

#220

I have deep aversion to "Open source projects should run office hours" title. Maybe "Office hours may be a good idea for open source projects"? This would not suggest obligation. In general, fact that someone created or maintains or supports open source projects should not be considered to create any obligations beyond lack of malice and abuse. I am not obligated to support any bugs, create any features and it is per…

The point of this article was to address the fact that open source project rarely get good user feedback. Developers wouldn't necessarily be the person offering time to talk with users, it would be the project owner. I know open-source projects don't have traditional roles like a product owner or scrum master, but there's still somebody prioritizing a list of features that have been requested. Offering to meet with real users provides valuable insight into what they actually need. This can help with prioritizating features, and even help with making decisions about whether to approve a random PR you get for a feature you didn't put into the backlog based on whether it might make future real needs harder to achieve.
Post reply on HN