On Feb 19, 2009, at 4:09 AM, Giovanni Marco Dall'Olio wrote:
> On Thu, Feb 19, 2009 at 3:28 AM, C. Titus Brown <[email protected]> wrote:
>>
>> On Wed, Feb 18, 2009 at 06:06:17PM -0800, Christopher Lee wrote:
>> -> On Feb 18, 2009, at 5:48 PM, Istvan Albert wrote:
>> ->
>> -> > I prefer github because of the neat interface.
>> -> >
>> -> > As for local repositories, everyone should host whatever  
>> repositories
>> -> > they want, wherever they want it.
>> -> > When they want to submit patches to you  it goes to this 'patch'
>> -> > repository.
>> ->
>> -> Sounds good.  OK, who is going to strike a blow for democracy and
>> -> create a pygr repository on github?
>>
>> FREEEDOM!
>>
>> http://github.com/ctb/pygr/tree/master
>>
>> Anyone who wants write access, please send me your github username.
>> I've already added ialbert as a collaborator.
>
>
> Great,
> but if I have understood well how github works, the right protocol to
> partecipate to a project is:
> - login/create an account on github
> - go on http://github.com/ctb/pygr/tree/master
> - click on the 'Fork' button'
> - this will create a clone of the repository in your personal account.

Hi Giovanni,

this particular github branch is the 'patch' branch so that people can  
submit patches to a central branch.
For that, we need to use collaboration, I believe.

Anyone who can host a git repo can publicly fork our repository;  
github just makes it pretty ;).

I enjoy the slight irony of setting up a centralized patch management  
process for a distributed version
control system!  And of course the bigger irony of github setting up a  
centralized place for git repos.

cheers,
--titus


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to