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

Steps towards submitting the product to GA4GH #35

Open
6 tasks done
andrewyatz opened this issue Sep 6, 2022 · 6 comments
Open
6 tasks done

Steps towards submitting the product to GA4GH #35

andrewyatz opened this issue Sep 6, 2022 · 6 comments
Milestone

Comments

@andrewyatz
Copy link
Collaborator

andrewyatz commented Sep 6, 2022

These are the steps I believe are needed before we can submit to GA4GH product approval

  • Fill out the necessary forms from secretariat (Reggan to distribute)
  • Complete security and REWS review forms
  • Complete two implementations of the seqcol specification
  • Formalise what will be submitted i.e. what is the spec and what is additional items we are writing that side alongside the spec
  • Complete client(s) for the specification
  • Compliance checks/suite of tool. @yash-puligundla to advise
@andrewyatz
Copy link
Collaborator Author

Note these should be considered not in order

@tcezard tcezard added this to the V1.0 milestone Sep 7, 2022
@yash-puligundla
Copy link
Member

It would be nice to have the compliance suite output report follow this schema so that it can be easily integrated into the testbed platform in the future.
I plan to move all the reusable components in the DRS compliance suite (https://github.com/ga4gh/drs-compliance-suite/tree/yp_add_test_cases_object_endpoint) to a common repo. But unfortunately, we are not there yet. In the meantime, I am available to discuss/ brainstorm so we are on the same page and are not duplicating any efforts.

@nsheff
Copy link
Member

nsheff commented Aug 23, 2023

Hi @yash-puligundla can you give us an update on this? I think we're ready for some help with starting to implement a compliance suite at this point.

@yash-puligundla
Copy link
Member

Hi @nsheff. As of now, we haven't proceeded with migrating the common code into a library.
Could you please provide an estimate of the timeframe within which you would like this common code library to be available?

I'm also looping in @jppay, our new team lead, to this conversation.

@nsheff
Copy link
Member

nsheff commented Dec 13, 2023

@andrewyatz can you talk about timeline here? I think we're wanting to move forward on this now, and I think we were targeting something in January, but I'm not exactly sure what that is. Can you give us a timeline and a bit more specifics on this?

@tcezard
Copy link
Collaborator

tcezard commented Dec 13, 2023

For information here are the documentation that we filled in for the RefGet v2 product approval:

Note that the forms might have changed.

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

No branches or pull requests

4 participants