Re: Better Package Descriptions?

Why not just email each package maintainer with a new proposed description. - if you have rights, and they agree go ahead and commit it.. Just saying 'yeap that sounds ok', is a little cleaner than messing around with revert's or a maintainer missing the commit message and wondering why they are getting conflicts. Regards Alan On Sat, 2005-08-27 at 22:53 -0400, Sean Coates wrote: > Hello fellow PEARs. > > <reference type="pop_culture:Simpsons">You might remember me from such > packages as PEAR::Mail_Mime</reference>, but today, I'm wearing my > Editor hat. > > Every month, we, at php|architect, run a "What's New" column, with a > part of that dedicated to new releases in PEAR. We generally borrow from > the package descriptions, to.. describe packages > > My job as editor (well, one of my jobs) is to make sure the text reads > well, and is proper English. This is not the case for many package.xml > files, unfortunately. > > So, now, I ask: would you, PEAR developers, be open to me editing the > descriptions in your package.xml files (when in CVS)? I can't promise > that I'll hit everything, but as this will save /me/ time each month, > I'll try to edit them as I come across mistakes. I wouldn't change the > meaning of what's there; I'd just fix spelling and grammar mistakes, and > make text flow in a more readable manner. > > Comments? > > -- > Sean Coates > Editor-in-Chief > php|architect > -- Alan Knowles <alan@akbkhome.com>