Last call: don't be shy! Let's take FOSDEM as an occasion for an overall "state of the project" where we inform each other on the current status and ways forward.

All talks will be pre-recorded as Peter wrote, so no problem with timezones; but after each talk we will have a live "questions and answers" session for community talk.

Suggestions of what could be added for a more complete schedule (I won't add names, but if you recognize yourself in the description please go ahead and file a proposal immediately, as the schedule will need to be defined on 31 Dec; see https://s.apache.org/openoffice-fosdem-2021-cfp for details).

- Releases: How we do them, possible improvements, what's coming in 4.2.0

- Recruitment: ideas on how to improve it

- History of a first contribution (issues with documentation, with first build, filing patches)

- Build system migration

- MWiki current status

- Reviewing patches on Github: our policies for testing, merging...

- Website migrations away from CMS (I see a proposal by Dave, but I read it as an overview of our ancillary sites, not the two that were moved away from the CMS; the migration itself would be an interesting topic for another presentation).

- whatever you feel presenting; and no problem if it is more questions than answers.

Important: please make sure you file your presentation/event in the "Apache OpenOffice" track, as otherwise it will be easy for us to miss it when preparing the final schedule.

Answering to Matthias below:
Wouldn't it be useful to have a link to the CfP also here:
https://fosdem.org/2021/schedule/tracks/

Yes, I sent it to FOSDEM just a few minutes after sending it here, then I sent it the week after that... but apparently it was stuck in some anti-spam filter until I let them notice again and then they published the link. They fixed it about two weeks ago.

Regards,
  Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to