[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [chairs] For those TCs using JIRA
When I get back from vacation, I'll explore what can be done. We are working on being able to sync up with the members list which would make setting up all TC members feasible. Right now, managing the member lists in batch modes is by-hand. I will see what we can do to manage the email traffic to make it more manageable for TC members. Thanks for all this feedback! /chet On Mon, Aug 6, 2012 at 10:51 PM, Robin Cover <robin@oasis-open.org> wrote: > On Mon, 6 Aug 2012, Farrukh Najmi wrote: > >> >> Respectfully I urge against restricting access to JIRA to some "special" >> TC members. >> >> In the spirit of openess and fairness, a TC JIRA should be writable by any >> TC voting member and should be readable by the world. > > > > Yes, thanks Farrukh. That ethos (and rule/policy) is historic, and should > be unassailable policy. It stems from core axiology. We do not > countenance a system where some people get more write authority than > others in a TC, much less greater visibility. > > > And so it is, for example, that you can read the OASIS policy about > openness, > etc, whereby all TC members are equaly guaranteed write access, in all > venues, and where the world is supposed to be granted read access, to all > resources (ALL resources) produced within the scope of TC activity. Below. > > > 1) all publication venues and associated activities (TC lists, VCS [SVN], > issues > tracker/list, Wiki, document repository, etc) are required to be > TC-Member-write > and World-read. Full stop. > > > 2) [modulo] in a small number of cases, Chairs and Secretaries are granted > some config privs that not all others on the TC have, per expediency, but > this is unofficial, formally unsanctioned, and may not be exploited to > disenfranchise any TC member who wants/needs a voice at any point. > > 3) There is actually a good reason for what's required in the TC Process, > which mandates no allowable OPT-out for subscription to the general > TC list. Everyone, including Observers, is required to be subscribed to > the list. > > For reminder, here is the OASIS policy text for equal write access by all TC > > members in all venues, and unimpeded world read for all TC resources: > > https://tools.oasis-open.org/ > > ============================================================== > [excerpt] > > Wikis: TC Wikis contain collaborative documents and documentation. > Issue Tracker: The Issue Tracker contains lists of items that > TC Members will address. > Version control: TC Members track versioned source code and > files here. > > This policy includes, but is not limited to, the following: > > * wikis located at wiki.oasis-open.org > * files located at tools.oasis-open.org/version-control, > with additional information in OASIS Tools Help > * issues lists maintained at tools.oasis-open.org/issues, > with additional information in OASIS Tools Help > > The site: > > * The site and all of its contents must be publicly > viewable/readable by the general public. > * The site and access to all of its contents must not > require a login for read-only access. > > Access Permissions: > > * Write access must be provided to all TC Members > (Members, Voting Members, Persistent Non-Voting Members, > Chairs, and Secretaries). > * TC Observers and the general public must not be allowed > write access. > > The TC home page: > The location (URI) and a brief description must be posted > on TC public home page (maintained by the TC Chair > and/or Secretary). > > Thanks, > > - Robin > > ============================================== > > > >> >> I think it goes against the grain of openness and fairness to restrict >> issue creation to a subset of TC members. The whole idea is to make it easy >> for any one on the TC to file issues as they thin of it. Filing an issue >> does not imply that it will be accepted or addressed. However, it makes sure >> that it is recorded and what the TC decided to do with it (along with >> rationale) to also be recorded. >> >> What does need to be limited are JIRA admin privileges which allow >> creation of versions, milestones etc. >> >> These are fairly established practice in open standards as well as open >> source projects from what I have seen. >> >> OASIS should not allow TC's to have less open issue management policies. >> >> On 08/06/2012 06:03 PM, Patil, Sanjay wrote: >>> >>> +1 as this approach means - less email traffic for TC members, and lesser >>> work load for the TC admin! >>> >>> One caveat I see here is that, the need for which TC members should have >>> access to JIRA and when the access should be enabled would depend upon the >>> particular TC's issue management practices. I think raising and resolving >>> issues is a core process most of the TCs depend upon for advancing their >>> deliverables (specifications, etc). If a TC has designated Issues Editors >>> who are responsible for logging and maintaining the issues, then only those >>> few Issues Editors would need access to JIRA. On the other hand, if a TC >>> aims to allow any TC member to directly open an issue in JIRA, then it would >>> be deemed as convenient for all the TC members to have implicit access to >>> JIRA (instead of having to contact the TC Admin at the time of raising the >>> first issue!). >>> >>> In my experience, several of the raised issues may not be approved by the >>> TC. Therefore, it may make sense to use TC mailing lists for submitting new >>> issues, and use JIRA for tracking only the approved issues (in which case >>> not every TC member would need access to JIRA). >>> >>> On a side note - support for single-sign-on between JIRA, Kavi and other >>> systems may resolve (or altogether eliminate) this issue in the future. But >>> until then it would make sense to provide JIRA access to only those members >>> who intend to use it, IMHO. >>> >>> Sanjay >>> >>> -----Original Message----- >>> From: Chet Ensign [mailto:chet.ensign@oasis-open.org] >>> Sent: Monday, August 06, 2012 2:41 PM >>> To: Peter F Brown >>> Cc: chairs@lists.oasis-open.org >>> Subject: Re: [chairs] For those TCs using JIRA >>> >>> 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> >>> wrote: >>>> >>>> Chet, >>>> I personally think that it is a bad idea to automatically add all TC >>>> members. >>>> 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 >>>> 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 >>>> ---------------- >>>> 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-996-2298 >>>> Mobile: +1 201-341-1393 >>>> >>>> TC Administration information and support is available at >>>> http://www.oasis-open.org/resources/tcadmin >>>> >>>> Follow OASIS on: >>>> LinkedIn: http://linkd.in/OASISopen >>>> Twitter: http://twitter.com/OASISopen >>>> Facebook: http://facebook.com/oasis.open >>>> >>>> >>> >>> >> >> >> -- >> Regards, >> Farrukh Najmi >> >> Web: http://www.wellfleetsoftware.com >> >> > -- /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-996-2298 Mobile: +1 201-341-1393 TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin 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]