Add Category Column for Adopters According to CNCF Definitions

[yada]

We propose adding a new column to identify each adopter's category to enhance clarity and ease the work of CNCF TOC and TAG members in analyzing and reporting on Microcks adopters. Categories will follow the CNCF definitions outlined:
CNCF End-User member, Another project, End-User, Service Provider or Consultancy.

This additional column is not mandatory but will help:

• Provide better visibility into the type of organizations adopting Microcks.
• Streamline analysis and reporting efforts.
• Ensure consistency and alignment with CNCF expectations.

Steps to complete this task:

• Review the existing adopter entries.
• Add a new column to the relevant file to specify the adopter category.
• Categorize each entry based on the CNCF definitions.
• Validate the updated file for consistency and formatting.

[lbroudoux]

Wouldn't that make adding new rows more complex for adopters? CNCF definitions are sometimes complex and fuzzy.

I understand we have to make this categorization for CNCF purposes but shouldn't we make it on our own, independently of the file used by adopters? I like the idea of keeping it lean and easy to understand. Is that practice adopted by other CNCF projects (using the same adopters list for both public-facing and internal CNCF purposes)?

[yada]

The first goal is to add the information ourselves for existing entries. We can help the adopter with new entries, but the definitions are very simple (see the link above). Yes, other projects have added the information in their public adopters' files, but again, this is not mandatory:

• https://github.com/litmuschaos/litmus/blob/master/ADOPTERS.md
• https://github.com/tektoncd/community/blob/main/adopters.md
• https://github.com/confidential-containers/confidential-containers/blob/main/ADOPTERS.md

I'm personally against creating another file to add this information; I do not think adopters will be reluctant to join due to this new column, but let's ask them on Discord ;-)

And let's decide what we want to do on this topic based on community feedback.