Re: GNOME Feature Proposal: Backup

[Allan Day <allanpday gmail com>]

Michael Terry wrote:
> It seems discussion died down around this, which means the status quo
> of "just" a GNOME external app will prevail.
> 
> But I'm going to go ahead and take some steps to increase potential
> cooperation between Deja Dup and GNOME, for those that are interested:
> 
> 1) I'll try to stay more on top of the jhbuild moduleset.  It got
> bit-rotten as Colin pointed out, but now it's up to date.
> 
> 2) I'll move my mailing list to GNOME.  That seems rather painless and
> seems to make it easier for GNOME people.  It's super low traffic, so
> doesn't really matter.  But I encourage people to make it high
> traffic.
> 
> 3) I'll experiment with moving my trunk to GNOME git.  This will let
> GNOME people more easily dip their toes in the Deja Dup waters.
> 
> Ideally this will be as low-cost an experiment for me as possible, so
> I'm curious about other people having done similar conversions.  I'll
> keep a bzr mirror in LP for existing developers.  But could I move
> back to bzr and not lose anything?  i.e. would a round-trip
> (bzr->git->bzr) imply some metadata loss?
> 
> And also, does being in git imply that the translation team would
> automatically consider the module?

These changes seem like good ones.

> But moving bugs out of LP is a step too far for me.  As would be
> carving up pieces of Deja Dup into other modules (like
> gnome-control-center).  So I'll just keep chugging along as a separate
> app for now.  But hopefully these changes will let the GNOME community
> become more involved if ya'll desire.

As I've said previously, it would be great to have an integrated GNOME
backup feature, and it would be cool to work together on this. The two
issues you mention above seem to be blocking us though.

Regarding bug tracking: I was waiting to hear some arguments about how
Deja Dup could continue to use LP bug tracking and be a core GNOME
module... if you do think that is possible, do make the case!

Likewise, let's be clear about what's in the way of keeping Deja Dup as
a single module: would whitelisting gcc panels solve that issue?

Best wishes,

Allan
-- 
Blog: http://afaikblog.wordpress.com/
IRC: aday on irc.gnome.org