Last meeting: https://github.com/SpaceApi/meeting-notes/blob/master/20191022-telco.md
- Website refactoring
- Milestones for 0.14 release
- Core vs. Community, where do which projects belong?
All participants of the meetup have general interest in a Geekend.
Sva had a sugestion for a location: A house near Rapperswil which we could use. Coredump itself would be backup location if it doesn't work out.
End of March beginning of April. Avoid conflicts with other events:
- 2020-03-21 spring(); break; Bochum
- 2020-04-12 Easterhegg
Suggestions: 27.03.-29.03.
Responsible Person: @rnestler
Bring community together. Involve people.
- Invite community
- Agenda
- Organize Food / Drinks
- Release process for schema
- Semver?
- What defines a breaking change
See https://content-refactor.spaceapi.io/ PR: SpaceApi/website#66
Feedback so far:
- Docs not found
- API docs are harder to find than before
It's hard to find out if people who heard about it the first time understand what the project is about.
Let's merge it as soon as possible and iterate afterwards.
@rnestler got the feedback that a "news" section or activity log is missing. So the project seems dead for some. It would be nice to have something blog-like where we note stuff like:
- Meetings with link to protocol
- Wrap-up on Directory changes (3 new space added in the last month)
- Anouncment of events (Geekend for example)
- Sum up work on new schema version
- Link to GitHub already provides some activity log
What hinders us to do the release?
- Add a document on upgrading and being compatible with both versions.
- Cleanup the CHANGELOG
- Update App to be compatible with pure 0.14
Where do which projects belong? We will discuss it in a later meeting.
Seems broken?
Should we decentralize the directory? One simple idea would be to just add a possibility to link to other SpaceAPI endpoints. So one could discover all endpoints by recursivly following the links.