Skip to content

Commit 0b0c0f9

Browse files
committed
Update documentation
0 parents  commit 0b0c0f9

File tree

109 files changed

+10214
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

109 files changed

+10214
-0
lines changed
+126
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
<!doctype html>
2+
<html lang="">
3+
<head>
4+
<meta charset="utf-8"/>
5+
<title>PythonKC Code of Conduct - PythonKC</title>
6+
<meta name="author" content="The PythonKC Organizer Team">
7+
8+
9+
<meta name="description" content="PythonKC Code of Conduct">
10+
11+
12+
13+
<link rel="stylesheet" href="/theme/css/main.css" type="text/css" />
14+
15+
16+
17+
</head>
18+
19+
<body>
20+
21+
<div class="container">
22+
23+
<header role="banner">
24+
<div class="feeds">
25+
</div>
26+
<a href="" class="title">PythonKC</a>
27+
</header>
28+
29+
<div class="wrapper">
30+
31+
<div role="main" class="content">
32+
<article class="full">
33+
34+
<h1>PythonKC Code of Conduct</h1>
35+
36+
<div class="metadata">
37+
<time datetime="2015-12-15T00:00:00-06:00" pubdate>Tue 15 December 2015</time>
38+
<address class="vcard author">
39+
by <a class="url fn" href="/author/the-pythonkc-organizer-team.html">The PythonKC Organizer Team</a>
40+
</address>
41+
in <a href="/category/code-of-conduct/">Code of Conduct</a>
42+
<p class="tags">tagged <a href="/tag/pythonkc/">pythonkc</a></p></div>
43+
<p>Like the technical community as a whole, the PythonKC community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the mission - including mentorship, teaching, and connecting people.</p>
44+
<p>Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to. This code applies equally to founders, mentors and those seeking help and guidance.</p>
45+
<p>This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the technical communities in which we participate.</p>
46+
<p>This code of conduct applies to all spaces managed by the PythonKC. This includes PythonKC meetups and events, IRC, Slack, Github, the mailing list, and any other forums created by the PythonKC organizers which the community uses for communication. In addition, violations of this code outside these spaces may affect a person's ability to participate within them.</p>
47+
<p>If you believe someone is violating the code of conduct, we ask that you report it by contacting the organizers via <a href="http://www.meetup.com/pythonkc/members/?op=leaders">Meetup</a>, direct message on <a href="https://pythonkc.slack.com">Slack</a>, or email.</p>
48+
<ul>
49+
<li><strong>Be friendly and patient.</strong></li>
50+
<li><strong>Be welcoming.</strong> We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.</li>
51+
<li><strong>Be considerate.</strong> Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we're a world-wide community, so you might not be communicating in someone else's primary language.</li>
52+
<li><strong>Be respectful.</strong> Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the PythonKC community should be respectful when dealing with other members as well as with people outside the PythonKC community.</li>
53+
<li><strong>Be careful in the words that you choose.</strong> We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren't acceptable. This includes, but is not limited to:<ul>
54+
<li>Violent threats or language directed against another person.</li>
55+
<li>Discriminatory jokes and language.</li>
56+
<li>Posting sexually explicit or violent material.</li>
57+
<li>Posting (or threatening to post) other people's personally identifying information ("doxing").</li>
58+
<li>Personal insults, especially those using racist or sexist terms.</li>
59+
<li>Unwelcome sexual attention.</li>
60+
<li>Advocating for, or encouraging, any of the above behavior.</li>
61+
<li>Repeated harassment of others. In general, if someone asks you to stop, then stop.</li>
62+
</ul>
63+
</li>
64+
<li><strong>When we disagree, try to understand why.</strong> Disagreements, both social and technical, happen all the time and PythonKC is no exception. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of PythonKC comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.</li>
65+
</ul>
66+
<p>Original text courtesy of the <a href="http://speakup.io/coc.html">Speak Up! project</a> and <a href="https://www.djangoproject.com/conduct/">Django</a>.</p>
67+
68+
</article>
69+
70+
<p>
71+
<a href="https://twitter.com/share" class="twitter-share-button" data-via="pythonkc" data-lang="en" data-size="large" data-related="pythonkc">Tweet</a>
72+
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
73+
</p>
74+
75+
76+
</div>
77+
78+
<div class="sidebar">
79+
<div class="sidebar-container" >
80+
81+
82+
<nav>
83+
<h2>Categories</h2>
84+
<ul>
85+
<li class="active"><a href="/category/code-of-conduct/">Code of Conduct</a></li>
86+
<li ><a href="/category/how-to/">HOW-TO</a></li>
87+
<li ><a href="/category/meeting-notes/">Meeting Notes</a></li>
88+
</ul>
89+
</nav>
90+
91+
<aside>
92+
<h2>Social</h2>
93+
<ul class="social">
94+
<li><a href="https://twitter.com/PythonKC">Twitter</a><i></i></li>
95+
<li><a href="https://github.com/pythonkc">GitHub</a><i></i></li>
96+
<li><a href="https://www.linkedin.com/groups/3996011">LinkedIn</a><i></i></li>
97+
</ul>
98+
</aside>
99+
100+
<aside>
101+
<h2>Blogroll</h2>
102+
<ul>
103+
<li><a href="https://www.meetup.com/pythonkc/">PyKC Meetup.com</a></li>
104+
<li><a href="https://pykc-slackipy.herokuapp.com/">PyKC Slack</a></li>
105+
<li><a href="http://docs.getpelican.com/en/stable/">Pelican</a></li>
106+
<li><a href="https://python.org/">Python.org</a></li>
107+
<li><a href="http://jinja.pocoo.org/">Jinja2</a></li>
108+
</ul>
109+
</aside>
110+
</div>
111+
</div>
112+
113+
</div>
114+
115+
<footer>
116+
<p role="contentinfo">
117+
The PythonKC Organizer Team - Proudly powered by <a href="http://alexis.notmyidea.org/pelican/">pelican</a>. Theme <a href="https://github.com/fle/pelican-sober">pelican-sober</a>.
118+
</p>
119+
120+
</footer>
121+
122+
</div>
123+
124+
125+
</body>
126+
</html>
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,135 @@
1+
<!doctype html>
2+
<html lang="">
3+
<head>
4+
<meta charset="utf-8"/>
5+
<title>PythonKC January 2016 Coffee & Code - PythonKC</title>
6+
<meta name="author" content="The PythonKC Organizer Team">
7+
8+
9+
<meta name="description" content="Meeting notes for January 2016 PythonKC Coffee & Code">
10+
11+
12+
13+
<link rel="stylesheet" href="/theme/css/main.css" type="text/css" />
14+
15+
16+
17+
</head>
18+
19+
<body>
20+
21+
<div class="container">
22+
23+
<header role="banner">
24+
<div class="feeds">
25+
</div>
26+
<a href="" class="title">PythonKC</a>
27+
</header>
28+
29+
<div class="wrapper">
30+
31+
<div role="main" class="content">
32+
<article class="full">
33+
34+
<h1>PythonKC January 2016 Coffee & Code</h1>
35+
36+
<div class="metadata">
37+
<time datetime="2016-01-09T00:00:00-06:00" pubdate>Sat 09 January 2016</time>
38+
<address class="vcard author">
39+
by <a class="url fn" href="/author/the-pythonkc-organizer-team.html">The PythonKC Organizer Team</a>
40+
</address>
41+
in <a href="/category/meeting-notes/">Meeting Notes</a>
42+
<p class="tags">tagged <a href="/tag/pythonkc/">pythonkc</a>, <a href="/tag/coffee-code/">coffee & code</a></p></div>
43+
<div class="highlight"><pre><span></span><span class="ch">#!/usr/bin/env python3</span>
44+
<span class="c1"># -*- coding: utf-8 -*-</span>
45+
46+
<span class="k">def</span> <span class="nf">greetings</span><span class="p">():</span>
47+
<span class="k">print</span><span class="p">(</span><span class="s2">&quot;Welcome to PythonKC Coffee &amp; Code.&quot;</span><span class="p">)</span>
48+
<span class="k">print</span><span class="p">(</span><span class="s2">&quot;Today is Saturday 9 January 2016.&quot;</span><span class="p">)</span>
49+
50+
<span class="k">if</span> <span class="vm">__name__</span> <span class="o">==</span> <span class="s1">&#39;__main__&#39;</span><span class="p">:</span>
51+
<span class="n">greetings</span><span class="p">()</span>
52+
</pre></div>
53+
54+
55+
<h2>PythonKC Winter 2016 Meetup</h2>
56+
<ul>
57+
<li><a href="http://www.meetup.com/pythonkc/events/227574245/">Thursday 28 January 2016</a></li>
58+
<li><a href="http://www.batstrading.com">BATS Global Markets</a></li>
59+
<li>Still seeking presentations</li>
60+
</ul>
61+
<h2>PythonKC February 2016 Coffee &amp; Code</h2>
62+
<ul>
63+
<li><a href="http://www.meetup.com/pythonkc/events/227778898/">Saturday 13 February 2016</a></li>
64+
<li>No location yet</li>
65+
</ul>
66+
<h2>PythonKC News</h2>
67+
<ul>
68+
<li><a href="https://github.com/pythonkc/code-of-conduct">Code of Conduct</a></li>
69+
</ul>
70+
<h2>Python News and Resources</h2>
71+
<ul>
72+
<li><a href="https://github.com/amontalenti/elements-of-python-style">The Elements of Python Style</a></li>
73+
<li>Anderson Resende: <a href="http://www.vinta.com.br/blog/2015/functional-programming-python.html">Functional programming in Python the simplest way</a></li>
74+
<li><a href="http://snarky.ca/">Brett Cannon's Blog</a></li>
75+
</ul>
76+
77+
</article>
78+
79+
<p>
80+
<a href="https://twitter.com/share" class="twitter-share-button" data-via="pythonkc" data-lang="en" data-size="large" data-related="pythonkc">Tweet</a>
81+
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
82+
</p>
83+
84+
85+
</div>
86+
87+
<div class="sidebar">
88+
<div class="sidebar-container" >
89+
90+
91+
<nav>
92+
<h2>Categories</h2>
93+
<ul>
94+
<li ><a href="/category/code-of-conduct/">Code of Conduct</a></li>
95+
<li ><a href="/category/how-to/">HOW-TO</a></li>
96+
<li class="active"><a href="/category/meeting-notes/">Meeting Notes</a></li>
97+
</ul>
98+
</nav>
99+
100+
<aside>
101+
<h2>Social</h2>
102+
<ul class="social">
103+
<li><a href="https://twitter.com/PythonKC">Twitter</a><i></i></li>
104+
<li><a href="https://github.com/pythonkc">GitHub</a><i></i></li>
105+
<li><a href="https://www.linkedin.com/groups/3996011">LinkedIn</a><i></i></li>
106+
</ul>
107+
</aside>
108+
109+
<aside>
110+
<h2>Blogroll</h2>
111+
<ul>
112+
<li><a href="https://www.meetup.com/pythonkc/">PyKC Meetup.com</a></li>
113+
<li><a href="https://pykc-slackipy.herokuapp.com/">PyKC Slack</a></li>
114+
<li><a href="http://docs.getpelican.com/en/stable/">Pelican</a></li>
115+
<li><a href="https://python.org/">Python.org</a></li>
116+
<li><a href="http://jinja.pocoo.org/">Jinja2</a></li>
117+
</ul>
118+
</aside>
119+
</div>
120+
</div>
121+
122+
</div>
123+
124+
<footer>
125+
<p role="contentinfo">
126+
The PythonKC Organizer Team - Proudly powered by <a href="http://alexis.notmyidea.org/pelican/">pelican</a>. Theme <a href="https://github.com/fle/pelican-sober">pelican-sober</a>.
127+
</p>
128+
129+
</footer>
130+
131+
</div>
132+
133+
134+
</body>
135+
</html>

0 commit comments

Comments
 (0)