On 24 May 2012 09:48, Michael Weber <firstname.lastname@example.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> On 05/23/2012 11:14 PM, Dan Douglas wrote:
>> On Wednesday, May 23, 2012 04:47:04 PM Robin H. Johnson wrote:
>>> 2. rsync generation is NOT going away. Users will still be using
> First, I'd stick with the current rsync to spread the tree (mirror
> work and mirrors+regular rsync users shouldn't notice any backend
> switch at all).
>> Would users have a way of gaining read-only access? This would be
>> EXTREMELY helpful.
> Sure, this would be possible like any other git checkout
> (layman-git-overlays, github.com, etc.).
> Please compare (browsing source and access description)
> - --
> Gentoo Dev
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
I think there should most definitely be an official github mirror of
the main tree, just a "read-only" mirror from githubs perspective.
Just how to best do the mirroring is the question
a) Replicate to github when a user does 'push' with a server-side push hook?
( Downside: if github goes down, gentoo devs will see it when
they push, and pushing takes longer because the output from the
replicated push is delivered to the original dev )
b) Daemonized hook that monitors for changes in the master repo, and
replicates commits to github after each push
c) Tie it with the rsync tree building system so every time the tree
is built for rsync clients, the master is replicated to github.
Also, this should obviously be force-pushed, so any branch rebases on
the master repo are replicated to the github mirror properly.
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"