Difference between revisions of "Community Council/Meeting Guidelines/Meeting Guidelines Development"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Small corrections)
(Added CC template)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Documentation/Note | This page is used to outline a proposal for the Community Council. If you have any questions or proposals, then please contact [[User:ChristophNoack|Christoph]] or add your thoughts to the talk page. Thanks!}}
+
{{Community_Council}}
 +
== Introduction  ==
  
== Introduction==
+
This wiki page describes the development of the meeting guidelines for the regular Community Council meetings.<br>
  
=== Current Situation<br> ===
+
Related page: [[Community Council/Meeting Guidelines|Meeting Guidelines]]<br>  
  
This wiki page contains a proposal to make [http://council.openoffice.org/ Community Council] status meetings a bit more efficient. Today, most of the meetings are held in the IRC with an already [http://wiki.services.openoffice.org/wiki/Community_Council/Agenda prepared agenda]. Once the meeting is finished, both the full IRC log and the new action items are [http://wiki.services.openoffice.org/wiki/Community_Council/Minutes published in the wiki].
+
== Development  ==
  
This procedure has its downsides, especially if council members haven't been able to prepare information or work on action items. Sometimes this causes the status meeting turn to a working meeting. Even the role „Council Coordinator“, which is meant to remind the community members to fulfill their duties in advance, did not finally solve that problem.<br>  
+
=== Initial Situation<br>  ===
 +
 
 +
This wiki page contains the d to make [http://council.openoffice.org/ Community Council] status meetings a bit more efficient. Today, most of the meetings are held in the IRC with an already [http://wiki.services.openoffice.org/wiki/Community_Council/Agenda prepared agenda]. Once the meeting is finished, both the full IRC log and the new action items are [http://wiki.services.openoffice.org/wiki/Community_Council/Minutes published in the wiki].
 +
 
 +
This procedure has its downsides, especially if council members haven't been able to prepare information or work on action items. Sometimes this causes the status meeting turn to a working meeting. Even the role „Council Coordinator“, which among others is meant to remind the community members to fulfill their duties in advance, did not finally solve that problem.<br>  
  
 
During the [http://wiki.services.openoffice.org/wiki/Community_Council/Minutes#2010-02-04.2F05_.28F2F_Meeting_in_Hamburg.29 face-to-face meeting in Hamburg], some proposals to improve the situation have been discussed. The main idea is to prepare the minutes in advance and to discuss the state during the meeting which might be held via IRC or – more efficient – via phone. Finally, the minutes are published to the community.<br>  
 
During the [http://wiki.services.openoffice.org/wiki/Community_Council/Minutes#2010-02-04.2F05_.28F2F_Meeting_in_Hamburg.29 face-to-face meeting in Hamburg], some proposals to improve the situation have been discussed. The main idea is to prepare the minutes in advance and to discuss the state during the meeting which might be held via IRC or – more efficient – via phone. Finally, the minutes are published to the community.<br>  
Line 42: Line 47:
  
 
|-
 
|-
| (Several People)<br>
+
| (Several People)<br>  
 
|  
 
|  
In the first discussion in a Council Meeting, there has been a request to identify the age of the items and some other things, too.<br>
+
In the first discussion in a Council Meeting, there has been a request to identify the age of the items and some other things, too.<br>  
  
*John: "One small suggestion - when I did the minutes for the f2f meeting I numbered the AIs according to the date of the meeting - e.g. 402.1 is the first AI from the 4th Feb meeting..."<br>
+
*John: "One small suggestion - when I did the minutes for the f2f meeting I numbered the AIs according to the date of the meeting - e.g. 402.1 is the first AI from the 4th Feb meeting..."<br>  
 
*Martin: "and they should be sortable after age"<br>
 
*Martin: "and they should be sortable after age"<br>
  
Source: [[Community_Council/Minutes#2010-02-18|Meeting Minutes 2010-02-18]]<br>
+
Source: [[Community Council/Minutes#2010-02-18|Meeting Minutes 2010-02-18]]<br>  
  
Comments by Christoph:
+
Comments by Christoph:  
  
*The basic requirement is to know how old the action items are, so I initially proposed to keep the "record date" element. If not, then...<br>
+
*The basic requirement is to know how old the action items are, so I initially proposed to keep the "record date" element. If not, then...<br>  
 
*New proposal is to use the format "YYYY-MM-DD#N" (e.g. 2010-02-03#2) and to order the elements in the agenda according to their age. Advantage: We get sorting for free and an unique numbering scheme, too. Disadvantage: It still feels a bit clumsy and the order may not reflect importance / similar topics.
 
*New proposal is to use the format "YYYY-MM-DD#N" (e.g. 2010-02-03#2) and to order the elements in the agenda according to their age. Advantage: We get sorting for free and an unique numbering scheme, too. Disadvantage: It still feels a bit clumsy and the order may not reflect importance / similar topics.
  
 
|}
 
|}
 
<br>
 
 
== Proposal  ==
 
 
=== Procedure  ===
 
 
Note: Once the proposal is accepted by the Community Council, it will be published on a separate wiki page.
 
 
#A wiki page serves both as the agenda for the next Community Council meeting and the current working status of "Accepted" action items. Besides that, the wiki page is intended to collect new topics which might be relevant for the Community Council. These topics might be raised by any community member – like today - with the status being set to "'''New'''".<br>
 
#A few days before a regular Community Council meeting …
 
##The Community Council Coordinator (or anybody who thinks it might be high time) asks the Community Council members on [council-discuss] to update the status of the action items and status.
 
##Each Community Council member updates his/her action items and outlines intermediate or final results. The description should match the complexity of the action item and should be – hopefully – understandable without any further explanation. The "Status" won't be changed by the action item owner - this has to be done in the meeting with the other Community Council members.<br>
 
#During the Community Council Meeting …
 
##One Community Council member agrees to work on the minutes of the meeting. The already introduced wiki page serves as a basis for that.
 
##The Community Council members accept or reject newly proposed topics. If not yet done (e.g. via mail), a responsible person is selected, the next few steps are quickly outlined and a due date is chosen. The "Status" of accepted topics is set to "'''Accepted'''". The rejected ones will be marked "'''Rejected'''" - and a short reason is provided.<br>
 
#The Community Council now continues with “Current Topics”:
 
##For each topic, the action item owners present results (intermediate or final).
 
##If there are open questions concerning this topic, then there might be a <u>short</u> discussion. If the topic requires some more attention, then the discussion should be continued off-line (e.g. after the Community Council meeting).<br>
 
##If it is agreed that a topic has been finished, then the keeper of the minutes will change the status from "Accepted" to “'''Finalized'''”.
 
#Directly / shortly after the Community Council Meeting …
 
##The keeper of the minutes will copy the entire agenda / working status page (worked on) to the one that lists the meeting minutes – like today. The IRC log is added there, too.<br>
 
##The keeper of the minutes will clean up the current wiki page and remove “Finalized” and "Rejected" action items. Thus - directly after a meeting - the wiki page represents a "clean" agenda of open action items.<br>
 
##The keeper of the minutes informs the public about the meeting: a short mail to the council-discuss mailing list and to the responsible for the OpenOffice.org newsletter.
 
 
'''Comments'''
 
 
*Adding "New" action items: If possible, a rather formal description of the request stated by any Community Member. If possible questions like “What?”, “Why?”, or “Urgency?” should already been answered and an appropriate action item ID should be chosen (format: YYYY-MM-DD#N, e.g. 2010-02-03#2). The action item will be added at the bottom of the action items table. Since only few members will consider to post this information directly, the Community Members serve as proxies to add this information and to inform the other members in advance – just like it is handled today.<br>
 
*Describing action items: If the description is missing any important information, the keeper of the minutes adds it during/after the meeting.<br>
 
*Status indication: The status of an action item is one of the following - New, Accepted, Rejected or Finalized.<br>
 
*The agenda / work status table be sortable (see below).
 
 
=== Template for Wiki Page Structure  ===
 
 
==== Structure<br>  ====
 
 
The following proposal outlines the revised wiki page structure.<br>
 
 
*'''Upcoming Meeting''': date and location
 
*'''Agenda and Work Status''': The section current topics lists all current action items with the following information... Here is an example. <br>
 
 
{| class="prettytable sortable"
 
|-
 
! scope="col" | ID<br>
 
! scope="col" | Topic<br>
 
! scope="col" | Status<br>
 
! scope="col" | Responsible<br>
 
! scope="col" | Last Update<br>
 
! scope="col" | Details<br>
 
|-
 
| 2010-02-04#1<br>
 
| Proposal for both a new Community Council meeting minutes template and general improvements<br>
 
| Accepted<br>
 
| Christoph<br>
 
| 2010-03-02 <br>
 
|
 
*In the face-to-face meeting it has been decided to improve the meeting minutes template and other things.
 
*The current issues have been outlined and a proposal has been worked out and is available here (link).
 
*Next steps: The proposal will be presented to the Community Council that may accept it. If the procedure and the template are accepted, a more detailed documentation will be worked out. A final decision for becoming official will be requested by the Community Council.
 
 
|-
 
| ...<br>
 
| ...<br>
 
| ...<br>
 
| ...<br>
 
| ...<br>
 
| ...<br>
 
|}
 
 
==== Template for Mail, Blog Posting  ====
 
 
(to be worked on)
 
  
 
== Open Points  ==
 
== Open Points  ==
  
=== Question ===
+
=== Questions ===
  
 
*Phone conference: Do we have numbers for a phone conference or at least access to a “free” audio/video conference system?  
 
*Phone conference: Do we have numbers for a phone conference or at least access to a “free” audio/video conference system?  
Line 138: Line 71:
 
*Live editing: If the moderator of the Community Council meeting works on the minutes during the meeting, is there any chance to track the changes „live“ so that at least the participants can check for completeness and comprehensibility?  
 
*Live editing: If the moderator of the Community Council meeting works on the minutes during the meeting, is there any chance to track the changes „live“ so that at least the participants can check for completeness and comprehensibility?  
 
*Keeper of the minutes: Is there any reasonable responsibility, e.g. the Community Council Char, Community Council Coordinator, “rotating” system, …&nbsp;?  
 
*Keeper of the minutes: Is there any reasonable responsibility, e.g. the Community Council Char, Community Council Coordinator, “rotating” system, …&nbsp;?  
*Agreement on minutes: Is there a need for agreeing on the minutes before it will be published?
+
*Agreement on minutes: Is there a need to agree on the minutes before they will be published?
  
 
=== Todo  ===
 
=== Todo  ===
  
*Better description of the whole procedure, move the content to a new wiki page<br>
 
*Template for the email message to the council-discuss list after a meeting
 
 
*Template for the blog posting after a meeting (including tags to be used)
 
*Template for the blog posting after a meeting (including tags to be used)
  
 
[[Category:Community_Council]]
 
[[Category:Community_Council]]

Latest revision as of 15:06, 30 May 2010

Community Council

The Community Council members are your representatives

About


Communication


Ideas related to the community? Tell us!

Introduction

This wiki page describes the development of the meeting guidelines for the regular Community Council meetings.

Related page: Meeting Guidelines

Development

Initial Situation

This wiki page contains the d to make Community Council status meetings a bit more efficient. Today, most of the meetings are held in the IRC with an already prepared agenda. Once the meeting is finished, both the full IRC log and the new action items are published in the wiki.

This procedure has its downsides, especially if council members haven't been able to prepare information or work on action items. Sometimes this causes the status meeting turn to a working meeting. Even the role „Council Coordinator“, which among others is meant to remind the community members to fulfill their duties in advance, did not finally solve that problem.

During the face-to-face meeting in Hamburg, some proposals to improve the situation have been discussed. The main idea is to prepare the minutes in advance and to discuss the state during the meeting which might be held via IRC or – more efficient – via phone. Finally, the minutes are published to the community.

Goals

  • More efficient meetings for the Community Council
  • Faster and more focused information for both the community and the Community Council deputies
  • Easier distribution of information for the community

Requirements and Wishes

The following table summarizes the requirements and wishes of some of the council members.

Louis Use of phone instead of IRC.
Stefan Instead of the wiki, the information may be collected via blog postings in advance.
Mathias Some people may not want to use a blog, therefore it shouldn't be a hard requirement.
Jürgen Keep it simple!
Stefan

Is there any extension which can be used to publish the information automatically? For example a RSS feed which can be used for the blogs/planets?

Comment by Christoph: There is some information concerning RSS feeds at Wikipedia:Syndication

(Several People)

In the first discussion in a Council Meeting, there has been a request to identify the age of the items and some other things, too.

  • John: "One small suggestion - when I did the minutes for the f2f meeting I numbered the AIs according to the date of the meeting - e.g. 402.1 is the first AI from the 4th Feb meeting..."
  • Martin: "and they should be sortable after age"

Source: Meeting Minutes 2010-02-18

Comments by Christoph:

  • The basic requirement is to know how old the action items are, so I initially proposed to keep the "record date" element. If not, then...
  • New proposal is to use the format "YYYY-MM-DD#N" (e.g. 2010-02-03#2) and to order the elements in the agenda according to their age. Advantage: We get sorting for free and an unique numbering scheme, too. Disadvantage: It still feels a bit clumsy and the order may not reflect importance / similar topics.

Open Points

Questions

  • Phone conference: Do we have numbers for a phone conference or at least access to a “free” audio/video conference system?
  • Grouping of topics: If many topics are in work, will it make sense to group them (e.g. community, development, …)?
  • Live editing: If the moderator of the Community Council meeting works on the minutes during the meeting, is there any chance to track the changes „live“ so that at least the participants can check for completeness and comprehensibility?
  • Keeper of the minutes: Is there any reasonable responsibility, e.g. the Community Council Char, Community Council Coordinator, “rotating” system, … ?
  • Agreement on minutes: Is there a need to agree on the minutes before they will be published?

Todo

  • Template for the blog posting after a meeting (including tags to be used)
Personal tools