-
Notifications
You must be signed in to change notification settings - Fork 10
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 - VF Governance #114
Comments
I think we should address this sooner than later -- and I think it's mostly about governance, I've updated the description accordingly. |
khawkins98
added a commit
that referenced
this issue
Apr 9, 2019
khawkins98
added a commit
that referenced
this issue
Apr 17, 2019
documentation: governance text #114
The pressing need here has been addressed in the above PR. Closing this one, we can iterate on the text as the need arises. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we enter the alpha releases we should start getting wider consensus on the approaches of the VF (note this is seperate from the EMBL brand).
So we should have some kind of governance, documented procedures, and some sort (or advisory group) that provides feedback and buyin, and results in some sort of documentation on:
So we need to:
The text was updated successfully, but these errors were encountered: