opengeospatial/ogcapi-coverages

Organization of a February 2024 OGC API - Coverages Virtual Code Sprint

Closed this issue · 10 comments

The SWG discussed today that there would be interest in hosting a 3 days virtual code sprint for OGC API - Coverages in February 2024, tentatively the week of the 12th.

The effort would continue the good implementation momentum from Testbed 19 GDC API Technology Integration Experiments, and provide validation for the latest OGC API - Coverages candidate standard, which we hope will be in the Request for Comments period at that time.

This will be a SWG Code Sprint, organised by SWG Members, and open to the general public.

  • SWG/DWG Chair identifies a date for the code sprint. The code sprint will be held from Tuesday, February 13th to Thursday, February 15th, 2024.
  • SWG/DWG Chair identifies a mode for the code sprint, if it is to be a hybrid event. This will be a virtual-only code sprint.
  • At least 3 months before the envisioned event date, the SWG/DWG Chair submits an Event Request to the OGC Event Manager.
  • OGC Staff discuss the proposed sprint schedule and together deconflict the event from other OGC event
  • OGC Staff confirm the dates have been reserved for the code sprint
  • SWG/DWG Chair identifies SWG Member to serve as SWG Event Organizer. Jerome St-Louis confirmed as the SWG Event Organizer.
  • SWG Event Organizer prepares initial draft announcement for Press Release.
  • OGC DPM adds the Sprint to the OGC API Website (if sprint involves OGC APIs).
  • SWG Event Organizer populates the GitHub wiki page on the developer-events repository.
  • SWG Chair reviews and approves the announcement for Press Release .
  • OGC DPM or DevRel reviews and approves the announcement for Press Release.
  • SWG Event Organizer prepares registration page on the ogcapi-coverages GitHub repo
  • SWG Event Organizer confirms communication platforms for the event. .
  • SWG Event Organizer sends out 1st notification to participants, with logistics details (one month before sprint)
  • SWG Event Organizer sends out 2nd notification to participants, with logistics details (two weeks before sprint)
  • SWG Event Organizer sends proposals for social media posts to the OGC Communications Manager (two months before)
  • All SWG members spread the word about the event among their contacts
  • SWG Event Organizer sends out Final notification to participants, with logistics details (1 day before sprint)
  • Hold the Sprint event

The OGC API - Coverages Virtual Code Sprint would have to be before 26 February to avoid clashing with the next Joint OGC ASF OSGeo Code Sprint.

@ghobona Yes this is why we tentatively suggest the week of the 12th (though this makes it less than 3 months away, can that still be ok?)

@jerstlouis I have just connected you with OGC's Event Manager via email so that the dates can be checked for calendar conflicts.

@jerstlouis Here is a example announcement from the OGC API - Processes Virtual Code Sprint https://www.ogc.org/press-release/developers-invited-to-the-2023-ogc-api-processes-virtual-code-sprint/

Thanks a lot @ghobona we'll start with that.

Hoping to make progress on some of the other SWG Event Organizer items as well today.

@jerstlouis I tried to add myself to the wiki page here, but I don't have write permissions on this repo. Not sure if anyone else who is not a committer here, tried to register.