Chris Lalancette wrote:
On 10/03/11 - 08:54:47AM, Jim Meyering wrote:
...
> If you want features or accessibility provided by github that are
not
> provided by fedorahosted, I suggest that you simply encourage committers
> to push to both of those repositories instead of just to fedorahosted.
> With that, no additional work needs to be done, since fedorahosted would
> continue to be just as useful.
True, but I think it is just easier and less confusing to have a single
canonical place. That way we don't confuse outsiders.
Hi Chris,
IMHO, as long as documentation is clear and consistent, having multiple
repositories does not cause confusion. Many projects are cloned on
multiple servers or in two or more places on the same hosting provider.
Just publicize the one you prefer and consider the other a handy backup
in case the primary one goes down or somehow gets corrupted.
> 1.5) Ensure that the server-side git hooks we rely on can be
> installed on GitHub.
>
> Personally, I rely on hooks that prevent me from accidentally pushing merge
> commits and on others that automatically send commit email to a list.
>
> >> 2.) Change our .git/config files to point there
>
> IMHO, there is PR value in publicizing and using fedorahosted.
I don't totally disagree, but I think there is better value for the project
in having everything in one place. Since the bulk of our repositories are now
on github, I would rather see us consolidate there and then look at our
options for migration to other hosting.
I think the message (at least for iwhd) is that you'd like
to have a "master" repository for it on github, and I can do that.
If this is important, give me a "please complete by ____" date.
However, I plan to continue pushing to the fedorahosted repository
indefinitely.
Be careful: if you ever switch away from a git server like
fedorahosted, you should ensure that old commits stays around
for a long time, so that its disappearance does not invalidate all
of its gitweb links. Also, if you stop pushing to such a repository,
you have to find a way to inform people that it's no longer being
updated. You can't assume that everyone will read a mailing list
or some web page, so best is to commit a change that git-removes all
files, then adds a README-project-has-moved file that points to the
new repository.