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

website: link to conformance.ipfs.tech from specs.ipfs.tech #456

Open
4 tasks
lidel opened this issue Nov 20, 2023 · 0 comments
Open
4 tasks

website: link to conformance.ipfs.tech from specs.ipfs.tech #456

lidel opened this issue Nov 20, 2023 · 0 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@lidel
Copy link
Member

lidel commented Nov 20, 2023

This is a placeholder issue for tracking follow-up tasks from ipfs/gateway-conformance#169:

  • https://conformance.ipfs.tech: replace placeholder squid with something IPFS-themed
  • Add rainbow to the dashboard, but this is not IPDX job, it is an oportunity for ipfs stewards to dogfood instructions from https://github.com/ipfs/gateway-conformance#building-the-dashboard
  • reorder implementations:
    • libraries first, products second
    • this means: boxo → kubo → rainbow → → rest (bifrost-gateway etc)
  • Link to https://conformance.ipfs.tech from https://specs.ipfs.tech
    • prior-art: we have some panels already commented-out at:

      specs/src/index.html

      Lines 23 to 58 in f54f480

      <!--
      <div class="basic-grid">
      <div class="pitch">
      <h3>High-quality open standards</h3>
      <p>
      We aim to fully define implementation behaviour and to empower anyone to build their
      own system that fits into the interplanetary ecosystem without needing to reverse-engineer
      the behavior of other implementations.
      </p>
      </div>
      <div class="pitch">
      <h3>Comprehensive test suites</h3>
      <p>
      A specification is only as useful as it is both testable and tested. We are building extensive
      test suites that allow specifications to prove their interoperability and implementations to demonstrate
      their correctness.
      </p>
      </div>
      <div class="pitch">
      <h3>Testing infrastructure</h3>
      <p>
      We build tools to support detecting interoperability issues early and often as part of CI/CD pipelines
      and to report on implementation maturity as the stack evolves so that people who build on top of the
      interplanetary stack can know what they can use in production.
      </p>
      </div>
      <div class="pitch">
      <h3>An open governance model</h3>
      <p>
      We guarantee community ownership of the standards, of the standards-production process, and of
      the infrastructure to operate it, in collective pursuit of efficient, transformative, ethical
      technology.
      </p>
      </div>
      </div>
      -->
@lidel lidel added the need/triage Needs initial labeling and prioritization label Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
No open projects
Status: No status
Development

No branches or pull requests

1 participant