Re: [Cvs-dev] Help CVS Project Solicitation

[Conrad T. Pino]

> From: Cvs-dev On Behalf Of Bob Proulx

> ...  I guess I did already say that I would 
> be sad to see cvs go elsewhere.  However CVS is not a GNU 
> Project project.  If the heir apparent for CVS is hosted 
> elsewhere I would be okay with it.  I would support it.  I 
> would help.  Many projects are hosted many different places.  
> Even many official GNU Project projects such as GCC are 
> hosted elsewhere.

CVS Project historically required substantial agreement before acting.

Anyone may fork and become a CVS heir with a new name as CVSNT did.

Forks may get CVS Project support if CVS Project remains inactive.

> But let me answer your questions.  Even if you don't like Savannah.

Savannah opinions were said but nothing said so far is a proposal.

> > http://savannah.nongnu.org/cvs/?group=cvs says "Getting a 
> Copy of the 
> > CVS Repository" but only contains instructions on how to get a 
> > checkout (working copy), not an actual copy of the repository.
> 
> We would love people to help improving the web interface.  :-)
> 
> > Can I use rsync over ssh, after recovering my account, to get the 
> > actual repository, over authenticated and secure transport?
> 
> Of course you can rsync any of the repositories.  Try this:
> 
>   rsync cvs.savannah.nongnu.org::
>   rsync cvs.savannah.nongnu.org::sources/
> 
> I know you said secure transport.  For members of any project 
> you can use ssh access.  Presently one must be a member of 
> any project, more than just registering an account but also a 
> member of any project, in order to have ssh access.  Commands 
> are restricted.  General shell access is not allowed.
> 
> Try this for ssh access.  Where $USER must match your 
> Savannah member account name.
> 
>   rsync address@hidden:/sources/cvs/
> 
> And of course that applies to all of the other version 
> control systems too.  Modify the paths as appropriate to get 
> to the other files.

Thank you! I did not know this.

> > If so, how, and why is that not documented?
> 
> As to where this is documented the documentation was, past 
> tense, in the form of a wiki.  Wikis are great when there are 
> many eyes to look at things and prevent spam.  But not so 
> good when there are not.
> Wikis become link spam farms unless watched over.  At the 
> present time the documentation is read-only unless a member 
> of the project due to past history of spam.  I say it was a 
> wiki because that also describes the documentation.  You know 
> how wikis can be, somewhat eclectic.
> 
> It would be wonderful if someone were to volunteer time and 
> effort to organize and improve the documentation.  Instead we 
> spend our time working on other things.  There are no paid 
> staff positions here.  We are all volunteers.
> 
>   https://savannah.gnu.org/maintenance/AccessToCVSROOT/
> 
> And rsync access is also mentioned here too:
> 
>   https://savannah.gnu.org/maintenance/CvSToSvN/
>   https://savannah.gnu.org/maintenance/CvsRsyncWriteAccess/

I'm Wiki proficient and volunteer for documentation upon request.

> > If not, Savannah fails at code hosting.
> 
> I know you don't like Savannah.  ...

There is much to discuss before any proposal to leave Savannah.

Best regards,
Conrad Pino