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.
Open source projects should run office hours
171–180 of 279 posts
Re: Open source projects should run office hours
#172I 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…
Re: Open source projects should run office hours
#173Since 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.
Re: Open source projects should run office hours
#174I 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…
Depending on license, aren't you obligated to provide a repo if you're using the code (ie GPL)? Or do I misunderstand it?
Note that the GPL specifically does not require publishing the source code, or having to distribute it along with the binaries. It allows the alternative of only providing the source code upon request by any third party, to that same third party.
Re: Open source projects should run office hours
#175I 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…
Re: Open source projects should run office hours
#176I think this format is much better and more organized, so I highly recommend that open-source maintainers who would like to learn more about how their projects are used to give it a try.
Re: Open source projects should run office hours
#177Earlier quoted context omitted.
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.
Rule of thumb when speaking or writing: replace "should" with "could". Simple way to avoid implying obligation.
Re: Open source projects should run office hours
#178Re: Open source projects should run office hours
#179Earlier 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.
Re: Open source projects should run office hours
#180Earlier quoted context omitted.
The title is kinda unclear for someone non-English/US, for me office hours only means the actual hours when things are worked on (rather than any kind of availability time). So skimming the title it quickly I read it as "Open source projects should run on office hours" since my mind filled that in, kinda implied that someone in another part of the world should adjust their life hours to contribute to OSS. (Yes after…
The difference in usage is not localized English: it's cultural student/academic vs. employed. To a student with no professional experience, "office hours" are posted times when a professor is available to further mentor and guide a student. "office hours" are designated times outside of the scheduled class times and professors are generally required to provide them so others can benefit. To a professional and others…