Skip to content

Commit d775407

Browse files
kgodeykgodey
authored
Merge pull request creativecommons#24 from creativecommons/add_code_of_conduct
Add code of conduct, update site styling.
2 parents 7ed66ff + f8a380a commit d775407

File tree

12 files changed

+274
-78
lines changed

12 files changed

+274
-78
lines changed

‎assets/static/style.css

Lines changed: 35 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,16 @@
11
body {
2-
font-family: 'Source Sans Pro', sans-serif;
2+
font-family: 'Source Sans Pro', sans-serif;
3+
color: #333333;
4+
}
5+
h2 {
6+
font-weight: 600;
7+
padding-bottom: 0.5rem;
38
}
4-
59
.page-content {
610
position: relative;
711
min-height: calc(100vh - 21vh);
812
padding-bottom: 3rem;
913
}
10-
1114
.main-header .navbar-brand {
1215
margin-right: 2rem;
1316
}
@@ -19,14 +22,12 @@ body {
1922
font-size: .9rem;
2023
letter-spacing: .15rem;
2124
}
22-
2325
.footer {
2426
bottom: 0;
2527
height: 7rem; /* Footer height */
2628
}
27-
2829
.card-columns {
29-
column-count: 2;
30+
column-count: 2;
3031
}
3132
.main-header {
3233
background-color: #EE5B32;
@@ -36,52 +37,53 @@ body {
3637
background-size: 100% 130px;
3738
background-position-y: bottom
3839
}
39-
40+
.page-title {
41+
background-color: #fff;
42+
border-bottom-style: solid;
43+
border-color: #EE5B32;
44+
border-width: 10px;
45+
padding-left: 0px;
46+
font-weight: 600;
47+
color: #333333;
48+
}
4049
.project-idea-header {
41-
background-color: #fff;
42-
border-color: #00b5da;
43-
border-width: 10px;
44-
padding-left: 0px;
45-
font-size: 1.5em;
50+
background-color: #fff;
51+
border-color: #00b5da;
52+
border-width: 10px;
53+
padding-left: 0px;
54+
font-size: 1.5em;
4655
}
47-
4856
#back-to-top {
49-
cursor: pointer;
50-
position: fixed;
51-
bottom: 20px;
52-
right: 20px;
53-
display: none;
54-
background-color: #00b5da;
55-
border: none;
56-
}
57-
57+
cursor: pointer;
58+
position: fixed;
59+
bottom: 20px;
60+
right: 20px;
61+
display: none;
62+
background-color: #00b5da;
63+
border: none;
64+
}
5865
.nav-item, .dropdown-item {
59-
font-size: 1.2em;
60-
font-weight: 900;
66+
font-size: 1.2em;
6167
}
62-
6368
.dropdown:hover .dropdown-menu {
64-
display: block;
69+
display: block;
6570
}
66-
6771
.dropdown-menu {
68-
margin-top: 0px;
72+
margin-top: 0px;
6973
}
70-
7174
.navbar-dark .navbar-nav .nav-item .nav-link {
7275
padding-bottom: .3rem;
7376
color: white;
7477
}
75-
7678
.navbar-dark .navbar-nav .nav-item.active .nav-link {
7779
border-bottom: 2px solid white;
7880
}
79-
8081
.toc-card {
8182
width: 18rem;
8283
margin-bottom: 1rem;
84+
float: right;
85+
margin: 1rem;
8386
}
84-
8587
.toc {
8688
margin-bottom: 0;
8789
}
@@ -91,4 +93,4 @@ body {
9193
}
9294
.main-footer .footer small .text-muted {
9395
margin-left: 2rem;
94-
}
96+
}

‎content/cclogo.png

-14.3 KB
Binary file not shown.

