On 01/02/2013 02:32 PM, Likitha Shetty wrote:
Even if a new branch is created won't a contributor's work flow for feature
development remain the same? Because from what I understand git by itself does
not allow branch-level access control.
Does that reflect back on the original question? I think Sateesh meant
that a "secure" location had to be non-local in case of data loss? Or
did I misunderstood?
Anyway, GIT doesn't support branch level access control, but does that
matter for an Open Source project?
Wido
Thank you,
Likitha
-----Original Message-----
From: Wido den Hollander [mailto:[email protected]]
Sent: Wednesday, January 02, 2013 5:59 PM
To: [email protected]
Subject: Re: Private development branch
On 01/02/2013 10:26 AM, Sateesh Chodapuneedi wrote:
Hi,
I think the current work flow for development (non-committer) fits well for
small patch development.
But in case of feature development or bigger patches which might need longer
period of development, developer need some place to push the code changes. It's
needed to push code changes to secure location rather than depend on commits to
local repository (in their development machine).
Would forking ASFCS on any public git host (github.com) sound good? Is that a
legitimate idea?
Why not create a new branch on the ASF repo? This way other committers can
easily see that a new feature is being worked on.
That said, you need to have committer rights to do so.
If you place the code on Github it will not be seen by other community members
and it could also mislead other users who find the code on Github.
Wido
Regards,
Sateesh
