Re: Hosting PEAR's git repositories on git.php.net

Hello all, > I'd like to see that for PEAR, too: > Using git.php.net as main repository server for PEAR packages, PEAR2 > packages, Pyrus and infrastructure code. > Github would only be a mirror of the git.php.net code. So we're split here. This here is the collection of plusses: git.php.net - full control (we keep all our data) - easy hooks for proper commit diff mails - central user/karma management github - faster than git.php.net - pull requests, 1-click merging - interaction + discussion - link to lines+files in diffs Another very basic question is if and why we need central repositories. Reasons I see: - We always had them (CVS, SVN) - All code is in one place, which makes tools like commit mails and bug tracker integration (not existing unfortunately) possible - Unmaintained packages can be QAed properly without moving the primary repository - Central karma/commit control - Users/other devs know exactly where to find the primary code repository Central karma control is only needed if the packages "belong" to the collective and not only single persons. PEAR packages have maintainers that care about them, but other devs only jump in for QA when the package gets unmaintained - this sounds more like a "my package" schema that does not need central karma. So, what is PEAR? A collective that cares for each other's packages, or a salad bowl of packages maintained by different people, only sharing the pear.php.net website? -- Regards/Mit freundlichen Grüßen Christian Weiske -=≡ Geeking around in the name of science since 1982 ≡=-

Attachment: [application/pgp-signature] signature.asc