Hi Carsten,

On Wed, May 12, 2010 at 10:09 AM, Carsten Munk <[email protected]> wrote:
> So, one of the approaches to open development we're trying in the N900
> team is public synchronisation meetings, described at
> http://wiki.meego.com/ARM/N900#Team_synchronisation_meetings
>
> To get initially started, we need to figure out the following:
>
> * When we have our first meeting
> * With what regular intervals we have the meetings
I would suggest biweekly meetings. In my opinion monthly meetings are
too far apart and weekly meeting might be too close together (consumes
to much time). However, exceptions can always be made.

> * Who chairs the meetings (I suggest Harri?) - this also means
> operating the meeting bot controls regarding what topic is the current
> one. There's a instruction guide linked in the page.
I vote for Harri as well, if he does not have any objections.

> * If we have some standard items on the agenda for each meeting.
I think that the current blockers for the next N900 release should be
discussed to ensure that each of them would be handled properly.

>
> We need to take into consideration when the 'meeting room' is booked
> as well, http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule
Thursdays after the TSG meetings are currently free? Could this be our
"spot"? Also the timing should be selected so that most of the members
of N900 adaptation team could attend the meeting during reasonable
hours (07:00-23:00?).

>
> I have proposed on the page a free-form agenda type initially - add a
> agenda item and it will be discussed provided you show up to discuss
> yourself (team membership not needed?). And that we freeze the agenda
> 24 hours before a meeting.
>
> After each meeting, minutes would be posted from the meeting bot
> output, the agenda moved to previous meetings and new date for meeting
> set up with a blank/standard agenda.
>
> What do you think?
>
> Regards,
> Carsten Munk
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
>

Regards,
Marko Saukko
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to