Differences between revisions 1 and 5 (spanning 4 versions)
Revision 1 as of 2007-06-13 00:20:04
Size: 2439
Comment: init
Revision 5 as of 2009-03-16 03:33:58
Size: 2645
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= DebianEdu/CipUX/Meeting/20070618 = ## page was renamed from DebianEdu/CipUX/Meeting/20070618
= CipUX/Meeting/20070618
=
Line 9: Line 10:
  * '''Preceeding of CipUX''' (''XavierOswald'')   * '''Preceeding of CipUX II''' (''XavierOswald'')
Line 19: Line 20:
  [:DebianEdu/CipUX/Meeting/20070618/log]   [[CipUX/Meeting/20070618/log]]
Line 23: Line 24:
  [:DebianEdu/CipUX/Meeting/20070618/Summary]   [[CipUX/Meeting/20070618/Summary]]
Line 36: Line 37:
If you do not use CR or Linefeed, it is much more readable. If you '''do not use CR or Linefeed''', it is much more readable.
Line 48: Line 49:
4) [ ] find log provider 4) [ ] set topic to CipUX meeting 200X-YY-ZZ in progress ...
Line 50: Line 51:
5) [ ] find summary writer 5) [ ] find log provider
Line 52: Line 53:
6) [ ] ask for self introduction /me = first name last name 6) [ ] find summary writer
Line 54: Line 55:
7) [ ] announce each topic 7) [ ] ask for self introduction /me = first name last name
Line 56: Line 57:
8) [ ] make sure that the report is finish 8) [ ] announce each topic (from meeting page)
Line 58: Line 59:
9) [ ] ask some further question, if no question on the report is ask, and if further question will enlighten the report 9) [ ] make sure that the report is finish
Line 60: Line 61:
10) [ ] announce next topic 10) [ ] ask some further question, if no question on the report is ask, and if further question will enlighten the report
Line 62: Line 63:
11) [ ] last topic: Next meeting 11) [ ] announce next topic
Line 64: Line 65:
12) [ ] remind log provider 12) [ ] last topic: Next meeting
Line 66: Line 67:
13) [ ] remind summary writer 13) [ ] remind log provider
Line 68: Line 69:
14) [ ] say thanks to the community 14) [ ] remind summary writer
Line 70: Line 71:
15) [ ] create next meeting page, as a copy of the last 15) [ ] say thanks to the community
Line 72: Line 73:
16) [ ] if you found something missing on this checklist enhance it! 16) [ ] create next meeting page, as a copy of the last page

17
) [ ] if you found something missing on this checklist enhance it!
Line 76: Line 79:

Starting:
Line 82: Line 87:
What to use:
Line 83: Line 90:
 * point (3) is for the meeting relevant not for the summary, exceptions possible  * point (1) can be skipped for summary, it is important for the actual flow of the meeting, exceptions possible
 * point (2) is most important, then point (3)
 * point (3) can be used for Todo list and what people say during the meeting

How to write:

 * 3rd pers. singular, not first person (Example: change "I" to "Xavier" or "he")
Line 85: Line 98:
 * 3rd pers. singular, not first person (Example: change "I" to "Xavier" or "he")

* try to focus on interesting points
* point (2) is most important

 * add a Todo point table of tasks (see [DebianEdu/CipUX/Meeting/20070611/Summary])
 * point (3) is interesting for Todo and what people say during the meeting






 * try to focus on interesting points of (2)
 * add a Todo point table of tasks (see [CipUX/Meeting/20070611/Summary])

CipUX/Meeting/20070618

Meeting for Coordination Features and Projects on #cipux

Monday 20:00h CET

Agenda:

  • Preceeding of CipUX II (XavierOswald)

  • Weekly Report on CipuxPHP (?JeanCharlesSiegel & ?ChristopheGoessen)

  • Setting up CipUX Infrstructure (?WolfgangDrotschmann)

  • CipUX Database Abstraction Layer (ChristianKuelker)

  • (?PhilippeFalvo)

  • Buildserver Lintian Warnings (JuergenLeibner)

  • (?SebiastianFriedel)

Log:

Summary:

Tip for make the meeting better: 3 points (1) .. (3)

Reports might written in advance (this save time):

  • (1) what drain my time (2) actual status of my work (main part): (3) my plan for next week

One sentence for one point would do it. If you do not use CR or Linefeed, it is much more readable.

Checklist for Moderator

0) [ ] print this section and use it as checklist

1) [ ] check meeting page

2) [ ] announce meeting page

3) [ ] announce start of meeting

4) [ ] set topic to CipUX meeting 200X-YY-ZZ in progress ...

5) [ ] find log provider

6) [ ] find summary writer

7) [ ] ask for self introduction /me = first name last name

8) [ ] announce each topic (from meeting page)

9) [ ] make sure that the report is finish

10) [ ] ask some further question, if no question on the report is ask, and if further question will enlighten the report

11) [ ] announce next topic

12) [ ] last topic: Next meeting

13) [ ] remind log provider

14) [ ] remind summary writer

15) [ ] say thanks to the community

16) [ ] create next meeting page, as a copy of the last page

17) [ ] if you found something missing on this checklist enhance it!

Hints for Summary Writer

Starting:

  • write date
  • write start time
  • write end time
  • write participants (/me = fist name last name people)

What to use:

  • use subject as section for summary, not the 3 points (1) .. (3)
  • point (1) can be skipped for summary, it is important for the actual flow of the meeting, exceptions possible
  • point (2) is most important, then point (3)
  • point (3) can be used for Todo list and what people say during the meeting

How to write:

  • 3rd pers. singular, not first person (Example: change "I" to "Xavier" or "he")
  • make it short(er)
  • try to focus on interesting points of (2)
  • add a Todo point table of tasks (see [CipUX/Meeting/20070611/Summary])