Re: [Savannah-hackers-public] Final-stage work/changes on adding the Git homepage source code web browsing option.

[Ian Kelling]

Ineiev <ineiev@gnu.org> writes:

> The group will use no more than one VCS for its homepage; a new
> field 'url_git_viewcvs_homepage' will only add unneeded complexity.

Ayushman didn't explain some of the ideas behind this. I believe we
actually want projects to be able to have CVS and Git homepage
repositories simultaneously on the savannah side, and then be able to
choose and switch back and forth between which one is the source of the
actually published homepage. To understand some thinking of why, imagine
the common use case of a project that has cvs based homepage,
transitioning to git:

1. Tell savannah to create a new git homepage repository.
2. git push homepage checkins.
3. Tell savannah to make the git repo be live.

At this point, the CVS repository should keep existing, we can't assume
or tell that the git repository has all the historical information that
the CVS repository did. Furthermore, CVS is not deprecated as far as I
know. Some people prefer CVS for various reasons and could want to
transition from git back to CVS as the source of the homepage. For
example, the maintain changes from someone who prefers git to someone
who prefers cvs. Since we have the repository there, we might as well
support doing that.