Re: Shifting Validate_* to github?

... and we're done. I've: 1. Created a team of all the contributors I could find github accounts for. We're still missing a few. This team is styled as a PEAR2 collective - access to all validate_ packages. 2. Migrated Validate 3. For all QA maintained/orphan validation packages, added a seperate build on http://test.pear.php.net:8080/ ; including splitting packages to their own repo. If anyone else wants to split a validate sub package out; do: 1. Make new repo by hand 2. Setup issues/wiki/etc off, post commit hooks to point to http://test.pear.php.net:8080/github-webhook 3. git clone ....Validate_Foo.git 4. git clone .....Validate.git 5. cd Validate_Foo && git pull ....Validate.git master Finish by $ git rm (all of the dead files for Validate and Validate_Foo in each respective repo) On Sat, Nov 26, 2011 at 6:12 PM, Daniel O'Connor <daniel.oconnor@gmail.com>wrote: > >> I think Validate_* are the most difficult packages to move, so go for it >> :) >> >> > Alright, no one seems to have objections; so I'll tackle it today. > > It's tempting to shift it; then split into multiple sub packages - it's > easy enough to create a "Validate" team which spans over all packages. >