8 ms·
How to be an open source gardener
- dtwwtd 13y agoI enjoyed reading this. I can relate to the point about reading open issues of a project to know exactly what state the project is in and where it is going. While I don't actively participate in many open source projects, I have found myself reading the mailing lists and watching the issue trackers for a few projects over the past few months and as a result I feel that I have a very good idea of what is going on with them.
- daleharvey 13y ago1000 times yes For PouchDB (gardeners welcome - https://github.com/pouchdb/pouchdb https://github.com/pouchdb/pouchdb), 90% of my time is between triaging issues and setting up infrastructure for contributions (mostly working on tests / CI). Sometimes every few days, at least every week I sit and go through all the issues, try and figure out whats needed to close out the old issues, a good percentage of the bugs are ones that need someone to investigate and produce a clear set of steps to reproduce. Actually after reading I am gonna start tagging these ones specifically for new contributors. Even as someone who considers myself very reactive to bug reports etc, its very easy to let it slip (https://twitter.com/daleharvey/status/451378807006838784 https://twitter.com/daleharvey/status/451378807006838784)
- jedahan 13y agoOpenFrameworks tags the low hanging fruit issues as 'bitesize'. :)
- donutdan4114 13y agoThis is a really good post, if only because it reiterates that code isn't the only way to help an open source project.
- onli 13y agoNot only that. It also shows that a project needs to invite help. A helper who wants to do something like like this does not necessarily need to code a lot (even though it is of course necessary to have basic programming knowledge to triage bugs). But he needs extensive rights in the issue tracker, so that he can tag and close and comment with authority, and the other developers need to respect that work. Something like that won't appear out of thin air, something like that needs a process, the possibility to build up trust, and an invitation.
- steveklabnik 13y agoThis is something important that I forgot: GitHub's permissions are such that you need to have commit to truly do this job effectively. For Rails, this means that the issue team has commit on GitHub, but isn't actually allowed to commit. It hasn't been a significant problem.
- shykes 13y ago+1 in doubt, err on the side of trust.
- allendoerfer 13y agoMaybe i am naive, but i think this screams for a system which enforces reproducing of bugs. 1. Bug is filed 2. System checks if bug is reproducible 3. As long as the bug is not reproducible it is hidden in the issue tracker and flagged as "needs reproducibility" and emails are sent to the creator. After a given time the bug is closed automatically. 4. When the testcase to reproduce the bug is provided, the build system checks against the current supported versions. If it passes, the bug is fixed as "needs reproducibility" again, if it fails, the bug is finally pushed to the main issue tracker. I can see how brutal this approach is, but this way, the number of bugs is kept to a minimum. Bug filers, who actually take the time will therefore have a high probability of immediate fixing. Motivated people can always play gardener additionally, but without the email spam, they can simply help in one step of the process.
- pavel_lishin 13y agoYou'd need a custom DSL to tell the system how to reproduce the bug; at this point, I'm already bored, and I don't even have a bug to submit.
- steveklabnik 13y agoIn theory it could be a pull request with a failing test.
- pavel_lishin 13y agoThat's still quite a bit of work - there are some projects I'd do that for, but if (for instance) an IRC bot was having an issue, I doubt I'd bother if submitting a bug required writing a new test, and submitting a PR.
- steveklabnik 13y agoOh yeah, I'm still not in favor of it as an idea, just tossing thoughts around.
- 13y ago
- orasis 13y agoThis article isn't about growing plants :-(
- kyberias 13y agoWhy not write an article about that yourself? :)
- britta 13y agoI'd suggest checking out http://growstuff.org/ http://growstuff.org/ to get your fill of more literal open source gardening! It's a neat project: "Growstuff is a community of food gardeners. We're building an open source platform to help you learn about growing food, track what you plant and harvest, and swap seeds and produce with other gardeners near you."
- bjohnso5 13y agoI also read it thinking someone had open-sourced some gardening tips or planting layouts. Whoops.
- awor 13y agoMe too! Here's a bunch of Arduino gardening (and other) links: http://www.rootsimple.com/2013/03/arduino-homesteading-projects/ http://www.rootsimple.com/2013/03/arduino-homesteading-proje...
- siscia 13y agoWondering why big project, backed by a real company that makes money don't pay someone to keep gardening? it could help some student pay the rent and definitely will help the project...
- hkmurakami 13y agoIf you don't "want" to take up this unglamorous task, and keep at it day after day at a high quality, the work will inevitably gradually slide to lower and lower quality.
- siscia 13y agoI would prefer to manage a issues page of some open source project rather than flip burgers... Still, if the gardener is not doing a good job you can always change him/her...
- izietto 13y agoThank you Steve for what you do for Rails; I admire the way you deal with it
- steveklabnik 13y agoAs I mentioned in the post, I don't do this for Rails anymore, but past me says thanks. :)
- izietto 13y agoDo you mean that you don't develop for Rails anymore, or just that you don't do the gardener?
- steveklabnik 13y agoI have been taking a break from most of my general open source work. I do a little bit here and there, but not as much as I used to.
- Ygg2 13y agoAren't you working on Rust?
- steveklabnik 13y agoI don't contribute as much _code_ as you'd think: https://github.com/mozilla/rust/commits/master?author=steveklabnik https://github.com/mozilla/rust/commits/master?author=stevek...
- deleted 13y ago[deleted]
- shime 13y agoI expected some command line tool for github instead of manual navigation through 800 issues. This way he could have saved batches of issues, neatly organized in a directory structure suiting his needs.
- steveklabnik 13y agoI almost used a fork of https://github.com/nashby/jose-vs-oss https://github.com/nashby/jose-vs-oss for a while...
- kylemaxwell 13y agoCheck out www.codetriage.com (albeit not CLI). In any case it sounds like you have a great angle for a fresh approach to the issue, maybe using the GitHub API.
- steveklabnik 13y agoI should have plugged it; Code Triage was actually directly inspired by the events in this post.
- shime 13y agocode triage is great, but I was thinking about something like ghi - https://github.com/stephencelis/ghi https://github.com/stephencelis/ghi
- bjourne 13y agoSorry to be contrarian, but bug reports aren't weeds. The count of open bugs on a project is just a number and it doesn't matter if it is large or small. Closing bugs that never should have been opened in the first place is of course great, but many times the bug report is open because it is a tricky issue to solve. You cant just mark old bugs as "stale" and close them and hope that the bug is fixed in a newer version of the software.
- steveklabnik 13y agoTo be clear, I only advocate that bugs with no reproduction instructions and an unresponsive submitter be closed as stale. The oldest open bug in Rails is three years old, and even says "This has been around a while" in the description. https://github.com/rails/rails/issues/1769 https://github.com/rails/rails/issues/1769
- mors_ontologica 13y agoNot one word about gardening. Fail train.
- shykes 13y agoWell said Steve, we have 500+ issues on Docker and are going through the same process. The most valuable contributors are those who show up day after day and are not afraid of repetitive and unglamorous tasks. Those are worth their weight in gold.
- patio11 13y agoDo they get salaries (or other consideration) commensurate with being the most valuable contributors who are worth their weight in gold?
- justinsteele 13y agoMaybe they could get free conference passes, or an invitation to a company gathering if they are in the area.
- dsfadadsffd 13y agoSteve, first off I respect you a lot for the work you have done. But, the elephant in the room is that when you changed jobs, you totally fell off the map with Rails: https://github.com/rails/rails/commits/master?author=steveklabnik https://github.com/rails/rails/commits/master?author=stevekl... I would have done the same thing, getting into to Rust, etc. after the job transition, as you have other things to focus on. However, you mentioned Rails, and I think this is an opportunity to talk about "leaving the garden". I have a few projects I had enjoyed working on, but when I left the old job, I was stuck with those projects and no one wanted to take them on- I tried to find help, but it was temporary- no one has taken over. Do you or others have suggestions for successfully abandoning a project, because I can't seem to, and those projects languish with the lack of effort I put into them because it is so infrequent, but I do just enough apparently to keep others from thinking I've abandoned them.
- pelasaco 13y agooh the hype hypermedia guy. does he gave up of marketing and now is working as gardener?
- nraynaud 13y agoI can't imagine being on the receiving side of those canned messages. In particular, beginners seeking help being told to go away. I still don't know how to do it in open source tho. In private companies that's what support technicians are for, they triage and they do the repro.
- steveklabnik 13y agoIf you submitted a bug report on Stack Overflow, they'd tell you to file it on the bug tracker instead. GitHub issues are a terrible way to teach someone how to use a project.
- nraynaud 13y agoThat's the expert point of view. But when you're learning a technology, you don't know what's the expected behavior, where's the problem (your code or the lib) and if you understood the spirit correctly, so you don't know where the problem is, you just need an expert pair of eyes to make sense of things. So you get kicked out of SO for lack of point-worthy question, and of github for lack of repro. Moreover some projects do their support on github (not saying it's good or bad, just confusing). I've had that recently, I don't even know where to ask what's the expected behavior (google chrome APIs, impossible to reach a human being).
- steveklabnik 13y ago> I don't even know where to ask what's the expected behavior Yup, this part can be super bad. This is why I'm happy CONTRIBUTING.md exists on GitHub, and why they show it whenever a new issue is opened.
- krebby 13y agofor certain projects, I like ost.io as a way of "ask me anything" to project authors. I wish something like it were more widely used however.
- teddyh 13y ago> Was this issue for an older version of Rails than is currently supported? If so, copy/paste an answer I wrote that asks if anyone knows if this affects a supported version of Rails. No. Please do not do this blindly. It is very discouraging for the bug reporter to see their bug being ignored for a few releases, followed by this response. Example: http://www.jwz.org/blog/2003/02/the-cadt-model/ http://www.jwz.org/blog/2003/02/the-cadt-model/
- steveklabnik 13y agoI know it's discouraging, but sometimes, bugs get fixed as an accident of another change, or the feature was removed, or a variety of other things. Leaving it sit open with no movement at all is even _more_ discouraging.
- teddyh 13y agoThe bug reporter reported a legitimate bug. It lies on you to act on this information. If you ignore the bug and make other random changes to the code, it still is your responsibility to fix the bug - the fact that you made it harder to find the bug by altering the code is entirely your own doing. It does not fall upon the bug reporter to test your code for bugs for every change you make. To demand this, and to close the bug when they do not comply, is entirely the wrong thing to do.
- Fasebook 13y agoHow do be a little bitch.