This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
Move data use to separate repositories #47
Comments
+1 from Jordi and Marc |
+1 Tony From: Miro Cupak [[email protected]] +1 from Jordi and Marc — |
@mcupak Could you link the repo here, please? |
The repository is here: https://github.com/ga4gh/ga4gh-consent-policy It looks like the specification has not been moved yet from its branch in this repository: https://github.com/ga4gh/beacon-team/tree/consent_code |
Update: ga4gh-consent-policy repository now contains the consent code spec. |
Hi Miro
Thanks for working on this (which I assume is the previous work now moved to a separate repository, correct?)
It would be good to start on what we agreed - creating the API for ADA-M, and ensuring this and the one for CC are aligned though both independent. Vagelis from my teams stands ready to work with you on this, but needs your help to get things started
Tony
…________________________________
From: Miro Cupak [[email protected]]
Sent: 05 December 2016 21:54
To: ga4gh/beacon-team
Cc: Brookes, Anthony J. (Prof.); Comment
Subject: Re: [ga4gh/beacon-team] Move data use to separate repositories (#47)
Update: ga4gh-consent-policy repository<https://github.com/ga4gh/ga4gh-consent-policy> now contains the consent code spec.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#47 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AI_EVBoundgO-_Wlpd_9FuaoypYYRINnks5rFIghgaJpZM4IWSZQ>.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Consider moving data use specifications to separate repositories so that they can be released/versioned independently from beacon. Beacon should treat their releases as dependencies.
The text was updated successfully, but these errors were encountered: