Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposal: Weekly "tree-age" party #2357
Ahem.. a "tree-age" (pronounced "triage", hehe)
We've been discussing internally among Logstashers at Elasticsearch various ways to improve our transparency and involvement with the community. One topic that came up strongly was to do a public triage-and-fix session, possibly weekly, which would involve the community directly with us (elasticsearch logstash folks) to help move logstash forward and discuss improvements, bugs, etc.
Once weekly, hold a public event on #logstash IRC channel where we discuss bugs, solicit feedback, , review patches, etc. The goal is to allow a predictable time and space for discussing things.
The result of each triage session will be summarized and emailed to the logstash-users@ mailing list.
Some implementation concerns:
@untergeek I don't know if we'd need a place to sign up; I think it could just be something where, if you can, you show up :)
Alternately - perhaps there could be a way to post an agenda as an issue, and people could say whether or not they're coming. (This seems like a not-fabulous idea to me, but throwing it out there anyway! The plus side of this is that people who are unable to attend might be able to at least comment on the agenda or etc. if they need to.)
For the record, I also <3 this idea. :) I think one thing to think about (and @jordansissel & @suyograo, correct me if I'm off track here) - is that at least initially we may want to focus on one area per meeting. But over time - especially as some "back-log" (heh heh) gets better - I think it's definitely something that could have a regular, consistent agenda with time to address all the areas Jordan mentioned above.
Does the bot in the #logstash channel have the meetbot plugin? It's a great way to record all the details and also capture the high-level topics, decisions made, etc. from IRC into something organized and readable, and is also saved as a webpage.
While we're going through a large backlog (like now), I like the idea of picking an area for each triage session (e.g. a specific plugin or category of concerns where a lot of requests / issues need attention). I think it will allow us to focus our efforts, but will also result in measurable improvement in areas where most pain is felt.
Also, part of the plan we discussed is to triage not only in Github, but also in the deprecated, but searcheable public JIRA and start closing those issues or moving them over, if they are still valid. I had a couple of users ask me about public JIRA, since they found useful content there via Googling, without realizing that it's no longer maintained :(
I'd love to hear thoughts on what topics / areas might benefit from triage most immediately.
Tree-age update at the end of 23 Jan 2015:
Today's theme was to start with the oldest open issues and pull requests. Most of the core developers were hanging out in the #logstash IRC channel too
Results from today:
Until next week!