New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Weekly "tree-age" party #2357

Closed
jordansissel opened this Issue Jan 14, 2015 · 15 comments

Comments

Projects
None yet
10 participants
@jordansissel
Contributor

jordansissel commented Jan 14, 2015

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.

@tbragin, @robynbergeron, myself, and @suyog were present in the internal discussion.
Summarizing this discussion, a rough sketch of this proposal follows:


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:

  • We'll want to be aware of timezone availability and probably will shift the meeting time around to allow different folks to participate.
  • In preparation, we'll internally prepare some kind of agenda for issues and PRs that need further study or review.
  • Rough idea is to spend 1-2 hours each week doing this specific triage event.

@jordansissel jordansissel changed the title from Proposal: Weekly triage party to Proposal: Weekly "tree-age" party Jan 14, 2015

@jordansissel

This comment has been minimized.

Show comment
Hide comment
@jordansissel

jordansissel Jan 14, 2015

Contributor

<3 to @untergeek for the "tree-age" punniness.

Contributor

jordansissel commented Jan 14, 2015

<3 to @untergeek for the "tree-age" punniness.

@untergeek

This comment has been minimized.

Show comment
Hide comment
@untergeek

untergeek Jan 14, 2015

Member

I love this idea! Where do I sign up?

Member

untergeek commented Jan 14, 2015

I love this idea! Where do I sign up?

@kurtado

This comment has been minimized.

Show comment
Hide comment
@kurtado
Member

kurtado commented Jan 14, 2015

triaging

@robynbergeron

This comment has been minimized.

Show comment
Hide comment
@robynbergeron

robynbergeron Jan 14, 2015

@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.)

robynbergeron commented Jan 14, 2015

@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.)

@robynbergeron

This comment has been minimized.

Show comment
Hide comment
@robynbergeron

robynbergeron Jan 14, 2015

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.

robynbergeron commented Jan 14, 2015

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.

@ph

This comment has been minimized.

Show comment
Hide comment
@ph

ph Jan 14, 2015

Member

Awesome! count me in!

Member

ph commented Jan 14, 2015

Awesome! count me in!

@jordansissel

This comment has been minimized.

Show comment
Hide comment
@jordansissel
Contributor

jordansissel commented Jan 14, 2015

81e31572-9bfa-11e4-94b3-8c9657c62edd

@tbragin

This comment has been minimized.

Show comment
Hide comment
@tbragin

tbragin Jan 15, 2015

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.

tbragin commented Jan 15, 2015

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.

@purbon

This comment has been minimized.

Show comment
Hide comment
@purbon

purbon Jan 16, 2015

Contributor

love the idea, count me in!

Contributor

purbon commented Jan 16, 2015

love the idea, count me in!

@colinsurprenant

This comment has been minimized.

Show comment
Hide comment
@colinsurprenant

colinsurprenant Jan 21, 2015

Contributor

Yes!! +1

Contributor

colinsurprenant commented Jan 21, 2015

Yes!! +1

@jsvd

This comment has been minimized.

Show comment
Hide comment
@jsvd

jsvd Jan 23, 2015

Member

A tree-age test run will happen in a couple of hours (14:00 CEST) in the #logstash freenode channel. I'll go through some very old issues and we'll decide a course of action for each.

Member

jsvd commented Jan 23, 2015

A tree-age test run will happen in a couple of hours (14:00 CEST) in the #logstash freenode channel. I'll go through some very old issues and we'll decide a course of action for each.

@suyograo

This comment has been minimized.

Show comment
Hide comment
@suyograo

suyograo Jan 24, 2015

Member

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:

  1. We closed 54 issues and updated/triaged about 55 issues. See list of issues
  2. Closed/migrated 24 pull requests

screen shot 2015-01-23 at 16 05 15

Until next week!

Member

suyograo commented Jan 24, 2015

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:

  1. We closed 54 issues and updated/triaged about 55 issues. See list of issues
  2. Closed/migrated 24 pull requests

screen shot 2015-01-23 at 16 05 15

Until next week!

@purbon

This comment has been minimized.

Show comment
Hide comment
@purbon

purbon Jan 26, 2015

Contributor

This is very nice, we should iterating this! I really enjoyed the experience!!

Contributor

purbon commented Jan 26, 2015

This is very nice, we should iterating this! I really enjoyed the experience!!

@suyograo

This comment has been minimized.

Show comment
Hide comment
@suyograo

suyograo Feb 7, 2015

Member

this week's theme was triaging issues from the old Logstash JIRA system.

At close today, we've resolved 157 issues in JIRA, migrated 30 issues to plugins repo and 10 issues to Logstash core

Member

suyograo commented Feb 7, 2015

this week's theme was triaging issues from the old Logstash JIRA system.

At close today, we've resolved 157 issues in JIRA, migrated 30 issues to plugins repo and 10 issues to Logstash core

@suyograo

This comment has been minimized.

Show comment
Hide comment
@suyograo

suyograo Aug 7, 2015

Member

Closing this, we'll open new themes for fix-it-friday

Member

suyograo commented Aug 7, 2015

Closing this, we'll open new themes for fix-it-friday

@suyograo suyograo closed this Aug 7, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment