Re: [ros-dev] Action list

[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