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

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

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

-----------------------------------------