I'm left wondering how many arguments will have over when a contrib module becomes important enough to merit discussion on the core contribution list, and whether my opinions are welcome as a contrib developer in api discussions and whether contrib developers will get the important messages about api changes and release timelines, etc. You see for me it's not about whether it's core or whether its contrib, but rather whether its meaty design strategy discussions or whether its "help me debug my code". My small modules won't matter to most, but when you start talking about views, cck, wysiwyg strategies.... well then we're all in it together aren't we?
On Mar 17, 2011, at 9:44 PM, Cameron Eagans wrote: > Perhaps we could go with the idea that this is a development support list and > simply create a new list called, for instance, core-contribution? That way, > there's absolutely no way that somebody could misinterpret the name of the > list to mean something that it's not intended to mean. > > That is, I think part of the problem that this list is having is that it's > called "development". It's not drupal-core-development or core-development or > no-noobs-allowed-development. Because of that, people can (and apparently > frequently have) misinterpreted the purpose of the list. > > We split off the core contribution part of #drupal to #drupal-contribute. I > propose that we do the same here. > > Thanks, > Cameron > > > > On Thu, Mar 17, 2011 at 21:45, <j...@ayendesigns.com> wrote: > This is probably a bad idea for more than one reason, but would there be a > way to have the list moderated for first-pass messages... i.e. those that are > not in reply? If by some chance it's not a horrid idea, and if there's a > process for it, I'd volunteer time to weed out and send a canned reply to > support questions...even my own :) > > > On 03/17/2011 11:40 PM, Ryan LeTulle wrote: > >> I wish there was some way to save the mailing list format. It is awesome >> for listening in on conversations and has always been a great way of ambient >> learning for me. >> >> Ryan LeTulle >> >
