| 1 |
WRT bug #256453, I'm proposing the following changes to the Council |
| 2 |
index page. |
| 3 |
|
| 4 |
Feedback is most welcome :) |
| 5 |
|
| 6 |
Index: index.xml |
| 7 |
=================================================================== |
| 8 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/council/index.xml,v |
| 9 |
retrieving revision 1.144 |
| 10 |
diff -u -B -r1.144 index.xml |
| 11 |
--- index.xml 10 Aug 2010 08:06:58 -0000 1.144 |
| 12 |
+++ index.xml 15 Aug 2010 00:21:04 -0000 |
| 13 |
@@ -53,14 +53,56 @@ |
| 14 |
</extrachapter> |
| 15 |
|
| 16 |
<extrachapter position="subproject"> |
| 17 |
-<title>Meeting logs</title> |
| 18 |
+<title>Meetings</title> |
| 19 |
<section> |
| 20 |
<body> |
| 21 |
<p> |
| 22 |
-Meetings are typically held every fourth Monday, at 2000 CET in the |
| 23 |
-#gentoo-council irc channel on irc.freenode.net. They may be moved to another |
| 24 |
-date as needed to accommodate council member availability. |
| 25 |
+Meetings are held at least once a month in the #gentoo-council irc channel on |
| 26 |
+irc.freenode.net. The time and date of each meeting is decided by the active |
| 27 |
+Council and is announced at least two weeks earlier through email to the |
| 28 |
+gentoo-project and gentoo-dev-announce mailing lists. The Council may hold more |
| 29 |
+than one meeting per month if deemed necessary by its members. |
| 30 |
+</p> |
| 31 |
+<p> |
| 32 |
+The current Council holds its monthly meeting on the second Monday of each |
| 33 |
+month, at <uri link="utctolocal.html?time=1900">1900 UTC</uri>. |
| 34 |
+</p> |
| 35 |
+<p> |
| 36 |
+Prior to each meeting, anyone may propose items to be included to the meeting's |
| 37 |
+agenda by replying to the original meeting announcement or by sending a new |
| 38 |
+email to the gentoo-project mailing list. For items to be considered for the |
| 39 |
+meeting, they should be sent at least one week before the meeting date, |
| 40 |
+otherwise they may be pushed back to a later meeting. Also, most, if not all |
| 41 |
+items should be discussed by mail prior to submission. An item may be pushed |
| 42 |
+back to a later meeting if further discussion is required. |
| 43 |
</p> |
| 44 |
+<p> |
| 45 |
+One week before each meeting a draft of the agenda is sent to gentoo-project |
| 46 |
+and gentoo-dev-announce. Item proposals are still accepted afterwards, but |
| 47 |
+their chance of actually getting in the current agenda is low. Items in the |
| 48 |
+agenda are discussed and some may be filtered out. |
| 49 |
+</p> |
| 50 |
+<p> |
| 51 |
+On each meeting, Council members discuss and vote on items included in its |
| 52 |
+agenda. They also go through bugs assigned to council@g.o and assign them to |
| 53 |
+individual Council members. |
| 54 |
+</p> |
| 55 |
+<p> |
| 56 |
+At the end of each meeting, one council member is selected to chair the next |
| 57 |
+meeting. That member is responsible for sending the next meeting |
| 58 |
+announcement and drafts of its agenda to the gentoo-project and |
| 59 |
+gentoo-dev-announce mailing lists for discussion prior to the meeting. They |
| 60 |
+are also responsible for committing the meeting's log and summary after its |
| 61 |
+completion. |
| 62 |
+</p> |
| 63 |
+</body> |
| 64 |
+</section> |
| 65 |
+</extrachapter> |
| 66 |
+ |
| 67 |
+<extrachapter position="subproject"> |
| 68 |
+<title>Meeting logs</title> |
| 69 |
+<section> |
| 70 |
+<body> |
| 71 |
<table> |
| 72 |
<tr><th>Date</th><th>Participants</th><th>AWOL</th><th>Log</th><th>Summary</th></tr> |
| 73 |
<tr> |
| 74 |
|
| 75 |
-- |
| 76 |
Alex Alexander -=- wired |
| 77 |
Gentoo Linux Developer -=- Council / Qt / KDE / more |
| 78 |
www.linuxized.com |
Archives