Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy policy file #207

Closed
jryans opened this issue Aug 29, 2019 · 9 comments

Comments

@jryans
Copy link
Member

commented Aug 29, 2019

Now that we have terms support, we should deploy a policy file for matrix.org and vector.im installations.

After some discussion with @lampholder, we'll go though these steps:

  1. Cut a v1 release of the policies repo (to create a link between human-oriented version number and a commit)
  2. Deploy the policy file content at a versioned, language-qualified URL on each domain:
  3. Configure matrix.org and vector.im IS terms config with these URLs
  4. Optionally change existing URLs like https://vector.im/identity-server-privacy-notice to redirect to the versioned URL
@lampholder

This comment has been minimized.

Copy link
Contributor

commented Aug 30, 2019

Cut a v1 release of the policies repo (to create a link between human-oriented version number and a commit)

I don't know if this will work with the repo in its current structure, because the different documents are theoretically different versions :\

@jryans

This comment has been minimized.

Copy link
Member Author

commented Aug 30, 2019

I don't know if this will work with the repo in its current structure, because the different documents are theoretically different versions :\

Well, the version is just an incrementing label for what's in the policy repo at any moment... We could cut release of the repo at any time, but it means a specific document might have it's first "URL version" as v8 or something if that's the first time it appeared in a repo release. Maybe that's okay...?

Otherwise, we could:

  • Use a commit hash in the URL
  • Give up and use manually crafted versions for each document that we will probably get wrong later
@turt2live

This comment has been minimized.

Copy link
Member

commented Aug 30, 2019

commit hash sounds great imo: the version is an arbitrary string anyways.

@lampholder

This comment has been minimized.

Copy link
Contributor

commented Sep 2, 2019

The thing is we'll certainly want to make changes to the document without forcing anyone to re-accept the terms - fixing typos, etc. So a commit hash is a bit restrictive :(

@jryans

This comment has been minimized.

Copy link
Member Author

commented Sep 2, 2019

If we want to craft a manual version to only trigger re-acceptance for "meaningful" changes, maybe we can put the text "Version 1" or similar in the document itself, and then policy authors can bump that when changes should trigger re-acceptance...? Then whoever deploys the policy can clearly see what version should be in the URL, since it's in the same document as the text.

@turt2live

This comment has been minimized.

Copy link
Member

commented Sep 2, 2019

tag it as a release on github and use that branch name as the version? I assume part of this is figuring out how to magically make it ansible itself.

@jryans

This comment has been minimized.

Copy link
Member Author

commented Sep 25, 2019

The IS policies are live at:

I am working on configuring the ISes to apply the terms.

@jryans

This comment has been minimized.

Copy link
Member Author

commented Sep 25, 2019

Deployed on matrix.org Sydent, will do vector.im soon.

@jryans

This comment has been minimized.

Copy link
Member Author

commented Sep 25, 2019

Deployed to vector.im as well. 🎉

@jryans jryans closed this Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.