-
Notifications
You must be signed in to change notification settings - Fork 37
Developer calls
Leif Denby edited this page Jun 24, 2024
·
5 revisions
Next meeting will be 1400 CEST on https://liu-se.zoom.us/j/62128717764?pwd=QnYyRVFOeEtQZHJGSEpHUlJBcTlNZz09
- Progress towards next tagged version (v0.2.0): How close are we? When do we expect to have this complete?
- https://github.com/mllam/neural-lam/pulls?q=milestone%3Av0.2.0
- @leifdenby will complete PR this week and ask for reviews
- Discussion for following release (v0.3.0): Are all changes we want included, or are some missing? How are discussions progressing?
- https://github.com/mllam/neural-lam/pulls?q=milestone%3Av0.3.0
- likely that zarr-reading will be merged in first, generalising graph construction will be based on this
- discussion around graph construction (e.g. work in https://github.com/mllam/neural-lam/issues/4) will continue on weather-model-graphs
- Longer term: Are you working on anything not currently on the roadmap? Is there something in neural-lam that you are missing? Are you working on something, but not sure how to fit it into neural-lam?
- (we didn't have time to discuss this item)
- Is there a need for some more defined roles around the Neural-LAM codebase (e.g. "maintainers", "core developers"). And if so, who should have these roles?
- no strict roles for now, we want to motivate people to review things they have interest and understanding in. Please tag people you think have an interest. @leifdenby is happy to do reviews in general, and ... (feel free to add yourself here)
- What do we require for merging PRs? An ok from one or multiple such "maintainers"?
- we agreed that nothing will be merged without being on the roadmap
- to get things on the roadmap we will use the develop calls to discuss and adapt the roadmap, please come to the developer calls to explain your idea so we can build the thing you need together 😄
- AOB
- next meeting 1400 CEST 5 august 2024