[haiku-development] Re: Haiku git migration status?
- From: Oliver Tappe <zooey@xxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 02 Aug 2011 20:53:33 +0200
Hi,
On 2011-08-02 at 13:00:53 [+0200], Niels Sascha Reedijk
<niels.reedijk@xxxxxxxxx> wrote:
>
> 2011/8/1 Travis Geiselbrecht <geist@xxxxxxxxxx>:
[ ... ]
> >
> > I think it'd make sense to have an auxiliary repository for people to
> > put temporary and development branches into. Ideally different
> > developers could even create their own entire repository, but I'm sure
> > that'd be a lot more work to set up. At various places I've worked
> > where git was in use, we usually had a main repo that has release tags
> > and official branches and is pretty locked down and then have a
> > separate scratch repository for developers to publish various branches
> > in progress.
> >
> > The scratch repos generally get pretty messy pretty fast, but at least
> > the average person that just wants to poke at the source doesn't have
> > to sort through all of that. They just clone the main one.
>
> I think that outsourcing the 'scratch repository' to Github (still)
> has the preference for me. They have great tools for social aspects of
> development embedded in their systems.
While I think it'd be feasible to provide a single scratch repo or even one
per developer on our own servers, I agree with Niels that hosting those on
Github is better. Not only because of their better infrastructure, but
because on Github there's no more separation between people with commit
rights on our repos and people without. So I think hosting our scratch repos
on Github should facilitate pulling more developers into the project.
cheers,
Oliver
Other related posts:
