Thanks Stephen, :-)
comments inline.
On 17/05/16 17:42, Mauro Condarelli wrote:
> Il 17/05/2016 16:24, Stephen Joyce ha scritto:
>
>> In the shorter term, my goal is to spend some spare time collecting patches
>> for the bugs that have been found in the past ~3 years (which may take some
>> time since they're scattered around), incorporate them into the existing
>> CVS tree, and issue a point release addressing those issues.
> As it seems we are moving to github I would like to ask You which are plans
> about
> current infrastructure (SourceForge).
> We do *not* want to fork the project or, worse, try to hijack it away from
> the old
> developers (Craig in primis, but not only).
> You are implying You will continue working on the old SF project.
> Is that temporary, something like a "last cleanup", or do You plan to revive
> the
> Project as-is?
As Mauro wrote, should we move to Github or not? :-)
Personally I'm very much a proponent of the move, since Github
encourages collaboration in a much easier way. The threshold for making
a patch and sending a pull request on Github is very low. While on
Sourceforge it's harder to collaborate, in my opinion. Also, with only
two committers, who are busy, it has been hard to get the patches merged
in a timely manner – I mean no offense to you or Craig here.
I have synced the CVS repo to Git in a one-shot way, and continuing
syncing with CVS is difficult and time consuming.
For that reason, it would be very good, IMHO, if we could have your
opinion on the switch, and if you condone the swtich then you could
instead spend your time incorprating the patches into Git.
If you have a Github account I will add your Github user to the
organization as Owner immediately. Also, if Craig could create an
account – the same.
> If the project will continue on SF and You can incorporate also other people
> work
> I think we should reconsider decision to move to GitHub at all.
> OTOH if You (and Craig, of course!) could consider leading us also on the new
> platform
> I think that could be beneficial.
I believe the best way is to disable the CVS repo and point the source
code page to the Github account.
> I am strongly against having two projects for any extended period of time.
However, I think this should be a clean switch, i.e. to stop commiting
new things to CVS and instead commit to Git.
>> In the longer term, Craig has stated he still has the desire to work on
>> BackupPC; the problem currently is time. I'm still hopeful that he will be
>> able to find some time to help review any major updates, releases, etc.
>> This is after all, still his baby.
> That is wonderful news.
I agree. That is great news. I hope he is willing to use Git and Github.
I believe his baby has grown and is now ready school. ;-)
> In particular, at present, this means:
> - should we move to github or not?
I vote yes, if I have a say in it.
> - should effort be concentrated on v3.x or on v4.x?
I think it should be v4.x.
However, let's merge in bug fixes for v3.x since a lot of users still
use v3.x and will not move until v4.x comes out of beta, and not even
until a few dot-releases of v4.x.
In fact, lets create a v3.x maintenance branch to merge in the bug fixes
and make releases, and then merge the v4.x branch into master.
> - has the effort to ease installation/configuration his blessing?
> - can he comment (and set priorities) to workpackages ("issues", in case we
> move to GH)
> - whatever he would like to indicate as a priority
>
> Thanks a lot Stephen and
> Regards to Craig
Seconded! Thanks a lot Stephen and Craig!
--
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/
|
