Our priorities
Our current list of priorities for the development of readyforwhatsnext shape when and how we need your help.
Tag: Project
How to help
There are a number of ways you can contribute to readyforwhatsnext.
Categories:
Terms of use
readyforwhatsnext is distributed without warranties under open source licenses - we just ask you to appropriately cite it.
Categories:
Overview
About the readyforwhatsnext model.
Categories:
Getting started
What you need to know to start using readyforwhatsnext.
Categories:
The readyforwhatsnext model
readyforwhatsnext is an in-development modular economic model of the systems shaping the mental helath of young people. It is comprised of four sub-models.
Categories:
Provide advice
ready4 needs the guidance of community members, decision-makers and technical experts to shape its development.
Categories:
Contribute code
Help improve the reliability, functionality and ease of use of ready4 software.
Categories:
Contribute to our development
How to contribute to readyforwhatsnext.
Categories:
Fund projects
Help us secure our future and accelerate our development.
Categories:
Undertake projects
Plan, conduct and disseminate readyforwhatsnext modelling projects.
Categories:
Support the readyforwhatsnext community
Help develop high quality, clear and comprehensive documentation, instruction and responsive help.
Categories:
Contributor covenant (code of conduct)
To foster an inclusive and respectful community, all contributors to readyforwhatsnext are expected to adhere to the Contributor Covenant.
Categories:
Open source licensing
readyforwhatsnext is freely available to all under copy-left licensing arrangements.
Categories:
Citing readyforwhatsnext
If you find readyforwhatsnext useful, please cite it appropriately - it is easy to do!
Categories:
Disclaimer
readyforwhatsnext is distributed without any warranties.
Categories:
Priority 1: Launch a Minimum Viable Product (MVP)
We want to give potential users confidence that they can appropriately apply readyforwhatsnext to their decision problems by bringing all our existing development release and unreleased software to production release status.
Categories:
Priority 2: Maintain readyforwhatsnext
We want the readyforwhatsnext to continually improve and update in response to the needs of potential users and stakeholders.
Categories:
Priority 3: Apply readyforwhatsnext to undertake replications and transfers
We want readyforwhatsnext to be used to implement replications and transfersof the original studies for which that software was developed.
Categories:
Priority 4: Grow a user community
We want to develop a community of readyforwhatsnext users, contributors and stakeholders to sustain the development, maintenance, application, extension and impact of the project.
Categories:
Priority 5: Extend the scope of the readyforwhatsnext model
We want progressively extend the capability of readyforwhatsnext to explore new economic topics in youth mental health.
Categories:
Priority 6: Integrate readyforwhatsnext software with other open source tools
We want coders and modellers working in languages such as python to be able to readily use and contribute to readyforwhatsnext.