Encourage public demo

[Ainali]

Several times in presentations of a codebase it has become clear that they would have benefited from having a demo version available so that potential reusers can try it out, even if it is in a limited way. Should we have a MAY, or perhaps even a SHOULD, requirement about that?

[Ainali]

If we should have a requirement, I think it perhaps fit best in Document codebase objectives.

[ericherman]

Is this more of a testing requirement?

We should be able to test the running code separately from a production deployment, yes?

[Ainali]

Is this more of a testing requirement?

Not really. When I created the issue, I reflected on that people had a hard time explaining what benefits the codebase would bring and that a "show, don't tell" approach would have been better. In that sense, it kind of relates to all three requirements in Document codebase objectives.

We should be able to test the running code separately from a production deployment, yes?

Yes, but I think that might be implicitly covered by "Reviews SHOULD include running both the code and the tests of the codebase." in Require reviews of contributions.

[ericherman]

Let's find some clear examples of this to inspire implementors in other codebases