Which makes me think about it: What could we do to better improve rails lists organization in a way that would benefit most out of it? While I agree that a Rails engine/plugin mailing list is useful, perhaps forking Rails-talk into specific categories, even if keeping a general rails-talk mailing list would benefit our general usage and understanding of where should we ask something specific. This mimics some IRC channels splitting strategies when the number of users talking generally about several stuff, like our rails-talk list, can lead to difficulty into separating noise from sound. rails-talk can still exits for most newcomers, but we would have the ability to redirect their questions to people more aware of their path to solve the problem.
i can clearly separate Engines, Railties and Assets for new mailing lists. What do you think? On Fri, Jul 20, 2012 at 10:29 PM, Andrew Kaspick <[email protected]> wrote: > Here's a past one... > > http://www.mail-archive.com/[email protected]/ > > dead! > > > On Fri, Jul 20, 2012 at 8:28 PM, Ryan Bigg <[email protected]>wrote: > >> rails-talk is a ghetto. >> >> A new engines list would be best. >> >> On Saturday, 21 July 2012 at 11:27 AM, Andrew Kaspick wrote: >> >> Engine lists have been created in the past, but they're not very active >> or are dead. >> >> -1 to a new engine list and +1 to just asking the questions in rails-talk >> first >> >> On Fri, Jul 20, 2012 at 7:41 PM, TuteC <[email protected]> wrote: >> >> +1 >> >> Agree that a Rails engine is in the frontier between custom app code >> and Rails architecture, yet a client (and not core) of Rails. >> >> >> On Fri, Jul 20, 2012 at 1:20 PM, Rodrigo Rosenfeld Rosas >> <[email protected]> wrote: >> > It is not always clear whether we should use Rails-talk or Rails-core >> list. >> > >> > In the same way we have a list for Rails documentation and we had one >> for >> > i18n, would you consider a new list oriented to Engine/Plugins >> developers? >> > >> > This would be a list we could subscribe for engine-related questions >> that >> > would't have a very big traffic like the Rails-talk one and I think >> such a >> > list could be pretty useful for gem authors. >> > >> > Would that be wanted? >> >> -- >> 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. >> >> >> -- >> 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. >> >> >> -- >> 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. >> > > -- > 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. > -- 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.
