Funny, you bring this subject on the table. I've initiate contact this
week with Savannah to figure out what we can do.
I would like to get rid of the savannah project completely and redirect
the traffic to github and rdiff-backup.net <http://rdiff-backup.net>,
but it's not going toward the direction I want.
If we want to go forward with this, the best is to contact the current
members of rdiff-backup project savannah:
https://savannah.nongnu.org/project/memberlist.php?group=rdiff-backup
Here the initial communication made by Otto on this subject:
https://lists.gnu.org/archive/html/savannah-hackers-public/2019-08/msg00005.html
Here mine:
https://lists.gnu.org/archive/html/savannah-hackers-public/2019-11/msg00014.html
@EricZolf <mailto:address@hidden> You are free to jump in the
conversation ! :P
--
Patrik Dufresne Service Logiciel inc.
http://www.patrikdufresne.com <http://patrikdufresne.com/>/
514-971-6442
130 rue Doris
St-Colomban, QC J5K 1T9
On Sat, Nov 23, 2019 at 9:45 AM <address@hidden
<mailto:address@hidden>> wrote:
Hi,
having a deeper look at being able to push a release to PyPI [1], I
realized that it has a dependency (2nd comment) on having control on
the
Savannah site and mailing list (and probably project) as stated in [2].
Now Otto and I are struggling to get a definitive answer on those
points, we've tried different approaches and got some promises but no
concrete actions. It might have gone lost in work day's turmoil but it
would be really nice to get this point addressed and closed.
I know that the relevant persons are on this list, alive and kicking,
and have been so far helpful to take over the GitHub repo, so is there
something we can do or is missing to finish the process, or can someone
else help us to get this resolved?
Thanks, Eric
[1] https://github.com/rdiff-backup/rdiff-backup/issues/58
[2] https://github.com/rdiff-backup/rdiff-backup.net/issues/1
(re-directed from
https://github.com/rdiff-backup/rdiff-backup/issues/52)