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

Where to put ancillary content #1246

Closed
RobDolinMS opened this issue Jun 30, 2017 · 3 comments
Closed

Where to put ancillary content #1246

RobDolinMS opened this issue Jun 30, 2017 · 3 comments
Labels

Comments

@RobDolinMS
Copy link
Contributor

Some items should live in spec and maybe some should be in their own repo(s):

  • Examples
  • Example fragments
  • Public-facing website
  • Implementations list
  • Schemas (?)
  • Registries of stuff
@czbcxy
Copy link

czbcxy commented Jul 3, 2017

good lucky

@handrews
Copy link
Member

  • Examples / example fragments should go in OAI/learn.openapis.org
  • Implementations list is already in OAI/Tooling
  • Should the registries and the rest of the non-Linux Foundation-maintained public web site move over to OAI/learn.openapis.org as well? Or is that tied to the spec enough to keep it here?
  • We currently sort-of treat this repo like a JavaScript package for deploying schemas, although I don't think it's ever actually worked that way. We also use the same JavaScript environment for PR checks and workflow automation. Since schemas are on main and we don't make spec changes there except to fix externally-broken links, theres not much benefit to keeping them here - you can't align spec and schema PRs. Should schemas be a separate JS package repo?

@handrews
Copy link
Member

No one objected to my list of where stuff goes from several months ago, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

3 participants