Hi I agree that GitHub would be preferable - in addition to it being more widely used these days (so would potentially be more familiar to new contributors), it also has functionality like CI via GitHub Actions that would be useful for ArcEm.
If it's OK with the current project admins, I would be happy to attempt to do the conversion myself if a lack of time is the main issue. Regards Cameron On Mon, 30 Oct 2023 at 23:50, <i...@jeffray.co.uk> wrote: > I’d vote for Github. Yes, it’s Microsoft, but ‘good things’ are there too. > > > > I. > > > > *From:* Cameron Cawley <ccawley2...@gmail.com> > *Sent:* 30 October 2023 23:46 > *To:* arcem-devel@lists.sourceforge.net > *Subject:* Migrating from CVS > > > > Hi > > > > Several years ago, there was some discussion about migrating the ArcEm > repository from CVS to Git or Subversion now that SourceForge has made all > CVS repositories read only. Is there any further update on this? > > > > I’d be happy to help with this if necessary. I’ve been working on updating > the Windows port as well as some new ones, so it would be nice to have > everything submitted upstream. > > > > Regards > > Cameron > > >
-- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
