To be clearer, my point is that work should be done on a public OASIS list and not off-list.
regards, Frederick
Frederick Hirsch
Nokia
On Jul 12, 2013, at 8:22 PM, ext Dennis E. Hamilton wrote:
@Frederick
Since subcommittee lists are no different than the main TC list in respect to public visibility and transparency, I am not
clear what point you are making. The key thing is that subcommittees don’t decide anything for the TC. All decision-making and the related deliberations
concerning the work products of the TC are at the TC level. A subcommittee can develop a proposal to the TC, but it is the TC that determines the way forward.
- Dennis
PS: I find work on subcommittee lists far more useful than face-to-face meetings where the discussion is not captured and
especially better than off-TC activities that work out-of-band, all of which I have observe in one place or another.
I support discussion and work appearing on the public OASIS mail list and repositories, in fact I think it is essential to enable transparency, openness and enabling new participants to catch
up, outsiders to learn and observe and members to have a record with context of earlier work and decisions.
I also note that IPR licensing obligations are only for essential claims in the final deliverables, but that contributions need to be explicit and sharing via the list is a good way to do
this.
On Jun 21, 2013, at 4:38 PM, ext Dennis E. Hamilton wrote:
Having a subcommittee doesn’t really change how contributions are made. Subcommittees
often have their own OASIS mailing lists as a way to avoid distraction of the full TC (and vice versa). (Cross-posting is usually not done). Subcommittee lists are archived
and subscription is limited to members of the TC. There is no separate Subcommittee membership. Any SC is open to any TC member. All
a TC member has to do is subscribe if they want “home delivery” of such lists. The same goes for any separate SC document areas (usually just a subfolder under the TC document repository), topics under the TC JIRA,
and any SVN set up for the TC. Any deliberations and official TC actions are done with the full TC and on the full TC lists, etc. The subcommittee and information about
it is all linked off of the TC main page. The TC IP regime applies across all of it.
I am not advocating creation of any subcommittees. I just want to emphasize that
it doesn’t create anything but a way to funnel specialized preliminary work into an identifiable place where the interested parties can develop proposals in plain view and then propose work products to the full TC.
I would prefer the contributions are done through TC mailing list.
Sent from my Nokia Windows Phone 8 smart phone
The work should be able to be done in a subcommittee but the document would have to go through the TC process for adoption, we have done this in several committees before
-----Original Message-----
From: pbd-se@lists.oasis-open.org [mailto:pbd-se@lists.oasis-open.org]
On Behalf Of Frank.Dawson@nokia.com
Sent: Friday, June 21, 2013 9:54 AM
To: pbd-se@lists.oasis-open.org
Subject: [pbd-se] Way of Working
Hei All.
In our call on Wednesday, it was raised whether work on the OASIS-PbD-SE-6.html document would be done in some kind of "sub-committee" of the TC. My understanding is that this is not typical OASIS way-of-working, as there would need to be some formality of
calling meeting, minute taking, etc that we are already doing for monthly TC meetings.
My recommendation would be that we develop the document through member contributions over the TC email list and use the monthly TC meetings to report progress updates and status of action items.
By the way, who is the editor(s) of this document?
Frank/
---------------------------------------------------------------------
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
|