|
1 | 1 | IRC Meetings
|
2 | 2 | ============
|
3 | 3 |
|
4 |
| -The purpose of this meeting is to discuss topics in real time with many of the Symfony2 devs. |
| 4 | +The purpose of this meeting is to discuss topics in real time with many of the |
| 5 | +Symfony2 devs. |
5 | 6 |
|
6 |
| -Anyone may propose topics on the symfony-dev mailinglist until 24 hours before the meeting, ideally including well |
7 |
| -prepared relevant information via some URL. 24 hours before the meeting a link to a `doodle`_ will be posted including |
8 |
| -a list of all proposed topics. Anyone can vote on the topics until the beginning of the meeting to define the order in |
9 |
| -the agenda. Each topic will be timeboxed to 15mins and the meeting lasts one hour, leaving enough time for at least 4 |
10 |
| -topics. |
| 7 | +Anyone may propose topics on the `symfony-dev`_ mailing-list until 24 hours |
| 8 | +before the meeting, ideally including well prepared relevant information via |
| 9 | +some URL. 24 hours before the meeting a link to a `doodle`_ will be posted |
| 10 | +including a list of all proposed topics. Anyone can vote on the topics until |
| 11 | +the beginning of the meeting to define the order in the agenda. Each topic |
| 12 | +will be timeboxed to 15mins and the meeting lasts one hour, leaving enough |
| 13 | +time for at least 4 topics. |
11 | 14 |
|
12 | 15 | .. caution::
|
13 |
| - Note that its not the expected goal of them meeting to find final solutions, but more to ensure that there is a |
14 |
| - common understanding of the issue at hand and move the discussion forward in ways which are hard to achieve with |
15 |
| - less real time communication tools. |
16 | 16 |
|
17 |
| -Meetings will happen each Thursday at 17:00 CET (+01:00) on the #symfony-dev channel on the Freenode IRC server. |
| 17 | + Note that its not the expected goal of them meeting to find final |
| 18 | + solutions, but more to ensure that there is a common understanding of the |
| 19 | + issue at hand and move the discussion forward in ways which are hard to |
| 20 | + achieve with less real time communication tools. |
18 | 21 |
|
19 |
| -The IRC `logs`_ will later be published on the trac wiki, which will include a short summary for each of the topics. |
20 |
| -Tickets will be created for any tasks or issues identified during the meeting and referenced in the summary. |
| 22 | +Meetings will happen each Thursday at 17:00 CET (+01:00) on the #symfony-dev |
| 23 | +channel on the Freenode IRC server. |
| 24 | + |
| 25 | +The IRC `logs`_ will later be published on the trac wiki, which will include a |
| 26 | +short summary for each of the topics. Tickets will be created for any tasks or |
| 27 | +issues identified during the meeting and referenced in the summary. |
21 | 28 |
|
22 | 29 | Some simple guidelines and pointers for participation:
|
23 | 30 |
|
24 |
| - * Its possible to change votes until the beginning of the meeting by clicking on "Edit an entry" |
25 |
| - * At doodle will be closed for voting at the beginning of the meeting |
26 |
| - * Agenda is defined by which topics got the most votes in the doodle, or whichever was proposed first in case of a tie |
27 |
| - * At the beginning of the meeting one person will identify him/herself as the moderator |
28 |
| - * The moderator is essentially responsible for ensurign the 15min timebox and ensuring that tasks are clearly identified |
29 |
| - * Usually the moderator will also handle writing the summary and creating trac tickets unless someone else steps up |
30 |
| - * Anyone can join and is explicitly invited to participate |
31 |
| - * Ideally one should familiarize oneself with the proposed topic before the meeting |
32 |
| - * When starting on a new topic the proposer is invited to start things off with a few words |
33 |
| - * Anyone can then comment as they see fit |
34 |
| - * Depending on how many people participate one should potentially retrain oneself from pushing a specific argument too hard |
35 |
| - * Remember the IRC `logs`_ will be published later on, so people have the chance to review comments later on once more |
36 |
| - * People are encouraged to raise their hand to take on tasks defined during the meeting |
| 31 | +* It's possible to change votes until the beginning of the meeting by clicking |
| 32 | + on "Edit an entry"; |
| 33 | +* The doodle will be closed for voting at the beginning of the meeting; |
| 34 | +* Agenda is defined by which topics got the most votes in the doodle, or |
| 35 | + whichever was proposed first in case of a tie; |
| 36 | +* At the beginning of the meeting one person will identify him/herself as the |
| 37 | + moderator; |
| 38 | +* The moderator is essentially responsible for ensuring the 15min timebox and |
| 39 | + ensuring that tasks are clearly identified; |
| 40 | +* Usually the moderator will also handle writing the summary and creating trac |
| 41 | + tickets unless someone else steps up; |
| 42 | +* Anyone can join and is explicitly invited to participate; |
| 43 | +* Ideally one should familiarize oneself with the proposed topic before the |
| 44 | + meeting; |
| 45 | +* When starting on a new topic the proposer is invited to start things off |
| 46 | + with a few words; |
| 47 | +* Anyone can then comment as they see fit; |
| 48 | +* Depending on how many people participate one should potentially retrain |
| 49 | + oneself from pushing a specific argument too hard; |
| 50 | +* Remember the IRC `logs`_ will be published later on, so people have the |
| 51 | + chance to review comments later on once more; |
| 52 | +* People are encouraged to raise their hand to take on tasks defined during |
| 53 | + the meeting. |
37 | 54 |
|
38 | 55 | Here is an `example`_ doodle.
|
39 | 56 |
|
40 |
| -.. _doodle: http://doodle.com |
41 |
| -.. _logs: http://trac.symfony-project.org/wiki/Symfony2IRCMeetingLogs |
42 |
| -.. _example: http://doodle.com/4cnzme7xys3ay53w |
| 57 | +.. _symfony-dev: http://groups.google.com/group/symfony-devs |
| 58 | +.. _doodle: http://doodle.com |
| 59 | +.. _logs: http://trac.symfony-project.org/wiki/Symfony2IRCMeetingLogs |
| 60 | +.. _example: http://doodle.com/4cnzme7xys3ay53w |
0 commit comments