OASIS Emergency Management TC

  • 1.  RE: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 13:18
    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


  • 2.  RE: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 13:35
    Standard behavior in the OASIS Jira set-up is that the TC list is subscribed to all Jira project changes. I don't think you have to do anything. "It is the theory that decides what can be observed." - Albert Einstein Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC    Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com


  • 3.  Re: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 13:45
    Elysa, Toby, et al - For these projects, I only signed up subcommittee members because I assumed that you did not want all TC members receiving all notices from JIRA. . As I explained when we talked, I have to do this by hand. There is very little fine-tuning that can be done as far as notices are concerned. If you want others added to the projects, please send me their names and I will add them in. Best, /chet On Thu, Jan 12, 2012 at 8:34 AM, Considine, Toby (Campus Services IT) <Toby.Considine@unc.edu> wrote: > Standard behavior in the OASIS Jira set-up is that the TC list is subscribed to all Jira project changes. I don't think you have to do anything. > > > "It is the theory that decides what can be observed."   - Albert Einstein > > Toby Considine > Chair, OASIS oBIX Technical Committee > U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee > Facilities Technology Office > University of North Carolina > Chapel Hill, NC > > Email: Toby.Considine@ unc.edu > Phone: (919)962-9073 > http://www.oasis-open.org > blog: www.NewDaedalus.com > > >


  • 4.  RE: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 13:53
    Yes, subcommittee members are what we want for these three projects. So, I will need to send you a list of SC members as Rex did for Msg/Not? If other TC members are interested, perhaps we could send you a request? Thanks, Elysa


  • 5.  RE: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 14:20
    Perhaps I am the only one confused... There is a difference between notifications and "being signed up", Signing up brings rights to enter, own, comment on issues. Someone who is signed up can request notifications on any change, whether by issue or by project. Email notifications are a separate set-up. In the Energy projects the TC was subscribed. In the OASIS Jira set-up, this is the TC List. The TC List role describes where all project notifications go to. A TC Chair, you can administer the project. From that screen you can look at the link in the upper section for "Project Roles". The TC List role arrived with just regular TC list subscribed. *If* your TC has sub-committee mailing lists, those would work as well. For us, it was usefull for the Chair to give the Editor full admin rights as well. I can't tell you what is best for emergency - but I think the chairs should look at the Roles page to understand what they are asking for. tc When each project "It is the theory that decides what can be observed." - Albert Einstein Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC    Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com


  • 6.  Re: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 14:25
    Toby, you're not confused.  Write-privs to JIRA are governed by the same rules that govern all OASIS venues, and independent of per-person write-privs, TC/SC activities are published in notifications to publicly archived lists... There are a couple anomalies in the EMTC projects being set up; I have a conference scheduled with Chet later this AM. Until then, maybe just put this conversation on hold, and Chet will send clarification soon, I think. - Robin On Thu, Jan 12, 2012 at 8:20 AM, Considine, Toby (Campus Services IT) < Toby.Considine@unc.edu > wrote: Perhaps I am the only one confused... There is a difference between notifications and "being signed up", Signing up brings rights to enter, own, comment on issues. Someone who is signed up can request notifications on any change, whether by issue or by project. Email notifications are a separate set-up. In the Energy projects the TC was subscribed. In the OASIS Jira set-up, this is the TC List. The TC List role describes where all project notifications go to. A TC Chair, you can administer the project. From that screen you can look at the link in the upper section for "Project Roles". The TC List role arrived with just regular TC list subscribed. *If* your TC has sub-committee mailing lists, those would work as well. For us, it was usefull for the Chair to give the Editor full admin rights as well. I can't tell you what is best for emergency - but I think the chairs should look at the Roles page to understand what they are asking for. tc When each project "It is the theory that decides what can be observed."   - Albert Einstein Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC    Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com


  • 7.  RE: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 14:28
    Thanks Toby and Robin for your input.  Until Chet gets back with us, I’ll make sure I understand the “roles”.  Elysa   From: emergency@lists.oasis-open.org [mailto:emergency@lists.oasis-open.org] On Behalf Of Robin Cover Sent: Thursday, January 12, 2012 8:25 AM To: Considine, Toby (Campus Services IT) Cc: Elysa Jones; Chet Ensign; Rex Brooks; emergency@lists.oasis-open.org; Robin Cover Subject: Re: [emergency] JIRA Projects for the EM-TC   Toby, you're not confused.  Write-privs to JIRA are governed by the same rules that govern all OASIS venues, and independent of per-person write-privs, TC/SC activities are published in notifications to publicly archived lists...   There are a couple anomalies in the EMTC projects being set up; I have a conference scheduled with Chet later this AM.   Until then, maybe just put this conversation on hold, and Chet will send clarification soon, I think.   - Robin On Thu, Jan 12, 2012 at 8:20 AM, Considine, Toby (Campus Services IT) < Toby.Considine@unc.edu > wrote: Perhaps I am the only one confused... There is a difference between notifications and "being signed up", Signing up brings rights to enter, own, comment on issues. Someone who is signed up can request notifications on any change, whether by issue or by project. Email notifications are a separate set-up. In the Energy projects the TC was subscribed. In the OASIS Jira set-up, this is the TC List. The TC List role describes where all project notifications go to. A TC Chair, you can administer the project. From that screen you can look at the link in the upper section for "Project Roles". The TC List role arrived with just regular TC list subscribed. *If* your TC has sub-committee mailing lists, those would work as well. For us, it was usefull for the Chair to give the Editor full admin rights as well. I can't tell you what is best for emergency - but I think the chairs should look at the Roles page to understand what they are asking for. tc When each project "It is the theory that decides what can be observed."   - Albert Einstein Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC    Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com


  • 8.  Re: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 15:40
    Hi Toby, hi Elysa - No confusion. Elysa and Rex asked that I set up JIRA projects for the work of the SC's and I agreed to do it as an experiment. Our prior practice has been to set up one JIRA project for the entire TC and use environment and component tags to distinguish between work products. In this case, the entire SC would be set up to receive messages except for EDXL SitRep where there is no SC so emails will go to the TC mailing list. Robin pointed out this morning that this raises possible conflicts with our commitment to having everything on the public record. This means that issues will be addressed and only appear on the SC mailing list. Perhaps not a show-stopper but something that I will have to watch. It may not be a major problem since it is ultimately up to the TC as a whole to approve whatever is done by the SC. But again, I need to watch how it plays out in practice. The much bigger problem however is that I don't see this approach as sustainable. Our JIRA set up is labor-intensive - I do it all by hand. So it is physically impossible for me to manage potentially hundreds of JIRA configurations. I may have to reassert the rule of 1 JIRA project to each TC in order to keep the work required manageable with all the other responsibilities - such as getting out PRs and announcements of which I am in the midst of multiple right now. For the purposes of the Emergency projects for now, I am signing up all members of each SC for each project. If other members of the TC want to be signed up, I will add them on request. Does that clarify things? Thanks - /chet On Thu, Jan 12, 2012 at 9:28 AM, Elysa Jones <elysajones@yahoo.com> wrote: > Thanks Toby and Robin for your input.  Until Chet gets back with us, I’ll > make sure I understand the “roles”.  Elysa > > > > From: emergency@lists.oasis-open.org [ mailto:emergency@lists.oasis-open.org ] > On Behalf Of Robin Cover > Sent: Thursday, January 12, 2012 8:25 AM > > > To: Considine, Toby (Campus Services IT) > Cc: Elysa Jones; Chet Ensign; Rex Brooks; emergency@lists.oasis-open.org; > Robin Cover > > Subject: Re: [emergency] JIRA Projects for the EM-TC > > > > Toby, you're not confused.  Write-privs to JIRA are governed by the same > > rules that govern all OASIS venues, and independent of per-person > > write-privs, TC/SC activities are published in notifications to publicly > > archived lists... > > > > There are a couple anomalies in the EMTC projects being set up; I have > > a conference scheduled with Chet later this AM. > > > > Until then, maybe just put this conversation on hold, and Chet will > > send clarification soon, I think. > > > > - Robin > > On Thu, Jan 12, 2012 at 8:20 AM, Considine, Toby (Campus Services IT) > <Toby.Considine@unc.edu> wrote: > > Perhaps I am the only one confused... > > There is a difference between notifications and "being signed up", Signing > up brings rights to enter, own, comment on issues. Someone who is signed up > can request notifications on any change, whether by issue or by project. > > Email notifications are a separate set-up. In the Energy projects the TC was > subscribed. In the OASIS Jira set-up, this is the TC List. The TC List role > describes where all project notifications go to. A TC Chair, you can > administer the project. From that screen you can look at the link in the > upper section for "Project Roles". The TC List role arrived with just > regular TC list subscribed. *If* your TC has sub-committee mailing lists, > those would work as well. > > For us, it was usefull for the Chair to give the Editor full admin rights as > well. I can't tell you what is best for emergency - but I think the chairs > should look at the Roles page to understand what they are asking for. > > tc > > > > When each project > > > > "It is the theory that decides what can be observed."   - Albert Einstein > > Toby Considine > Chair, OASIS oBIX Technical Committee > U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee > Facilities Technology Office > University of North Carolina > Chapel Hill, NC > > Email: Toby.Considine@ unc.edu > Phone: (919)962-9073 > http://www.oasis-open.org > blog: www.NewDaedalus.com > > > >


  • 9.  Re: [emergency] JIRA Projects for the EM-TC

    Posted 01-12-2012 15:47
    Wasn't aware of this, Folks, So my previous message could be superceded by this. I will test for this later today by updating an issue. Cheers, Rex On 1/12/12 5:45 AM, Chet Ensign wrote: Elysa, Toby, et al - For these projects, I only signed up subcommittee members because I assumed that you did not want all TC members receiving all notices from JIRA. . As I explained when we talked, I have to do this by hand. There is very little fine-tuning that can be done as far as notices are concerned. If you want others added to the projects, please send me their names and I will add them in. Best, /chet On Thu, Jan 12, 2012 at 8:34 AM, Considine, Toby (Campus Services IT) <Toby.Considine@unc.edu> wrote: Standard behavior in the OASIS Jira set-up is that the TC list is subscribed to all Jira project changes. I don't think you have to do anything. "It is the theory that decides what can be observed." - Albert Einstein Toby Considine Chair, OASIS oBIX Technical Committee U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Facilities Technology Office University of North Carolina Chapel Hill, NC Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com