Endorsement of https://github.com/fedoraproject

[Bruno Wolff III]

On Wed, Feb 01, 2012 at 16:50:49 +0100,
  Carlo de Wolf <cdewolf at redhat.com> wrote:
> >On Wed, Feb 01, 2012 at 16:19:08 +0100,
> >   Carlo de Wolf<cdewolf at redhat.com>  wrote:
> >>Whilst it is possible to maintain such a git branch at
> >>fedorahosted.org it would suffer from a lack of integration with the
> >>upstream branch hosted on GitHub itself.
> >Wouldn't make more sense for maintainers to either get their own github
> >accounts or just keep a local checkout of upstreams they are interested in
> >so that they can work easier with upstreams?
> 
> That works, until you get to a point where both upstream developers
> and packagers need to work together.

Packagers can still ask for upstream commit access.

> https://github.com/fedoraproject/jboss-as/commit/47a33041eb75290629fec7869604f39c19881366
> is something an upstream developer can work with right away.
> 
> https://github.com/fedoraproject/jboss-as-rpm/blob/master/SOURCES/0002-Fix-initd-script.patch
> is something only useful and usable by rpmbuild. (Note that this
> repo must be relocated to pkgs.fedoraproject.org.)

That's more or less what I said. That's why I don't see a reason for Fedora
to have their own github mirror.

However even if a packager can't get upstream commit access they can still
keep a local checkout of the upstream repo and use that for both creating
patches for Fedora and for sending patches back upstream (either having
thir own git server or emailing patches created using git).