‎content/community/code-of-conduct/contents.lr

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
_model: page
2+
---
3+
_template: page-with-toc.html
4+
---
5+
title: CC Open Source Code of Conduct
6+
---
7+
body:
8+
9+
The following Code of Conduct applies to all digital spaces managed by the Creative Commons engineering team, including GitHub, mailing lists, IRC and any other spaces which the development community uses for communication. Our Slack code of conduct is separate and [can be found here][slack-coc].
10+
11+
[slack-coc]: https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct
12+
13+
## Our Pledge
14+
15+
In the interest of fostering an open and welcoming environment, we as
16+
contributors and maintainers pledge to making participation in our project and
17+
our community a harassment-free experience for everyone, regardless of age, body
18+
size, disability, ethnicity, sex characteristics, gender identity and expression,
19+
level of experience, education, socio-economic status, nationality, personal
20+
appearance, race, religion, or sexual identity and orientation.
21+
22+
## Our Standards
23+
24+
Examples of behavior that contributes to creating a positive environment
25+
include:
26+
27+
* Using welcoming and inclusive language
28+
* Being respectful of differing viewpoints and experiences
29+
* Gracefully accepting constructive criticism
30+
* Focusing on what is best for the community
31+
* Showing empathy towards other community members
32+
33+
Examples of unacceptable behavior by participants include:
34+
35+
* The use of sexualized language or imagery and unwelcome sexual attention or
36+
advances
37+
* Trolling, insulting/derogatory comments, and personal or political attacks
38+
* Public or private harassment
39+
* Publishing others' private information, such as a physical or electronic
40+
address, without explicit permission
41+
* Other conduct which could reasonably be considered inappropriate in a
42+
professional setting
43+
44+
## Our Responsibilities
45+
46+
Project maintainers are responsible for clarifying the standards of acceptable
47+
behavior and are expected to take appropriate and fair corrective action in
48+
response to any instances of unacceptable behavior.
49+
50+
Project maintainers have the right and responsibility to remove, edit, or
51+
reject comments, commits, code, wiki edits, issues, and other contributions
52+
that are not aligned to this Code of Conduct, or to ban temporarily or
53+
permanently any contributor for other behaviors that they deem inappropriate,
54+
threatening, offensive, or harmful.
55+
56+
## Scope
57+
58+
This Code of Conduct applies both within project spaces and in public spaces
59+
when an individual is representing the project or its community. Examples of
60+
representing a project or community include using an official project e-mail
61+
address, posting via an official social media account, or acting as an appointed
62+
representative at an online or offline event. Representation of a project may be
63+
further defined and clarified by project maintainers.
64+
65+
## Enforcement
66+
67+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
68+
reported by contacting the project team at <strong>conduct@creativecommons.org</strong>. All
69+
complaints will be reviewed and investigated and will result in a response that
70+
is deemed necessary and appropriate to the circumstances. The project team is
71+
obligated to maintain confidentiality with regard to the reporter of an incident.
72+
Further details of specific enforcement policies may be posted separately.
73+
74+
Project maintainers who do not follow or enforce the Code of Conduct in good
75+
faith may face temporary or permanent repercussions as determined by other
76+
members of the project's leadership.
77+
78+
## Attribution
79+
80+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
81+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html.
82+
83+
[homepage]: https://www.contributor-covenant.org
84+
85+
For answers to common questions about this code of conduct, see
86+
https://www.contributor-covenant.org/faq.
87+

