I don't think we need to do something. If you look at projects with same
size of Rails or closer you will see we are very active.

We just released a major feature and, well, I think we deserve some kind of
rest. When we need to work you will see that issue page decreasing like
crazy.

Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca


On Thu, Jul 18, 2013 at 7:54 AM, "Marc Schütz" <[email protected]> wrote:

> Thanks for the responses so far. This certainly wasn't meant to criticize
> the people who work on Rails and put in a lot of their free time.
>
> It's just that, quite obviously, for whatever reasons, the Rails team
> isn't able to keep up with the large number of pull requests (and bug
> reports anyway). It seems Andrew Vit also talked about this about a month
> ago, which I hadn't seen before I posted.
>
> It was suggested in Andrew's thread and in this one to triage bugs and
> help reviewing. However, while this might be useful, I don't think lack of
> reviewing is the real problem.
>
> I took a closer look at the open PR's on page 4 (i.e. to avoid the really
> new ones). Of these, there are:
>
> New features:   5
> Refactoring:    7
> Bug fixes:     11
> Documentation:  2
> Total:         25
>
> With votes from the community:     2
> With comm. feedback/suggestions:   8
> Open questions for submitter/WIP:  6
> Feedback from core team:          12
>
> This means that for most PRs, there has already been some kind of
> review/feedback from either the community or the core team (i.e. those that
> I think are members). "Open questions/WIP" are those where the submitter
> still needs to do something. There are some others with open questions, but
> these are waiting for feedback from the core team. Many of the PR's end
> with someone requesting a specific team members opinion, after which
> nothing happens.
>
> So... I'd like to ask again, what can be done? Give more people commit
> access? Funding for some core team members to be able to dedicate more time
> to Rails development? Maybe a better way to prioritize PR's, as Andrew
> suggested? Make it easier to decide which features are desired? Other
> options?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to