On Tue, Jul 3, 2012 at 9:00 AM, Jody Garnett <jody.garn...@gmail.com> wrote:
> Aside: I don't think I yet fully comprehend the purpose of our
> developer forks. I'm using "Pro Git" as my reference book and its
> discussion of alternative work-flows for projects, developer forks are
> only mentioned in the context of very restricted access to the
> canonical repo, ie. I would commit to my fork and then make a pull
> request to the higher beings with canonical access.
>
> I think we mostly use this because it is so very well supported by github.
>
> By doing your "pull request" from:
> a) a developer fork - it allows us to work with groups who do not want to
> take part in the project directly
> b) a developer fork + branch - it allows your patch to sit there out of
> your way until it is reviewed an accepted
>
> As for it being so very well supported by github, we are kind of stuck
> with the "fork-me" workflow. It is such a low-effort way of taking part
> that projects get forked on github when they are not looking, and even when
> they are not on github. At least by going to where the action is we can
> have the changes easily available to us for review/merge etc...
>
Regardless of this, I believe that using your own fork, as a core developer
having direct access to the canonical
repo, is warranted when:
* you're doing some large amount of work that cannot be committed directly,
but you want to have
a "backup" of your commits on github
* the stuff you're doing needs a review
* you're working on something that might or might not even be intended to
be committed to the
canonical repo (e.g., experiments)
Cases where, imho, one can work directly against the canonical repo:
* bug fixing that does not require reviews
* small work on your own module, or even large on an unsupported module
There are cases that are sort of borderline. Say you want to work on a
large new feature with someone
else that is also a core developer. One way is to keep the same branch in
the personal forks and
push changes to each other... however this seems overkill to me, isn't it
easier to just create a branch
in canonical and work there?
Cheers
Andrea
--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
