Skip to content

Added 'Privacy and Security Considerations' section to CSS Bikeshed Module #241

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

Merged
merged 2 commits into from
Jun 27, 2016

Conversation

SebastianZ
Copy link
Contributor

No description provided.


<h2 class=no-num id=priv-sec>Privacy and Security Considerations</h2>

Make some considerations about privacy and security.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about making this “Make some considerations about privacy and security.” into an issue, to make sure it doesn't get forgotten?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a strong opinion about that, but there is no other issue marking a 'must edit'.

Sebastian

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, adding this to the template only serves to silence a Bikeshed warning telling you you need to write this part. If we replace the warning with an issue in the spec, that's fine, but there was a reason for that warning: this is a part of the spec that is at risk of being forgotten unless you are explicitly reminded about.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That it can be easily forgotten is one reason I opened issue #240.
Obviously very few editors actually added this section to their specs so far. So it seemed to me the Bikeshed warning is not enough and I was wondering about how to push people more to add that section.

It's ok for me to add an issue instead, though before I do that I'm asking about this at #240 (comment).

Sebastian

@tabatkins tabatkins merged commit 0f0e29f into w3c:master Jun 27, 2016
@SebastianZ SebastianZ deleted the issue-240 branch June 28, 2016 05:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants