Action list

[Olaf Siejka]

Dear colleagues

We need to some short-term planning within our project, as the amount of
tasks awaiting will simply turn into chaos. I propose a list to be kept,
named "Action list". It should list our goals, things to be done, for
example Winesync, fixing some particular bug, etc. Every task should be
assigned to particular person, who would choose to be responsible for
getting it done. It doesn't need to be the only person working on this, but
rather someone making sure its done and not forgotten. Other variable
assigned to task would be a deadline - approximate one, susceptible to
extension when necessary. Goals are removed from the list when completed.

Action list should be reviewed at every meeting, by querying people
responsible for every task, being asked for an update.

I can keep such list.

Awaiting proposals for tasks if you think this makes sense.

Regards

[Aleksey Bragin]

That’s what I wanted and tried to do quite a few times, but people were too lazy to keep
such list fresh. I would be very glad, and am going to fully support it if you are going
to maintain that list.

Long term planning is much harder, so let’s start (Nth time) from the shortest possible
one.

WBR,
Aleksey Bragin.

From: Olaf Siejka 
Sent: Tuesday, April 26, 2011 12:35 AM
To: ReactOS Development List 
Subject: [ros-dev] Action list

Dear colleagues


We need to some short-term planning within our project, as the amount of tasks awaiting
will simply turn into chaos. I propose a list to be kept, named "Action list".
It should list our goals, things to be done, for example Winesync, fixing some particular
bug, etc. Every task should be assigned to particular person, who would choose to be
responsible for getting it done. It doesn't need to be the only person working on
this, but rather someone making sure its done and not forgotten. Other variable assigned
to task would be a deadline - approximate one, susceptible to extension when necessary.
Goals are removed from the list when completed.

Action list should be reviewed at every meeting, by querying people responsible for every
task, being asked for an update.

I can keep such list.

Awaiting proposals for tasks if you think this makes sense.

Regards



--------------------------------------------------------------------------------
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[victor martinez]

I am fully agree with your idea :)
Even more, we can not forget Testing Tasks neither and non-related coding tasks as the
mythical Website Revamp (among others).
I'd add one more Task called "Full GoldenApps/CandidateApps testing after LDR
rewrite", I offer myself to try to coordinate this testing with Forum Users and
Regular Testers.
Any other tasks /ideas?

Regards

Date: Mon, 25 Apr 2011 22:35:28 +0200
From: caemyr(a)gmail.com
To: ros-dev(a)reactos.org
Subject: [ros-dev] Action list

Dear colleagues

We need to some short-term planning within our project, as the amount of tasks awaiting
will simply turn into chaos. I propose a list to be kept, named "Action list".
It should list our goals, things to be done, for example Winesync, fixing some particular
bug, etc. Every task should be assigned to particular person, who would choose to be
responsible for getting it done. It doesn't need to be the only person working on
this, but rather someone making sure its done and not forgotten. Other variable assigned
to task would be a deadline - approximate one, susceptible to extension when necessary.
Goals are removed from the list when completed.

Action list should be reviewed at every meeting, by querying people responsible for every
task, being asked for an update.
I can keep such list.
Awaiting proposals for tasks if you think this makes sense.

Regards


_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[Timo Kreuzer]

It would be cool to have some kind of interface for our website.
What I'm imagining is, that every developer has a list of "workitems" he 
can define. A Workitem consists of a short name, an optional desription, 
optional notes, possibly something like percentage done, estimated time. 
A bug can also be a workitem. You can enqueue multiple workitems, that 
is the stuff you plan to work on in the future. You can mark one or two 
items as active, these are what you are currently working on.
People can also push workitems to other people. For example someone 
starts to find a bug, then he notices that the bug is not in his area of 
expertise. So after talking to another dev, he pushes that item to him, 
so the other dev can handle it.
There could be a global list that shows all items, who owns them and if 
they are active.
Bugs from bugzilla can also be pushed to devs. every dev should have 
only one bug at a time to avoid having huge lists of stuff that doesn't 
look like fun.
The interface should be easy to use, not require much work to maintain 
it and still flexible enough for advanced stuff.
Whenever something happens in the list, it could appear on a feed on the 
front page

Ok, that was all just ideas. Maybe one day we can have something like 
that :)

[Olaf Siejka]

Such task or workitem should have then at least three parameters: deadline,
person responsible and dependencies. We can easily think of an example of a
given task, depending on another, just like Winesync is currently depending
on finishing LDR rewrite.

2011/4/26 Timo Kreuzer <timo.kreuzer(a)web.de>

