Re: [Nssbackup-team] Schedule
Additional notes to my own mail: Maybe it would be reasonable to remove the choices (recommended, custom, manual) from the main page and introduce a toolbar button/menu entry instead. The toolbar button could provide functionality like 'Set default settings now'. If the user presses it, a dialog window appears: 'This will replace your current settings with the recommended default values. Check them before you save the configuration.' Doing so, we would just modify the way to access the creation of a new configuration with the defaults. However, such button would be much more intuitive and differences for root/non-root users were easier to handle. Ok, we would break the UI from the last Release candidate but frankly we're not really ready for RCs yet. Good night. Jean-Peer Am Donnerstag, den 11.02.2010, 00:21 +0100 schrieb Jean-Peer Lorenz: > Hi, > > in order to document the schedule feature I had a deeper look into it > and discovered some issues I want to discuss: The currently implemented > scheduling doesn't work properly and is quite confusing/messy. > > I've fixed some obvious bugs related to this so far: > > * I moved the 'max. incremental backups in days' from the time tab/page > to the general page since this is not related to scheduling at all. > * I disabled the scheduling for non-default profiles since they can > overwrite schedule settings made in the default profile and this can be > very confusing. > * I fixed some issues with updating of the cron services. > > These changes are not pushed upstream so far. > > > What I intend to do for the series 0.2 is to simplify the schedule UI > even more: > > * I suggest to remove the *precise* settings for > hourly/daily/weekly/monthly backups completely from the UI. I think we > should keep only the *simple* settings and the custom setting. The > reason is that precise scheduling is always loaded as a custom setting > (when opening such configuration again) and this is hard to fix in > series 0.2. For average users a simple setting on a > hourly/daily/weekly/monthly base would be sufficient and experienced > users (assuming they know what a cronline is) can still define their own > custom setting. There are better ways that should be implemented > (crontab) for later releases and it is not necessary to spend too much > effort to fix this in 0.2 since it keeps a hack and lacks support for > non-root users. > > * Moreover, I suggest to simplify the general backup settings on the > main page. The current implementation is buggy and misleading. My idea > is to remove the radio button for 'Manual backups only' completely and > to keep only the choices for 'recommended' and 'custom' backups. I think > this is much clearer than it is now. The problem that remains is that > for non-root users we cannot set up daily backups as a recommended > setting in 0.2. So, either we also modify the description for > 'recommended settings' on the main page for non-root users or remove it > completely. > > In general: > * For release 0.2 we should provide a simple but working application as > fast as possible and then implement new features like scheduling for > root/non-root users in 0.3. This means, we should not try to fix every > aspect in 0.2 rather making it working well (even if some features a > missing or get cut) and then go on with the development of the project > (I really want to see the notification working in a release - this would > be a huge improvement in usability ;-) > > What do you think? I'm looking forward to your thoughts. > > Regards. > Jean-Peer > > ___ > Mailing list: https://launchpad.net/~nssbackup-team > Post to : nssbackup-team@lists.launchpad.net > Unsubscribe : https://launchpad.net/~nssbackup-team > More help : https://help.launchpad.net/ListHelp signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] Schedule
Hi, in order to document the schedule feature I had a deeper look into it and discovered some issues I want to discuss: The currently implemented scheduling doesn't work properly and is quite confusing/messy. I've fixed some obvious bugs related to this so far: * I moved the 'max. incremental backups in days' from the time tab/page to the general page since this is not related to scheduling at all. * I disabled the scheduling for non-default profiles since they can overwrite schedule settings made in the default profile and this can be very confusing. * I fixed some issues with updating of the cron services. These changes are not pushed upstream so far. What I intend to do for the series 0.2 is to simplify the schedule UI even more: * I suggest to remove the *precise* settings for hourly/daily/weekly/monthly backups completely from the UI. I think we should keep only the *simple* settings and the custom setting. The reason is that precise scheduling is always loaded as a custom setting (when opening such configuration again) and this is hard to fix in series 0.2. For average users a simple setting on a hourly/daily/weekly/monthly base would be sufficient and experienced users (assuming they know what a cronline is) can still define their own custom setting. There are better ways that should be implemented (crontab) for later releases and it is not necessary to spend too much effort to fix this in 0.2 since it keeps a hack and lacks support for non-root users. * Moreover, I suggest to simplify the general backup settings on the main page. The current implementation is buggy and misleading. My idea is to remove the radio button for 'Manual backups only' completely and to keep only the choices for 'recommended' and 'custom' backups. I think this is much clearer than it is now. The problem that remains is that for non-root users we cannot set up daily backups as a recommended setting in 0.2. So, either we also modify the description for 'recommended settings' on the main page for non-root users or remove it completely. In general: * For release 0.2 we should provide a simple but working application as fast as possible and then implement new features like scheduling for root/non-root users in 0.3. This means, we should not try to fix every aspect in 0.2 rather making it working well (even if some features a missing or get cut) and then go on with the development of the project (I really want to see the notification working in a release - this would be a huge improvement in usability ;-) What do you think? I'm looking forward to your thoughts. Regards. Jean-Peer signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 515449] Re: some oddities
sorry for the time elapsed, I have been busy with music I uninstalled from synaptic, and checked that it has been done. Now the gui shows the correct configuration, without any reinstallation. I'll wait one day to see what happens, and report. -- some oddities https://bugs.launchpad.net/bugs/515449 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10
Thank you for your extensive reply! I suspect that this makes the bug Won't Fix for the sBackup project since the code base is completely different. I'm marking the bug in Ubuntu as a Won't Fix as well to reflect situation. ** Changed in: sbackup (Ubuntu) Status: Triaged => Won't Fix -- simple backup restore error in 9.10 https://bugs.launchpad.net/bugs/471385 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 519839] Re: untranslatable strings in sbackup
Hum, le second lien aurait dû être : https://translations.launchpad.net/sbackup/trunk -- untranslatable strings in sbackup https://bugs.launchpad.net/bugs/519839 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 519839] Re: untranslatable strings in sbackup
Merci de signaler le problème. La prochaine fois, tu peux commencer à aller voir toi-même d'où il vient: tu peux voir sur https://translations.launchpad.net/ubuntu/lucid/+source/sbackup que sbackup n'est pas traduit par Ubuntu, et en allant voir sur le projet d'origine, tu tombes sur : https://translations.launchpad.net/ubuntu/lucid/+source/language-selector où tout semble traduit. Pourtant le LiveCD (daily-live) de Lucid a toujours la version non traduite, je ne sais pas s'il s'agit d'une problème d'importation... Les autres, des idées? -- untranslatable strings in sbackup https://bugs.launchpad.net/bugs/519839 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 519839] Re: 3 missing French translations
Simple Backup is fully translated in French : https://translations.launchpad.net/sbackup/trunk/+pots/sbackup/fr/+translate I can't find "Abort backup" and "About" in po/pot files. The .pot file should be regenerated to reflect changes in .glade files. ** Changed in: sbackup (Ubuntu) Status: New => Confirmed ** Changed in: sbackup (Ubuntu) Assignee: Ubuntu French Translators (ubuntu-l10n-fr) => (unassigned) ** Summary changed: - 3 missing French translations + untranslatable strings in sbackup -- untranslatable strings in sbackup https://bugs.launchpad.net/bugs/519839 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 519839] [NEW] 3 missing French translations
Public bug reported: Binary package hint: sbackup 1) in Simple Backup config -> Destination tab, the sentence "Abort backup if destination directory does not exist" is not translated in French. 2) in Simple Backup Retore -> Destination tab, the sentence "Use custom" is not translated in French. 3) in "About" (A propos), the description of the software is not localized (Ubuntu 9.10, sbackup 0.10.4) ** Affects: sbackup (Ubuntu) Importance: Undecided Assignee: Ubuntu French Translators (ubuntu-l10n-fr) Status: New ** Tags: french sbackup translation ** Changed in: sbackup (Ubuntu) Assignee: (unassigned) => Ubuntu French Translators (ubuntu-l10n-fr) -- 3 missing French translations https://bugs.launchpad.net/bugs/519839 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 471385] Re: simple backup restore error in 9.10
As one of the contributors of the nssbackup project I want to give some information on the state of sbackup/nssbackup: * the project sbackup is not actively maintained since more than 2 years now (the current version sticks to 0.10.5) and it is very likely (in fact it is pretty sure) that the original developer will not continue working on sbackup. * nssbackup is a fork of the sbackup project. It shares the same ideas as sbackup but does not share code. It is fully rewritten. The main reason for the creation of this fork were differences between the developers regarding sbackup's behaviour and future. While the original sbackup author seems not very able to spend time on sbackup, some good job was done by the other developers on bugs and features. Also, with respect to the code base, sbackup is a dead-end. After a discussion with Aigars Mahinovs, the founder of sbackup project, we agreed that nssbackup could and should be renamed in sbackup, taking over the sbackup project. * the nssbackup-team (2 active developers at the moment) is denoted as maintainer for sbackup. However, we will not spend any effort into sbackup rather improving nssbackup and finally replacing sbackup in the repositories. * at the moment we are still working on release nssbackup 0.2. * Many of the bugs present in sbackup are fixed in nssbackup resp. doesn't exist there. So, please just give it a try and help making it better. You can use it as usual software including installing via package manager. Have a look at the project's site at https://launchpad.net/nssbackup and at the FAQs: https://answers.edge.launchpad.net/nssbackup/+faqs. Hope this helps - Thank you. Jean-Peer (nssbackup-team) -- simple backup restore error in 9.10 https://bugs.launchpad.net/bugs/471385 You received this bug notification because you are a member of NSsbackup team, which is subscribed to sbackup in ubuntu. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
