Hi folks,
We're trying to make status.l.o more useful to engineers and the first thing we're planning to do is a new page listing the upcoming work assigned to a given person. I'm attaching a mockup of that view here and we'd like to know what you think of it... Do you think that would be useful to you? Is there any other information you'd like to see there, or maybe a different way to present/group them?
Cheers,
Hey,
On Wed, Feb 1, 2012 at 1:54 PM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi folks,
We're trying to make status.l.o more useful to engineers and the first thing we're planning to do is a new page listing the upcoming work assigned to a given person. I'm attaching a mockup of that view here and we'd like to know what you think of it... Do you think that would be useful to you? Is there any other information you'd like to see there, or maybe a different way to present/group them?
Awesome, that looks a lot better from what we have now, and easier to read.
Just a few questions and comments: 1 - Are we tracking bugs that are not assigned to a milestone? 2 - What will happen when the cycle is finished, but there are still WIs to be done? 3 - While I see that is useful to see what was already done for a cycle, for me I believe this view should behave similarly as a TODO list, that once something is done, it's either removed from the view, or changed in a way it'll not get much attention as the ones that are still to be done. 4 - Do you know if a similar page, but for a team, will also be available?
Thanks
On Thu, Feb 2, 2012 at 4:24 AM, Ricardo Salveti ricardo.salveti@linaro.org wrote:
Hey,
On Wed, Feb 1, 2012 at 1:54 PM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi folks,
We're trying to make status.l.o more useful to engineers and the first thing we're planning to do is a new page listing the upcoming work assigned to a given person. I'm attaching a mockup of that view here and we'd like to know what you think of it... Do you think that would be useful to you? Is there any other information you'd like to see there, or maybe a different way to present/group them?
Awesome, that looks a lot better from what we have now, and easier to read.
Just a few questions and comments: 1 - Are we tracking bugs that are not assigned to a milestone?
The engineer's view shows upcoming work by showing the most urgent work on top, that is by nearest deadline (unless something is blocked). It would be tricky to determine when that work is due if a bug is not targeted to a milestone. Perhaps all bugs assigned to this person, but not targeted to a milestone should be listed by themselves somewhere further down the page?
2 - What will happen when the cycle is finished, but there are still WIs to be done?
Our PM usually kindly reminds me about those WIs and I get the option to complete them or split them off to a new blueprint for next cycle. Moving the entire blueprint to the next milestone would probably be ok too. So work items that are not done or postponed should not get stuck on a blueprint for a finished cycle, right?
3 - While I see that is useful to see what was already done for a cycle, for me I believe this view should behave similarly as a TODO list, that once something is done, it's either removed from the view, or changed in a way it'll not get much attention as the ones that are still to be done. 4 - Do you know if a similar page, but for a team, will also be available?
There will be. Guilherme has circulated a mockup for that too, on the techleads list.
Thanks
Ricardo Salveti de Araujo
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Hi Ricardo,
On 02/02/12 05:28, Mattias Backman wrote:
On Thu, Feb 2, 2012 at 4:24 AM, Ricardo Salveti ricardo.salveti@linaro.org wrote:
Hey,
On Wed, Feb 1, 2012 at 1:54 PM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi folks,
We're trying to make status.l.o more useful to engineers and the first thing we're planning to do is a new page listing the upcoming work assigned to a given person. I'm attaching a mockup of that view here and we'd like to know what you think of it... Do you think that would be useful to you? Is there any other information you'd like to see there, or maybe a different way to present/group them?
Awesome, that looks a lot better from what we have now, and easier to read.
Just a few questions and comments: 1 - Are we tracking bugs that are not assigned to a milestone?
The engineer's view shows upcoming work by showing the most urgent work on top, that is by nearest deadline (unless something is blocked). It would be tricky to determine when that work is due if a bug is not targeted to a milestone. Perhaps all bugs assigned to this person, but not targeted to a milestone should be listed by themselves somewhere further down the page?
2 - What will happen when the cycle is finished, but there are still WIs to be done?
Our PM usually kindly reminds me about those WIs and I get the option to complete them or split them off to a new blueprint for next cycle. Moving the entire blueprint to the next milestone would probably be ok too. So work items that are not done or postponed should not get stuck on a blueprint for a finished cycle, right?
3 - While I see that is useful to see what was already done for a cycle, for me I believe this view should behave similarly as a TODO list, that once something is done, it's either removed from the view, or changed in a way it'll not get much attention as the ones that are still to be done.
That's a good point, and one thing we're already doing to address that is to initially expand only the BPs that have TODO/INPROGRESS/BLOCKED work-items assigned to that person. However, if a BP has one TODO item and 10 DONE, it will be expanded and those DONE items will unnecessarily clutter the table. We could replace them all with a dummy row saying "10 more work items DONE in this BP" or something to that effect. If we do that we might not be able to allow its expansion to see all the DONE WIs, though.
Cheers,
On 2 February 2012 08:28, Mattias Backman mattias.backman@linaro.org wrote:
On Thu, Feb 2, 2012 at 4:24 AM, Ricardo Salveti ricardo.salveti@linaro.org wrote:
4 - Do you know if a similar page, but for a team, will also be available?
There will be. Guilherme has circulated a mockup for that too, on the techleads list.
Is there going to be a way of viewing project-level todo stuff? I'm thinking about (a) "show me all the QEMU related things" (just-me-personally is too narrow, and whole-toolchain-group is too wide), and (b) KVM work, which is likely to span multiple cards, working groups, blueprints and engineers.
Feel free to say "that's an uncommon use case and we're going to ignore it" :-)
-- PMM
On 02/02/12 12:28, Peter Maydell wrote:
On 2 February 2012 08:28, Mattias Backman mattias.backman@linaro.org wrote:
On Thu, Feb 2, 2012 at 4:24 AM, Ricardo Salveti ricardo.salveti@linaro.org wrote:
4 - Do you know if a similar page, but for a team, will also be available?
There will be. Guilherme has circulated a mockup for that too, on the techleads list.
Is there going to be a way of viewing project-level todo stuff? I'm thinking about (a) "show me all the QEMU related things" (just-me-personally is too narrow, and whole-toolchain-group is too wide), and (b) KVM work, which is likely to span multiple cards, working groups, blueprints and engineers.
We don't have any plans for that as the time we have to work on this stuff is barely enough for the person/team pages. However, we've already started teaching Launchpad about Blueprint work-items and once that's done it'd be straightforward to extend a page like https://launchpad.net/qemu-linaro/+milestone/2012.02 to show the progress based on the state of work-items.
Feel free to say "that's an uncommon use case and we're going to ignore it" :-)
I'm sure it's a common use case and there are more people who would appreciate to have a view like that in LP.
On Wed, Feb 01, 2012 at 12:54:29PM -0300, Guilherme Salgado wrote:
We're trying to make status.l.o more useful to engineers and the first thing we're planning to do is a new page listing the upcoming work assigned to a given person. I'm attaching a mockup of that view here and we'd like to know what you think of it... Do you think that would be useful to you? Is there any other information you'd like to see there, or maybe a different way to present/group them?
Crazy idea to expand on: why not merge the p.l.o patch queues into the status.linaro.org view?
On Fri, Feb 3, 2012 at 11:32 AM, Christian Robottom Reis kiko@linaro.org wrote:
On Wed, Feb 01, 2012 at 12:54:29PM -0300, Guilherme Salgado wrote:
We're trying to make status.l.o more useful to engineers and the first thing we're planning to do is a new page listing the upcoming work assigned to a given person. I'm attaching a mockup of that view here and we'd like to know what you think of it... Do you think that would be useful to you? Is there any other information you'd like to see there, or maybe a different way to present/group them?
Crazy idea to expand on: why not merge the p.l.o patch queues into the status.linaro.org view?
Indeed an interesting idea. Let's add this to our status topics to be discussed at connect!
-
Alexander Sack -
Christian Robottom Reis -
Guilherme Salgado -
Mattias Backman -
Peter Maydell -
Ricardo Salveti