Skip to content

Commit 640fe0a

Browse files
jywarrensashadev-skypydevsgmastal88samagragupta
authored
update gh-pages demo (#405)
* Update README.md * Update CODE_OF_CONDUCT.md as per new revision (#262) update code of conduct to reflect changes on https://publiclab.org/conduct Aug, 28 2019 and standardize formatting with MK, LDI, Plots2 * Footer UI changes (#255) * Footer UI change * fixed the social media icons on mobile view * Remove redundant function from community-toolbox.js #218 (#268) * Added author thumbnail to issue display (#266) * Update usage.md * fixed UI bug: footer elements not centered (#273) * Bump browserify from 16.3.0 to 16.5.0 (#250) Bumps [browserify](https://github.com/browserify/browserify) from 16.3.0 to 16.5.0. - [Release notes](https://github.com/browserify/browserify/releases) - [Changelog](https://github.com/browserify/browserify/blob/master/changelog.markdown) - [Commits](browserify/browserify@v16.3.0...v16.5.0) Signed-off-by: dependabot-preview[bot] <[email protected]> * Bump node-snackbar from 0.1.15 to 0.1.16 (#286) Bumps [node-snackbar](https://github.com/polonel/SnackBar) from 0.1.15 to 0.1.16. - [Release notes](https://github.com/polonel/SnackBar/releases) - [Commits](polonel/SnackBar@0.1.15...0.1.16) Signed-off-by: dependabot-preview[bot] <[email protected]> * Bump chart.js from 2.8.0 to 2.9.3 (#292) Bumps [chart.js](https://github.com/chartjs/Chart.js) from 2.8.0 to 2.9.3. - [Release notes](https://github.com/chartjs/Chart.js/releases) - [Commits](chartjs/Chart.js@v2.8.0...v2.9.3) Signed-off-by: dependabot-preview[bot] <[email protected]> * Added a language attribute (#287) Added it because the language attribute helps to specify the language of the element's content * Bump tape from 4.11.0 to 4.12.0 (#303) Bumps [tape](https://github.com/substack/tape) from 4.11.0 to 4.12.0. - [Release notes](https://github.com/substack/tape/releases) - [Commits](tape-testing/tape@v4.11.0...v4.12.0) Signed-off-by: dependabot-preview[bot] <[email protected]> * fix header UI issue. (#307) * Bump tape from 4.12.0 to 4.12.1 (#304) Bumps [tape](https://github.com/substack/tape) from 4.12.0 to 4.12.1. - [Release notes](https://github.com/substack/tape/releases) - [Commits](tape-testing/tape@v4.12.0...v4.12.1) Signed-off-by: dependabot-preview[bot] <[email protected]> * [Security] Bump handlebars from 4.1.2 to 4.5.3 (#305) Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.1.2 to 4.5.3. **This update includes a security fix.** - [Release notes](https://github.com/wycats/handlebars.js/releases) - [Changelog](https://github.com/wycats/handlebars.js/blob/master/release-notes.md) - [Commits](handlebars-lang/handlebars.js@v4.1.2...v4.5.3) Signed-off-by: dependabot-preview[bot] <[email protected]> * Bump tape from 4.12.1 to 4.13.0 (#312) Bumps [tape](https://github.com/substack/tape) from 4.12.1 to 4.13.0. - [Release notes](https://github.com/substack/tape/releases) - [Commits](tape-testing/tape@v4.12.1...v4.13.0) Signed-off-by: dependabot-preview[bot] <[email protected]> * Bump http-server from 0.11.1 to 0.12.1 (#311) Bumps [http-server](https://github.com/http-party/http-server) from 0.11.1 to 0.12.1. - [Release notes](https://github.com/http-party/http-server/releases) - [Commits](http-party/http-server@0.11.1...v0.12.1) Signed-off-by: dependabot-preview[bot] <[email protected]> * sort dropdown made responsive (#313) * fixed the stale issues which fixes issue #282 (#314) * fixed the stale issues * Fixed the stale issues * Plugged the function and fixed the key-value pair * Fixed the browser issue * Fixed the index.html issue Co-authored-by: Rishabh Rawat <[email protected]> * Bump jest from 24.9.0 to 25.1.0 (#322) Bumps [jest](https://github.com/facebook/jest) from 24.9.0 to 25.1.0. - [Release notes](https://github.com/facebook/jest/releases) - [Changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md) - [Commits](jestjs/jest@v24.9.0...v25.1.0) Signed-off-by: dependabot-preview[bot] <[email protected]> * JS code enhancement (#298) * Fixed the hyperlink issue (Fixes issue #320) (#329) * Fixed the hyperlink issue * fixed the hyperlink issue * Update getting_started.md (#327) We start the the server with npm start so this we should follow like we have in other projects. * Fix The Position Of Fork me Ribbon (#332) * Fix The Position Of Fork me Ribbon * fixed the indent issue * Added the scrolling in-list (#336) * Add a all repositories button to dropdown (#338) * Show Github username over avatar (#340) * Add gitter option in connect with us section (#342) * Add gitter option in connect with us section * fix the indentation * Bump tape from 4.13.0 to 4.13.2 (#344) Bumps [tape](https://github.com/substack/tape) from 4.13.0 to 4.13.2. - [Release notes](https://github.com/substack/tape/releases) - [Commits](tape-testing/tape@v4.13.0...v4.13.2) Signed-off-by: dependabot-preview[bot] <[email protected]> * Bump grunt from 1.0.4 to 1.1.0 (#347) Bumps [grunt](https://github.com/gruntjs/grunt) from 1.0.4 to 1.1.0. - [Release notes](https://github.com/gruntjs/grunt/releases) - [Changelog](https://github.com/gruntjs/grunt/blob/master/CHANGELOG) - [Commits](gruntjs/grunt@v1.0.4...v1.1.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * [Security] Bump acorn from 6.0.4 to 6.4.1 (#346) Bumps [acorn](https://github.com/acornjs/acorn) from 6.0.4 to 6.4.1. **This update includes a security fix.** - [Release notes](https://github.com/acornjs/acorn/releases) - [Commits](acornjs/acorn@6.0.4...6.4.1) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * updated installation instructions (#345) * Bump jquery from 3.4.1 to 3.5.0 (#357) Bumps [jquery](https://github.com/jquery/jquery) from 3.4.1 to 3.5.0. - [Release notes](https://github.com/jquery/jquery/releases) - [Commits](jquery/jquery@3.4.1...3.5.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump browserify from 16.5.0 to 16.5.1 (#351) Bumps [browserify](https://github.com/browserify/browserify) from 16.5.0 to 16.5.1. - [Release notes](https://github.com/browserify/browserify/releases) - [Changelog](https://github.com/browserify/browserify/blob/master/changelog.markdown) - [Commits](browserify/browserify@v16.5.0...v16.5.1) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * [Security] Bump websocket-extensions from 0.1.3 to 0.1.4 (#374) Bumps [websocket-extensions](https://github.com/faye/websocket-extensions-node) from 0.1.3 to 0.1.4. **This update includes a security fix.** - [Release notes](https://github.com/faye/websocket-extensions-node/releases) - [Changelog](https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md) - [Commits](faye/websocket-extensions-node@0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump moment from 2.24.0 to 2.27.0 (#375) Bumps [moment](https://github.com/moment/moment) from 2.24.0 to 2.27.0. - [Release notes](https://github.com/moment/moment/releases) - [Changelog](https://github.com/moment/moment/blob/develop/CHANGELOG.md) - [Commits](moment/moment@2.24.0...2.27.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump grunt from 1.1.0 to 1.2.0 (#377) Bumps [grunt](https://github.com/gruntjs/grunt) from 1.1.0 to 1.2.0. - [Release notes](https://github.com/gruntjs/grunt/releases) - [Changelog](https://github.com/gruntjs/grunt/blob/master/CHANGELOG) - [Commits](gruntjs/grunt@v1.1.0...v1.2.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump grunt from 1.2.0 to 1.2.1 (#378) Bumps [grunt](https://github.com/gruntjs/grunt) from 1.2.0 to 1.2.1. - [Release notes](https://github.com/gruntjs/grunt/releases) - [Changelog](https://github.com/gruntjs/grunt/blob/master/CHANGELOG) - [Commits](gruntjs/grunt@v1.2.0...v1.2.1) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump browserify from 16.5.1 to 16.5.2 (#383) Bumps [browserify](https://github.com/browserify/browserify) from 16.5.1 to 16.5.2. - [Release notes](https://github.com/browserify/browserify/releases) - [Changelog](https://github.com/browserify/browserify/blob/master/changelog.markdown) - [Commits](browserify/browserify@v16.5.1...v16.5.2) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * [Security] Bump elliptic from 6.4.1 to 6.5.3 (#380) Bumps [elliptic](https://github.com/indutny/elliptic) from 6.4.1 to 6.5.3. **This update includes a security fix.** - [Release notes](https://github.com/indutny/elliptic/releases) - [Commits](indutny/elliptic@v6.4.1...v6.5.3) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump grunt from 1.2.1 to 1.3.0 (#387) Bumps [grunt](https://github.com/gruntjs/grunt) from 1.2.1 to 1.3.0. - [Release notes](https://github.com/gruntjs/grunt/releases) - [Changelog](https://github.com/gruntjs/grunt/blob/master/CHANGELOG) - [Commits](gruntjs/grunt@v1.2.1...v1.3.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump moment from 2.27.0 to 2.28.0 (#391) Bumps [moment](https://github.com/moment/moment) from 2.27.0 to 2.28.0. - [Release notes](https://github.com/moment/moment/releases) - [Changelog](https://github.com/moment/moment/blob/develop/CHANGELOG.md) - [Commits](moment/moment@2.27.0...2.28.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * [Security] Bump http-proxy from 1.18.0 to 1.18.1 (#390) Bumps [http-proxy](https://github.com/http-party/node-http-proxy) from 1.18.0 to 1.18.1. **This update includes a security fix.** - [Release notes](https://github.com/http-party/node-http-proxy/releases) - [Changelog](https://github.com/http-party/node-http-proxy/blob/master/CHANGELOG.md) - [Commits](http-party/node-http-proxy@1.18.0...1.18.1) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump tape-run from 6.0.1 to 8.0.0 (#379) Bumps [tape-run](https://github.com/juliangruber/tape-run) from 6.0.1 to 8.0.0. - [Release notes](https://github.com/juliangruber/tape-run/releases) - [Changelog](https://github.com/juliangruber/tape-run/blob/master/History.md) - [Commits](tape-testing/tape-run@v6.0.1...v8.0.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump moment from 2.28.0 to 2.29.1 (#393) Bumps [moment](https://github.com/moment/moment) from 2.28.0 to 2.29.1. - [Release notes](https://github.com/moment/moment/releases) - [Changelog](https://github.com/moment/moment/blob/develop/CHANGELOG.md) - [Commits](moment/moment@2.28.0...2.29.1) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump tape from 4.13.2 to 5.0.1 (#372) Bumps [tape](https://github.com/substack/tape) from 4.13.2 to 5.0.1. - [Release notes](https://github.com/substack/tape/releases) - [Commits](tape-testing/tape@v4.13.2...v5.0.1) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Update demo.css to fix font links to League Spartan CDN via fontsource (#402) re publiclab/image-sequencer#1741 * Bump browserify from 16.5.2 to 17.0.0 (#396) Bumps [browserify](https://github.com/browserify/browserify) from 16.5.2 to 17.0.0. - [Release notes](https://github.com/browserify/browserify/releases) - [Changelog](https://github.com/browserify/browserify/blob/master/changelog.markdown) - [Commits](browserify/browserify@v16.5.2...v17.0.0) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump jquery from 3.5.0 to 3.5.1 (#369) Bumps [jquery](https://github.com/jquery/jquery) from 3.5.0 to 3.5.1. - [Release notes](https://github.com/jquery/jquery/releases) - [Commits](jquery/jquery@3.5.0...3.5.1) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump http-server from 0.12.1 to 0.12.3 (#360) Bumps [http-server](https://github.com/http-party/http-server) from 0.12.1 to 0.12.3. - [Release notes](https://github.com/http-party/http-server/releases) - [Commits](http-party/http-server@v0.12.1...v0.12.3) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> * Bump chart.js from 2.9.3 to 2.9.4 (#398) Bumps [chart.js](https://github.com/chartjs/Chart.js) from 2.9.3 to 2.9.4. - [Release notes](https://github.com/chartjs/Chart.js/releases) - [Commits](chartjs/Chart.js@v2.9.3...v2.9.4) Signed-off-by: dependabot-preview[bot] <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> Co-authored-by: Sasha Boginsky <[email protected]> Co-authored-by: Sudipto Ghosh <[email protected]> Co-authored-by: mastal88 <[email protected]> Co-authored-by: Samagra Gupta <[email protected]> Co-authored-by: kay nguyen <[email protected]> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> Co-authored-by: Elizabeth Owufuni Agada <[email protected]> Co-authored-by: Rishabh Rawat <[email protected]> Co-authored-by: rounak176 <[email protected]> Co-authored-by: Devansh Agarwal <[email protected]> Co-authored-by: somenath sarkar <[email protected]> Co-authored-by: Devansh Agarwal <[email protected]> Co-authored-by: Govind Goel <[email protected]>
1 parent 11fb4dd commit 640fe0a

23 files changed

+7137
-4550
lines changed

CODE_OF_CONDUCT.md

Lines changed: 5 additions & 107 deletions
Original file line numberDiff line numberDiff line change
@@ -1,113 +1,11 @@
1-
This document was copied from its home at https://publiclab.org/conduct on October 12, 2017. See that page if you would like to submit your concerns in a safe, completely anonymous way, and to learn more about this document.
2-
3-
****
4-
51
# Public Lab Code of Conduct
62

7-
_Public Lab, PO Box 426113, Cambridge, MA 02142_
8-
9-
We are coming together with an intent to care for ourselves and one another. We want to nurture a compassionate democratic culture where responsibility is shared. We -- visitors, community members, community moderators, staff, organizers, sponsors, and all others -- hold ourselves accountable to the same values regardless of position or experience. For this to work for everybody, individual decisions will not be allowed to run counter to the welfare of other people. This community aspires to be a respectful place both during online and in-person interactions so that all people are able to fully participate with their dignity intact. This document is a piece of the culture we're creating.
10-
11-
12-
This code of conduct applies to all spaces managed by the Public Lab community and non-profit, both online and in person. It was written by the Conduct Committee (formed in 2015 during Public Lab’s annual conference “The Barnraising”) and facilitated by staff to provide a clear set of practical guidelines for multi-day events such as Barnraisings, events led by organizers and community members, and online venues such as the website, comment threads on software platforms, chatrooms, our mailing lists, the issue tracker, and any other forums created by Public Lab which the community uses for communication.
13-
14-
15-
## We come from all kinds of backgrounds
16-
17-
Our community is best when we fully invite and include participants from a wide range of backgrounds. We specifically design spaces to be welcoming and accessible to newcomers and folks from underrepresented groups. Public Lab is dedicated to providing a harassment-free, safe, and inclusive experience for everyone, regardless of personal and professional background, gender, gender identity and expression, style of clothing, sexual orientation, dis-/ability, physical appearance, body size, race, class, age, or religion. Public Lab resists and rejects: racism, sexism, ableism, ageism, homophobia, transphobia, body shaming, religion shaming, “geekier-than-thou” shaming, education bias, the shaming of people nursing children, and the dismissal or bullying of children or adults.
18-
19-
## We do not tolerate harassment or shaming
20-
21-
While we operate under the assumption that all people involved with Public Lab subscribe to the basic understanding laid out above, we take these issues very seriously and think they should, in general, be taken seriously. Therefore, individuals who violate this Code both in and outside of Public Lab spaces may affect their ability to participate in Public Lab ranging from temporarily being placed into online moderation to, as a last resort, expulsion from the community. If you have any questions about our commitment to this framework and/or if you are unsure about aspects of it, email [email protected] and we will do our best to provide clarification.
22-
23-
## How It Works
24-
25-
Sometimes things go wrong. When a situation is uncomfortable, hurtful, exclusionary, or upsetting, there is a problem that should be addressed. This code of conduct is an effort to maintain a safe space for everyone, and to talk about what might happen if that space is compromised. Please see additional guidelines below for community behavior on how we expect people to interact with one another.
26-
27-
### Two helpful groups
28-
29-
__Conduct Committee (ConductCom)__: If at any time you experience something that you are not comfortable with, you may contact the Conduct Committee. As established during the 2015 Annual Barnraising, the following individuals are on the Conduct Committee: Klie Kliebert, Carla Green, Nick Shapiro, and Shannon Dosemagen, the executive director of the Public Lab nonprofit.
30-
31-
32-
If you would like to have a confidential conversation, connect with ConductCom in person or email via [[email protected]](mailto:[email protected]). A minimum of two committee members will confer and respond as swiftly as possible. If you would prefer to speak privately with a representative of the nonprofit, please contact the executive director directly either in person or by email: [[email protected].](mailto:[email protected])
33-
34-
35-
To submit a report anonymously for review by ConductCom, go online via phone or computer to our anonymous “contact” app, located at [http://bit.ly/PLReport](http://bit.ly/PLReport). This contact app will be monitored daily at 8am CST during in-person events like Barnraisings and weekly at all other times. During multi-day in-person events hosted by the Public Lab non-profit, there will also be a physical suggestion box available. This box will be monitored throughout the event and can also be used to let us know if you need us to check on an anonymous online submission sooner.
36-
37-
38-
__Moderators Group:__ The moderators group is responsible for addressing immediate moderation issues that arise during online violations of the code over email lists and Public Lab community websites, as well as approving first-time posts and generally handling spam. Instructions on how to become a moderator, and, if you’ve been placed in moderation how to begin the process of getting out of moderation can be found at: https://publiclab.org/wiki/moderation.
39-
40-
****
41-
42-
## A Culture of Empathy
43-
44-
We begin interactions by acknowledging that we are part of a community with complementary goals. Different views are allowed to respectfully coexist in the same space. When something's happened and someone is uncomfortable, our first choice is to work through it. Endeavor to listen and appropriately adjust your behavior if someone approaches you privately with a request that you apologize or publicly requests that you stop an ongoing presentation. If someone questions your words, actions or motives, or "calls you out", hear their feedback and respond respectfully. It’s okay to not understand why something is hurtful or causes discomfort, as long as you approach it respectfully, with empathy. Repeating hurtful behavior after it has been addressed is disrespectful and is not allowed. Doing so will result in removal and subsequent banning from in-person events and being placed into moderation in online spaces.
45-
46-
###The first rule of engaging with others is consent
47-
During in-person gatherings, consent is important to highlight because the negotiation of consent can be subtle, and it’s easy to miss each other’s non-verbal cues, resulting in miscommunication and/or offense. During online interactions, consent can be even harder to distinguish.
48-
49-
We make guesses or assessments of consent (willingness, welcome, invitation) all the time. Then we stay open to signs that the consent isn't there. Handshakes are a clear example of consent: someone offers a hand, and you take it if you want to shake it. A friendly smile might indicate consent to start a conversation. It might not. We learn that in the interaction. Sometimes we ask directly. We are open to making mistakes, and learning from them. The more we learn to be empathetic and see other people, the more we're able to talk about consent.
50-
51-
Before you engage with someone on any level, be sure you have their consent. If your indications aren't being heard, you can also ask for help from other folks, especially Conduct Committee members and staff of the non-profit: "They aren't taking the hint. Will you help?" Turning a blind eye to hurtful interactions can be as bad for our community as the exchange itself. If you witness something, it's your responsibility to say something. This is how we keep each other accountable, encourage empathy, and keep our community safe.
52-
53-
## Guidelines for in-person community behavior
54-
55-
56-
Do | Don’t
57-
----------- | -----------
58-
Respectfully share what method works best for you, while giving others space to think differently and contribute other ideas | Disparage entire groups/sets of people for their beliefs or methods
59-
Ask permission to take pictures of and post about others on social media (see Media Consent, above)| Upload photos, tag or mention others online without their consent
60-
Speak your own narrative, from your own unique culture | Caricature the cultural expressions of groups you are not a member of
61-
Model inclusionary expertise - if others in the group appear to be “lost”, slow down; stop and ask for input | Present information in a way / at a level that no one else in the room can understand, with no attempt to include others in the discussion
62-
Create events that are all-ages appropriate | Use language that excludes youth and their experiences as vital contributors
63-
Give everyone a chance to talk, only interrupting if absolutely necessary - for example, Code of Conduct violations | Repeatedly disrupt a discussion
64-
Stop, listen and ask for clarification if someone perceives your behavior or presentation as violating the Code of Conduct | Ignore others’ request to stop potentially harmful behavior, even if it was an accident
65-
Cultivate a sense of humor based on other subjects, such as word play (especially puns!) | Joke using words related to actual or insulting descriptions of people
66-
Use words that accurately describe the situation - For example, “The wind was ridiculously strong!” instead of “The wind was crazy!” | Use disability and mental/emotional health terminology to describe a situation metaphorically, especially if the phrasing is meant as an insult
67-
Only discuss someone else’s lifestyle practices if they invite you to a conversation on the topic | Make unwelcomed comments regarding a person’s lifestyle practices, including those related to food, health, parenting, relationships, and employment
68-
Ask someone before you hug them; keep your hands/body to yourself, even when joking, unless the other person has given verbal consent | Initiate physical contact or simulate physical contact without consent
69-
Disengage and find another activity if someone did not invite you and is not engaging with you | Violate personal space by continuing your physical presence into private spaces without consent
70-
Exercise the right to talk about your own identity if you want to, or not if you don’t want to | Deliberately “out” any aspect of a person’s identity without their consent
71-
Use the pronouns people have specified for themselves | Purposely misgender someone (ie, refusing to use their correct gender pronouns) after they have told you their correct pronouns
72-
73-
74-
## Additional guidelines for online community behavior
75-
76-
77-
Online modes of interaction involve large numbers of people without the helpful presence of gestural, expression, and tonal cues regarding consent. Because of this, respectful and self-aware online conduct is both especially important and difficult. Our community has evolved specific guidelines for online interactions.
78-
79-
_If someone violates these guidelines, someone from the Moderators group will place them into moderation by changing that person’s posting permission on the relevant list, on the website, or both._
80-
81-
Our triple notification standard for moderation means a point person from the Moderators group will:
82-
83-
1. e-mail the person directly with a brief explanation of what was violated,
84-
2. send a summary email to the rest of the moderators group,
85-
3. if it happened on a public list (vs a website), notify the list that one of our members has been placed into moderation with a brief explanation of what is not tolerated.
86-
87-
88-
If you wish to begin the process of getting out of moderation, respond to the email sent to you from [[email protected]](mailto:[email protected]). The Moderators group has the option to involve ConductCom.
89-
90-
91-
Do | Don’t
92-
-------|--------
93-
Stay on topic to make long threads easier to follow |Send spurious one-line responses that effectively "spam" hundreds of people and lower the overall content quality of a conversation. (Exception: expressions of appreciation and encouragement!)
94-
Start a new thread to help others follow along. Important if your response starts to significantly diverge from the original topic | Respond with off-topic information making it hard for the large group of readers to follow along
95-
Write short and literal subject lines to help the readers of the list manage the volume of communication | Humor and euphemisms in subject lines are easily misunderstood, although enthusiasm is welcome!
96-
Mind your tone. We are not having this conversation in person, so it is all the more important to maintain a tone of respect | Write in aggressive tone, disrespectful tone, mocking tone, off-color tone. Note: writing in all caps is regarded as shouting
97-
98-
## Media Consent
99-
100-
* ALWAYS check with parents about posting anything with minors.
101-
* Never post the names of minors in conjunction with their photo.
102-
* During multi-day events like Barnraisings most people will have signed media releases. Those who haven’t will be responsible for placing stickers on their nametags, and/or raising their hands in the moment to alert photographers to move them out of frame.
103-
* For events where people have not signed blanket media release forms, the photographer is responsible for letting the room know that you are taking photos that will be posted online. Pay special attention to the presence of minors and their parent's wishes.
3+
_Public Lab, 55 Cromwell Street, 1C, Providence, RI 02907_
1044

5+
We are coming together with an intent to care for ourselves and one another as we produce knowledge in pursuit of environmental justice. For this to work for everybody, individual decisions will not be allowed to run counter to the welfare of other people. We—visitors, community members, community moderators, staff, organizers, sponsors, and all others—hold ourselves accountable to the same values regardless of position or experience. This community aspires to be a respectful place both during online and in-person interactions so that all people are able to fully participate with their dignity intact. This document is a piece of the culture we're creating.
1056

106-
## Addendum for all staff
7+
This code of conduct applies to all spaces managed by the Public Lab community and non-profit, both online and in person. It provides a clear set of practical guidelines for events led by organizers and community members, multi-day events such as Barnraisings, and online venues such as the website, comment threads on software platforms, chatrooms, our mailing lists, the issue tracker, and any other forums created by Public Lab which the community uses for communication. For interactions with additional groups, see our Partnership Guidelines at https://publiclab.org/partners.
1078

108-
Staff are bound by their Employment Handbook, you must reference it. Additionally:
9+
To read the full Code of Conduct and learn how to contact the Conduct Committee or the Moderators group, see:
10910

110-
* Direct problems that come up among community members to the Conduct Committee.
111-
* When organizing events, circulate access information regarding wheelchair-accessible ADA bathrooms, non-gendered bathrooms, the presence of stairs or curb ramps in the parking lot, et cetera.
112-
* During events that you are attending in person, solve accessibility issues by making sure attendees know where bathrooms are located and can access them by wheelchair without being obstructed by things like chairs, kites, contraptions, or cords.
113-
* Watch for people feeling left out and include them.
11+
https://publiclab.org/conduct

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ A platform dedicated to community growth and getting insights on organization-wi
88
[![visit here](https://img.shields.io/badge/live_at-URL-yellow)](https://code.publiclab.org/)
99
[![GitHub license](https://img.shields.io/github/license/publiclab/community-toolbox)](https://github.com/publiclab/community-toolbox/blob/main/LICENSE)
1010
[![GitHub stars](https://img.shields.io/github/stars/publiclab/community-toolbox)](https://github.com/publiclab/community-toolbox/stargazers)
11-
[![Newcomers welcome](https://img.shields.io/badge/newcomers-welcome-pink.svg)](https://img.shields.io/badge/newcomers-welcome-pink.svg)
11+
[![Newcomers welcome](https://img.shields.io/badge/newcomers-welcome-pink.svg)](https://code.publiclab.org)
1212

1313

1414
## Table of Contents
@@ -74,4 +74,4 @@ There are 3 major categories to this:
7474

7575
### Up next
7676

77-
- ### [Getting started guide](./docs/getting_started.md)
77+
- ### [Getting started guide](./docs/getting_started.md)

0 commit comments

Comments
 (0)