Add CoC to website

[mattsayler]

Need to get the Code of Conduct up on the new website.

[geografa]

👍 let's make this dynamic so it either pulls from a repo or just lives here. @bethschechter where is the latest?

[bethschechter]

It is the version that's live on Maptime.io :)

Beth Schechter
Education + Outreach, Stamen Design http://stamen.com/
Founder, Maptime http://maptime.io/
+1 415-558-1610

On Fri, Oct 17, 2014 at 3:57 PM, geografa [email protected] wrote:

[image: 👍] let's make this dynamic so it either pulls from a repo or
just lives here. @bethschechter https://github.com/bethschechter where
is the latest?

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

[geografa]

@bethschechter Pefecto. Should we make a repo so others can contribute via pull requests, keep it under maptime.github.io, or just in doc?

[jqtrde]

Created maptime/code-of-conduct

[jqtrde]

Where should the CoC live on this page?

• /
• /about

+1 for it's own repo, but how do we integrate this into maptime.github.io? Jekyll has a nice Gist embedding feature, is there a way to do the same with a file in a repo?

[geografa]

@jacquestardie I think a subpage of /about is fine for now with a prominent link (maybe in sidebar?).

[jqtrde]

👍

[bethschechter]

subpage of /about is great

[rhewitt22]

@jacquestardie embed a file from a github repo

edit: Just tried this on a dev branch and it looks really ugly.

[geografa]

Not pretty but I put it here: http://maptime.io/code-of-conduct/

It's based on Starter. Next actions:

• remove master branch
• create links within /about to code of conduct
• make blog post and tweet it

[lyzidiamond]

@geografa shall we add these as individual issues on that repo and close this issue?

[geografa]

yus. been a lazy day today. :/

#101
maptime/code-of-conduct#1
#102

[lyzidiamond]

Thanks @geografa! 🍍 🎀 🌵

[rhewitt22]

@lyzidiamond @geografa

Question: could we use a git submodule to pull the CoC into this repository, and keep it up to date that way? That way we could continue to use the existing site styles.

Basically we'd create a code-of-conduct directory which would mirror the CoC repository. If someone sent a PR to the repository we could pull those changes into the submodule without manually copying and pasting.

I can't remember if I thought of this earlier and came up with a reason it wouldn't work.

[geografa]

@rhewitt22 I've used them in the past and didn't have the best experience with them. If you use them a lot, it can get unwieldy and hard to keep track of. But this could be the exception use case. I'm still torn on the CoC needing to be in its own repo or not. We can give this a shot here, though.

[lyzidiamond]

@rhewitt22 @geografa I like CoC being in its own repo because I could see it facilitating lots of discussion, which it should! 🌃 🍞 💳

[rhewitt22]

@lyzidiamond @geografa It's definitely a balancing act; I think we all agree the CoC should be open for discussion. We're adding extra complexity to maintain it in a separate repo. The question is it worth the extra work to maintain it separately vs. does merging it into the main site preclude the discussion we want to encourage?