Menu
▾
▴
geomview-devel
|
From: Lloyd W. <llo...@ya...> - 2017-10-08 04:42:44
|
We've had a long 17-year run out of cvs in SourceForge, but it's now reached end of life, and cvs clients are getting as rare as telnet clients in distros these days (e.g. not in current Mac OS X Xcode). So, geomview has to migrate to a new primary repository, per the SourceForge note below. Mark was playing with github, and could bring that up to date: https://github.com/geomview which is one possibility, as are git on Sourceforge, mercurial on sourceforge -- or even svn on sourceforge, which I'll be looking at migrating SaVi to (as I'm pretty much the only developer there, and mercurial and git are complex configuration overkill for that project and this user. if you're capable of building the development geomview autoconf toolchain, git probably won't cause you too many difficulties.) thoughts on the approach to take? thanks, Lloyd Wood http://savi.sf.net ----- Forwarded Message ----- From: SourceForge Support <cvs...@so...> Sent: Sunday, 8 October 2017, 3:22 Subject: CVS support at SourceForge and Nov. 30 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 |
|
From: Lloyd W. <llo...@ya...> - 2017-10-09 03:38:08
|
Okay, it looks like Mark bringing https://github.com/geomview up to date, then sticking a note in the sourceforge CVS that github is where any current development is at, and my then updating various geomview webpage pointers would be the approach to take. thanks Lloyd Wood http://savi.sf.net ________________________________ From: Claus-Justus Heine <hi...@cl...> To: Steve Robbins <st...@su...>; geo...@li...; Lloyd Wood <llo...@ya...> Cc: "geo...@li..." <geo...@li...>; Mark Phillips <mb...@ge...> Sent: Monday, 9 October 2017, 14:20 Subject: Re: [geomview-users] Sourceforge cvs support for geomview ending 30 Nov 2017 Sorry, being buried in my every day's job activities I will not be able to help much, unfortunately. For practical reasons I would vote for github if I had a vote. Kind thanks for your efforts to keep Geomview alive! Claus Am 09.10.2017 um 05:13 schrieb Steve Robbins: > On Sunday, October 8, 2017 4:42:33 AM CDT Lloyd Wood via geomview-users wrote: > >> thoughts on the approach to take? > > I'm fine with whatever the committers decide -- they are the biggest user of > the source control system. > > If I had a vote, however, I'd place mine on git. Probably github. The main > reason is that I think SVN will similarly die out at some point. For > instance, Debian's forge (alioth) is being replaced and will likely only > support git; see https://wiki.debian.org/Sprints/2017/Alioth/MeetingMinutes/ > VCS > > -Steve > -- Claus-Justus Heine hi...@cl... http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de |
|
From: Claus-Justus H. <hi...@cl...> - 2017-10-09 03:46:04
|
Sorry, being buried in my every day's job activities I will not be able to help much, unfortunately. For practical reasons I would vote for github if I had a vote. Kind thanks for your efforts to keep Geomview alive! Claus Am 09.10.2017 um 05:13 schrieb Steve Robbins: > On Sunday, October 8, 2017 4:42:33 AM CDT Lloyd Wood via geomview-users wrote: > >> thoughts on the approach to take? > > I'm fine with whatever the committers decide -- they are the biggest user of > the source control system. > > If I had a vote, however, I'd place mine on git. Probably github. The main > reason is that I think SVN will similarly die out at some point. For > instance, Debian's forge (alioth) is being replaced and will likely only > support git; see https://wiki.debian.org/Sprints/2017/Alioth/MeetingMinutes/ > VCS > > -Steve > -- Claus-Justus Heine hi...@cl... http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de |
|
From: Lloyd W. <llo...@ya...> - 2017-11-07 20:42:30
|
While saying that github can host active geomview development, there's a bunch of other dormant little things in geomview cvs - maniview, orrery, gv1-modules, the fabled gv2. sourceforge isn't guaranteeing the longevity of read-only cvs, so worth also copying everything over to svn via e.g. a cvs2svn import for longevity/archival? thanks Lloyd Wood http://savi.sf.net/ ________________________________ From: Lloyd Wood via geomview-users <geo...@li...> To: Claus-Justus Heine <hi...@cl...>; Steve Robbins <st...@su...>; "geo...@li..." <geo...@li...> Cc: "geo...@li..." <geo...@li...>; Mark Phillips <mb...@ge...> Sent: Monday, 9 October 2017, 14:38 Subject: Re: [geomview-users] Sourceforge cvs support for geomview ending 30 Nov 2017 Okay, it looks like Mark bringing https://github.com/geomview up to date, then sticking a note in the sourceforge CVS that github is where any current development is at, and my then updating various geomview webpage pointers would be the approach to take. thanks Lloyd Wood http://savi.sf.net ________________________________ From: Claus-Justus Heine <hi...@cl...> To: Steve Robbins <st...@su...>; geo...@li...; Lloyd Wood <llo...@ya...> Cc: "geo...@li..." <geo...@li...>; Mark Phillips <mb...@ge...> Sent: Monday, 9 October 2017, 14:20 Subject: Re: [geomview-users] Sourceforge cvs support for geomview ending 30 Nov 2017 Sorry, being buried in my every day's job activities I will not be able to help much, unfortunately. For practical reasons I would vote for github if I had a vote. Kind thanks for your efforts to keep Geomview alive! Claus Am 09.10.2017 um 05:13 schrieb Steve Robbins: > On Sunday, October 8, 2017 4:42:33 AM CDT Lloyd Wood via geomview-users wrote: > >> thoughts on the approach to take? > > I'm fine with whatever the committers decide -- they are the biggest user of > the source control system. > > If I had a vote, however, I'd place mine on git. Probably github. The main > reason is that I think SVN will similarly die out at some point. For > instance, Debian's forge (alioth) is being replaced and will likely only > support git; see https://wiki.debian.org/Sprints/2017/Alioth/MeetingMinutes/ > VCS > > -Steve > -- Claus-Justus Heine hi...@cl... http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ geomview-users mailing list geo...@li... https://lists.sourceforge.net/lists/listinfo/geomview-users |
|
From: Lloyd W. <llo...@ya...> - 2017-11-24 05:45:53
|
As Sourceforge CVS stops allowing commits and goes read-only for some indefinite time, I've made copies of everything we have in CVS as tarballs under http://www.geomview.org/dev (This also buys more time for cvs2svn conversion, which is a nice idea in theory, but which I can't make work.) cheers Lloyd Wood http://savi.sf.net ________________________________ From: Lloyd Wood <llo...@ya...> To: Lloyd Wood <llo...@ya...>; Steve Robbins <st...@su...>; "geo...@li..." <geo...@li...> Cc: "geo...@li..." <geo...@li...>; Mark Phillips <mb...@ge...> Sent: Wednesday, 8 November 2017, 7:42 Subject: Re: [geomview-users] Sourceforge cvs support for geomview ending 30 Nov 2017 While saying that github can host active geomview development, there's a bunch of other dormant little things in geomview cvs - maniview, orrery, gv1-modules, the fabled gv2. sourceforge isn't guaranteeing the longevity of read-only cvs, so worth also copying everything over to svn via e.g. a cvs2svn import for longevity/archival? thanks Lloyd Wood http://savi.sf.net/ ________________________________ From: Lloyd Wood via geomview-users <geo...@li...> To: Claus-Justus Heine <hi...@cl...>; Steve Robbins <st...@su...>; "geo...@li..." <geo...@li...> Cc: "geo...@li..." <geo...@li...>; Mark Phillips <mb...@ge...> Sent: Monday, 9 October 2017, 14:38 Subject: Re: [geomview-users] Sourceforge cvs support for geomview ending 30 Nov 2017 Okay, it looks like Mark bringing https://github.com/geomview up to date, then sticking a note in the sourceforge CVS that github is where any current development is at, and my then updating various geomview webpage pointers would be the approach to take. thanks Lloyd Wood http://savi.sf.net ________________________________ From: Claus-Justus Heine <hi...@cl...> To: Steve Robbins <st...@su...>; geo...@li...; Lloyd Wood <llo...@ya...> Cc: "geo...@li..." <geo...@li...>; Mark Phillips <mb...@ge...> Sent: Monday, 9 October 2017, 14:20 Subject: Re: [geomview-users] Sourceforge cvs support for geomview ending 30 Nov 2017 Sorry, being buried in my every day's job activities I will not be able to help much, unfortunately. For practical reasons I would vote for github if I had a vote. Kind thanks for your efforts to keep Geomview alive! Claus Am 09.10.2017 um 05:13 schrieb Steve Robbins: > On Sunday, October 8, 2017 4:42:33 AM CDT Lloyd Wood via geomview-users wrote: > >> thoughts on the approach to take? > > I'm fine with whatever the committers decide -- they are the biggest user of > the source control system. > > If I had a vote, however, I'd place mine on git. Probably github. The main > reason is that I think SVN will similarly die out at some point. For > instance, Debian's forge (alioth) is being replaced and will likely only > support git; see https://wiki.debian.org/Sprints/2017/Alioth/MeetingMinutes/ > VCS > > -Steve > -- Claus-Justus Heine hi...@cl... http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ geomview-users mailing list geo...@li... https://lists.sourceforge.net/lists/listinfo/geomview-users |
Thanks for helping keep SourceForge clean.
X