(Online) submission artifact

[rolyp]

I think there is a strong case for a software submission along with the paper itself (as well as for the later artifact evaluation process). We could for example have an anonymised version of the spec website/running examples/playground, either hosted anonymously somewhere, or provided as an easy-to-install container. (But a reviewer is much more likely to follow a link.)

See also:

• Website with runnable examples #6
• Separate spec artifact pure-py-spec#134
• VSCode plugin pure-py-spec#141
• Test compliance against pure-py-spec repo fluid-org/fluid#1556

[rolyp]

@pure-py/purepy We should also think about having the conformance tests online in a readily usable form (i.e. perhaps slightly more accessible than just navigating to the GitHub repo). There's a Fluid issue (linked above) to get this working to test Fluid's PurePy compliance. (Maybe it's just a question of treating the tests as a versioned artifact so we're always testing against a known version.)