Our personality sets the tone for interactions within I2P platforms.
It reflects a wide variety of values from different backgrounds associated with I2P. It's vital that these values are recognizable in the external-facing software and mediums it builds and maintains.
Concise
I2P provides privacy-preserving software. As such, the project leads have a responsibility to inform users about possibilities and limitations without creating false expectations. The software is used by people with different threat models and there should be no assumptions with regards to any specific one for people using I2P. The project does not over-promise the ability of features in the software or the ease of using them is . We are aware that our tools are at time complicated and strive to help and simplify this path.
Grounded
The project understands that perfect privacy and anonymity are not attainable. It can only indicate best practices to help achieve what is possible.
Patient
We don't expect people to be of any skill level by default. I2P software and documentation should be designed and written to guide any person no matter their technical background. We value patience and empathy. It's okay to take things slowly. Doing them right is more important.
Plain Language
It is very easy to use tech jargon, but we do our best to use plain language in our documentation. Using plain and language supports ease of translation and localization efforts, and makes I2P content and tools more accessible to global audiences.
Shoalsteed
commented
2 years ago
Personality
Our personality sets the tone for interactions within I2P platforms.
It reflects a wide variety of values from different backgrounds associated with I2P. It's vital that these values are recognizable in the external-facing software and mediums it builds and maintains.
Concise I2P provides privacy-preserving software. As such, the project leads have a responsibility to inform users about possibilities and limitations without creating false expectations. The software is used by people with different threat models and there should be no assumptions with regards to any specific one for people using I2P. The project does not over-promise the ability of features in the software or the ease of using them is . We are aware that our tools are at time complicated and strive to help and simplify this path.
Grounded The project understands that perfect privacy and anonymity are not attainable. It can only indicate best practices to help achieve what is possible.
Patient We don't expect people to be of any skill level by default. I2P software and documentation should be designed and written to guide any person no matter their technical background. We value patience and empathy. It's okay to take things slowly. Doing them right is more important.
Plain Language It is very easy to use tech jargon, but we do our best to use plain language in our documentation. Using plain and language supports ease of translation and localization efforts, and makes I2P content and tools more accessible to global audiences.