Website should maintain neutrality by treating all spec implementations equally

[chlins]

Thank you for your work on establishing ModelPack as an open standard for AI/ML packaging. As a collaborative project, I wanted to share some constructive feedback regarding the current website presentation.

I noticed that the "Reference Implementations" section prominently features KitOps as what appears to be the primary implementation, with detailed feature listings and installation instructions occupying significant real estate on the homepage. While I absolutely appreciate KitOps's contributions and maturity as an implementation, this presentation raises some concerns about the neutrality expected of a vendor-neutral specification project.

For an open standard specification to maintain its integrity and community trust, I believe we should:

1. Keep the specification distinct from implementations - The spec should stand on its own merit, with implementations treated as separate entities that happen to conform to the standard

2. Avoid appearing to endorse specific implementations - Prominent placement with detailed feature lists and installation guides could be perceived as official endorsement, potentially discouraging other implementers or creating confusion about the project's scope

3. Provide equal visibility to all conformant implementations - If we list implementations, perhaps a neutral "Implementations" page with a comprehensive list of all projects (current and future) would be more appropriate

Suggested approach:

• Keep the homepage focused on the specification itself - its benefits, use cases, and technical details
• Create a separate "Implementations" or "Ecosystem" page listing all conformant projects with equal treatment
• Allow each implementation to be presented with equal weight, perhaps in alphabetical order or by maturity level with transparent criteria

This approach would reinforce ModelPack's position as a truly open, vendor-neutral standard while still acknowledging the valuable work of all implementing projects, including KitOps.

I hope this feedback is received in the collaborative spirit intended. Looking forward to continued discussion on how we can best serve the community.

[aftersnow]

I agree, ModelPack is an open and vendor-neutral specification project. We need to focus on aspects like transparency, how to participate, adoption, roadmap, and technical details. Like https://opencontainers.org/.

I suggest we remove all the vendor-specific parts on the homepage:

1. Remove the Reference Implementations part or make it a separate page.

2. Remove the Support part from the homepage and only keep the Adoptions part. Since ModelPack is a specification, it doesn't really need Support. What needs support are the Reference Implementations, so Support can be added on the separate Reference Implementations page, corresponding to each specific implementation.

[sabre1041]

Many of the concerns are associated with #3 which will create a separate page for the enterprise options