Clean up text about notices #33
Conversation
draft-ietf-git-using-github.md
Outdated
| In addition to Working Group policies, notices on repositories MUST include | ||
| citations for BCPs 78 and 79 ({{!COPYRIGHT=RFC5378}}, {{!IPR=RFC8179}}) and | ||
| other IETF contribution policies. A copy or reference to the [IETF Note | ||
| Well](https://www.ietf.org/about/note-well/) is appropriate. |
There was a problem hiding this comment.
also appropriate? Or do you mean this is an appropriate way to meet the 78/79 requirements?
draft-ietf-git-using-github.md
Outdated
| need. A link to the CONTRIBUTING file from the README is advised. | ||
|
|
||
| In addition to Working Group policies, notices on repositories MUST include | ||
| citations for BCPs 78 and 79 ({{!COPYRIGHT=RFC5378}}, {{!IPR=RFC8179}}) and |
There was a problem hiding this comment.
Could we instead just mandate a reference to the note well? I think the IETF Code of Conduct and Anti-Harassment Procedures are at least as import as Copyrights and IPR, and singling out some parts of the Note Well doesn't make sense to me.
There was a problem hiding this comment.
I agree. It also simplifies this text more, so double win.
draft-ietf-git-using-github.md
Outdated
| A document editor can still use GitHub independently for documents that they | ||
| edit, even if the Working Group does not expressly choose to use GitHub. Any | ||
| such public repository MUST follow the guidelines in BCPs 78 and 79 | ||
| ({{!COPYRIGHT=RFC5378}}, {{!IPR=RFC8179}}) and bear notices to that effect. |
There was a problem hiding this comment.
can we also replace these with the note well?
There was a problem hiding this comment.
I honestly don't know.
There was a problem hiding this comment.
In that case, can we require a link to the Note Well on top of what's already required?
This consolidates text about notices in the "communicating policies"
section, which seems most appropriate.