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.kreu...@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@reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev >
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