‎content/community/code-of-conduct/enforcement/contents.lr

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
_model: page
2+
---
3+
_template: page-with-toc.html
4+
---
5+
title: Codes of Conduct Enforcement
6+
---
7+
body:
8+
9+
## Codes of Conduct
10+
11+
This document provides incident reporting guidelines and an enforcement manual for the following codes of conduct used by Creative Commons:
12+
13+
* [CC Open Source Code of Conduct](/community/code-of-conduct)
14+
* [Slack/Code of Conduct](https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct)
15+
16+
## Reporting Guidelines
17+
18+
If you believe someone is violating the code of conduct, we ask that you report it to Creative Commons by emailing
19+
**conduct@creativecommons.org**. **All reports will be kept confidential.** In some cases we may determine that a public statement will need to be made, which the committee may make in its discretion. The identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
20+
21+
**If you believe anyone is in physical danger, please notify appropriate emergency personnel first.** If you are unsure what proper authorities are appropriate, please include this in your report and we will attempt to notify them.
22+
23+
If you are unsure whether the incident is a violation, or whether the space where it happened is covered by this Code of Conduct, we still encourage you to report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. Knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.
24+
25+
In your report please include:
26+
27+
* Your contact info (so we can get in touch with you if we need to follow up)
28+
* Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well.
29+
* When and where the incident occurred. Please be as specific as possible.
30+
* Your account of what occurred. If there is a publicly available record (e.g. a mailing list archive or a Slack message) please include a link.
31+
* Any extra context for the incident.
32+
* If you believe this incident is ongoing.
33+
* Any other information the committee should have.
34+
35+
### Conflicts of Interest
36+
37+
In the event of any conflict of interest a committee member must immediately notify the other members, and recuse themselves if the other committee members believe a conflict exists. If a report concerns a possible violation by a current committee member, this member must be excluded from the response process. For these cases, anyone can make a report directly to the **CC Legal team at [legal@creativecommons.org](mailto:legal@creativecommons.org)** instead of through the regular process, above.
38+
39+
## Enforcement Manual
40+
41+
This manual mainly covers reports of code of conduct violations from community members. If an administrator of a forum notices ongoing or dangerous behavior that violates the code of conduct (such as spam), they may act unilaterally as described in the **Acting Unilaterally** section below.
42+
43+
### The Code of Conduct Committee
44+
45+
All responses to reports of conduct violations will be managed by a Code of Conduct Committee ("the committee"), which will be comprised of three members of Creative Commons staff. The Code of Conduct Committee will serve in the role of “project maintainers” as described in the Contributor Covenant.
46+
47+
### How the committee will respond to reports
48+
49+
When a report is sent to the committee they will reply promptly, and within no more than 2 Creative Commons business days.
50+
51+
See the reporting guidelines above for details of what reports should contain. If a report doesn't contain enough information, the committee will obtain all relevant data before acting.
52+
53+
The committee will then review the incident and determine, to the best of their ability:
54+
55+
* what happened
56+
* whether this event constitutes a code of conduct violation
57+
* who, if anyone, acted in contravention of the policy
58+
* whether this is an ongoing situation, and if there is a threat to anyone's physical safety
59+
60+
The committee should aim to have a resolution agreed upon within one week. In the event that a resolution can't be determined in that time, the committee will respond to the reporter(s) with an update and projected timeline for resolution.
61+
62+
### Acting Unilaterally
63+
64+
Not every situation acted upon by the Code of Conduct Committee will be the result of a report from the community. In some cases, a Code of Conduct Committee member will witness a violation themselves. If the act is ongoing (such as someone engaging in harassment in an IRC channel or spamming a Slack channel), or involves a threat to anyone's safety (e.g. threats of violence), any committee member may act immediately (before reaching consensus) to end the situation. In ongoing situations, any member may at their discretion employ any of the tools available to the committee, including bans and blocks.
65+
66+
If the incident involves physical danger, any member of the committee may -- and should -- act unilaterally to protect safety. This can include contacting appropriate emergency personnel first or speaking on behalf of Creative Commons.
67+
68+
In situations where an individual committee member acts unilaterally, they must report their actions to the committee for review within 1 business day.
69+
70+
### Resolutions
71+
72+
The committee should strive to agree on a resolution by consensus (i.e. no one on the committee chooses to veto the course of action). As soon as the committee determines it is unable to reach consensus or it has been deadlocked for over 2 business days after acknowledging receipt of the issue, the committee will turn the matter over to the CC legal team for resolution.
73+
74+
Possible responses may include:
75+
76+
* Taking no further action (if the committee determines no violation occurred).
77+
* A private reprimand from the committee to the individual(s) involved. In this case, a committee member will deliver that reprimand to the individual(s) directly through appropriate means, cc'ing the committee.
78+
* A public reprimand. In this case, a committee member will attempt to deliver that reprimand in the same venue that the violation occurred (i.e. in Slack for an Slack violation; email for an email violation, etc.). The committee may choose to publish this message elsewhere for posterity.
79+
* A temporary or permanent ban from some or all Creative Commons spaces (mailing lists, Slack, etc.). The committee will maintain records of all such bans so that they may be reviewed in the future, extended to new Creative Commons fora, or otherwise maintained.
80+
81+
Once a resolution is agreed upon, but before it is enacted, the committee will contact the original reporter and any other affected parties and explain the proposed resolution. The committee will ask if this resolution is acceptable, and must note feedback for the record. However, the committee is not required to act on this feedback.
82+
83+
### Reconsideration
84+
85+
Any of the parties directly involved or affected can request reconsideration of the committee’s decision. To make such a request, contact the **CC Legal team at [legal@creativecommons.org](mailto:legal@creativecommons.org)** with your request and reason and they will review the case.
86+
87+
## Current Code of Conduct Committee
88+
89+
* Jennie Rose Halperin ([jennie@creativecommons.org](mailto:jennie@creativecommons.org))
90+
* Kriti Godey ([kriti@creativecommons.org](mailto:kriti@creativecommons.org))
91+
* Mari Moreshead ([mari@creativecommons.org](mailto:mari@creativecommons.org))
92+
93+
## Policy Revision
94+
95+
This policy may be revised and updated by Creative Commons from time to time. You should not participate in our digital communities unless you agree with and comply with the current policy.
96+
97+
## Last Revised
98+
99+
2019-03-06
100+
101+
## Attribution
102+
103+
This document is adapted from the Django project's Code of Conduct [enforcement manual](https://www.djangoproject.com/conduct/enforcement-manual/) and [reporting guidelines](https://www.djangoproject.com/conduct/reporting/), licensed under <a href="https://creativecommons.org/licenses/by/3.0/">CC BY 3.0</a>.

‎content/community/contents.lr

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Join the CC Developer Community
44
---
55
body:
66

7-
#### Slack
7+
## Slack
88
CC has an active Slack community open to the public. [Sign up here](http://slack-signup.creativecommons.org/). We have a lot of channels to explore, but the ones most relevant to CC's developer community are:
99
* `#intro` – introduce yourself here
1010
* `#cc-developers` – for general technical discussion
@@ -17,13 +17,13 @@ Note that channels like `#general` on Slack consist of a fair amount of users. W
1717

1818
If you're looking to talk to someone on CC's tech team, we are all in the Americas and someone is usually around on Slack between 11:00 and 23:00 UTC on weekdays.
1919

20-
#### Mailing List
20+
## Mailing List
2121

2222
Join the [current CC Developers mailing list here](https://groups.google.com/a/creativecommons.org/forum/#!forum/cc-developers).
2323

2424
The archives of our [previous mailing list are here](https://lists.ibiblio.org/pipermail/cc-devel/).
2525

26-
#### IRC
26+
## IRC
2727
IRC isn't very active anymore, but we have two channels on [Freenode](https://freenode.net/).
2828
- `#creativecommons-dev` – for technical discussion
2929
- `#creativecommons` – for general discussion (this is mirrored to the `#general` channel on Slack, use only if you want to reach 4000+ people)

‎content/contents.lr

Lines changed: 6 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -6,38 +6,28 @@ body:
66

77
**[Creative Commons](https://creativecommons.org/)** has been building free software for over a decade to support our mission of maximizing digital creativity, sharing, and innovation. Our projects come in all sizes and shapes, from simple static websites to providing a fast and relevant search interface to the billion-plus Creative Commons works currently available on the internet. Our engineering team is fairly small and spread thin, so we're really appreciative of volunteers who help us build or test our software.
88

9-
### Getting Involved
9+
## Getting Involved
1010

1111
You can contribute to CC's software in a few different ways.
1212

13-
----
14-
15-
##### Finding bugs and suggesting features
13+
### Finding bugs and suggesting features
1614

1715
Using our software (such as [the new version of CC Search](http://ccsearch.creativecommons.org/)) and letting us know how it's working for you is very helpful. General suggestions, bug reports, a request to build a new feature – any form of feedback is excellent, no matter how small.
1816

1917
You can send us feedback in a few different ways. If you have a GitHub account, [creating a GitHub issue](https://help.github.com/articles/creating-an-issue/) is easiest for us because that's where we track our work. If you know which GitHub repository (see [a full list here](/projects)) corresponds to the software about which you'd like to give us feedback, then please create an issue attached to that repository. If you're not sure what that means or you don't know the correct repository, please create an issue [on the creativecommons.org repository](https://github.com/creativecommons/creativecommons.org/issues). You can also send us feedback in the `#cc-usability` channel [on the CC Slack community](https://creativecommons.org/2016/10/18/slack-announcement/) or via email at `software@creativecommons.org`.
2018

21-
----
22-
23-
##### Contributing code
19+
### Contributing code
2420

2521
Please see [Contributing Code](/contributing-code).
2622

27-
----
28-
29-
##### Integrating CC license metadata into your app
23+
### Integrating CC license metadata into your app
3024

3125
Please see [the "Integrate" page on the CC wiki](https://wiki.creativecommons.org/wiki/Integrate).
3226

33-
----
34-
35-
##### Helping translate our content
27+
### Helping translate our content
3628

3729
Please see [the "Translate" page on the CC wiki](https://wiki.creativecommons.org/wiki/Translate).
3830

39-
----
40-
41-
##### Contributing design
31+
### Contributing design
4232

4333
If you'd like to improve the design of one of our tools or products, please propose your change in [one of our community forums](/community) and collaborate with a CC staff member if requested to before making any changes.

0 commit comments

Comments
 (0)