-
Notifications
You must be signed in to change notification settings - Fork 0
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
Making the events repository public #56
Comments
I've no issue with making it public. Thanks for checking. |
No issues on my end 👍 |
No problem with me. Thanks! 💪🏼 |
Im ok with making this repo public :) |
No Problem with me, Thanks! :) |
Sounds great to me! |
Thank you all to those who responded so far. @jmanitz @andyofsmeg @emilliman5 - just wanted to give a quick reminder of our hope to have all responses by this Friday in case you had any disagreement with making the repository public. Hope you have a great rest of your Tuesday! |
Thank you to those who replied about consenting to making the repository public. As the August 23rd deadline has passed, we will assume consent from the remaining contributors and move forward to make the repository public. |
Hello @jmanitz @aclark02-arcus @dgkf @anujadas185 @Xyarz @andyofsmeg @marlycormar @DrLynTaylor @emilliman5 !
I hope you all are well!
If you are tagged in this issue, it is because you have been identified as a past and/or current contributor in this repository. We are planning to make the repository open to the public to easily link our content to our website and increase transparency to available resources. A majority of our other repositories are already public, so this would be keeping up with that standard.
Kindly comment/respond in this issue and state if you agree with the proposal of making the repository public. If you have any content you contributed that you would like to maintain private, please indicate which content that is and we can figure out a path forward in which we secure that content accordingly elsewhere. If you could comment/respond EOD Friday, August 23rd, that would be great. Thank you!
The text was updated successfully, but these errors were encountered: