Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Open source projects should run office hours

simonwillison.net

Post reply on HN
Print view View original

271–279 of 279 posts

Re: Open source projects should run office hours

#271

Post by fuzzfactor »

1f60c wrote: post #141
mcherm wrote: post #140

Earlier quoted context omitted.

I saw the title and thought to myself, "No one has the right to tell open source volunteers how to spend their time! The only way an article with that title is acceptable is if it's talking about benefits to the DEVELOPER, not the user." Then I read the article and it IS using "should" in the sense of "I found this beneficial, you may too" rather than "this is an obligation".

For me (a non-native English speaker) the title was confusing for a related, but entirely different reason: it's referring to the kind of "office hours" a professor might have, not saying that you "should" work on your open source project during office hours (i.e. from Monday through Friday from 9 AM till 5 PM).

>saying that you "should" work on your open source project during office hours (i.e. from Monday through Friday from 9 AM till 5 PM).

That was my first impression too.

Had to think that M-F 9-5 would not be enough for some projects, in total hours alone not just to accommodate different time zones.

Doesn't seem so bad to me, my "office" is staffed 24/7 and I always look forward to solving a user's million-dollar problem with a single phone call at any hour.

Even if it's not one of my regular clients. That's how some of the best ones got that way.

Re: Open source projects should run office hours

#272

Post by nxpnsv »

matkoniecz wrote: post #109
nxpnsv wrote: post #99

Earlier quoted context omitted.

I don't think this is about obligations. I feel the developer had a hugely positive experience in inviting interested strangers for 20 minute chats and wanted to spread the positivity. Seems like a nice person, with a nice project, and clearly some extra time available.

I referred specifically to the title in my comment. It is part of things personally irritating to me, and something what is biggest threat to small open source projects that I like. People are mistaken in thinking that having an open source project implies any obligation beyond lack of malice. And people tired by dealing with that are one of top reason why open source projects disappear or are never created.

I understand your point, and I also think it's weird how people feel entitled to the free time of others. Still - here the choice of title has gotten in the way of what the author wanted to convey, and I feel the story deserves a read beyond the title.

Re: Open source projects should run office hours

#273

Post by oauea »

selfhoster11 wrote: post #217
oauea wrote: 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.

No one gets to demand anything from me during the weekend, no thanks.

Re: Open source projects should run office hours

#275

Post by account42 »

m463 wrote: post #249
shadowfox wrote: post #228

Earlier quoted context omitted.

It is overruled by the "law of the topmost comment" - the top comment is very likely a negative take on some subpart of the topic at hand, sometimes unrelated to the actual article, worded in the strongest way possible.

your take on his take is meta-humorous. If your argument holds, I would expect my agreeable comment of mine to be downvoted or replaced by a comment possibly critical of your viewpoint.

Well...

Although in general, you can't expect replies to other comments and comments on posts to follow the same patterns.

Re: Open source projects should run office hours

#276

Post by account42 »

carols10cents wrote: post #236
throwawinsider wrote: post #193

Earlier quoted context omitted.

It seems pretty obvious to me that should means should. Pro tip: if you don't mean should, don't write should.

Pro tip: the best RFC is 2119 https://tools.ietf.org/html/rfc2119

Don't you mean "Pro tip: you SHOULD read RFC 2119"

Re: Open source projects should run office hours

#277

Post by account42 »

capableweb wrote: post #163
mysterydip wrote: post #156

Earlier quoted context omitted.

Depending on license, aren't you obligated to provide a repo if you're using the code (ie GPL)? Or do I misunderstand it?

There are a few MUSTs if using GPL, yes (btw, GPL is considered a "free" license, not a "open source" one), but providing a repository is not one of them. Although you do need to provide the source (in any means you want, as long as it's accessible, making a repository is one of the ways, bundling a zip file would be another). Short version of your obligations if using GPL as a license: https://tldrlegal.com/license/…

> btw, GPL is considered a "free" license

Yes.

> not a "open source" one

It is also an open source license.

Re: Open source projects should run office hours

#278

Post by kyawzazaw »

dylan604 wrote: post #105
kyawzazaw wrote: post #82

Earlier quoted context omitted.

you could just write a post on teamblind.com if you are that level or just make a tweet

you're putting a lot of weight on someone having the right followers or someone casually reading some rando.com website. comparing that roll of the dice big bang level of random vs having direct contact with someone that uses code you created and can vouch for you seems skewed in the wrong direction to me.

yeah but that's how many have gotten jobs. It's just a matter of ROI.

Wrong direction for whom?

Re: Open source projects should run office hours

#279

Post by whizzter »

simonw wrote: post #201
ddoeth wrote: post #200

Earlier quoted context omitted.

I think the authors explanation with the german word "Sprechstunde" is really great. There is a clear distinction between "Arbeitszeit" which is the working time and the "Sprechstunde" which is the time someone is available to talk to.

I added that paragraph about fifteen minutes ago based on feedback in the comments here.

Props on recognizing issues in your work. The article has solid advice so getting lost in the message would be a shame.
Post reply on HN