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

Added a code of conduct #140

Merged
merged 1 commit into from
Feb 9, 2016
Merged

Added a code of conduct #140

merged 1 commit into from
Feb 9, 2016

Conversation

larister
Copy link
Contributor

@larister larister commented Feb 7, 2016

@yanneves @gablaxian @Rosa-Fox what do you guys think? Copypasta'd and adapted.

Important: This would mean I'd want volunteers who'd be willing to be listed as "Staff" on the Lanyrd page, who would have responsibilities as outlined in our Code of Conduct. Do you think this is reasonable to ask of the group?

@Rosa-Fox
Copy link

Rosa-Fox commented Feb 7, 2016

Excellent, I am more than happy to be listed as Staff along with my contact details. Sorry I haven't been at Async for a while, the commute is making me so tired! Will be along again soon :)

@yanneves
Copy link
Member

yanneves commented Feb 7, 2016

That's great, also happy to be listed as Staff, let me know if you're missing any contact details for me. Just dropping a reference here as fix for #128

@Finetuned
Copy link
Contributor

The code looks good to me. Quite short which is probably good. Also happy to be listed as Staff.

@larister
Copy link
Contributor Author

larister commented Feb 8, 2016

Really appreciate that all, thanks! Question though; should we list our contact details on a publicly accessible website? Would it be better to print out some flyers or something to have available at each event?

@Finetuned
Copy link
Contributor

The staff list on lanyrd already has twitter accounts listed. Wouldn't this be more appropriate for the async website?

@larister
Copy link
Contributor Author

larister commented Feb 8, 2016

Yeah happy to put twitter accounts, and maybe add photos of people as well so they're recognisable, but if one puts oneself in the shoes of somebody who has experienced harassment they may prefer to simply leave as soon as possible, and then report the incident separately. Twitter wouldn't be a great medium for that, so I think personal emails and phone numbers should be available to delegates. Flyers are the only solution I can think of but what do you guys reckon?

@Finetuned
Copy link
Contributor

Yes, good point. What about a large size hard copy (foam core mounted) on the bar that has the code of conduct and our details. If it's propped up people will see it when they arrive and everyone can be reminded periodically. People can take the details if and when.

@almost
Copy link
Member

almost commented Feb 8, 2016

This looks good to me also. I hope it's not actually needed but good to have it for if it is.

@yanneves
Copy link
Member

yanneves commented Feb 8, 2016

Photos are a good shout, anything that helps to identify us at the events.

@larister
Copy link
Contributor Author

larister commented Feb 8, 2016

Good idea @Finetuned, will have a look at getting a foam core board. You're
right, people can just take a photo of the details eh?

@almost indeed I shudder at the thought of this being needed, but much
better to have it anyway.

@yanneves thanks will get a staff page sorted on the website.

On 8 February 2016 at 11:32, Yann アウネ Eves notifications@github.com wrote:

Photos are a good shout, anything that helps to identify us at the events.


Reply to this email directly or view it on GitHub
#140 (comment)
.

@larister
Copy link
Contributor Author

larister commented Feb 9, 2016

Have added a couple of issues
#141 and
#142. Could we solve
those separately and merge as is for now possibly?

On 8 February 2016 at 12:23, Alastair Lockie alastair.lockie@gmail.com
wrote:

Good idea @Finetuned, will have a look at getting a foam core board.
You're right, people can just take a photo of the details eh?

@almost indeed I shudder at the thought of this being needed, but much
better to have it anyway.

@yanneves thanks will get a staff page sorted on the website.

On 8 February 2016 at 11:32, Yann アウネ Eves notifications@github.com
wrote:

Photos are a good shout, anything that helps to identify us at the events.


Reply to this email directly or view it on GitHub
#140 (comment)
.

yanneves pushed a commit that referenced this pull request Feb 9, 2016
@yanneves yanneves merged commit 4142c27 into asyncjs:master Feb 9, 2016
@larister
Copy link
Contributor Author

Thanks Yann <3

On 9 February 2016 at 16:08, Yann アウネ Eves notifications@github.com wrote:

Merged #140 #140.


Reply to this email directly or view it on GitHub
#140 (comment).

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

Successfully merging this pull request may close these issues.

5 participants