BackupPC-users

Re: [BackupPC-users] Status on new BackupPC v4

2016-05-16 08:05:54
Subject: Re: [BackupPC-users] Status on new BackupPC v4
From: Stephen Joyce <stephen AT email.unc DOT edu>
Date: Mon, 16 May 2016 08:05:21 -0400
Hi,

Thanks to Lars and Mauro. It's great that you've taken this on.

FWIW, I contacted Craig directly last week and received a reply over the weekend. It sounds like he's quite busy, and does not regularly read these lists, but he still hopes to be able to contribute more in the future (ie, review updates and releases).

He also mentioned that the one remaining feature he had planned for 4.0 before it became beta was FTP. Unless there is a large demand among users for FTP, I'm unsure it should hold up the beta label. Thoughts?

In any event, since the sourceforge pages are currently the 'official' location where new users land (and where distros look for new code), I asked him to make me an admin on the sourceforge project page. So if changes are needed there, including a link to patched and/or bleeding-edge source on github before it makes it into an official release, I can do that. I'm also amenable to a few other regular contributors having admin as long as they have the time, inclination, and ability to help out.

I think if it's eventually officiallyhosted on github, it's important to leave the door open for Craig to assist when/if time permits.

Cheers,
Stephen

On Mon, 16 May 2016, Lars Tobias Skjong-Børsting wrote:

On 16/05/16 13:23, Mauro Condarelli wrote:
My current plans are:

1) bring github up to date.

I have now finished bringing it up to date and have published it on github:

https://github.com/backuppc/backuppc
https://github.com/backuppc/backuppc-xs
https://github.com/backuppc/rsync-bpc

4) there are several alpha tarballs for v4.0.0, keeping them as a bit of 
history in the
    branch would be nice.

I have created a branch "v4.0.0" and imported each tarball release as a
commit.
https://github.com/backuppc/backuppc/tree/v4.0.0

5) request everyone to open "issues" on backuppc/backuppc for:
    a) patches already sent against current code-base.
       this is necessary to consolidate them and avoid losing a lot of good 
work.
    b) bug (or "rough edges") reports against current code-base.
       this is necessary to evaluate the magnitude of involved initial effort.
    c) wishes.
       as we want to move ahead we could as well understand where we want to go.

Issues is open for business, go ahead and report.

Mauro has been invited to the organization already. Please post your
username if you would like to join in.

--
Best regards,
Lars Tobias

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/