As Richard pointed out in the other thread, we have a lot of open issues, and 
it'd be nice if we could do something about that. Evan tried to get people to 
review GH issues at Railsconf, and I believe there were some success there. Any 
interest in formalizing this effort and make it sustainable?

There are a few things about these issues that is pretty mechanical and almost 
anyone could do it (I'll be the first to volunteer):

1. As new issues are coming in -
        - Tag them appropriately (activerecord, activesupport, etc) - I think 
someone is already doing this and they might or might not need more help doing 
this
        - Ask for logs and other clarifications from reporter if necessary
        - Do preliminary (re)searches in the source, find out who is most 
likely to be the "owner" of the affected code and /cc (or perhaps even assign 
the issue with the tag "needs triage" or something) them for feedback
        - Close inappropriate issues (inflector patches, feature requests, 
questions etc) and direct the reporter to the right channels (stack overflow, 
rails guides, mailing lists, etc)

2. For older tickets -
        - Review if they are still relevant 
        - Ping the reporters or the code owner for updates, and close the 
issues as appropriate

While some of these (mostly the communications part) can be done by just 
anyone, I believe certain parts of the flow (tagging and closing tickets) 
requires repo-collab access, so some formalized recruiting and management 
effort would be necessary to make this effective. If granting full collaborator 
access is a problem, perhaps it is something that we could try working out with 
Github?

Anyways, I'm happy to help here, and I'm sure there would be a few others on 
the list who wouldn't mind committing a few hours per week doing this. So let 
me know how I could best spend my time helping out here.

Godfrey

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en.

Reply via email to