W3C home > Mailing lists > Public > www-qa-wg@w3.org > December 2001

Re: SourceForge and issues tracking

From: Dimitris Dimitriadis <dimitris@ontologicon.com>
Date: Thu, 20 Dec 2001 19:25:51 +0100
Cc: "Lofton Henderson" <lofton@rockynet.com>, www-qa-wg@w3.org
To: Rob Lanphier <robla@real.com>
Message-Id: <FF1087D1-F576-11D5-B347-000393556882@ontologicon.com>
Hi Rob

We actually have no issues at present, that's why it's empty. We have no 
issues primarily because the tests needed to e converted into our DOM TS 
ML only, not discussed that much further.


On Wednesday, December 19, 2001, at 11:28 PM, Rob Lanphier wrote:

> I don't see any issues in this bug tracker?  Is that just because you 
> are getting started?
> If you'd like to look at an example of a project actively using 
> SourceForge for specification writing, look at the RTSP spec:
> http://sourceforge.net/tracker/?atid=377744&group_id=23194&func=browse
> We've just started using it pretty heavily, and it's been very nice.
> However, as I brought up at the face-to-face, the W3C staff is 
> beta-testing something very similar to this.  It seems as though this 
> group should be the beta testers for that system, seeing as how this 
> group will need to recommend said system to other groups.
> Rob
> At 12:01 AM 12/20/01 +0100, Dimitris Dimitriadis wrote:
>> To begin with, let me give the correct pointer to the actual DOM TS 
>> project at sourceforge: http://sourceforge.net/projects/domconftest/
>> comments inlined
>> Kind regards,
>> /Dimitris
>> On Wednesday, December 19, 2001, at 02:58 PM, Lofton Henderson wrote:
>>> Hi Dimitris,
>>> Dimitris, I have been looking at SourceForge, per your pointer for 
>>> the issues-tracking topic.  I don't exactly know my way around yet.  
>>> But a search on "issue tracking" turns up about a dozen hits.  Is one 
>>> of these the tool/project you use for DOM?
>>> I was looking at the DOM issues tables on 
>>> http://www.w3.org/2001/12/DOM-Level-2-issues, which I assume are the 
>>> result of the SourceForge tool.  Two thoughts:
>>> 1) It seems to cover all of the issue-tracking information items and 
>>> clear presentation that we would need;
>>> 2) "Contingency" issue (if the tool became unavailable) -- most of 
>>> the stuff (perhaps all) in your HTML tables could be pretty 
>>> transformed pretty easily and automatically w/ XSLT into a simple XML 
>>> "issue information" grammar such as Kirill and I were thinking about 
>>> (the intermediate step to XHTML looks pretty trivial, probably 
>>> wouldn't even need 'Tidy').
>> [dd] Actually, given that we don't use the sourceforge project for 
>> issue tracking for the DOM in general, but only for the DOM TS (which 
>> is something I should have pointed out, sorry for forgetting), I'll 
>> try to relate my answer to DOM TS specific things: we've thought along 
>> the lines of generating a simple intermediary format for quick 
>> browsing of issues (we thought of posting this on the .../DOM/Test 
>> pages), like the one you and Kirill proposed. However, I haven't 
>> managed to find out what formats sourceforge as such supports. It's an 
>> action item on me, and unfortunately it's stil pending. (I'll try to 
>> resolve this until tomorrow's telcon).
>>> Thanks,
>>> -Lofton.
>>> [1] http://www.SourceForge.net
Received on Thursday, 20 December 2001 12:36:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:25 UTC