Re: [Cvs-dev] Help CVS Project Solicitation

[Conrad T. Pino]

> From: Cvs-dev On Behalf Of Thorsten Glaser

> Conrad T. Pino dixit:
> 
> >The CVS Project hosts on GNU Savannah as a non-GNU "group":
> >https://savannah.nongnu.org/projects/cvs/
> 
> Yes, historically.

CVS Project arrived on Savannah after hosting support at "cvshome.org" was
withdrawn. While the transition was orderly it required substantial labor
from the members.

CVS Project hosting as critical issue was reinforced when "ximbiot.com"
(documentation host) abruptly ceased operation around June 2014. The hard
lesson there was even the most devoted can fall way unexpectedly.

Both times the above providers were, well intended, sincere, devoted,
providing excellent service, but could not sustain the effort over long
time.

I can support substantial CVS Project reorganization but not the complete
departure from FSF GNU Savannah. IMO complete departure raises an
existential threat as CVS Project might not survive another hosting
providers demise. Over and above the labor costs becoming unbearable, FSF
GNU Savannah may not permit a return.

> >> |If any one of you is interested in stepping up to be the chief 
> >> |upstream maintainer of cvs - that would be
> >> 
> >> I am volunteering to do that, if nobody else wants.
> >> I am most certainly not volunteering to join an existing 
> CVS project 
> >> on
> >Savannah.
> >
> >Unless CVS Project migrates away from Savannah, the last two 
> statements 
> >above contradict with respect to granting CVS Project commit 
> privilege.
> 
> Exactly, you fully understood my point ;)

No, I'm not sure I do but what you say next helps.

> My current view of CVS on Savannah is that the last commit 
> was eight (8) years ago, and so, I'd be starting from what I 
> have in my own CVS repo and is known to work. (That is, if I 
> were to become the. "chief upstream".) I would accept Windows 
> contributions, though, of course.

I believe a good path is there to find with better understanding here.

I view GNU Savannah and CVS Project as layered resources:

1) GNU Savannah generally & common to all groups
2) GNU Savannah "CVS" group resources as a whole
3) GNU Savannah "CVS" group CVS repositories (code and web)
4) GNU Savannah "CVS" group CVS code repository specifically

Your last paragraph above suggests Level 4, working with current code
repository is unattractive.

The current code repository contains CVS Project revision history going back
to late 1994 I prefer we retain but how that occurs can be accomplished
multiple ways. You can expect my help balancing these interests.

Understanding where concerns specifically fall within GNU Savannah layered
architectures helps here.

> But, for now, let's not be hasty. Give everyone the chance to 
> respond, maybe two weeks or so, and this includes Mark and 
> Larry. Then, after that, let's have a look at the collected 
> opinion pieces.

Agreed; nothing so far requires hasty decisions.

Thank you,
Conrad T. Pino