mainstoreBackup - Support: sr #109023, collaborative development


sr #109023: collaborative development

Submitter:  None
Submitted:  Tue 26 Apr 2016 10:04:46 PM UTC
Category:  None Priority:  5 - Normal
Severity:  1 - Wish Status:  None
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup

Mon 02 May 2016 11:59:08 PM UTC, comment #3: 

Now it makes sense why "doNotDelete" is coded how it is.

I don't understand your comment about github, but there are many other platforms (BitBucket for example). And, as I see it, a collaborative development approach should alleviate your work on this project and not increase it.

But anyway, thanks for this fantastic tool!

Fri 29 Apr 2016 10:41:05 AM UTC, comment #2: 


there are two reasons why options in storeBackup are how they are:

1. historical reasons
Options were add in a way they do not change the behavior of older versions so the users can upgrade without issues.

2. compatibility with command line
storeBackup supports options on the command line an in configuration files. These two possibilities must fit together. Example doNotDelete:
The "normal" (default) behavior of storeBackup is to delete old backups (depending on keep* configuration). To change this, you can use --doNotDelete. That's perfectly clear. Using the same option in the configuration file may be confusing. But therefore it's explained in detail in the comments.

I do not have the time to handle all the issues of a collaborative development approach. At the moment I'm very busy in my job and this probably will happen in the next years. Especially I would no use github which has been taken over by feminists - as far as I know.

Best Regards

Heinz-Josef Claes <hjclaes>
Group administrator
Tue 26 Apr 2016 10:21:00 PM UTC, comment #1: 

I forgot to say hi...

Hello! :)
And again, thanks for this amazing tool!

Tue 26 Apr 2016 10:04:46 PM UTC, original submission:  

I just started to use this tool and it is amazing!

But I think it could have little improvements...
For example, the names for configuration variables are very confusing: some are "doIT" and others are "doNOTdoIT". When I see "doNotDelete = yes|no" I have to over think what it is and how to set it to do what I want. If the name was "deleteOldBackup = yes|no", it would be a lot easier!!

But I think this kind of little modification/improvement could be done by someone interested in contributing to this tool. Also, other people could help develop the tool, improve it, and fix bugs (if any).

So, I would ask you to adopt a collaborative development approach. Maybe using github. Have you ever thought about it?




(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by hjclaes (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-ee12.
    Corresponding source code