Re: Requiring SCM

Pierre-Alain Joye wrote:

On Tue, 29 Mar 2005 09:27:46 -0500 chuck@horde.org (Chuck Hagenbuch) wrote:

And I say that I don't think that's a good idea. I think there is a better argument for forcing everyone to use cvs.php.net than there is for this. For one thing, it creates enforcement/policy problems. Consider: - package is proposed. It's in accessible CVS somewhere other than cvs.php.net - package is accepted - one or two releases are made - CVS goes away (hosting dies, lapses, whatever) What do you do now? Sure, you can answer that, but I'd rather not get into the position of *having* to answer it. I don't see the need.

Got the point. In theory, our QA team should warn the maintainers to set back a CVS server or use the php.net cvs. It's not like this kind of issues will be that dramatic. But could be right after a release for example ;) How I will resolve it? If you they are not able to setup back a cvs, and say: "hello, you have an account with cvs.php.net/pear/Foo karma, use it from now.". As I said earlier, I would like to force the php.net cvs server, without that much choices, but this is my dream and your nightmares ;-) I concur that requiring that maintainers use cvs.php.net/pear is a bit

draconian. I'd rather give people a chance with liberty and tighten as necessary. The way I see it, the worst case is that we're back to where we are now: we still have the last release and any bug reports. Still, it would be nice to be in better shape. I suggest setting up a system for fetching nightly tarballs. We could offer CVS, Subversion, and possibly a couple others if people want them for some reason (arch comes to mind). This provides a backup in case the server goes down and a daily check. QA and the maintainer can be automatically notified after n failures to checkout a copy. I hate to dump more work on the server admins, but this seems like a reasonable enough compromise. I imagine package maintainers could use a web form to manage their SCM settings: - use cvs.php.net/pear or external - if external: * versioning system * server * path/module * user (anonymous?) * (preferably empty) password This information could also be used to guide people who want to check out the source themselves (i.e. "This package uses CVS. You can check it out with the following command ...") -Nikolas 'Atrus' Coukouma