What does Privacy Guides see as OpenSource?

The issue is complex because there isn’t always a lot of choices in softwares or platforms to be used. This topic comes to mind:

I would love to have a straight criteria list for all tools, but it’s simply not possible. There are some category of products that are much more mature then others.

I think the approach being used right now on PG, to have a per category criteria, makes the most sense.

There could also be a logic applied across the site like when a category is mature enough, meaning it has many options, audits, FOSS options, etc., THEN the category criteria gets stricter.

There could be a category maturity level, that isn’t necessarily apparent to the user, but managed by PG internally.

Edit: to develop more on the maturity level:

Level 1 Maturity - not a lot of options:

  • Source Available requirement
  • Criteria 2
  • Criteria 3, etc.

Level 2 Maturity - more options:

  • Source-first requirement
  • Criteria 2
  • Criteria 3, etc.

Level 3 Maturity - even more options:

  • FOSS requirement
  • Audited by whatever authority that makes sense
  • Criteria 3, etc.