[Product-Developers] Mr. Developer vs. GitHub

[Enrique Pérez Arnaud]

Hi,

I don't find it too bad to give mr.developer a read only 'origin'
remote, and then push to the rw url instead of to the origin. You can
of course add a new remote if you don't want to type the rw url every
time. You then have to pull from origin to let git know that you are
in sync with it:

$ git remote add rw-origin git at github.com:xxx/yyy.git
$ git push rw-origin master
$ git pull origin master

2011/8/4 Mikko Ohtamaa <mikko+plone at redinnovation.com>:
> Hi,
>
> Is it possible to have one URL on GitHub which would allow Mr. Developer to
> checkout the project so that
>
> * anonymous users do not need to set up SSH keys, or access to the project,
> etc.
>
> * people with commit access would still get commit enabled URL
>
> I don't want to have different buildout.cfg for developers with different
> access level to GitHub projects.
>
> Meanwhile what are the best practices to work around this little problem?
>
> Yours sincerely,
> Git hater
> (but github is almost ok)
>
> -----
>
> Follow me in Twitter
>
>
>
> Download mFabrik News for iPhone
> or Android
>
>
>
>
> --
> View this message in context: http://plone.293351.n2.nabble.com/Mr-Developer-vs-GitHub-tp6652959p6652959.html
> Sent from the Product Developers mailing list archive at Nabble.com.
> _______________________________________________
> Product-Developers mailing list
> Product-Developers at lists.plone.org
> https://lists.plone.org/mailman/listinfo/plone-product-developers
>



-- 
Enrique Pérez Arnaud
Yaco Sistemas S.L. | http://www.yaco.es
C/ Rioja 5, 41001 Sevilla (España)
Teléfono: (+34) 954 50 00 57 | Fax (+34) 954 50 09 29