Re: [ws-dd] Issues Tracking System now Live

[Mary McRae <mary.mcrae@oasis-open.org>]

Oh yeah. Thanks - it wouldn't let me put the dash in the group name.  
Same goes for Caps in user names. Sorry!

Mary







On Jun 10, 2009, at 4:34 PM, Toby Nixon wrote:

> Thanks very much, Mary.
>
> It appears that the URL in the email below is broken; the correct  
> URL is http://tools.oasis-open.org/issues/browse/WSDD.
>
> We'll get to work on this right away.
>
> Best regards,
>
>        -- Toby
>
> Toby Nixon  |  Senior Standards Program Manager  |  Windows Device  
> and Storage Technologies  |  Microsoft Corporation
> toby.nixon@microsoft.com  |  www.microsoft.com | V: +1 425 706 2792   
> |  M: +1 206 790 6377  |  F: +1 425 708 4811
>
>
> -----Original Message-----
> From: Mary McRae [mailto:mary.mcrae@oasis-open.org]
> Sent: Tuesday, June 09, 2009 8:23 PM
> To: ws-dd@lists.oasis-open.org
> Subject: [ws-dd] Issues Tracking System now Live
>
> The OASIS Web Services Discovery and Web Services Devices Profile (WS-
> DD) Issue Tracking Project has been created and can be accessed at:
> http://tools.oasis-open.org/issues/browse/ws-dd
>
> Each Member of the TC should have received an email with their login
> information. I have created accounts corresponding to your OASIS login
> name. Once you log in, please change your password to correspond to
> your OASIS password. (Note that uppercase letters have been changed to
> lowercase.)
>
> Below is an overview from the TC Handbook. For more information, the
> JIRA User's Guide is online here:http://www.atlassian.com/software/jira/docs/v3.13.1/introduction.html
>
> Please let me know if you encounter any problems or if something isn't
> clear. And of course I'd love to hear any suggestions you might have!
>
> Regards,
>
> Mary
>
> -----------
>
> OASIS-hosted Issues Tracking System
> OASIS has now installed a JIRA issues tracking system that will be
> made available to Technical Committees upon request. While any of the
> existing methods are still viable, Technical Committees may want to
> consider migrating their existing method to a new JIRA Project.
>
> Access
> In accordance with the OASIS Technical Committee Process Policy,
> Technical Committee Members have read/write access.  Access control is
> at the Project level. All Projects are publicly-viewable.
>
> Projects
> Each Technical Committee will be a unique Project and identified by
> Technical Committee name.
>
> Components
> Components are used to group a set of related issues. Components may
> identify Subcommittees or unique work products (that is,
> specifications or other document types) within a Technical Committee.
>
> Roles
> There are four (4) roles defined:
> TC Chair
> TC Editor
> TC Member
> Anyone
>
> Workflows
> There is currently only one workflow available: Technical Committee
> Issues. Additional workflows can be created based on Technical
> Committee requirements.
> New - When an issue is created it is automatically assigned a status
> of New. A New issue has not yet been accepted by the Technical
> Committee. A new issue may either be accepted (Open Issue) or rejected
> (Close Issue) by the TC. Once an issue has been entered, the system
> will automatically send an e-mail to the TC list with the URI.
> Open - An issue accepted by the Technical Committee. Actual discussion
> of the issue takes place on the TC e-mail list and should include the
> URI to the actual issue.
> Deferred - An issue accepted by the Technical Committee, but agreed
> that its resolution will be not be included in the current version.
> Resolved - An issue with an agreed-upon resolution that requires a
> change to the work product.
> Applied - An issue to which the agreed-upon resolution has been
> incorporated into a draft work product.
> Closed - An issue that has either been rejected or resolved and
> incorporated into a Committee-approved work product.
>
> All discussion on issues should happen on the Technical Committee's e-
> mail list and in TC meetings. As much detail as possible should be
> included when a new issue is opened. Additionally, the issue should
> note:
> -          resolution, if accepted
> -          reason for closing (completed, duplicate, rejected, etc.)
>
>
> NOTE: The issues tracking system is not tied into the OASIS groupware
> (KAVI) authentication. Permissions must be managed manually.
>
>
>
> Mary P McRae
> Director, Standards Development
> Technical Committee Administrator
> OASIS: Advancing open standards for the information society
> email: mary.mcrae@oasis-open.org
> web: www.oasis-open.org
> twitter: fiberartisan  #oasisopen
> phone: 1.603.232.9090
>
> Standards are like parachutes: they work best when they're open.
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>