Something to signal the level of maturity of tools is needed. As it is now we have a mix of (more or less) abandoned repositories, experimental code and production grade code.
Without this distinction it's more difficult than it should be for newcomers to get started. The overall impression of Eiffel suffers.
Exemplification
When users deploying RemRem,, they ran into a number of unexpected problems. Refer to the issues filed in eiffel-remrem-generate and eiffel-remrem-publish.
Benefits
Having information about the status of projects upfront makes it easier for potential users to estimate the effort needed for deployment.
Possible Drawbacks
If we're not careful it might give the wrong impression and make users hesitant to try out, and contribute to, the development of new tools.
Description
Something to signal the level of maturity of tools is needed. As it is now we have a mix of (more or less) abandoned repositories, experimental code and production grade code.
This issue is about applying sandbox badge as described in project lifecycle document.
Motivation
Without this distinction it's more difficult than it should be for newcomers to get started. The overall impression of Eiffel suffers.
Exemplification
When users deploying RemRem,, they ran into a number of unexpected problems. Refer to the issues filed in eiffel-remrem-generate and eiffel-remrem-publish.
Benefits
Having information about the status of projects upfront makes it easier for potential users to estimate the effort needed for deployment.
Possible Drawbacks
If we're not careful it might give the wrong impression and make users hesitant to try out, and contribute to, the development of new tools.