Re: [tag] Starting an issues list?

[Stephen Green <stephen.green@documentengineeringservices.com>]

Excellent. I think we do, as an OASIS TC, have the availability
of a TAG TC Jira account which can be set up by OASIS TC Admin.

There is also a TC Admin Jira account which we can use to monitor
the progress of the submissions through their processing to public
review (if we vote for public review of course).

Best regards

Steve
---
Stephen D Green




On 4 February 2010 16:04, Kevin Looney <Kevin.T.Looney@sun.com> wrote:
> On 2/4/10 7:23 AM, Stephen Green wrote:
>>
>> Dear TAG TC,
>>
>> I guess we will need an issues list. Any progress/thoughts
>> about having and using a Jira account?
>
> Stephen,
>
> We were recently looking at hosting our Open Source projects on a Sun site
> called "Kenai", which was using Jira as the defect reporting system.   We
> found Jira to be better than our other Open Source alternatives (such as
> IssueTracker).  I think Jira would work well for TAG.
>>
>> I'm not sure how our TC comments will need to be separated
>> from external/public comments. I will have a few comments
>> of my own on how things might be improved after public review.
>> After this month I may have to submit comments via the
>> public comments list. Are we supposed to keep TC comments
>> separate and try to make such comments before the review
>> rather than during it?
>
> I think you can define keywords (called 'tags' in Jira speak) and attach
> them to bugs/tasks/new-feature/improvements.  This is probably the best way
> to do this.  You can filter reports based on these things.
>
> Regards,
> Kevin
>>
>> My comment for now is that I think there would be special
>> benefit in having the schema itself reviewed. I passed it
>> through the W3C online schema validator and found I got
>> a few warnings because there are places where simpleContent
>> is specified as having mixed content (mixed content when
>> there are no child elements, I think that means). Some
>> review of this and any other related schema design features
>> might be warranted and might require minor changes to the
>> model as well as the schema (but these should not, I hope,
>> affect XML instances).
>>
>> Best regards
>>
>> Steve
>> ---
>> Stephen D Green
>>
>
>