>  
>  It would be cool to have some kind of interface for our website.
>  What I'm imagining is, that every developer has a list of "workitems" he
>  can define. A Workitem consists of a short name, an optional desription,
>  optional notes, possibly something like percentage done, estimated time. A
>  bug can also be a workitem. You can enqueue multiple workitems, that is the
>  stuff you plan to work on in the future. You can mark one or two items as
>  active, these are what you are currently working on.
>  People can also push workitems to other people. For example someone starts
>  to find a bug, then he notices that the bug is not in his area of expertise.
>  So after talking to another dev, he pushes that item to him, so the other
>  dev can handle it.
>  There could be a global list that shows all items, who owns them and if
>  they are active.
>  Bugs from bugzilla can also be pushed to devs. every dev should have only
>  one bug at a time to avoid having huge lists of stuff that doesn't look like
>  fun.
>  The interface should be easy to use, not require much work to maintain it
>  and still flexible enough for advanced stuff.
>  Whenever something happens in the list, it could appear on a feed on the
>  front page
>
>  Ok, that was all just ideas. Maybe one day we can have something like that
>  :)
>
>
>
>  _______________________________________________
>
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Javier Agustìn Fernàndez Arroyo]

hmm... i dont really like deadlines.... but still, it might be a good
idea...

---------- Forwarded message ----------
From: Olaf Siejka <caemyr(a)gmail.com>
Date: Tue, Apr 26, 2011 at 9:11 PM
Subject: Re: [ros-dev] Action list
To: ReactOS Development List <ros-dev(a)reactos.org>


Such task or workitem should have then at least three parameters: deadline,
person responsible and dependencies. We can easily think of an example of a
given task, depending on another, just like Winesync is currently depending
on finishing LDR rewrite.


2011/4/26 Timo Kreuzer <timo.kreuzer(a)web.de>

>  
>  It would be cool to have some kind of interface for our website.
>  What I'm imagining is, that every developer has a list of "workitems" he
>  can define. A Workitem consists of a short name, an optional desription,
>  optional notes, possibly something like percentage done, estimated time. A
>  bug can also be a workitem. You can enqueue multiple workitems, that is the
>  stuff you plan to work on in the future. You can mark one or two items as
>  active, these are what you are currently working on.
>  People can also push workitems to other people. For example someone starts
>  to find a bug, then he notices that the bug is not in his area of expertise.
>  So after talking to another dev, he pushes that item to him, so the other
>  dev can handle it.
>  There could be a global list that shows all items, who owns them and if
>  they are active.
>  Bugs from bugzilla can also be pushed to devs. every dev should have only
>  one bug at a time to avoid having huge lists of stuff that doesn't look like
>  fun.
>  The interface should be easy to use, not require much work to maintain it
>  and still flexible enough for advanced stuff.
>  Whenever something happens in the list, it could appear on a feed on the
>  front page
>
>  Ok, that was all just ideas. Maybe one day we can have something like that
>  :)
>
>
>
>  _______________________________________________
>
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  

_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[Olaf Siejka]

Perhaps the deadline term is bit too strict. Some kind of time scale/limit
is required

2011/4/26 Javier Agustìn Fernàndez Arroyo <elhoir(a)gmail.com>

>   hmm... i dont really like deadlines.... but still, it
> might be a good
>  idea...
>
>
>  ---------- Forwarded message ----------
>  From: Olaf Siejka <caemyr(a)gmail.com>
>  Date: Tue, Apr 26, 2011 at 9:11 PM
>  Subject: Re: [ros-dev] Action list
>  To: ReactOS Development List <ros-dev(a)reactos.org>
>
>
>  Such task or workitem should have then at least three parameters: deadline,
>  person responsible and dependencies. We can easily think of an example of a
>  given task, depending on another, just like Winesync is currently depending
>  on finishing LDR rewrite.
>
>
>  2011/4/26 Timo Kreuzer <timo.kreuzer(a)web.de>
>
> >  
> >  It would be cool to have some kind of interface for our website.
> >  What I'm imagining is, that every developer has a list of "workitems" he
> >  can define. A Workitem consists of a short name, an optional desription,
> >  optional notes, possibly something like percentage done, estimated time. A
> >  bug can also be a workitem. You can enqueue multiple workitems, that is the
> >  stuff you plan to work on in the future. You can mark one or two items as
> >  active, these are what you are currently working on.
> >  People can also push workitems to other people. For example someone starts
> >  to find a bug, then he notices that the bug is not in his area of expertise.
> >  So after talking to another dev, he pushes that item to him, so the other
> >  dev can handle it.
> >  There could be a global list that shows all items, who owns them and if
> >  they are active.
> >  Bugs from bugzilla can also be pushed to devs. every dev should have only
> >  one bug at a time to avoid having huge lists of stuff that doesn't look like
> >  fun.
> >  The interface should be easy to use, not require much work to maintain it
> >  and still flexible enough for advanced stuff.
> >  Whenever something happens in the list, it could appear on a feed on the
> >  front page
> >
> >  Ok, that was all just ideas. Maybe one day we can have something like that
> >  :)
> >
> >
> >
> >  _______________________________________________
> >
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >  
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>