- Agree on a mission statement for JuliaGeo
- Can package owners veto SC decisions?
- Package can decide that it has a BDFL, who can veto an SC decision
- Website PR final decision
- Make sure all repos have branch protection
- Felix to send over a Doodle calendar (?) for availability
- Martijn to create a
steering@juliageo.orgthat will autoforward to the SC- It could forward to a mailing list created by Fabian
- Institutions with multiple members may have one person resign at their option
- Discuss in January with Joao about if he wants to be on SC
- Maybe also add Alex Gardner
- If a confidential vote is needed then send the result to steering@juliageo.org, instead of registering it.
- Steering Committee meetings should be closed, but we shouldn’t use them as a private community call.
- Discussed JuliaGeo/juliageo.github.io#7.
- What counts as a JuliaGeo package?
- Packages in JuliaGeo and packages tightly knit to the ecosystem
- Authors of packages could put their package under the JuliaGeo governance
- JuliaGeo Affiliated: Rasters, DiskArrays (weak affiliation), DimensionalData (weak affiliation), JuliaClimate (?)
- The website is for users, so e.g. Rasters should really be up top
- If you cannot recommend anything outside JuliaGeo, then you create a walled garden as opposed to being open.
- We need a mission statement we can take seriously