RE: [opencsa-liaison] FW: [chairs] OASIS Issues Tracker

+1

 

From: Mike Edwards
[mailto:] 

Sent: 03 November 2009 02:07

To: OASIS Liaison

Subject: Re: [opencsa-liaison] FW: [chairs] OASIS Issues Tracker

 

Sanjay, 

In my view, the
OASIS TCs made a decision at the time that the OASIS JIRA system first became
available, that 

they would
stick with using the OSOA JIRA system simply because the effort of moving to
the new JIRA system 

was too great.
  

I am not aware
that anything has changed since this original decision - with the continual
increase in the number of 

issues, the
work effort of a move has only increased. 

I am not aware
of any problems that are caused by using the OSOA JIRA, which seems to work
well for all TCs. 

If there are
any contrary views, it would be good to hear them. 

PS If we were
starting a new SCA TC now, then I think that it would naturally use the OASIS
JIRA system. 

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:   

 

  
  
From: 

  
  
  
"Patil,
  Sanjay" <> 

  
 

 

  
  
To: 

  
  
  
"OASIS
  Liaison" <> 

  
 

 

  
  
Date: 

  
  
  
02/11/2009
  20:01 

  
 

 

  
  
Subject: 

  
  
  
[opencsa-liaison]
  FW: [chairs] OASIS Issues Tracker

  
 

 

I think the following email does not concern the OpenCSA TCs because we

(the OpenCSA TCs) decided to continue with the OSOA provided JIRA system

for issues management. Just making sure if anybody has a different view.

Sanjay

-----Original Message-----

From: Mary McRae [mailto:] 

Sent: Saturday, Oct 31, 2009 10:50 AM

To: 

Subject: [chairs] OASIS Issues Tracker

Hi everyone,

  You may remember that about this time last year we rolled out a
 

JIRA Issues Tracking system for use by OASIS TCs. For each TC that  

requests it, a JIRA project is created for use by the TC and its  

subcommittees. The one catch is that this system is not integrated in
 

our Kavi authentication system (unlike the wiki and SVN projects) and
 

therefore logins/passwords must be maintained manually. Due to  

numerous time constraints, new projects have not been rolled out in  

quite some time.

  Sabine has taken over the roster management for JIRA projects - for
 

those of you that have a JIRA project already set up, the roll of  

project members should now correspond to your TC roster. Of course  

rosters are continually changing as new members join and others leave;
 

Sabine will be updating the rosters on a monthly basis.

  If your TC does not yet have a JIRA project and would like to  

request one, please send me an email and we'll do our best to get  

these added over the next month. If you have no idea whether your TC  

would actually use it or not, please first take the time to review the
 

existing projects and talk it over with your TC. It's quite a bit of  

work to set up the accounts and roles.

http://tools.oasis-open.org/issues/

Regards,

Mary

Mary P McRae

Director, Standards Development

Technical Committee Administrator

OASIS: Advancing open standards for the information society

email: 

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 

 

Unless
stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU