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

[Bastian M. <bma...@we...>]

Hello Ethan,

In the past we had a few discussions on migrating away from CVS on the list - with different opinions on Git, Hg, or Subversion.  Personally, I am not unhappy about the end of CVS support by SF, but I hardly have experience with repository conversion myself.

Eric S. Raymond and Allin Cottrel kindly offered help to convert about two years ago. I am attaching a copy of one of their emails below.

Bastian


> -----Ursprüngliche Nachricht-----
> Von: Eric S. Raymond [mailto:es...@th...]
> Gesendet: Montag, 23. November 2015 23:25
> An: Allin Cottrell <cot...@wf...>
> Cc: gnu...@li...
> Betreff: Re: CVS woes
> 
> Allin Cottrell <cot...@wf...>:
> > Any plans for gnuplot to migrate to git? That seems to be _much_
> > better supported at sourceforge. I recently converted gretl
> > (econometrics software on sourceforge) from CVS to git and it has been
> > trouble-free since. If there's interest I can send my recipe for the
> > transition. (There are several "how-to"s out there, but they're not
> > all up to date.)
> 
> I still lurk on this list because I offered to do a git conversion a couple years
> back.  I'm a former GNUPlot contributor and now maintain cvs-fast-export; I'm
> the author of one of those how-tos.
> 
> The maintainers weren't interested, last time.  We'll see if anything has
> changed.  It should; in 2015 still using CVS has gone beyond quaint and retro
> into embarrassing, do-you-never-want-to-have-new-contributors
> territory.
> --
> 		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>

> -----Ursprüngliche Nachricht-----
> Von: sfeam via gnuplot-beta [mailto:gnu...@li...]
> Gesendet: Samstag, 7. Oktober 2017 20:31
> An: gnu...@li...
> Betreff: A plea for volunteers (Fwd: CVS support at SourceForge ends Nov. 30)
> 
> Well guys, it's been fun.
> 
> SourceForge has announced that they will shut down CVS support next month.
> I have little time available to deal with this, and minimal prior experience with
> git.
> 
> So I am making a plea for a  volunteer to step up and transfer the project files
> to some git repository.
> 
> I don't really care much where the repository lives, but unless the associated
> gnuplot web site, bug trackers, mailing lists, etc are also moved it would seem
> simplest to continue using SourceForge.
> 
> If no one steps up, then I'm afraid gnuplot development will be offline
> indefinitely.   I will try to put out a 5.2.1 release before the deadline so
> that at least the current state of development is captured.
> I'll also make and keep an rsync backup.
> 
> Please feel free to contact me privately if you don't want to reply here, but
> everyone reading this has a stake in the project and is welcome to offer
> opinions, suggestions, or whatever help you can.
> 
> 	Ethan
> 
> ----------  Forwarded Message  ----------
> 
> Subject: CVS support at SourceForge and Nov. 30
> Date: Saturday, 07 October 2017, 16:20:47
> From: SourceForge Support <cvs...@so...>
> 
> Greetings project admin,
> 
> We have been planning to discontinue CVS support here at SourceForge for
> several years now, and that time has finally arrived. Since your project is
> making use of CVS for your source version control, you should now convert your
> repository over to another version control system.
> 
> The current plan is to stop allowing CVS commits by November 30th. To be able
> to continue making source code changes you’ll need to have your CVS repo
> converted by then. The ssh access method will stop working, but read-only
> access via both pserver, rsync, and interactive shell will continue to be available
> past the cutoff date (we haven’t determined if or when the read-only support
> will end). This means that you will have plenty of time to convert your data to a
> new SCM format, even well past the cutoff date.
> 
> If you don’t have a particular SCM choice in mind, we recommend choosing
> Subversion (SVN) since it has a workflow that is most similar to that of CVS. You
> might also want to choose Git, which is very popular these days, though it does
> have a steeper learning curve compared to switching to Subversion. You can
> even give each one a try and keep the one you like best. Don’t be afraid to
> experiment.
> 
> For information on how to convert your repository from CVS to SVN or Git, visit
> the following web page: https://sourceforge.net/p/forge/documentation/CVS/
> 
> The page also documents the rsync backup method.
> 
> We hope that your conversion goes smoothly. You can let us know if you run
> into any issues by replying to this email.
> 
> Sincerely,
> 
> SourceForge Support
> 
> -----------------------------------------
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via:
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta