Re: A plea for volunteers (Fwd: CVS support at SourceForge ends Nov. 30)

[sfeam <sf...@us...>]

On Monday, 09 October 2017 21:54:42 Hans-Bernhard Bröker wrote:
> 
> ESR's tool, cvs-fast-import, which "man git-cvsimport" itself recommends 
> to be used instead, shows none of those messages, so I believe that 
> these can be fixed by a change towards cvs-fast-import.
> 
> I've tried out reposurgen on our repository (with the "faq" module 
> removed), and it seems to work almost perfectly.  "make allcompare" 
> showed nothing missing from the git version.  The original import 
> pseudo-branch GNUPLOT_BETA is, correctly, dropped, all other tags and 
> branch tips compare equal, and .cvsignore files are also taken care of.
> 
> All in all, I'm quite impressed by this tool.

It looks to me that there is general consensus that 

- we should move to git,

- that Eric Raymond's toolset is the best way to do that, and that 

- if Eric himself is willing to guide the conversion it has the greatest chance of success.

So let's do that.

There is no obvious consensus on where the repository should live.
I'm going to step in and vote to stay with SourceForge for now 
because I know how to manage their infrastructure for issue trackers and
putting out a release.   

Eric - several people responded with bits and pieces of meta-info that
you asked for.   Do you have everything you need?

Do I understand correctly that the git repository can be created 
initially anywhere that you find convenient  and then replicated to 
SourceForge afterwards?  If not then maybe we do need additional
discussion about where to do this.

Should we set a freeze date for the existing CVS source [*]?
Anything else that needs to be done in preparation?

	Ethan


[*] freeze concerns -

5.2:  I want to package up the current 5.2 branch as an incremental
release, just so that's out of the way and there is no time pressure after
the conversion while we deal with any cleanup or fallout.  That takes
very little time, but I need to know when to do it.

5.3:  So far as I know this is as good a time as any to freeze.
The current build is usable as it stands.

Older branches:  There should not be any activity there anyhow.