[oslc-core] Decision process in OSLC...

[Dave]

We discussed this topic during yesterday's Core workgroup meeting and
as a result of that discussion, I've written some new text for the
workgroup best practices page [1]. My original text did not emphasize
that decisions should only be made on the mailing list.

<newText>

Making decisions

Workgroups should strive to do all of their work on their mailing
lists or the community wiki provided at open-services.net. All
decisions should be discussed and made on the mailing lists where all
can participate.

Workgroups use regularly scheduled meetings to have additional
discussions, review proposals and share news, but decisions should not
be made during such meetings. If meeting attendees feel that a
decision should be made, they should recommend that decision to the
mailing list, summarize the arguments, find consensus via discussion
there.

Meeting agendas should be published and noted on the workgroup mailing
list two days in advance of meetings and detailed meeting minutes and
recommended decisions should be posted by the day after. Each
recommended decision should be stated in its own email so that it can
have its own thread of discussion.

</newText>

Unless I hear objections, or suggestions for better text that is what
I'll add to the wiki.

Thanks,
Dave

[1] http://open-services.net/bin/view/Main/OslcWorkgroupPrinciplesandBestPractices



On Thu, Feb 10, 2011 at 3:57 PM, Steve K Speicher <sspeiche at us.ibm.com> wrote:
>> From: Dave <snoopdave at gmail.com>
>> To: oslc-core at open-services.net
>> Date: 02/10/2011 12:46 PM
>> Subject: Re: [oslc-core] Decision process in OSLC... Re: Renaming
> property
>> oslc:discussion to oslc:partOfDiscussion for oslc:Comment
>> Sent by: oslc-core-bounces at open-services.net
>>
>> On Tue, Jan 25, 2011 at 9:48 AM, Dave <snoopdave at gmail.com> wrote:
>> > Regarding the decision making process, I'd like to follow-up on this.
>> > I'm sympathetic to your concerns about the process being open to all,
>> > and not just those who attend WG meetings.
>> >
>> > I think this is something we should document as part of the OSLC
>> > process. I believe this is the best description of the process that we
>> > have so far:
>> >
>> >
> http://open-services.net/bin/view/Main/OslcWorkgroupPrinciplesandBestPractices
>
>> >
>> > Perhaps we should add some text to that and require that decisions
>> > made during WG meetings be documented, highlighted on the WG mailing
>> > list and not finalized until the next WG meeting... giving the wider
>> > community a chance to discuss and possibly reverse the decision before
>> > it is acted upon.
>>
>> I've been thinking more about this issue and a plan for addressing this
> issue:
>> 1) Add text to the Workgroup best practices page above
>> 2) Publicize the change on OSLC community mailing list
>> 3) Ask workgroups to link to the Best Practices on their home pages
>>
>> Here's the new text to be added:
>>
>> <new text>
>> Sometimes workgroup members cannot attend workgroup meetings due to
>> time-zone differences, conflicts and other factors but we still want
>> them to be able to fully participate in the OSLC community.
>>
>> To help those members who cannot attend some or all meetings,
>> Workgroups should provide detailed meeting minutes for each meeting,
>> and share any materials discussed, e.g. presentations, wiki pages and
>> other documents.
>>
>> Workgroups should also take special care when making decisions during
>> meetings. Any decisions made should be called out in the meeting
>> minutes, and workgroup members should hold off on implementing such
>> decisions until either the decision has been discussed on the
>> workgroup mailing list or the next meeting.
>> </new text>
>>
>>
>> Maybe that will not fully resolve the problem, but will the above plan
>> improve things?
>>
>> Any other comments on the plan or text? Other ideas?
>
> All sounds good but I think it is key also to have a meeting agenda posted
> before the meeting, so even the attendees, will see what issues or
> decisions will be expected to be discussed in the meeting.  A best
> practice might be to have an agenda more that 2 days before the meeting
> occurs.
>
> Though each WG needs to be clear how they communicate these items. Whether
> WG members are expected to use the TWiki notification features or if
> members are to send items via each WG's mailing list.
>
> Thanks,
> Steve Speicher | IBM Rational Software | (919) 254-0645
>
>
>
>
>
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
>