Re: [pear-webmaster] Services_TrackBack?

From: Date: Tue, 25 Jan 2005 09:21:58 +0000
Subject: Re: [pear-webmaster] Services_TrackBack?
References: 1 2 3 4 5 6 7 8  Groups: php.pear.webmaster 
Request: Send a blank email to pear-webmaster+get-3802@lists.php.net to get a copy of this message
On Tue, 25 Jan 2005 01:21:23 -0500 toby@php.net (Tobias Schlitt) wrote: > Hi Pierre-Alain Joye! > On 01/24/2005 06:14 PM you wrote: > > >>Sorry for my roceeding in this case, but the idea to release the > >>pure trackback part as a package was born during development of > >>trackbacks for PEARWeb. Therefore, I outsourced the code from > >>PEARWeb into that package. If the package gets rejected, I'll > >>re-import the code to PEARWeb immediatelly. > > > Do you think that a package that is not good for pear is good > > for pearweb, the heart of pear infrastructure? I do not. > > I don't think that this is compareable. Ok, if the package would > be rejected because of bugs/crapy code/... I agree with that, but > there maybe another bunch of reasons, why a package may be > rejected, which have nothing to do with using the code in PEARWeb. There is obviously many reasons to reject a package, some are not related to the beauty of the implementation. But that does change the result, rejected. > Which would also mean leass peaces of documentation. I don't like > the idea of having maintainers deactivate trackbacks. I prefer > much more, to have a webmaster approve a trackback, if the > maintainer does not feel responsible for. So, if you insist on not > sending those mails to pear-webmaster, I see only 2 solutions: > > a) send those mails to pear-doc (since trackbacks are a kind of > documentation) > b) create a new list for them (which would obviously be breaking a > butterfly on a wheel). I see the 3rd, the one I proposed. If maintainers do not care about trackbacks, we cannot force them. Maitainers should put a minimum effort into their pear projects, clicking some links a couple of mins per week is on these efforts. --Pierre

« previous php.pear.webmaster (#3802) next »