Differences between revisions 4 and 5
Revision 4 as of 2008-02-12 22:33:17
Size: 3269
Comment: update link
Revision 5 as of 2009-03-16 03:32:53
Size: 3271
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
  [:CipUX/Meeting/20070625/log]   [[CipUX/Meeting/20070625/log]]
Line 34: Line 34:
  [:CipUX/Meeting/20070625/Summary]   [[CipUX/Meeting/20070625/Summary]]

CipUX/Meeting/20070625

Meeting for Coordination Features and Projects on #cipux

Monday 20:00h CET

Agenda:

  • Preceeding of CipUX III (XavierOswald)

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

    • CipUX package is working?
  • Setting up CipUX Infrstructure (?WolfgangDrotschmann)

    • actual status
  • Buildserver Lintian Warnings (JuergenLeibner)

    • status about elemination of lintian warnings
    • integrating moodle-cipux package to build server
  • Weekly ReportCipUX Sarge Project (?SebiastianFriedel)

  • Documentation Project (Roland Teichert)

    • what fixes have to be done: JuergenLeibner

    • what is the status of the project
    • actual status of Rolands infrastructure.

Log:

Summary:

  • ?CipUX/Meeting/20070625/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

{{{Example:

1) [ ] check meeting page

  • (this page!)

2) [ ] announce meeting page

  • (this page!)

3) [ ] announce start of meeting

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

/topic  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)

 /topic ...

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])