Re: Better Package Descriptions?

> On principle I think it is a good idea, but rather than commit directly, > open a bug report or send the maintainer a patch. This seems to be the general concensus, and I'm OK with that. This is what I'll do in the coming months. Thanks for the feedback, all. -- Sean Coates Editor-in-Chief php|architect >> 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? >> >> >> >