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

documentation feedback from committee meeting #114

Open
denis-yuen opened this issue Sep 3, 2019 · 0 comments
Open

documentation feedback from committee meeting #114

denis-yuen opened this issue Sep 3, 2019 · 0 comments

Comments

@denis-yuen
Copy link
Member

denis-yuen commented Sep 3, 2019

There were the following questions from the steering committee meeting that should result in documentation improvements

  • the docs might reference Docker specifically at times and do not make it clear that we believe that the standard as it exists should support Singularity and other Docker alternatives
  • should emphasize that this is a standard for computationally actionable tools, this is different both from a simple unformatted list of tools, but it also means that this is a standard for registries to implement as opposed to a registry implementation itself
  • Highlight 4053fcd which describes our process for guaranteeing ID uniqueness when exchanging tools

┆Issue is synchronized with this Jira Story
┆containerName: GA4GH tool-registry-service
┆Issue Number: TRS-28

@denis-yuen denis-yuen added this to the v2 milestone Sep 3, 2019
@denis-yuen denis-yuen removed this from the v2 milestone Jun 14, 2022
denis-yuen added a commit that referenced this issue Feb 16, 2023
denis-yuen added a commit that referenced this issue Apr 3, 2023
* update readme

* swagger and v2 clean-up #229

* script seems broken with feature branches

* Documentation updates for #114

* typo fix and trigger build

* fix link and really re-genrate TOC

* prep for next version and even more re-generate

* Incorporated current PR feedback

* Update README.md

* Update README.md
denis-yuen added a commit that referenced this issue Apr 5, 2023
* update readme

* swagger and v2 clean-up #229

* script seems broken with feature branches

* Documentation updates for #114

* typo fix and trigger build

* fix link and really re-genrate TOC

* prep for next version and even more re-generate

* propose tag-based search #205

* Add tool version specific description #228
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant