Ha, thanks for bringing out the whole list. GitHub was down, so I can't remember who else are on the list. And yeah, Rafael really sums it up pretty well.
Thanks guys, - Prem On Tuesday, September 11, 2012 at 12:11 PM, Carlos Antonio da Silva wrote: > Ok, Rafael has just listed everything a lot better than I did :) > > On Tue, Sep 11, 2012 at 1:07 PM, Carlos Antonio da Silva > <[email protected] (mailto:[email protected])> > wrote: > > We have done a lot of work on the issues this year, and we were able to > > bring the number down to almost a half - it was over 800 - and we didn't > > even know about what happened at RailsConf. The problem is that now it's > > getting harder to bring this number down. > > > > Going through old and stale tickets is an awesome way to help for sure, > > some folks like Rafael, Prem, Steve, Richard and I (among others) have been > > trying to do this, and we're getting some of them closed as possible. But > > as we close, more and more keep coming, so the number stays the same. It > > was over 500 these days, not we got it back to ~470. I have around 50 or > > more tickets bookmarked here to take a look, but real life always happens > > :). > > > > So please, if you can that'd be a great help. In any case, just pay > > attention to some issues that have people assigned to them, those are > > probably the ones that need work to be done and shouldn't be just closed. > > Trying to go through the issues list, and making sure bugs are still real > > bugs in master, are also another great way to help. > > > > When in doubt, just ping some of us to help. > > Thanks. > > > > > > -- > > At. > > Carlos Antonio > > > > > > On Tuesday, September 11, 2012 at 12:50 PM, Godfrey Chan wrote: > > > > > I thought this was obvious and it turns out I'm right :P Since you and > > > steve are probably focusing on newer tickets, I guess I can start going > > > through the stale tickets from the end and ping the reporters… if no one > > > responded in a while (a week or so?) then I'll ping one of you to close? > > > Would that work? > > > > > > (Perhaps we can be more proactive in closing stale PRs that aren't > > > receiving enough attention from the core team, and ask the author to > > > reopen if they are still interested in pursuing that? That way we can > > > escalate PRs that have been re-opened a few times and make sure they get > > > a final yes/no from the core.) > > > > > > Godfrey > > > > > > > > > On 2012-09-11, at 8:42 AM, Prem Sichanugrist wrote: > > > > We actually already have a team that's working on the issues (such as > > > > me and Steve K.) We might be a little slow sometimes, but please trust > > > > me that it's getting better than before now. :) > > > > > > > > I think currently everyone are so busy with Rails 4 release (we do want > > > > to send some patches in as well) as they're right around the corner, so > > > > the respond time might be a little slow. After the RC goes out, I'm > > > > planning to do a big going-through the issues queue. > > > > > > > > If you would like to help us for now, feel free to go through those > > > > issues, ping the appropriate person to respond to it, or ask if it can > > > > be close. Rails Core team always appreciate your contribution, and I'm > > > > pretty sure they won't hesitate to give you out the permission to > > > > manage tickets when it's time. > > > > > > > > Thank you so much for stepping up for this. > > > > > > > > - Prem > > > > > > > > On Tuesday, September 11, 2012 at 11:28 AM, Godfrey Chan wrote: > > > > > > > > > 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] > > > > > (mailto:[email protected]). > > > > > To unsubscribe from this group, send email to > > > > > [email protected] > > > > > (mailto:[email protected]). > > > > > For more options, visit this group at > > > > > http://groups.google.com/group/rubyonrails-core?hl=en. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > 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] > > > > (mailto:[email protected]). > > > > To unsubscribe from this group, send email to > > > > [email protected] > > > > (mailto:[email protected]). > > > > For more options, visit this group at > > > > http://groups.google.com/group/rubyonrails-core?hl=en. > > > > > > -- > > > 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] > > > (mailto:[email protected]). > > > To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:[email protected]). > > > For more options, visit this group at > > > http://groups.google.com/group/rubyonrails-core?hl=en. > > > > > > -- > At. > Carlos Antonio > -- > 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] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. -- 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.
