Re: [Cvs-dev] Help CVS Project Solicitation

[Conrad T. Pino]

> Conrad T. Pino dixit:
> 
> >May I nominate you to join the CVS Project?
> 
> I'm not sure what you mean with that. Assaf wrote:

The CVS Project hosts on GNU Savannah as a non-GNU "group":
https://savannah.nongnu.org/projects/cvs/
GNU or Savannah provide mailing lists, web site, CVS repositories, trackers,
etc.

Historically, CVS Project "membership" was CVS Project commit privilege
grant which is my intent now.

GNU Savannah mechanics require committers hold an account, add SSH public
key to account, apply to groups, and acceptance by group administrator with
appropriate privilege grants.

This is my understanding of CVS Project structure:
https://savannah.nongnu.org/project/memberlist.php?detailed=1&group=cvs&boxo
ptionwanted=1#options

Historically, CVS Project "members" have commit privileges, and greater
tracker (bugs, tasks, patches) rights. Only a CVS Project "project admin"
has full group management rights on Savannah.

> Just for clarification (Assaf and I already wrote what stakes 
> we have), what is your position, qualification and role in 
> this discussion?

I am CVS Project "member" previously contributing to CVS Windows client,
mailing list message approvals, CVS web site maintenance, and other lesser
tasks as requested.

I lack experience with CVS core code, Autoconf, Automake, and platforms
other than Windoze, CentOS, Debian, and older NetBSD.

I can make frequent limited contributions, deliver unencumbered copyright,
commit changes, and host virtual machines.

=======================

The CVS Project benefited vastly from immense contributions by a highly
skilled visionary (Derek Robert Price) now absent some years. That absence
leaves CVS Project without the combined skills, time, and legal rights to
move forward RAPIDLY. Move forward we can but what pace remains to be seen.

The remaining CVS Project "project admin" are Mark D. Baushke and Larry
Jones.

Mark is active in these discussions and elsewhere said, "At the present
time, my current employer has not waved rights for any new contributions to
GNU projects I might make, so I am not really able to commit to the
repository without direct permission on a case by case basis or it would
leave the copyrights in a tangled situation." Mark is making suggestions I
say we heed.

Larry's availability is unknown here.

=======================

My observations on CVS Project mailing lists suggest leaders within
downstream projects have skills to appropriately balance the competing
interests that may arise within CVS Project scope.

I suggest granting CVS Project commit privilege appropriately can accelerate
CVS Project progress.

> |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.

IMO CVS Project progress without adding committers is possible. More capable
committers may arrive. Absent that and with appropriate guidance I'm willing
to make commits where "appropriate guidance" is EITHER consent from Mark or
Larry OR consensus within CVS Project membership OR unanimous consent on
appropriate CVS Project mailing list.

IMO expanding CVS Project membership (committers) is the path forward having
the least friction.

Best regards,
Conrad T. Pino
CVS Project member