Possible 2023 code sprints ...

[pvretano]

An issue to capture plans for code sprints in 2023. OGC has type 2 code sprints that can be organized by SWGS. All that needs to be done is to sumbit an event request with the following information ...

The Event Request would provide the following information:
• Name of the event
• Date(s) of the event, comma separated in YYYY-MM-DD format
• Start and end times for each date of the event
• Point of contact for the event (likely the SWG Event Organizer)
• Location (‘City/Town, Country’ if hybrid event or ‘Virtual’ if virtual-only)
• Scope of the events (standards covered)
• Link to a Google Doc or GitHub wiki page that presents the announcement of the event

scheduled, please submit an email to [email protected] with the subject heading: Request for Type 2 OGC Code Sprint.

Code Sprint plan is at https://portal.ogc.org/files/?artifact_id=103032

[m-mohr]

Anything planned for 2023?

[pvretano]

@m-mohr nothing yet but I think we should plan for something in the Fall ... Sept. perhaps.

[ghobona]

We are planning to hold a Type 1 Code Sprint in October. Exact dates are yet to be confirmed. Type 1 means that all OGC working groups will be invited to participate. The Sprint Plan for 2023 is available here.

[pvretano]

15-MAY-2023: So, SWG agrees that a code sprint in the Fall is what we want. Still trying to decide whether we do our own dedicated one in early Sept., join the OGC code sprint in Oct. or do both. The idea with the "both" scenario is that we start code sprint work in Sept. and then (if necessary) continue on in the Oct. code sprint.

[m-mohr]

There will also be a STAC sprint in September and we could potentially co-host, but I'm not hosting it so no promises ;-)

[pvretano]

21-AUG-2023: SWG members do not have time to organize and participate in 2 code sprints as originally planned. So the current plan is:

1. Between now and the end of Sept. the editors (@pvretano, @tomkralidis, @kalxas) will work on the document to get it ready. The technical content of the document has not changed in months so most of the work involves ATS and fixing broken references, etc.
2. The goal of the Oct. code sprint would be to validate the specification so that we can tag a release candidate by the end of Dec. and then hand it off to the OAB.

[pvretano]

16-OCT-2023 SWG MEETING: Tasks for the upcoming Oct/Nov 2023 code sprint in London UK ...

1. @kalxas @tomkralidis want to work on the ATS.
2. @tomkralidis work on federated search extension.
3. @cportele will be working on AsyncAPI for Features which would also be transferable to Records.
4. @pvretano work on Crawlable and Local Resources catalogues to validate specification

With regard to the next SWG meeting, the feeling is to cancel the scheduled SWG meeting in 2 weeks and simply let the participants at the Code Sprint meet on a flexible schedule to discuss issues ... discusson and conclusion from Code Sprint meetings related to records will be recorded (or cross linked) in this repo.

[tomkralidis]

As well, @fgravin will be attending (remote + day 3 in person) to help out on facets.

[tomkralidis]

@pvretano should we close given #321?