Skip to content

Update/Remove privacy level docs page #4743

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

Closed
humitos opened this issue Oct 10, 2018 · 3 comments · Fixed by #7013
Closed

Update/Remove privacy level docs page #4743

humitos opened this issue Oct 10, 2018 · 3 comments · Fixed by #7013
Labels
Accepted Accepted issue on our roadmap Needed: documentation Documentation is required

Comments

@humitos
Copy link
Member

humitos commented Oct 10, 2018

Although we are deprecating Privacy Levels in #2663 and #3781, we still expose the docs for this and it's completely broken and confuse our users.

https://docs.readthedocs.io/en/latest/privacy.html

I think we should take one of these actions:

  1. remove that page completely
  2. add a warning note saying that Privacy Levels are deprecated. Although, I think this doesn't make too much sense

Any action taken will need to write "a new documentation" page for the Corporate site, where these permission levels do work.

@humitos humitos added the Needed: documentation Documentation is required label Oct 10, 2018
@humitos humitos added this to the Better user documentation milestone Oct 10, 2018
@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jan 10, 2019
@stsewd stsewd added the Accepted Accepted issue on our roadmap label Jan 10, 2019
@stale stale bot removed the Status: stale Issue will be considered inactive soon label Jan 10, 2019
@dojutsu-user
Copy link
Member

dojutsu-user commented Jan 13, 2019

@humitos
I am +1 on the first option.
Just needed to know that does this issue needs to wait for some time or not?
I am interested in sending a PR for this.

@stsewd stsewd mentioned this issue Apr 30, 2019
16 tasks
@humitos
Copy link
Member Author

humitos commented Jul 17, 2019

We took a first step by removing the "Protected" level at #5833

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Needed: documentation Documentation is required
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants