Create a Code of Conduct Page

[abregorivas]

Dependency

Tabling for now due to lift required and release of VRMS 0.4 - you can check vrms by opening in a browser window https://vrms.io

Overview

We want to add people seeing / agreeing with the code of conduct before they can get a slack invite, without making it prone to breaking if CfA changes code of conduct that we are forking.

Background

HFLA code of conduct is located at https://github.com/hackforla/codeofconduct

Original ask

- but we have revised since then - see comments below in issue:
We need to add this to a page on the website.
This issue is site page called that holds our code of conduct.
The page should have an an accept / decline button at the bottom.
Accept button redirects to https://hackforla-slack.herokuapp.com/
Decline button redirects back to home page

[thekaveman]

@abregorivas @ddrosario sorry if I missed a convo at DTLA, but I'm not sure I agree with this approach of porting the CoC into the website.

The reason it is in the repo is because this was Code for America's CoC, and we as a Brigade forked it. They have subsequently updated the upstream, and added some additional docs around Slack usage and the expectations at Summit (the CfA conference). In my mind, we should be keeping up to date with upstream via our fork, rather than trying to reproduce content in multiple places.

Now making sure people accept before using Slack and all that - makes total sense. But since this content has a lineage that didn't begin with us, can we find a way to keep that intact?

[ExperimentsInHonesty]

@thekaveman I agree about replicating the content and then it getting out of date is not the ideal way to do it. Do you have another way that we can accomplish an attractive version of the code of conduct, and insert it into the click stream so that they don't get a slack invite without agreeing to it?

[ExperimentsInHonesty]

p.s. I added people from the team that I thought could benefit from the planning part of this issue from UI/UX to implementation and stability. This is a good issue to see how and why we make the decisions we do.

[thekaveman]

The "attractiveness" of the content should be a secondary concern; the words themselves are what matter here.

I think we should go all the way down the stack to the Heroku app that sends the Slack invite link. Rather than try and hijack the click stream with redirects everywhere, I'd rather we build this directly into the sign-up app so we know it is part of the flow.

EDIT: i think this is the app that powers the sign-up: https://github.com/rauchg/slackin

[ExperimentsInHonesty]

Let's talk about this post Summit. And possibly table this until after we figure out what the plan for the site is moving forward