You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
* 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
* 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
There were the following questions from the steering committee meeting that should result in documentation improvements
┆Issue is synchronized with this Jira Story
┆containerName: GA4GH tool-registry-service
┆Issue Number: TRS-28
The text was updated successfully, but these errors were encountered: