Re: Services_W3C_CSSValidator - want to do a new release?

Second: Rather than make the job and ask after if author is agree with you, > you should reverse actions, and ask before to begin. This is a bit more > polite in my point of view (probably a too old school: I learnt respect and > values when I was young). > Well, my apologies, but I saw it was failing a unit test and marked as unmaintained, then got around to discovering there was documentation on your site which would be outdated (ie, something I can't fix myself); so it wasn't intended to be rude. > > Finally: you or someone else, even PEAR Group can do whatever you want on > all my packages, where I'm declared as inactive. That means for all: > > * HTML_CSS (lead, inactive) * HTML_Progress (lead, inactive) > * HTML_Progress2 (lead, inactive) > * HTML_QuickForm_advmultiselect (lead, inactive) * PEAR_Info (lead, > inactive) * PEAR_PackageFileManager (lead, inactive) * > PEAR_PackageFileManager2 (lead, inactive) > * PEAR_PackageFileManager_Frontend (lead, inactive) * > PEAR_PackageFileManager_Frontend_Web (lead, inactive) > * PEAR_PackageFileManager_Plugins (lead, inactive) > * PEAR_PackageUpdate (lead, inactive) * PEAR_PackageUpdate_Web (lead, > inactive) > * PHP_CompatInfo (lead, inactive) * Services_W3C_CSSValidator (lead, > inactive) Regards, > Laurent Laville >