Path towards publishing climix
"Publishing climix" [and clix-meta] may be divided into two partly related components:
- decision that climix [ands clix-meta] includes the functionality we want to achieve, and has the stability and maturity we want (based on whatever tests we deem relevant) to tag a version 1.0 and make it publicly available (announcements how?)
- writing a scientific peer reviewed paper in a relevant journal.
These two components are somewhat abstract in relation to the hands-on work on issues and milestones in the two repositories. So, here follows an attempt at breaking down the two components to more tangible action items in relation to issues and milestones, etc. Clearly, it is my own views at this moment and should as such be regarded as a starting point for further development.
- As new issues are frequently raised, review them and make sure that they are assigned to the right milestone. Regularly review open issues.
- Get back on track having a schedule for milestones, and try to approximately stick to it. If this is not possible, review the schedule and update it.
Ahead of releasing version 1.0
- Review relevant issues (and pull requests) to make sure that the two repositories are in phase with each other, and stays in phase in the future.
- Make a list of functionality we want to have before releasing version 1. I.e follow up and update #194.
Towards a peer review paper
- Very concrete schedule for releasing version 1. When submitting the manuscript version 1 should be released. I.e. this is closely related to point 1 and 2.
- Outline what key components of the two repositories we want to focus on in the paper. I.e. from a scientific [/technical] point of what do we add?
- Basic online documentation should be available. Could be a just better description in the repositories themselves, or more elaborate on readthedocs.io
- We must be able to demonstrate that all indices perform produce results per the reference software (climpact 2.) for a suitable test dataset (same as delivered with climpact2).