RE: [regrep] JIRA Accounts created

["Mary McRae" <marypmcrae@gmail.com>]

Hi Farrukh,

  Not quite - we need to ensure it conforms to our policies. Atlassian
wouldn't give us a non-profit (free) license; they said open source projects
only.

  That said, I have no problems with JIRA itself, but it must conform to the
OASIS policies.

  Here's what's required - Policy below

---

In an effort to accommodate Technical Committees with multiple editors and
support the use of collaborative authoring/editing tools that are not
currently provided by OASIS to its members, the following policy is set
forth to provide a set of guidelines related to the use of collaborative
authoring/editing/versioning systems hosted on non-OASIS servers. Please
note that explicit authorization must be received from the OASIS TC
Administrator before proceeding to use any non-OASIS-hosted version control
system. 

The site:
-	The site and all its contents must be publicly viewable/readable by
the general public 
-	The site and access to its contents must not require a login for
read-only access

The TC home page:
-	The location (URI) and a brief description must be posted on TC
public home page

Access Permissions:
-	Write access (login/password protected) must be provided to all TC
Members, Voting Members, Chairs and Secretaries - ONLY. Alternatively, write
access must be provided to all Editor Subcommittee Members, Voting Members,
Chairs and Secretaries - ONLY. The TC or SC Chair must maintain the login
accounts to correspond to the current Roster.
-	TC Observers and the general public must not be allowed write
access, as that could pollute the IP licensing status of the TC's output.

TC Document Repository
-	At least once a month (unless no work has been done), and prior to
each TC meeting at which the document will be discussed, a Working Draft of
any/all documents must be uploaded to the TC document repository, properly
identified according to the Naming Guidelines (links to the third-party
system are insufficient)
-	All TC member reviews and ballots must be based on a Working Draft
as posted to the TC document repository (links to the third-party system are
insufficient)

Notification:
-	Chair must notify TC Administrator of the following:
-	The system they plan to use (i.e. Sourceforge, etc.)
-	The URI for the TC-specific work
-	Acknowledge the guidelines and agree to their terms 

Approval:
The TC must receive explicit authorization from the TC Administrator before
proceeding to use any non-OASIS-hosted version control system.


> -----Original Message-----
> From: Farrukh Najmi [mailto:farrukh@wellfleetsoftware.com]
> Sent: Friday, October 03, 2008 2:08 PM
> To: mary.mcrae@oasis-open.org
> Cc: regrep@lists.oasis-open.org
> Subject: Re: [regrep] JIRA Accounts created
> 
> 
> Hi Mary,
> 
> It is hosted by MIT Lincoln Labs. Recall we had discussed the issue of
> lack of issue tracking and version control with you around June 10,
> 2008
> over the phone. Based on my recollection you had said it was OK for us
> to use external resources since OASIS did not provide these. Also
> recall
> that JIRA is available for non-profit use to OASIS from Atlassian but
> OASIS would have to host it at their site.
> 
> Please reconfirm that we are OK with using MIT's JIRA for our issue
> management. Thanks.
> 
> Mary McRae wrote:
> > Hi folks,
> >
> >   Where is this hosted?
> >
> > Mary
> >
> >
> >> -----Original Message-----
> >> From: Oliver Newell [mailto:olivern@LL.mit.edu]
> >> Sent: Friday, October 03, 2008 12:30 PM
> >> To: Breininger, Kathryn R; david@drrw.info;
> nikola.stojanovic@acm.org;
> >> carlmattocks@gmail.com; Farrukh S. Najmi
> >> Cc: regrep@lists.oasis-open.org
> >> Subject: [regrep] JIRA Accounts created
> >>
> >> Hi All -
> >>
> >> I have set up a JIRA Issue tracker project for the RegRep 4.0 spec
> >> work.
> >> So far, I have created user accounts for the five TC members who are
> >> actively working on editing the 4.0 spec for the December time-
> frame.
> >> The five TC members listed as the primary recipients of this email
> >> should (in theory) have received an email yesterday from the JIRA
> >> system
> >> containing username/password information. Please let me know if you
> did
> >> not receive such an email (Subject will be something like '[JIRA]
> >> Account Created'  (Farrukh, I know you didn't so no need to
> respond).
> >> Also let me know if the individual email addresses I used are not
> the
> >> appropriate ones.
> >>
> >> If any other TC members would like to be added to the JIRA project
> for
> >> ebXML regrep 4.0 spec work, drop me a line and I will create an
> account
> >> for you.
> >>
> >> Within the JIRA project, I have so far created two separate
> components
> >> -
> >> one for the work on the ebRS spec and on for the ebRIM spec.  If you
> >> submit issues, please categorize the issue using the appropriate
> >> component, as it will make managing the issues easier.
> >>
> >> Kathryn - I did check that it is possible to create documents from
> the
> >> issue lists. We can theoretically choose between Word docs and Excel
> >> spreadsheets. When I actually test the feature, I notice that
> documents
> >> get generated as expected, but under the hood they are HTML-based
> >> documents with MS Office extensions.  I think that will work ok, but
> >> maybe we can discuss what exactly is needed during one of the
> upcoming
> >> telcons.
> >>
> >> -Oliver
> >>
> >>
> >>
> >>
> >> --------------------------------------------------------------------
> -
> >> 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
> >>
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> 
> 
> --
> Regards,
> Farrukh Najmi
> 
> Web: http://www.wellfleetsoftware.com