Backup Central

Hi all, for the past year or so since I got my degree and started in
on the "real world" I have not given rdiff-backup the attention that a
maintainer should, and that I think it deserves. So I believe
rdiff-backup will be better off with another maintainer.

I realize this message is far too late, but I retain an interest in
rdiff-backup and still consider it a very worthwhile project. However
I never focused enough to do what I thought was the next task: fix
some of the bugs (especially restoring bugs) reported on the mailing
list, but still hard to reproduce, and make sure rdiff-backup is not
vulnerable to similar bugs.

My tendency to do everything in a FIFO fashion added to this: I would
get stuck on a hard-to-solve bug, and other rdiff-backup emails would
pile up behind it, making it harder for me to get started, especially
as time went on.

It was painful for me to catch up on the mailing list, because by
marking messages with unresolved issues as "read" I'm resigning to
never fully appreciate the hard work, insight, and experience
contributed by members of this mailing list. Of course, letting
hundreds of unread messages pile up is much worse, and I apologize for
this.

In the future, I don't think I will have the energy to track down
every bug, answer every email, or add significant new features to
rdiff-backup. This is why I think someone else working on the project
is needed in the long term. However, I do commit in the medium-term
to checking patches in on a timely basis (as I have not done
recently), and do a better job of processing the mailing list.

I'd like to thank all the people who helped out regularly even when I
wasn't, like Dean Gaudet, Andrew Bressen, Troels Arvin, and Trevor
Harman, and especially Keith Edmunds and David Kempe.

I also welcome any suggestions on where to go from here.


--
Ben Escoto

On Thu, 24 Mar 2005 22:17:32 -0800
Ben Escoto <ben < at > emerose.org> wrote:

Quote:

In the future, I don't think I will have the energy to track down
every bug, answer every email, or add significant new features to
rdiff-backup. This is why I think someone else working on the project
is needed in the long term. However, I do commit in the medium-term
to checking patches in on a timely basis (as I have not done
recently), and do a better job of processing the mailing list.

Well done, Ben. That's a tough thing to say - giving away the baby isn't
easy.

Does anyone feel that they can take over the project from Ben? I don't
think I can commit the time it needs, but it would be a shame to see either
Ben be "forced" to continue with it or the project die.

While one person to take over is preferable, if that fails is there a core
of people that would be prepared to co-ordinate patch integration and
releases?

Keith

--
----------------------------------------------------------------------
Business computing support: http://www.tiger-computing.co.uk
Linux consultancy: http://www.TheLinuxConsultancy.co.uk
----------------------------------------------------------------------

On Wed, 30 Mar 2005 13:41:06 +0100, Keith Edmunds <keith < at > midnighthax.com> wrote:

Quote:

Does anyone feel that they can take over the project from Ben? I don't
think I can commit the time it needs, but it would be a shame to see either
Ben be "forced" to continue with it or the project die.

While one person to take over is preferable, if that fails is there a core
of people that would be prepared to co-ordinate patch integration and
releases?

I could help if there needs to be some sort of core team. I don't code
much but don't mind helping out with documenting the internals (API
documentation etc.) so that we could maybe we can flatten the learning
curve for users to get on board.



--
Mohanaraj
Operations
Asix Solutions Sdn. Bhd.

Quote:

Quote:

Quote:

Quote:

Quote:

Keith Edmunds <keith < at > midnighthax.com>
wrote the following on Wed, 30 Mar 2005 13:41:06 +0100

Quote:

Does anyone feel that they can take over the project from Ben? I
don't think I can commit the time it needs, but it would be a shame
to see either Ben be "forced" to continue with it or the project
die.

Hi, I don't feel forced to continue, I plan to keep working a bit on
it even if a new maintainer steps up. But consider all the added
features from 0.12 -> 0.13: resource fork, extended attributes, ACLs,
filesystem autodetection, user/group mapping, etc. If there are
similar advances in the future someone else would have to implement
most of them.


--
Ben Escoto

Quote:

Quote:

Quote:

Quote:

Quote:

David Kempe <dave < at > solutionsfirst.com.au>
wrote the following on Mon, 04 Apr 2005 20:16:36 +1000

Quote:

I am happy to become a co-maintainer of rdiff-backup.
I feel I can commit the time of myself or one of my staff to get to know
the code a bit better.
I have to say that I'm not a python programmer, just heavy user of
rdiff-backup and would look to others for useful programming expertise.

So, I am happy to help to ease Ben's burden, but I am not sure I am
the right person for the job. I may be able to conjole some people I
know into it tho

Thanks Dave, I have added you as a project admin to Savannah. You can
let me know if you need anything else or what to discuss.

Now assign all your employees to find some bugs and fix them ;)


--
Ben Escoto