developer-events
developer-events copied to clipboard
Lessons Learned/Recommendations from the March 2025 Code Sprint
- Recommendation to organise sprints outside the academic period (Luis)
- OGC help envagelise OGC API Standards (Mahidhar); start with blog posts (connect with CDPG).
- Daniel: is STA in its current form the right Standard to address Time Series? Which Standard would be best suited to address vector data time series?
- Ricardo developed a tool for easing compliance assessment.
- Joao, Luis (and other people) have started a DGGS software that supports multiple grids: contributors are welcome
- Node coordination: adapting to the timezone, by starting a bit later; it was a bit difficult in the beginning, to orient, but it was a learning experience for future sprints.
- Record tutorials and provide a stream during the entire code sprint; provide more learning resources;
- Use the specialised channels to provide more specific information (even if it is a bot) , could trigger more engagement
- The number of meetings is fine, but people can create ad-hoc meetings to discuss specific topics.