RE: [bpel4people] Issues Process

[Dave Ings <ings@ca.ibm.com>]

A background question for Martin:

The process (as outlined in SCA TC Proposed Issues Processv3.ppt) looks to
be quite reasonable and of a standard design (a good thing!)

That being the case why was JIRA chosen, and in particular chosen over
Bugzilla? Like Luc I'm not familiar with JIRA.

Regards, Dave Ings,
Emerging Software Standards
Email: ings@ca.ibm.com
Yahoo Messenger: dave_ings


                                                                       
  From:       "Mary McRae" <mary.mcrae@oasis-open.org>                 
                                                                       
  To:         "'Luc Clement'" <luc.clement@active-endpoints.com>, "'Martin Chapman'" <martin.chapman@oracle.com>,
              <bpel4people@lists.oasis-open.org>                       
                                                                       
  Date:       2008/03/05 08:23 PM                                      
                                                                       
  Subject:    RE: [bpel4people] Issues Process                         
                                                                       





I was hoping we weren't going to have this discussion until the next
meeting,
but here's a couple of pointers in the meantime.

1. A blog post in which I describe the methods used by the vast majority of
OASIS Technical Committees for issues tracking:
http://oasistcadmin.wordpress.com/2007/07/10/you-have-an-issue-with-that/

2. The rules governing resources that can be used by Technical Committees
to
conduct their work are contained in Section 2.8 of the TC Process:
http://www.oasis-open.org/committees/process-2008-02-05.php#visibility

" The official copies of all resources of the TC and its associated
subcommittees, including web pages, documents, email lists and any other
records
of discussions, must be located only on facilities designated by OASIS. TCs
and
SCs may not conduct official business or technical discussions, store
documents,
or host web pages on servers or systems not designated by OASIS. All web
pages,
documents, ballot results and email archives of all TCs and SCs shall be
publicly visible."

Regards,

Mary

-----------------------------------
Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org
phone: 603.232.9090



> -----Original Message-----
> From: Luc Clement [mailto:luc.clement@active-endpoints.com]
> Sent: Wednesday, March 05, 2008 7:46 PM
> To: 'Martin Chapman'; bpel4people@lists.oasis-open.org
> Subject: RE: [bpel4people] Issues Process
>
> I'm not familiar with JIRA but from what I can surmise the process
proposed
> is workable and proven. Let's adopt. What's required to get an instance
> hosted for our use?
>
> Luc Clément
> Active Endpoints, Inc
> +1.978.793.2162  | luc.clement@active-endpoints.com
>
>
> -----Original Message-----
> From: Martin Chapman [mailto:martin.chapman@oracle.com]
> Sent: Wednesday, March 05, 2008 13:35
> To: bpel4people@lists.oasis-open.org
> Subject: [bpel4people] Issues Process
>
> One of the first things we need to do as a TC is to agree a process for
> raising, tracking, resolving, and
> closing issues we have against our specifications.
>
> Recently, several TCs under the OpenCSA Member Section adopted an  Issues
> Process, which leveraged experience from past TCs. I have
> attached their process to this email and I suggest this TC review this
> process with a view to adopting it.
>
> There are two aspects that we need to consider:
>            1. What are the issue states and how do you transition between
> states
>            2. What tools are we going to use to support this process.
>
> I hope we can put this on the agenda for the next TC meeting.
>
> Cheers,
>   Martin.
> _________________________________________________________________
> Martin Chapman
> Consulting Member of Technical Staff
> Oracle
> P: +353 87 687 6654
> e: martin.chapman@oracle.com
>
>
> ---------------------------------------------------------------------
> 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


---------------------------------------------------------------------
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