[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency] JIRA Projects for the EM-TC
Let me just clarify something about notifications. The notification scheme is automatic - all notifications regarding additions and changes to JIRA tickets will go to the respective mailing lists - the SC or as I noted above the TC for SitRep. That is to ensure that JIRA is part of our public record. Plus anyone who wants to go to JIRA and review the list of issues can do so anytime. From a read-only perspective it is a totally open, public record. Membership in the JIRA project means that members can add new issues and comments and edit their comments. The chair and editors can further update tickets, change their status, etc. So notifications will happen - no one has to forward or take any other action. Project membership is just needed so the people can add issues and comment on them. Let me know if you have any questions. /chet On Thu, Jan 12, 2012 at 10:39 AM, Rex Brooks <rexb@starbourne.com> wrote: > Hi Elysa, > > After conversing with Chet, I decided to just send the issues manually to > the active individuals on the roster. It turns out to be more work for Chet > than a few keystrokes, and, if I remember correctly, not possible to do "en > masse" so that is what I am doing. I plan to do this over the weekend or > Monday, before next week's SC meeting for SitRep. Tim wasn't on the call > Tuesday, so we didn't take any major decisions on this. That's still going > to be a bit of work for me. > > Cheers, > Rex > > > On 1/12/12 5:17 AM, Elysa Jones wrote: >> >> Rex and Chet, >> >> I am just now about to embark on entering comments into the CAP-AU Profile >> Project and I'm sure I'll need some help. We decided in a meeting >> yesterday >> to use JIRA and that we wanted all SC members noticed on JIRA activity. >> We >> have the same issue that we want other TC members to be able to optionally >> be included in any notifications. I agree with Rex below. So, which way >> will we go? I want to be able to announce and give a little direction to >> the TC members on our call Tues >> >> Thanks, >> Elysa >> >> -----Original Message----- >> From: Rex Brooks [mailto:rexb@ncoic.org] >> Sent: Wednesday, January 04, 2012 5:42 PM >> To: Chet Ensign >> Cc: Rex Brooks; Elysa Jones; emergency@lists.oasis-open.org >> Subject: Re: [emergency] JIRA Projects for the EM-TC >> >> Chet, >> >> I have attached an html file for the roster page of Messages and >> Notifications SC. Is there a way to ask them to reply with an affirmative >> that they are participating in the adjudication of the EDXL-SitRep >> specification public review or wish to have the issues sent to them as >> observers if they are not, and then give them an account-login? That would >> almost certainly be the best way to avoid annoying them if they are not >> interested sufficiently. Otherwise the only sane thing to do is the add >> them >> all and let them opt out on their own. >> >> Elysa, do you agree? >> >> Cheers, >> Rex >> >> On 1/4/12 1:52 PM, Chet Ensign wrote: >>> >>> Rex, who all is in the Messages& Notifications SC? I will have to add >>> them all to the JIRA project in order for them to receive >>> notifications of issues for it. >>> >>> Thx, >>> >>> /chet >>> >>> On Tue, Jan 3, 2012 at 7:20 PM, Rex Brooks<rexb@ncoic.org> wrote: >>>> >>>> Thanks Chet, >>>> >>>> I really appreciate it. >>>> >>>> The question also arose that we seem to need to have all members of >>>> the Messages and Notifications SC receive notification of the issues, >>>> which I would prefer to do 'en masse' if possible, so that we can >>>> conduct our adjudication process with everyone on the same page for >>>> each of these as we move into our next meeting, next Tuesday, in >>>> which I want to familiarize them all with the process. >>>> >>>> Cheers, >>>> Rex >>>> >>>> >>>> On 1/3/12 9:33 AM, Chet Ensign wrote: >>>>> >>>>> Hi Rex - I will get these set up for you today. >>>>> >>>>> /chet >>>>> >>>>> On Tue, Jan 3, 2012 at 12:16 PM, Rex Brooks<rexb@ncoic.org> wrote: >>>>>> >>>>>> Hi Chet, >>>>>> >>>>>> I'm replying to this message today in order to remind you that we >>>>>> need to do this soon. I have entered all comments received so far >>>>>> for EDXL-SitRep that were received under the OASIS Emergency >>>>>> Management TC, so all of those can be moved under the new heading >>>>>> as a block if that's possible. >>>>>> >>>>>> Happy New Year All, >>>>>> Rex >>>>>> >>>>>> >>>>>> On 12/13/11 3:49 AM, Elysa Jones wrote: >>>>>> >>>>>> Hi Chet, >>>>>> >>>>>> >>>>>> >>>>>> Per our call yesterday, could you open or rename the following JIRA >>>>>> projects for the EM-TC? It is fine to spell out the name or use >>>>>> the acronym as you see fit. >>>>>> >>>>>> >>>>>> >>>>>> 1. EDXL Situation Reporting (Sit-Rep) (Currently: Emergency >>>>>> Management TC) >>>>>> >>>>>> 2. EDXL Distribution Element (DE) (Currently: EM >>>>>> Infrastructure) >>>>>> >>>>>> 3. EDXL CAP 1.2 Australia Profile (CAP-AU) >>>>>> >>>>>> >>>>>> >>>>>> Thank you, >>>>>> >>>>>> Elysa >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: emergency-unsubscribe@lists.oasis-open.org >> For additional commands, e-mail: emergency-help@lists.oasis-open.org >> >> >> > > > -- > Rex Brooks > President, CEO > Starbourne Communications Design > GeoAddress: 1361 Addison #A > Berkeley, CA 94702 > Phone: 510-898-0670 > -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-378-3472 Mobile: +1 201-341-1393 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]