PRISM-Break is largely driven by community participation in discussions
surrounding the inclusion or exclusion of various solutions. Given that
user privacy is (by definition) a very personal matter and that the
security community in general tends to have strong opinions, my
observation is that many issues that come up are fairly highly changed
even before somebody looses their cool or makes a nasty remark.
I think it would behoove the project to officially adopt a Code of
Conduct document that can be considered binding on participants in
discussion. Getting this into the repository early before any particular
major issue between participants comes up gives everybody something to
reference and a relative standard by with to judge a situation. This
could potentially save some grief vs. the possibility of working out the
details of such a code in the middle of a disputed discussion.
The Open Code of Conduct seems like a likely candidate. I'm not a huge
fan of some of the items as worded but for this project I think it will
be fine. See http://todogroup.org/opencodeofconduct/ for details.
Startpage
This commit also changes "It also provides [...]" in the "notes" section
for Startpage to "Ixquick also provides [...]" so that there's less
confusion as to which project provides the service, despite the name of
the service giving it away anyway.
Ref #1376.
After this change, the only differences (I think) left are:
1. "fr-projects.json" has Wikipedia urls for the "Disconnect",
"EtherCalc" and "Kamailio" projects, which no other locale has.
2. "zh-CN-projects.json" has translations for the "I2P" and "Ixquick"
projects' "notes" section, which no other locale has, as introduced
by b5495f7 from #932.
- Notice that in the diff of b5495f7, the "notes" section for both
these projects were empty before the change.
3. "fi-projects.json" has a translation for the "Off-the-Record
Messaging" project's "notes" section, which no other locale has, as
introduced by 1bd7801 from #1177.
- Notice that in the diff of 1bd7801, the "notes" section for this
project was empty before the change.
1 however should not be a problem because it does not look like there
are Wikipedia articles for these projects under any other language,
including English.
Note that this change does not actually check for *outdated*
translations (obviously). This change has only checked if a string type
key is empty when it should not be, or if an array type key (i.e.
"protocols" and "categories") is not equal to the rest of the keys from
all the other locales.
