Re: keeping traffic on this list manageable

On Fri, Oct 31, 2008 at 20:59, Rasmus Lerdorf <rasmus@lerdorf.com> wrote: > Hannes Magnusson wrote: >> >> Behavioural change is desperately needed, and I think developers >> should lead by example. >> One way to to that is to add a new internal-core@ mailinglist which is >> read-only to the world, and writeable by people with appropriate >> karma. >> >> That list would be dedicated for _development_ discussion (including >> implementation, patches, "edge-case voting" and such things) and would >> include posts like are going on between greg, stas and dmitry, and >> posts which are going on between release managers and individual >> developers. This way we keep _everything_ in the open and maintain a >> "high quality" on-topic discussions. >> >> "external" patches and "general" discussions would still be on the >> internals@ list, as it would be the main discussion list. However, >> those who simply do not have the time to read over the entire thing >> have a specific low-traffic list which they can easily follow. > > This is the same as just making internals@ read-only. Once we have an > internals-core, many core people will just unsubscribe from the internals > list. I know I probably would. And once the core developers no longer read > it, it becomes php-general2 and it ends up excluding people from the > development process. I have more faith in our devs then that. And I doubt you would unsubscribe, you care to much (and one of the few devs I've seen to reply to posts on php-general@ and then pear-dev@ the next day..). Most of us do. You would probably filter those posts into a different reading priority, but you would still browse through it. I expect bunch of silent listeners to unsubscribe from internals@ and subscribe to internals-core@ and I can even see some devs only subscribed to internals-core@ but I have no doubt that over 51% would stay stay subscribed to internals@ and would forward interesting discussions to internals-core@. -Hannes