Kevin Horton wrote:
If Ben lacks the time and/or interest to maintain rdiff-backup, is
there anyone who is interested and capable of taking over? If so, he
could inquire if Ben is willing to hand over control. If Ben doesn't
want to hand over control, then the new maintainer could fork a new
project using the rdiff-backup code.
[PLUG]
Ya know, this is one of the things that's nice about distributed
revision control: Anyone can create a repository on their own server, so
there's not necessarily one single Source Of Truth which only a primary
maintainer can commit or control access to, and since alternate
maintainers commit to their own (publicly accessible) branches on their
own servers, the primary maintainer doesn't need to pick a selected few
folks who are trusted to get commit access -- anyone with their own
public webspace can have commit access to their own separately-hosted
branch, and merging between those branches is straightforward.
There are quite a lot of distributed revctl tools out there these days;
Bazaar is arguably one of the lower-barrier-to-entry ones, but darcs and
mercurial and git and so forth all have this basic advantage and premise.
[/PLUG]
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
