Jan Ainali

This has been prioritized for work during the summer.

> We can also consider the option of linking to archive.org if something is not reliably available. > > e.g.: > http://web.archive.org/web/20201027095103if_/https://www.youtube.com/watch?v=QWt6vB-cipE&gl=US&hl=en Perhaps we should give some priority to #275...

I don't think we want breadcrumbs, we should remove it

Now, two years later, I think that the glossary entries are uniform enough to not call for a complete overhaul. Rather, I think that small improvements can be made per...

Now that we have the Implementation guide, specifically made to highlight really nice examples, we should move this sentence there. We could still improve the sentence, but optimize it for...

Is this a possible phrasing? > A codebase MUST NOT have functionality using features from a standard that is not an open standard unless it is only in addition to...

> > Use of a standard which is not open MUST NOT hinder collaboration or reuse. I think this is in the right direction!

Should we put that before the Table of contents or try to bake it into the introduction?

Me and @ericherman was thinking about this in publiccodenet/about#414 and were thinking that the actual examples would fit better in about rather than in the standard itself. When we have...

I think this is a great observation, and I like the direction of your suggestion. How about: > The codebase MUST include instructions for how to privately report security issues...