Mark A. Hershberger wrote:
Trevor Parscal tparscal@wikimedia.org writes:
My understanding is that PEAR has a specific coding style and set of standards, which is different than that of MediaWiki.
Coding style is flexible, especially if we're the ones doing the distribution.
By this, I mean that “putting it in PEAR” could just mean setting up a MediaWiki PEAR channel. PHPUnit, for example, moved http://pear.php.net/package/PHPUnit to its own PEAR channel http://pear.php.net/package/PHPUnit. Other packages related to PHPUnit are also maintained there.
I think the second should be http://pear.phpunit.de/
And as Rob pointed out, putting these “sharable artifacts” in a PEAR channel doesn't mean that we can't continue to maintain them in SVN.
Setting up pear.mediawiki.org seems like a good solution to me.
Mark.
That's an interesting idea. But I'm not sure if it would achieve the "make it discoverable" goal.