Organization of the September 2023 OGC API - Processes Virtual Code Sprint
ghobona opened this issue · comments
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 18 to 20 September.
- 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. @bpross-52n confirmed as the SWG Event Organizer during the 2023-06-26 SWG telecon.
- SWG Event Organizer prepares initial draft announcement for Press Release.
- OGC DevRel adds the Sprint to the OGC Developer Website.
- 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-processes GitHub repo (for example, this one. )
- SWG Event Organizer updates the Agenda with names of speakers.
- SWG Event Organizer invites SWG members to be Stream Leaders and/or Mentors.
- SWG Event Organizer confirms communication platforms for the event. (Preference stated on 2023-06-26 as Gotomeeting and Gitter).
- 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
Notes from 2023-06-26 SWG telecon
- @ghobona to provide @bpross-52n with a template for Press Releases announcing code sprints.
- @doublebyte1 to confirm location of the landing site. Confirmed.
- @bpross-52n to identify some suitable free-to-use graphics from Unsplash . To send the suggestions to the OGC Marketing Team. Deadline July 3rd, 2023.
Agreement: The sprint will use the ogcapi-processes repository (https://github.com/opengeospatial/ogcapi-processes), so that the SWG has greater control over merging of pull requests
Communications Platform
The following plan was identified as preferable to because it gives the SWG greater control over the running of the code sprint.
Plan A
- Gotomeeting would be used for the plenary sessions.
- Gitter would be used for the chat.
Plan B
- Discord
Notifications will be sent out through Gitter and/or through a GitHub Issue. The participants will be asked to Watch the specific GitHub Issue.
21-AUG-2023: Start of agenda for code sprint ...
- Introduction session where we find out what everyone is bringing to the code sprint with regard to implementations so that we get a sense of those who have implementation already versus those who will be working on one at the code sprint.
- Intro for the editor's that described the changes between 1.0 and the latest editors' Part 1 draft.
- Primary goal of the code sprint is to validate the current editors' Part 1 draft. That is to verify that it is implementable and testing the standard and also that clients can interact with servers. So the first bit is to test the standard and the second bit is to test the implementations.
- Another goal is to determine whether the current editor's draft should be a 1.X or 2.X version. If, it turns out that a single endpoint can support both the current adopted specification and the editor's draft, then that inidicates that the editor's draft should be a 1.X.
- Secondary goal is to test Part 2 (DRU) and Part 3 (workflows) as well.
- We should also try to make sure that we come to the code sprint with a substantially complete ATS.
The code sprint depends on people coming with substantial implementations already in hand. There will likely not be enough time for someone to start implementing during the code sprint.
We will not be testing the specific processes since it is likely that different implementations will make different processes available.
@pvretano
We should focus on the "echo" process since this is what the specification proposes, and also what the ATS expects. If time allows it, testing DRU for that "echo" process (redeploying it using e.g. "echo-test") would be great as well.
@pvretano @jerstlouis Please update the OpenAPI definition documents, especially the bundle version.
During the code sprint, the OGC API - Processes - Part 1: Core v2.0.0 candidate standard will be automatically built every two hours between 13:30 and 21:30 UTC.
The document can be found at https://opengeospatial.github.io/ogcna-auto-review/18-062r3.html
All, thanks for participating in the code sprint, and for the great team work.
Special thanks to @bpross-52n for serving as the SWG Event Organiser.