Some codes in the context of the Materials Project have only been developed based on short-term funding, and long-term support is hard/impossible to guarantee.
This code might still be used in the community. One of the recent example codes is Matminer that triggered the discussion.
Decision Drivers
These codes are still useful to the community
There will likely not be any long-term funding for such codes
Considered Options
Use specific versions of the dependencies (via toml or setup.py-based installations) and then release a final version (or release candidate)
Good as the code can still be used
Bad as it might not be easy to use together with other software
Transfer code ownership to a fork outside of MP (if someone wants to take over code)
Good as the code will still be maintained
Give maintaining rights to people outside of MP
Good as more people can merge and contribute
Not clear how such a decision can be made
Ask on the repo if someone might want to take over
Good as someone else might maintain the code in the future
Connected with transferring code ownership to someone else
How to treat old (non-core) codes of MP
Context and Problem Statement
Some codes in the context of the Materials Project have only been developed based on short-term funding, and long-term support is hard/impossible to guarantee. This code might still be used in the community. One of the recent example codes is Matminer that triggered the discussion.
Decision Drivers
Considered Options
Use specific versions of the dependencies (via toml or setup.py-based installations) and then release a final version (or release candidate)
Transfer code ownership to a fork outside of MP (if someone wants to take over code)
Give maintaining rights to people outside of MP
Ask on the repo if someone might want to take over
Decision Outcome
Implementation Plan
More Information