If / where to send trackback notifications (was: "Re: Services_TrackBack?")
| From: | Tobias Schlitt | Date: | Tue, 25 Jan 2005 09:51:31 +0000 |
| Subject: | If / where to send trackback notifications (was: "Re: Services_TrackBack?") | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.qa php.pear.webmaster |
| Request: | Send a blank email to pear-webmaster+get-3803@lists.php.net to get a copy of this message | ||
Hi Pierre-Alain Joye!
On 01/25/2005 04:21 AM you wrote:
By the way, can you not post new entries on pear-webmasters but only to the related maintainers?
I don't think that this is a good idea. Some maintainers might not feel responsible for dealing with the trackback stuff. Therefore I'd prefer to keep a copy of notification mails to pear webmaster.
If some maintainers do not feel responsible about their trackbacks, disable it. Just put a link down each of them to allow developers to delete their subscribtion, less trafic, less "noises" on pearweb.
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.OK, if you don't see that approving/deleting trackbacks belongs to a webmasters action, I propose to send the trackback mails to pear-qa. The reason for that is, that the goal of my trackback implementation is to raise the ammount of documentation for packages, which raises the quality of our packages. Sorry, Pierre, but I do not see, that approving trackbacks is just a matter of the maintainer. What if he's on holiday? What if he simply ignores the trackback mails? What if a package is orphan, what was not recognized until now? We will lose a pretty low hanging fruit of docs for our packages. Having those notifications on a publically available mailinglist ensures, that trackbacks are well maintained and approved/deleted ASAP after their arrival. Regards, Toby -- Tobias Schlitt GPG Key: 0xA6529579 a passion for php http://www.schlitt.info Like to say "thank you"? - http://pear.php.net/wishlist.php/toby