- From: Evangelos Vlachogiannis <evlach@aegean.gr>
- Date: Thu, 07 Dec 2006 16:03:46 +0200
- To: public-wai-ert-tsdtf@w3.org
Hi all, IMO I find wiki appropriate for more document-oriented processes, that is not our case here. On the other hand, I think that a bug tracking system offers a more structured / clear way for people to contribute in situations like the one of this task force. I also don't think that we can afford the overhead of installing and maintaining Jira (which I really like). Having also in mind that Jira offers a "Bugzilla to Jira" migration mechanism my vote goes to Bugzilla. regards, Vangelis Carlos A Velasco wrote: > Hi all, > > In the last call, we discussed three different software possibilities > (actually lying under two categories: Wikis and issue tracking systems) > to support the whole validation process of the test samples generated by > the task force, or sent by third parties, namely: Wiki (whichever > software supported by W3C system's people), Bugzilla > <http://www.bugzilla.org/> (also supported by W3C) and JIRA > <http://www.atlassian.com/software/jira/>. > > The software must support the assignment of validators, the highlighting > of issues and validation errors, communication with the author, etc. > > - Wikis have the advantage, that have a simpler interface for users, but > they will be have a bigger load to manage and monitor results and > progress (sorry, my personal bias, although I know I should be neutral). > > - Bugzilla has a not so-friendly UI, and there are not too many > possibilities to customise it. Good news is that W3C system's people > will provide some level of support (TBD). > > - JIRA seems the most customisable and user friendly option (IMHO), at > least to monitor and manage. The bad news is that we will be on our own, > from the installation to the backup. > > Thus, the question is now which option you think is suitable, to select > it as soon as possible. > > regards, > carlos > >
Received on Thursday, 7 December 2006 14:04:08 UTC