De : [email protected] [mailto:[email protected]] De la part de Xavier Antoviaque
Then I found this: http://wiki.creativecommons.org/CcTeamspace It's basically a very smart and creative use of Mediawiki with semantic extensions. It allows to keep track of tasks within mediawiki. The features are basic, but if it's enough for us there are three huge advantages: * It's very easy to extend and adapt (for example, we can very easily plug it into the contributions widget I did, and have certain tasks automatically appear on the home page; we can also easily display and track custom lists of bugs from any page in the wiki; we can add/remove fields; we can customize the presentation of individual tickets; etc.) * We can probably use it to create the different production workflows in a centralized way - for example, when we describe a feature on the wiki, we wouldn't need to create a separate task or a blueprint to follow its progress - the page on the wiki can be the task itself. * It doesn't require to add yet another tool : ) [David] Thx Xav. I really like the idea of using an existing tool, and the flexibility that goes with the tool. I think it’s going to be interesting if we can go for that. Now, I’ve had a look, and I’ve got a few preliminary questions before moving to the next steps : * First, about what is currently there in the tool : o I create a task, that works. But then I can’t find it anymore, in any of the tabs (dashboard, past due, open tasks, etc) of my page. I can only find it by using the email that was sent to me. And I can’t find how to destroy the task. I did not look in the right place ? o The dashboard does not seem to work : I can’t see the tasks due for the current month, and I can’t change the month that is displayed * The basic question that will help me think about the way we can track tasks : how much work would it be to have a page that lists all tasks, with possibility to filter by assignee, status, target, etc. The idea would be that anyone can add tasks, take them, and it’s easy to have a view of the current list of tasks that for instance don’t have an assignee yet. * Regarding the production pipeline (and not the follow up of tasks in general), I need to discuss with you and have a clear idea of the workflow before I can look at the needs for this tool. See the mail I sent yesterday on the topic, http://community.hackit.cx/forum/index.php?t=msg&th=3444&goto=8063&#msg_8063 , penultimate bullet point. Basically I think it will be interesting to have a page that list the features we know we will have in next builds n+1, n+2, etc. This comes from uservoice and discussions on the ml. Then each of these features is a link towards a page that lists the tasks attached to it (we can use a tag for this I guess). * This makes me think of another feature that would be very interesting, either for the generic tracking of tasks or for the production pipeline. It’s if we can attach tasks to another (father and sons). That would be useful. This way we can have on the form of the feature task the overall blueprint, and on the forms of the sons of this task the details of each task. I did not find a way to attach a task to another though in the present tool. The idea here is to reduce the number of tools by having if possible only uservoice and this mediawiki for the workflow. Thoughts welcome ! D
<<attachment: winmail.dat>>
_______________________________________________ Hackit Bar mailing list - [email protected] Wiki: http://community.hackit.cx/ List: http://community.hackit.cx/ml/ Forum: http://community.hackit.cx/forum/ Ideas: http://community.hackit.cx/ideas/ IRC: irc://irc.freenode.net/#politis
