Mechanics to publish EDs separately from releases

[kjetilk]

I don't find it terribly appealing to effectively use directories (like https://github.com/solid/specification/tree/main/2021 and https://github.com/solid/specification/tree/main/ED ) to what is actually a version control task. This is quite likely to lead to a messy situation where we end up committing stuff to the wrong directory. We should use version control for version control tasks.

And I believe we should prioritize that so thus this issue.

Eventually, there's consensus that we should have this write to a Solid server, but if that can't be done right away, I believe we should look into a fix even for the short term.

[kjetilk]

Posted this: https://github.community/t/publishing-several-versions-of-a-page-using-releases/219874

[kjetilk]

The response was:

This is not something we support today.

So, there goes my short term solution. Which leaves us with the solution of publishing to a Solid server.

[elf-pavlik]

I think you should be able to achieve it with github actions. When you tag a new release it could get auto deployed to gh-pages or solid server (given authn/authz can be sorted out).

[kjetilk]

Depends on solid/team#3

[elf-pavlik]

Solid-OIDC now has a GitHub action to automate the creation of snapshots from the ED, it was added in solid/solid-oidc#100 It gets triggered based on a specific pattern in the tag: https://github.com/solid/solid-oidc/#releasing-a-new-solid-oidc-draft-report

At this moment it doesn't address publishing to solidproject.org but it can be extended once a clear workflow gets established.