[Action] supported software (Re: [Action] Software to support the validation process)

Hi,

As per my action item, W3C Systems Team maintains a version of the 
MoinMoin Wiki software:
* <http://moinmoin.wikiwikiweb.de/>

As far as I know it supports e-mail notifications as Christophe outlined 
below. The W3C-wide public instance also has some information about 
other issue tracking systems used in different Working Groups:
* <http://esw.w3.org/topic/TrackingIssues>

Note: most of these tools are not supported by the Systems Team and we 
would be on our own to install and configure.

Regards,
   Shadi


cstrobbe wrote:
> Hi,
> 
> Quoting Carlos A Velasco <Carlos.Velasco@fit.fraunhofer.de>:
>> 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).
> 
> One argument that was raised in favour of a bug tracking system and 
> against a wiki, was that a bug tracking system like JIRA can send an e-
> mail to the submitter of the test sample (and probably also to other 
> interested parties, if my understanding is correct) when the bug 
> changes. However, it appears that there is similar functionality in 
> some wiki software: wikis always have a "history" or "recent changes" 
> page, and this page can have an Atom or RSS feed, so anyone who's 
> interested can be notified of changes.
> Examples:
> * the css-discuss wiki: http://css-discuss.incutio.com/?page=FrontPage 
> (go to "RecentChanges" and select the link "[RSS feed]");
> * Wikimedia meta wiki: http://meta.wikimedia.org/wiki/Main_Page (go to 
> "Recent changes" and then select either "RSS" or "atom" in the 
> "toolbox");
> * SWiK wiki: http://swik.net/SWiK (go to "Recent Edits", then 
> "Subscribe"; this feed is not so useful, unfortunately).
> 
> So if we have a Wiki with 
> * an overview page (list of test samples, assigned to whom, ...), and
> * one page per test case or test sample (with a "recent changes" feed),
> I think that can also work.
> 
> I admit that I'm prejudiced against issue tracking systems because of 
> my experience with Bugzilla (just finding stuff in it, let alone 
> changing things ... ).
> 
> 
>> - 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.
> 
> Best regards,
> 
> Christophe
> 

-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe |
Chair & Staff Contact for the Evaluation and Repair Tools WG |
World Wide Web Consortium (W3C)           http://www.w3.org/ |
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ |
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ |
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ |
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France |
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 |

Received on Friday, 8 December 2006 11:29:55 UTC