Format

same page. There will be regular breaks, as it's not wildly interactive if there are lot of organisations/projects presenting. The position statements

1st Day

Morning: Short "four slide" position statements in the morning, with each group identifying their work and current challenges they're facing.

Position Statements

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. Regular breaks are recommended, as it's not wildly interactive if you have a lot of organisations/projects presenting. The position statements are done with a standardised four slide deck, respectively:

1. 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.
2. 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.
3. Dependencies - describe the organisations, projects and components that your organisation depends on. This helps everyone understand the map of the community.
4. 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.

2nd Day

Forward looking, start with some 40 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 hack away.

2nd day: forward looking, start with some 40 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 hack away.

1st day: short "four slide" position statements in the morning, with each group identifying their work and current challenges they're facing. Afternoon will be topic identification and breakout, or longer in-depth presentations about the details of important bits of architecture.

1st day: short "four slide" position statements in the morning, with each group identifying their work and current challenges they're facing.

2nd day: forward looking, start with some 40 minutes "what could be" presentations in the morning, have focused workshops, fixits in the afternoonty of time to address these issues to go off in smaller groups and hack away.

The first morning will concentrate on short "four slides" position statements, with each group identifying their work and current challenges they're facing. The second will consist of longer, 40 minute talks, presenting targets we'd like to achieve.

Shoot away with your topic/talk proposals on the foms mailing list or directly add it to the program plan.

1st day:

2nd day: forward looking, start with some "what could be" presentations in the morning, have focused workshops, fixits in the afternoonty of time to address these issues to go off in smaller groups and hack away.

The FOMS meeting is a two-day event.

Shoot away with your topic/talk proposals on the foms mailing list or directly add it to the program plan.

OMSDEM is a two-day event.

We will collect topics and talk proposals over the next few weeks (DEADLINE: 31st October).

The plan is to have two large topics each day, one in the morning and one in the afternoon, which each will consist of several smaller talks during which software is presented, and issues (bugs, feature requests, API design etc) are brought up and discussed. There will also be plenty of time to address these issues to go off in smaller groups and hack away.

Shoot away with your topic/talk proposals on the omsdem mailing list or directly add it to the program plan.