Re: Shorten subjects of PHPDOC commit emails

From: Date: Tue, 27 Feb 2007 20:02:18 +0000
Subject: Re: Shorten subjects of PHPDOC commit emails
References: 1 2 3 4 5 6 7  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969375677@lists.php.net to get a copy of this message
The most important info are the files and the module.
Even if it is important in 99% of cases (i.e. 99 files from 100)
the
module is obvious and those extra symbols make me constantly
scroll to
see what name is at the end of /en/reference/bla-bla-bla/path.xml
I prefer consistency with other modules over an edge case "useless" fix.
You will get your [PHP-DOC] tag anyways. Common - it is a very simple and intuitive fix. There is no "useful" information lost over an edge case (for what it means). If I am receiving spam like any other user on a planet Earth I am against that consistency. =)
I don't see a true need here and would rather not deviate from the other php mailing lists so prefer to keep the subject line as is. Get a wider monitor ;)
Ok, what about making a separate list for maintaining
phpdoc/ tools then? You said earlier that it was already decided to split the lists down... make it happen :)
Gimme da passwoodzzz! =) No, seriously - I just do not know what is the next thing to do - I've already mailed systems several times.
Then do it again. Short, to-the-point mail (and links to back up the decision). Heck, I read the posts you linked to before but I didn't understand the motivation nor the exact conclusion...
You mean this one? - http://beeblex.com/lists/index.php/php.doc.chm/1262?s= It is a copy of my post sent to systems@ and there was a follow-up thread, but I can't find public archive for systems@, so I can't point you to it. I can rewrite the mail to clearly outline the motivation to separate manual editors work from manual tools work. I just afraid the explanation will be too banal.
Please write the mail and send it here as a new thread. We'll all discuss (again?) then as a group plan how to move forward. If we want this list then I know we can make it happen but few, except you, even remember thinking about this topic. Also, writing down your thoughts will help us all know which list to use as sometimes there is overlap, like between docweb, phpdoc, and the newly proposed list for tools. So three doc lists, will it be (or is it already) too confusing? I don't know. In the future let's discuss these topics here and then post the final results to systems@ because although our discussions are exciting, they don't need our spam. Regards, Philip

« previous php.doc (#969375677) next »