dukeofgaming wrote:
The question is, now, will github be part of the integration workflow?, or
is that yet to be discussed?. I imagine the project wants to retain
governability and I applaud that instead of using a 3rd party service as the
"master" repository, however, given the social impact these services have
—specially github— I think github must at least be part of the workflow,
because, you know, the repository is distributed now, no place
is necessarily special.
github is something completely different!
And I _hope_ that the PEAR repo is pulled back in house as well.
As I have already said - the decision should have had nothing to do with "mine
is bigger than yours". Proper integration with the rest of the support
infrastructure is not possible, if a key component is subbed out? If the repo's
move to github, are you then going to start using github bug tracking, wiki,
blogs ... where does one stop?
From my point of view, the choice of git was inevitable, and something many of
us will just have to live with, but since I'm already using git ( and github )
locally VIA hg it's not really a problem, and an hg mirror _will_ exist even if
not officially. The reverse way around is not currently even possible given that
git *IS* impractical in a number of current development set-ups and does not
have the same cross DVCS facilities. But there is nothing to stop us just
continuing to use hg if that is our preference :)
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
