[Maria-developers] WL enhancements
Hi. That's a rough list of enhancement ideas for worklog. Some of them I'm going to do (but not all). Feel free to suggest more or "get rid of WL, use X instead", just don't forget the "because of" part. report: easy to do tasks make it to provide a list of "low-handing fruits", tasks that could be done relatively easily and without prior extensive MySQL source knowledge. For community members that want to help. report: who's doing what NOW that's pretty obvious report: tasks for specific version, roadmap worklog kind of does it now, mostly listed for completeness ability to remove hours Somebody mentioned that a number of hours could be increased by mistake, and there should be a way to decrease is back. I'm not convinced it's a good idea, though. generate weekly report templates to reduce the need for double or tripple reporting. WL generates a weekly report for a developer, based on its data, and sends it to this developer. The developer in question can edit it and sent to reports@, or copy-paste from it, or filter it out and ignore completely. private tasks and categories There should be a way to have private categories and tasks in WL. this includes fixing "private" field in WL tasks. distingushing between employees and users for many tasks from the above WL needs to distinguish between MPAB employees and other registered users. better search Sanja seems to be unhappy with WL search make it more readable for novice wl readers no big redesign or anything, though. but I think that moving task description up and, say, attached files and estimated number of hours down could help somewhat. not editable unless authenticated that's more a bug than a new feature. no changes in tasks should be allowed unless a user is authenticated. subscribe w/o authentication but perhaps we may want to allow users to subscribe to tasks w/o being authenticated ? I'm not going to do that, though. embeddable views a couple of pages that could be easily inserted (iframe-ed ?) into other pages without disrupting the design too much. Mainly "roadmap" and "easy tasks" reports, but also "WL of the day" too. "WL of the day" - it's a new crazy idea, I wanted to discuss. Basically, that's a small block somewhere on the main page that shows a randomly (?) selected WL task - only the description (or a part of it), a link to a full task page, and voting controls (useless... very important). Regards, Sergei
Wednesday 03 March 2010 17:07:13 Sergei Golubchik wrote:
ability to remove hours Somebody mentioned that a number of hours could be increased by mistake, and there should be a way to decrease is back. I'm not convinced it's a good idea, though.
You can't assume that people don't make mistakes. Even simple typos are currently impossible to fix unless they happen to be less than the intended hours. Kind regards, Bo Thorsen, Monty Program AB.
Hi! 3 марта 2010, в 18:07, Sergei Golubchik написал(а): [skip]
ability to remove hours Somebody mentioned that a number of hours could be increased by mistake, and there should be a way to decrease is back. I'm not convinced it's a good idea, though.
Actually it would be better to be able to edit record during (for example) one hour. IMHO it is enough to fix mistakes in text and hours. (IMHO) [skip]
Thursday 04 March 2010 10:42:09 Oleksandr Byelkin wrote:
Hi!
3 марта 2010, в 18:07, Sergei Golubchik написал(а): [skip]
ability to remove hours Somebody mentioned that a number of hours could be increased by mistake, and there should be a way to decrease is back. I'm not convinced it's a good idea, though.
Actually it would be better to be able to edit record during (for example) one hour. IMHO it is enough to fix mistakes in text and hours.
The two times I put something in WL and made a mistake, it took several days before I realised it. Bo.
On Wed, Mar 3, 2010 at 6:07 PM, Sergei Golubchik <sergii@pisem.net> wrote:
Feel free to suggest more or "get rid of WL, use X instead",
Just to update you on discussion we've had last August (I think). Our, or at least my, current thinking is that worklog is currently used as a "default" option since it is the tool that everyone is familiar with from MySQL. However, eventually we may spend some time on comparing worklog and other tools, especially launchpad blueprints. This means that small fixes to WL are ok, but before doing a lot of wok we should have the discussion "what do we really want to use long term".
just don't forget the "because of" part.
The points in favor of launchpad would be + nice user interface + integration between bzr, bugs, blueprints... (if one uses lp for all of this!) + widely used/known (you should always use popular open source tools rather than writing your own) Against launchpad: - usually it is always too simple for our needs (at least bugs part). Needs investigation on how easy it is to extend and whether Canonical is actually responsive to outside developed features. The points in favor of worklog would be + We currently use it for basic project management tasks like counting hours per project. This would have to be implemented as launchpad extension or by separate software if not using worklog. + In principle supports Scrum oriented working mode (which we don't use atm) Against worklog: - Needs nicer ui and also better usability. Some of your items below actually improve it here (such as better search) henrik -- email: henrik.ingo@avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc
I might also add... *What happens when/if Canonical/Ubuntu goes bunk? Using all of the tools provided by one vendor can be a great thing but not if the vendor's existence is "tenuous." If that happens, how easy would it be to migrate data away from the vendor and would we even have that option? On Mon, Mar 15, 2010 at 5:47 AM, Henrik Ingo <henrik.ingo@avoinelama.fi>wrote:
On Wed, Mar 3, 2010 at 6:07 PM, Sergei Golubchik <sergii@pisem.net> wrote:
Feel free to suggest more or "get rid of WL, use X instead",
Just to update you on discussion we've had last August (I think).
Our, or at least my, current thinking is that worklog is currently used as a "default" option since it is the tool that everyone is familiar with from MySQL. However, eventually we may spend some time on comparing worklog and other tools, especially launchpad blueprints. This means that small fixes to WL are ok, but before doing a lot of wok we should have the discussion "what do we really want to use long term".
just don't forget the "because of" part.
The points in favor of launchpad would be + nice user interface + integration between bzr, bugs, blueprints... (if one uses lp for all of this!) + widely used/known (you should always use popular open source tools rather than writing your own) Against launchpad: - usually it is always too simple for our needs (at least bugs part). Needs investigation on how easy it is to extend and whether Canonical is actually responsive to outside developed features.
The points in favor of worklog would be + We currently use it for basic project management tasks like counting hours per project. This would have to be implemented as launchpad extension or by separate software if not using worklog. + In principle supports Scrum oriented working mode (which we don't use atm) Against worklog: - Needs nicer ui and also better usability. Some of your items below actually improve it here (such as better search)
henrik
-- email: henrik.ingo@avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
Adam,
I might also add...
*What happens when/if Canonical/Ubuntu goes bunk?
Using all of the tools provided by one vendor can be a great thing but not if the vendor's existence is "tenuous." If that happens, how easy would it be to migrate data away from the vendor and would we even have that option?
AFAIU this is a non-issue. LP is open source: http://blog.launchpad.net/general/launchpad-is-now-open-source One can host it locally if one wants to. So the question is only about the data. I don't know if one can easily migrate all the hosted data about a project to a local host. Timour <cut>
And the data is the important part... I think it's a good idea, but I am just trying to bring up a counterpoint that might not have been discussed. On Mar 15, 2010 9:08 AM, "Timour Katchaounov" <timour@askmonty.org> wrote: Adam,
I might also add...
*What happens when/if Canonical/Ubuntu goes bunk?
Using all of the t... AFAIU this is a non-issue. LP is open source: http://blog.launchpad.net/general/launchpad-is-now-open-source One can host it locally if one wants to. So the question is only about the data. I don't know if one can easily migrate all the hosted data about a project to a local host.
Timour <cut>
Monday 15 March 2010 11:47:43 Henrik Ingo wrote:
The points in favor of worklog would be
+ it's independent of bzr. Compared to git, bzr seems to have only the launchpad integration as the selling point. Moving to blueprints gives us an additional argument for staying with bzr. If Canonical would switch to git and keep the rest of launchpad running, that would be fantastic. Kind regards, Bo Thorsen, Monty Program AB.
On Wed, Mar 3, 2010 at 6:07 PM, Sergei Golubchik <sergii@pisem.net> wrote:
ability to remove hours Somebody mentioned that a number of hours could be increased by mistake, and there should be a way to decrease is back. I'm not convinced it's a good idea, though.
Then again, it should also not be easy to accidentally remove hours :-) ...at least not without a track record. Possibly the ability to insert negative hours is an easy fix here, this way the progress report would show the audit trail of all changes to hours. henrik -- email: henrik.ingo@avoinelama.fi tel: +358-40-5697354 www: www.avoinelama.fi/~hingo book: www.openlife.cc
Monday 15 March 2010 11:49:49 Henrik Ingo wrote:
On Wed, Mar 3, 2010 at 6:07 PM, Sergei Golubchik <sergii@pisem.net> wrote:
ability to remove hours Somebody mentioned that a number of hours could be increased by mistake, and there should be a way to decrease is back. I'm not convinced it's a good idea, though.
Then again, it should also not be easy to accidentally remove hours :-)
...at least not without a track record. Possibly the ability to insert negative hours is an easy fix here, this way the progress report would show the audit trail of all changes to hours.
I like this idea, if it's this simple. It would solve the problem, and, as Henrik says, remember who did it and why. Kind regards, Bo Thorsen, Monty Program AB.
participants (6)
-
Adam M. Dutko -
Bo Thorsen -
Henrik Ingo -
Oleksandr Byelkin -
Sergei Golubchik -
Timour Katchaounov