-
Notifications
You must be signed in to change notification settings - Fork 23
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
Code of conduct agreement #235
Code of conduct agreement #235
Conversation
…ec to account for a code of conduct agreement
Hey @aackerman - What's the scoop on some of these Travis failures? Wondering if the setup is still in progress or if we're good to merge some of these even with it failing. |
@jennapederson at some point the default build image on travis changed from ubuntu trusty to ubuntu xenial and the CI setup stopped working, looks like about 5 months ago. I've added configuration to run on ubuntu trusty. |
@aackerman I want to make sure I understand how this will work in real life... a person creates a session and goes to add another presenter to the session. they won't be able to until that person has agreed to the coc, right? and each coc agreement is for an event, right? what happens if we push this to production after some sessions/presenters have already been created/added? they'll be ok, but any new sessions/presenters added will have to agree? I think that's ok, but want to be able to message Maria and others who get to field questions in case something comes up! Thank you for working on this! |
@jennapederson it's been a few months but yes that's how I expect it to work, new sessions and new participants will have to agree. |
@aackerman Same for this -- can you fix conflicts and then we'll get it merged? Thanks! |
Fixes #218