Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Define the term "open source" #2732

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

blacklight447
Copy link
Member

@blacklight447 blacklight447 commented Aug 23, 2024

@blacklight447 blacklight447 changed the title Update criteria.md Define PrivacyGuides's definition of the term "Open source". Aug 23, 2024
@blacklight447 blacklight447 added the c:enhancements new features or other enhancements to the website itself label Aug 23, 2024
@blacklight447 blacklight447 self-assigned this Aug 23, 2024
@privacyguides-bot
Copy link
Collaborator

This pull request has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/what-does-privacy-guides-see-as-opensource/20230/43

Copy link

github-actions bot commented Aug 23, 2024

Your preview is ready!

Name Link
🔨 Latest commit 93bed9e
😎 Preview https://2732--glowing-salamander-8d7127.netlify.app/

@blacklight447
Copy link
Member Author

If we move forward with this, we should overlook all pages with opensource requirements and check the currently listed software

@@ -5,7 +5,7 @@ title: General Criteria
Below are some general priorities we consider for all submissions to Privacy Guides. Each category will have additional requirements for inclusion.

- **Security**: Tools should follow security best-practices wherever applicable.
- **Source Availability**: Open-source projects are generally preferred over equivalent proprietary alternatives.
- **Source Availability**: Open-source projects are generally preferred over equivalent proprietary alternatives. Our definition of Open-source follows the [OSI definition](https://opensource.org/osd). Licenses not under the OSI are allowed as long as they are compatible with the OSI definition. The Open-source part is only mandatory for pages with "Open-source" as a minimum requirement.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed not making this change in #2727 (comment)

Copy link
Member Author

@blacklight447 blacklight447 Aug 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its only a draft of what I think will be the final decision, theres a reason im not asking for reviews yet ;p

(About those comments you linked to, I didnt see those yet.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I was more saying in the comment I linked is that regardless of the final decision, I'm not sure this is the best place on the website to expand on these details.

@dngray dngray marked this pull request as draft August 25, 2024 05:02
@privacyguides-bot
Copy link
Collaborator

This pull request has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/change-criteria-for-front-ends/20555/2

@jonaharagon jonaharagon changed the title Define PrivacyGuides's definition of the term "Open source". docs: Define the term "open source" Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:enhancements new features or other enhancements to the website itself
Projects
Status: Unreviewed
Development

Successfully merging this pull request may close these issues.

4 participants