OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [chairs] For those TCs using JIRA

Few points:

1) Obviously for those TC that don't want to use JIRA (and use spreadsheets or some other bespoke mechanism), how JIRA users are created and emails are sent should not be an issue. IIRC, JIRA project is created for a TC only if the chair requests it.

2) I think we should use an opt-out mechanism (for not getting the JIRA ML updates), regardless of where the JIRA update emails are sent (to the TC ML or a separate ML per Doug's suggestion). I see almost no different between how once you join a TC you automagically get subscribed to the TC mailing list, get access to the doc repo etc, and being subscribed to the JIRA list. I like Doug's idea of a separate mailing list: more aid for email filtering. An opt-in mechanism for those TC that want to use JIRA heavily means unless a member takes an action they will not get any notification regarding ongoing issue discussion, status updates etc. My personaly preference is to not provide the option to opt-out at all: why is someone signing up as a TC member if they don't want to be alerted of issue discussion?

3) Long term a single-signon/single identity store (as Sanjay has suggested) between various OASIS assets seems like the right solution. In the interim, for those TCs that intend to use JIRA heavily, is it possible for a script to run daily (or some appropriate duration) to sync the two separate identity stores? IMHO, for those TC that want to use JIRA heavily, it is important to provide write access to *all* the TC members.

My $0.02


On 08/06/2012 03:54 PM, Farrukh Najmi wrote:

Doug's suggestion sounds like the best solution so far. Chet, any reason
that could not be the standard way to deal with JIRA instances for all
TCs by having JIRA traffic be sent to
<tcname>-issues@lists.oasis-open.org (e.g.
regrep-issues@@lists.oasis-open.org) mailing list?

This makes it easy for TC Admins too by removing this as their ongoing

On 08/06/2012 06:41 PM, Doug Davis wrote:

In other groups the Jira type messages are sent to a mailing list
which people can subscribe themselves to. Then its up to each person
to decide whether they want to be flooded or not - no need for any
admin involvement.  Plus you then also have a history of the messages
in the archives.  just a thought...

STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  | dug@us.ibm.com
The more I'm around some people, the more I like my dog.

*Farrukh Najmi <farrukh@wellfleetsoftware.com>*

08/06/2012 06:20 PM

	Re: [chairs] For those TCs using JIRA


+1 on everyone in a TC being registered automatically with JIRA and
receiving notifications by default (with option to opt out if really

Here are my reasons...

  * One can always send emails from a particular source to
    automatically get filed in an email folder or even gets sent to Trash
  * Issue tracker such as JIRA is the institutional memory of a spec
    or implementation project and the single point of truth for the
    entire team
  * Dealing with JIRA traffic seems to be a fairly minimal thing to
    ask from a TC member
  * I think it may be a familiarity issue that can be overcome easily
    that makes people hesitate about JIRA traffic. Once we know it we
    love it :-)

On 08/06/2012 05:58 PM, William Cox wrote:
The "original" philosophy was that discussions and decisions were made
in the Jira items, so the TC list should be notified to keep people in
the loop. This differs from the assumption of just the listed members,
but I'm not aware of the details of that configuration.

Not disputing that original approach, I just filter anything obviously
from Jira and don't read it...I do status updates in the tool itself.

The default (way back when) was that all TC members were included, and
I believe that to enter items (remember that comments to the TC list
are still comments, and if you use Jira SOMEONE needs to enter them)
you had to also be listed as a "developer".

Fortunately my TCs are relatively slowly changing now, and relatively
small, so this hasn't been much of an issue.

But I'd rather people enter their own comments than find that special
someone to take all of the emails and figure out what's being
commented on.

My two cents...Jira is a useful tool; notification was the original
reason for making all TC members aware of changes, but anyone can read
the summary at any time.


*William Cox*
Email: _wtcox@CoxSoftwareArchitects.com_
Web: _http://www.CoxSoftwareArchitects.com_
+1 862 485 3696 mobile
+1 908 277 3460 fax
On 8/6/12 5:40 PM, Chet Ensign wrote:
True Peter, it is easy to add a person. And you bring up another good
reason not to bulk add people, particularly for those who work on
multiple TCs.

On Mon, Aug 6, 2012 at 5:35 PM, Peter F Brown
_<peter@peterfbrown.com>_ <mailto:peter@peterfbrown.com>wrote:

I personally think that it is a bad idea to automatically add all TC
By default, once added, users receive notifications of everything. The
resultant flood can turn people off as much as please those for whom
this information is valuable.
If someone wants to be added, it's a relatively simple task, no?

-----Original Message-----
From: Chet Ensign [_mailto:chet.ensign@oasis-open.org_]
Sent: Monday, 06 August, 2012 11:58
To: _chairs@lists.oasis-open.org_ <mailto:chairs@lists.oasis-open.org>
Subject: [chairs] For those TCs using JIRA

Bill Cox of the EMIX TC suggested that I should share the following
information with you.

Apparently, it was past practice to regularly update JIRA with new
members who joined TCs. I wasn't aware of the practice and I have been
updating participants in TCs only when asked.

Adding members to JIRA is presently very time consuming. We may have a
fix in place in the future to work off the member database but for now
I must set up users by hand. So I don't plan at present to resume
regular whole-scale updates.

If you are aware of people in your TC who should have access to the
TC's JIRA project but do not, please let me know and I will be happy
to set them up.

Let me know if you have any questions.

Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
_http://www.oasis-open.org_ <http://www.oasis-open.org/>

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

TC Administration information and support is available at

Follow OASIS on:
LinkedIn: _http://linkd.in/OASISopen_
Twitter: _http://twitter.com/OASISopen_
Facebook: _http://facebook.com/oasis.open_



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]