mirror of
https://github.com/privacyguides/i18n.git
synced 2025-08-04 23:21:07 +00:00
2.1 KiB
2.1 KiB
title
title |
---|
General Criteria |
Below are some general priorities we consider for all submissions to Privacy Guides. 每个类别都会有额外的纳入要求。
- Security: Tools should follow security best practices wherever applicable.
- Source Availability: Open-source projects are generally preferred over equivalent proprietary alternatives.
- Cross-Platform Availability: We typically prefer recommendations to be cross-platform to avoid vendor lock-in.
- Active Development: The tools that we recommend should be actively developed. Unmaintained projects will be removed in most cases.
- Usability: Tools should be accessible to most computer users. An overly technical background should not be required.
- Documentation: Tools should have clear and extensive documentation for use.
财务披露
我们不通过推荐某些产品赚钱,我们不使用联盟链接,我们也不为项目捐赠者提供特殊考虑。
开发商自行提交的资料
我们对希望提交其项目或软件供审议的开发者有这些要求。
-
Must undergo our self-submission process as a way to engage with our community, address any potential concerns, and elicit any feedback that can help improve your project.
-
必须披露隶属关系,即您在提交的项目中的职位。
-
Must have a security whitepaper if it is a project that involves the handling of sensitive information like a messenger, password manager, encrypted cloud storage, etc.
- Regarding third party audit status, we want to know if you have undergone one, or have requested one. 如果可能,请说明谁将进行审计。
-
必须解释该项目在隐私方面带来了什么。
- What new problem(s), if any, does it solve?
- 为什么有人要使用它而不是其他的东西呢?
-
必须说明其项目的确切威胁模式是什么。
- 潜在的用户应该清楚地知道该项目能提供什么,以及不能提供什么。 Ideally, a developer should be able to identify what common threat(s) their project protects against.