RE: [bpel4people] JIRA Accounts

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

Hi Dave,

  Since the accounts need to be tied to the specific JIRA workspace, until
permission is given to create such a workspace I'm not sure how this would help.
Additionally, we need to get the editor subcommittee set up - I need a request
from you with a link to the meeting minutes where creation of the subcommittee
was approved (I know, I was there, but it's a formality) along with the name of
someone to be identified as "chair." Once that group is set up, the editors can
join the subcommittee. If a restricted list is to be created, it must match that
subgroup's roster.

  Sorry for the procedural hassle, but you can imagine how this could go south
very quickly if the osoa group decided not to grant the assurances after all.

Regards,

Mary

> -----Original Message-----
> From: Dave Ings [mailto:ings@ca.ibm.com]
> Sent: Wednesday, March 19, 2008 2:10 PM
> To: mary.mcrae@oasis-open.org
> Cc: bpel4people@lists.oasis-open.org
> Subject: RE: [bpel4people] JIRA Accounts
> 
> Hi Mary,
> 
> In today's TC (which I believe you did not attend) I discussed that OSOA
> anticipates sending the required letter (assurances) to OASIS "real soon
> now" :-) as all OSOA companies have agreed to provide the required
> assurances. I also discussed that until this topic is closed with OASIS, we
> aren't able to use JIRA for TC business, but that our goal is to have this
> closed by next TC meeting.
> 
> I would split hairs with you on one point :-) while the TC can't use JIRA,
> as you observe, nothing I am aware of prevents us working the
> administrative side in parallel.. :-) Please correct me if you believe
> differently.
> 
> BTW we actually voted last week to create an editing subcommittee, based on
> Martin's recommendation, so I think we're in sync with your process
> observations on that point.
> 
> Regards, Dave Ings,
> Emerging Software Standards
> Email: ings@ca.ibm.com
> Yahoo Messenger: dave_ings
> 
> 
> 
>   From:       "Mary McRae" <mary.mcrae@oasis-open.org>
> 
>   To:         Dave Ings/Toronto/IBM@IBMCA, <bpel4people@lists.oasis-
> open.org>
> 
>   Date:       2008/03/19 01:58 PM
> 
>   Subject:    RE: [bpel4people] JIRA Accounts
> 
> 
> 
> 
> 
> 
> Hi Dave,
> 
>   Just a reminder that the bpel4people TC does not yet have permission to
> use
> the osoa JIRA system. No accounts should be created until the TC
> Administrator
> is in receipt of assurances from the osoa funding members.
> 
>   Once that letter is received, there will be two options - according to
> OASIS
> rules, anyone who is a Member of a TC (including Voting Member, Chair, or
> Secretary) must have write-access. The CSA-associated TCs have limited
> write
> permissions by creating an editors subcommittee, thereby limiting write
> access
> to those in that group.
> 
> Regards,
> 
> Mary
> 
> > -----Original Message-----
> > From: Dave Ings [mailto:ings@ca.ibm.com]
> > Sent: Wednesday, March 19, 2008 1:53 PM
> > To: bpel4people@lists.oasis-open.org
> > Subject: [bpel4people] JIRA Accounts
> >
> >
> > Hi,
> >
> > In order to open issues in JIRA, you need write permission and in order
> to
> > do that, you need to have a JIRA account. (Read only access does not
> > require an account). I'll have to supply the OSOA folks with a list of
> > names and IDs to create those accounts. So the question has arisen as to
> > how many people on our TC will want/need accounts.
> >
> > I've spoken with Mike Edwards and his advice, based on the SCA
> experience,
> > is that it works mostly smoothly if the spec editing team (which in our
> > case includes the issues editor) are the only people with JIRA write
> > access. Recall that in the SCA process that we adopted last week, raising
> a
> > new issue starts with an email sent to the list with the subject ?NEW
> > ISSUE: [title]?. So the question really is who can/will translate these
> > emails into a JIRA artifact.
> >
> > I don't have a strong opinion. I can see the merit in channeling new
> issues
> > through the editing team / issues editor. On the other hand, especially
> > when the TC is new, I can see the merit in having anyone be able to open
> > issues directly in the tool. Opinions?
> >
> > In the meantime, so we are up and running by next meeting, I will request
> > IDs for all members of the editing team - the default ID will be your
> last
> > name unless I'm advised to the contrary (and in particular please advise
> me
> > if you already have an ID).
> >
> > Thanks ... Dave.
> >
> > Regards, Dave Ings,
> > Emerging Software Standards
> > Email: ings@ca.ibm.com
> > Yahoo Messenger: dave_ings
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  You may a link to this group and all your TCs in
> > OASIS
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
>