RE: [oic] Observations on the TC use of CMIS

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

Hi everyone,

  I'm not sure if I was asked to chime in and missed it, but I'm chiming in
anyway ;-) I think I can add a bit more data to Dennis' observations. There
are about 10 TCs currently using JIRA - the first seven have been using JIRA
for at least a couple of years. These are the OpenCSA TCs. When they first
came to OASIS they asked us to provide a JIRA installation which we were
unable to do and instead authorized their continued use of the system at
osoa.org. They adhere to a set of rules I established to ensure that OASIS
Policies were not violated. There are hundreds of issues, and a
well-documented process in place.
http://www.osoa.org/jira/secure/BrowseProjects.jspa

The attached powerpoint shows the flow in use by the SCA TCs.

You will see that some TCs have a single spec, while others have several.
The "project" is for the TC - each TC has only one. Each spec should be a
"component" - this allows for managing them independently. The current
workflow is devised for issues; a second workflow is under development for
requirements.

Regards,

Mary


> -----Original Message-----
> From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org]
> Sent: Tuesday, January 13, 2009 7:19 PM
> To: oic@lists.oasis-open.org
> Cc: ODF TC List
> Subject: [oic] Observations on the TC use of CMIS
> 
> This note fulfills my promise to report on the CMIS TC use of JIRA to
> the
> OIC TC.  Because the ODF TC is also interested in using JIRA for issue
> tracking, I am including that list in this report as well.
> 
> 1. ACCESS TO JIRA
> 
> The JIRA system is organized by TC for those groups that have been set
> up.
> 
> The Content-Management Interoperability Services (CMIS) TC piloted the
> use
> of JIRA.  The current JIRA has 30/31 issues and the entry page is at
> <http://tools.oasis-open.org/issues/browse/CMIS>.
> 
> The new OpenDocument Interoperability and Conformance (OIC) TC one is
> at
> <http://tools.oasis-open.org/issues/browse/OIC>.
> 
> When there is one for the ODF TC, I expect it will be at
> <http://tools.oasis-open.org/issues/browse/office>.
> 
> These JIRA repositories are public, although only members of the
> individual
> TCs can create and manipulate entries.
> 
> You can find out more about Atlasian JIRA at
> <http://www.atlassian.com/software/jira/>.  JIRA supports import-export
> of
> various kinds.  To run a personal version of JIRA, there is a personal
> license available:
> <http://www.atlassian.com/software/jira/personal.jsp>.
> It is a Java, server-based product and the installation requirements
> need to
> be understood
> <http://www.atlassian.com/software/jira/docs/latest/requirements.html>
> for
> all versions.  The only difference in the personal version is the
> license
> that is used to activate one of the production trial downloads.
> 
> 2. PREPARING TO USE JIRA
> 
> Although the CMIS TC has been slowly accumulating issues, they are not
> being
> managed at the moment.  You can still see the capabilities of the
> support
> for individual issues, comments and discussion, and issue status, by
> exploring the CMIS JIRA repository.
> 
> You can see there is a nice form for the description of an issue and
> for
> comments on it, change tracking, etc.  The URL for an issue by its
> number is
> also handy (e.g., <http://tools.oasis-open.org/issues/browse/CMIS-19>).
> 
> You can also see that issues on CMIS, at the moment, are rather broad.
> That
> will change, I expect.
> 
> One reason that the CMIS JIRA is not heavily used just yet is that it
> has
> been felt that there needs to be an agreed process on how issues will
> be
> managed through to resolution.  (Some built-in structure for that is
> shown
> in Mary's note, below).
> 
> CMIS will be nailing down its process for managing issues and how they
> advance to approved resolution this month at a Face-to-Face meeting.
> 
> The CMIS issue-resolution process will be an interesting one to review.
> It
> may be relatively close to the ODF TC standing rules, but with JIRA the
> vehicle for tracking everything.  The OIC TC also needs to define its
> issue-resolution process, and the ODF TC standing rules (customized
> around
> use of JIRA) would be a good point of departure.
> 
> 3. RECOMMENDATION
> 
> One concern I have for using a system of this kind has to do with the
> mingling of issues of different kinds in one large pot.  Also, it
> should be
> understood that proposals probably don't work with this the sole
> mechanism.
> The processing of a proposal can be handled, but the development and
> tracking of a proposal needs something more.
> 
> Since this resource is now available to OASIS TCs, I think it would be
> useful to add it in as a resource.  But its management support is not
> magical.  There must be some process to manage issues and have forward
> progress on resolution.  With that, the great advantage is that issues
> don't
> fall on the floor or become lost from view.  They are always recorded
> in
> JIRA.
> 
>  - Dennis
> 
> -----Original Message-----
> From: Mary McRae [mailto:marypmcrae@gmail.com] On Behalf Of Mary McRae
> Sent: Monday, January 05, 2009 17:53
> To: oic@lists.oasis-open.org
> Subject: [oic] Issue Tracking System for OIC
> 
> The OIC Issue Tracking Project has been created and can be accessed at:
> 
> http://tools.oasis-open.org/issues/browse/OIC
> 
> 
> 
> Each Member of the TC should be receiving an email with their login
> information. I am creating accounts corresponding to your OASIS login
> name.
> Once you log in, please change your password to correspond to your
> OASIS
> password.
> 
> I am in the process of setting everyone's privileges.
> 
> 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
> 
> 
> You are the first TC to be assigned a Project in this new system.
> 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!
> 
> [ ... ]
> 
> 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, an email will automatically be sent
> to
> the TC list.
> 
> 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.)
> 
> 
> 
>  Requesting a Project
> 
> To request a Project, the Chair should send an e-mail to the OASIS TC
> Administrator and identify the name(s) of any Issues Editor(s).
> 
> 
> 
> NOTE: The issues tracking system is not tied into the OASIS groupware
> (KAVI)
> authentication. Permissions must be managed manually.
> 
> 
> 
> 
> 
> 
> 
> ___________________________________________________________
> 
> Mary P McRae
> 
> Director, Technical Committee Administration
> 
> OASIS: Advancing open standards for the information society
> 
> email: mary.mcrae@oasis-open.org
> 
> web: www.oasis-open.org <http://www.oasis-open.org/>
> 
> phone: 1.603.232.9090
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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

SCA TC Proposed Issues Processv3.ppt