The FOMS meeting is a two-day event.
Morning: Short "four slide" position statements in the morning, with each project identifying their work and current challenges.
We start with position statements and a 'getting to know you' section at the beginning of the meeting. This introduces everyone and gets the group on the same page. There will be regular breaks, as it's not wildly interactive if there are lot of projects presenting. The position statements are done with a standardised four slide deck, respectively:
- Focus and activity - describe the areas that your organisation is focusing and working on. This will put your goals and contributions in context for other participants.
- Problem areas - describe problems that your organisation has encountered, things that are not working or not available. These items will contribute to a gap analysis and areas for further discussion.
- Dependencies - describe the organisations, projects and components that your organisation depends on. This helps everyone understand the map of the community.
- Next steps - suggest concrete goals and objectives that you wish to see followed.
Afternoon: topic identification and breakout, or longer in-depth presentations about the details of important bits of architecture.
Forward looking, start with some 20 minutes "what could be" presentations in the morning, have focused workshops, fixits in the afternoon, time to address the issues identified on the first day to go off in smaller groups and code away.
Melbourne at night - Photo by mugley