Jani Taskinen wrote: > On Thu, 2007-12-13 at 10:00 +0100, Derick Rethans wrote: >> To to get back to the point of the noise on the lists - it's getting out >> of hand, and I am afraid that if we don't solve this any time soon, the >> lists will be useless for any sort of decent discussion and promoting >> even more secret cults. > > There's already public list, it's called "php-general". So just > unsubscribe all people from this list and subscribe all @php.net addies > only.
that's doesn't seem like a good idea imho. 1. most people reading the internals list already subscribed to general 2. general is in no way suitable for the kind of discussion currently occuring on internals - the difference between internals and general is akin to the difference between fine art and drawing with crayons. if the consensus amongst devs is that no-one other than devs have any right to offer input to internal implementation discussions then make internals readonly for every other than the devs. personally I think that just doing that is not good for the cause at all - there are plenty of people using php that do offer worthwhile feedback to implementation discussions, excluding them will just lower the quality and usefulness of the stuff your releasing. my suggestion would be to split internals into 2 lists internals - readonly except for devs internals-discussion - anyone may post of course this would only work if devs actually took the internals-discussion list seriously which given the current sentiments floating about seems unlikely, don't get me wrong I understand your sentiment! alternatively moderation could be applied to internals, whereby dev can post unmoderated and everyelse has to go through a filter - ofcourse you have to find a couple of people to do the moderation, my guess is that it would not be too hard to find a few intelligent, interested & knowledgable people from within the php community who would be willing to help the devs in this way. I would hazard to say that php is becoming a victim of it's own success in this regard - to really tackle the issue would probably require the implementation of a more structured proposal/implementation/release process ... I will grant that that is a mammoth task to undertake! > > Another solution is to simply stop discussing things and just commit. :) somehow I doubt that that strategy will help to improve php's reputation for stability and usefulness (percieved or otherwise) especially with regard to the 'enterprise market' which is increasing being aimed at. > > Same worked for bugs: my blood pressure got normal again since I've > ignored the reports. :D > > --Jani > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
