Skip to content

Commit 15872f7

Browse files
dannyadairdannyadair
committed
Add Event Organisers documents
1 parent 19f4fc7 commit 15872f7

File tree

5 files changed

+262
-6
lines changed

5 files changed

+262
-6
lines changed

‎bylaws/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
| ------------------------------------- | ----------- | ------ |
55
| [Activities](activities.md) | 29 Sep 2025 | Draft |
66
| [Bank](bank.md) | 22 Oct 2025 | Draft |
7-
| [Event Organisers](event_organisers/) | 29 Sep 2025 | Draft |
7+
| [Event Organisers](event_organisers/) | 11 Nov 2025 | Draft |
88
| [Membership](membership.md) | 29 Sep 2025 | Draft |
99
| [Term limits](term_limits.md) | 29 Sep 2025 | Draft |
1010
| [Transparency](transparency.md) | 29 Sep 2025 | Draft |

‎bylaws/event_organisers/README.md‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Event Organisers (Bylaw)
22

3-
**Python New Zealand<br> Last update: 29 Sep 2025<br> Status: Draft**
3+
**Python New Zealand<br> Last update: 11 Nov 2025<br> Status: Draft**
44

55
The relationship between Python New Zealand and individual event organisers is described
66
by three documents:
@@ -10,7 +10,4 @@ by three documents:
1010
- [Event Organiser Commitment](commmitment.md) - a form signed by event organisers to
1111
confirm their commitment
1212
- [HOWTO Python New Zealand Events](howto_events.md) - describes "how we currently do
13-
things" - the framework organisers are expected to follow
14-
15-
**Note: These are currently in a separate repository while the initial versions are
16-
being finalised between committee and current organisers.**
13+
things"

‎bylaws/event_organisers/commitment.md‎

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
# Python New Zealand - Event Organiser Commitment
2+
3+
As an organiser of one or more events under the banner of Python New Zealand, I
4+
understand that I am representing the charity. I commit to the following:
5+
6+
1. I will ensure these events align with the spirit and mission of Python New Zealand,
7+
as outlined in section "4. Purposes" of the Society’s Constitution (see Appendix A).
8+
2. I will ensure that all participants adhere to Python New Zealand’s Code of Conduct
9+
(see Appendix B), and I will report any breaches to the committee.
10+
3. I will use the Python New Zealand name and logo only as provided, and in accordance
11+
with any branding guidelines.
12+
4. If I promote non-Python New Zealand events via Python New Zealand platforms or
13+
channels, I will clearly indicate that they are not affiliated with Python New
14+
Zealand.
15+
5. I understand that my access to Python New Zealand platforms and tools may be revoked
16+
if I breach this commitment. Final decisions rest with the Python New Zealand
17+
committee.
18+
19+
**Type of event(s):** **\*\***\*\***\*\***\_**\*\***\*\***\*\***
20+
21+
**Name:** **\*\***\*\***\*\***\_**\*\***\*\***\*\***
22+
23+
**Role:** **\*\***\*\***\*\***\_**\*\***\*\***\*\***
24+
25+
**Date:** **\*\***\*\***\*\***\_**\*\***\*\***\*\***
26+
27+
**Signature:** **\*\***\*\***\*\***\_**\*\***\*\***\*\***
28+
29+
_Note: See Appendix A (excerpt from the Cconstitution) and Appendix B (Code of Conduct).
30+
The two documents referenced in point 5 are available at_
31+
[_github.com/pythonnz/rules_](https://github.com/pythonnz/rules).
32+
33+
## Appendix A
34+
35+
### Constitution
36+
37+
_Excerpt from
38+
[https://python.nz/about/constitution](https://python.nz/about/constitution)_
39+
40+
### **4. Purposes**
41+
42+
4.1. The **Society** is established and maintained exclusively for charitable purposes
43+
(including any purposes ancillary to those charitable purposes), namely:
44+
45+
- (i) advancing education by providing meetups, courses, conferences, and written
46+
information around the Python programming language to the public.
47+
- (ii) as a support community for the Python programming language.
48+
- (iii) as a vector for the promotion of the Python programming language within
49+
non-profit, commercial and industrial organisations.
50+
- (iv) as a vector for the promotion of the Python programming language within
51+
government bodies, including but not limited to educational bodies of all levels,
52+
medical bodies, local and national government, and political parties.
53+
54+
<!-- -->
55+
56+
4.2. Any income, benefit, or advantage must be used to advance the charitable purposes
57+
of the **Society**.
58+
59+
## Appendix B
60+
61+
### Code of Conduct
62+
63+
_From
64+
[https://python.nz/about/code-of-conduct/](https://python.nz/about/code-of-conduct/)_
65+
66+
Python New Zealand aims to foster an inclusive community which invites diverse groups of
67+
people from all backgrounds, regardless of age, body size, race, gender, gender identity
68+
and expression, sexuality, disability, or religion to discuss and learn about all things
69+
Python in an environment of mutual respect, tolerance and encouragement.
70+
71+
Python New Zealand organises and sponsors a diverse range of online and physical spaces
72+
including (but not limited to) the Python New Zealand mailing list, the Kiwi PyCon
73+
conference, our online chat channels, and local Python meetups. In order to achieve our
74+
goals, we encourage all participants to create a friendly, welcoming environment for
75+
everyone involved.
76+
77+
We expect participants to treat each other respectfully. Python New Zealand will not
78+
tolerate any intimidation, harassment, and/or any abusive, discriminatory behaviour by
79+
any participants. The use of inappropriate, derogatory, and/or offensive
80+
content/behaviour in any of these spaces is strictly prohibited. The Python New Zealand
81+
committee has the final decision on what is acceptable behaviour. A breach of conduct
82+
may lead to disciplinary actions, up to and including dismissal from the Python New
83+
Zealand related events and spaces.
84+
85+
If you see or hear something that makes you uncomfortable, we encourage you to make a
86+
complaint. To make a complaint:
87+
88+
1. Contact the organisers of the event (if applicable), or members of the Python New
89+
Zealand committee [[email protected]](mailto:[email protected]).
90+
2. You may also contact any member of the committee individually if you prefer.
91+
92+
If you make a complaint, the Python New Zealand committee undertake to:
93+
94+
1. Keep your identity private, maintaining your anonymity.
95+
2. Take your complaint seriously, investigate the incident, and take any action we deem
96+
necessary.
97+
3. The committee may, at its discretion, publish a ‘transparency report’ to the Python
98+
New Zealand mailing list that includes the nature of the complaint and what the
99+
committee decided to do about it. These reports help us inform the community of the
100+
actions the committee have taken, and will be published unless there’s a good reason
101+
not to. In all cases, the offender and the complainant will be made anonymous in any
102+
such report.
103+
104+
Python New Zealand may take any or all of the following measures:
105+
106+
- The offender may be told to stop/modify their behaviour appropriately and a warning
107+
will be issued.
108+
- The offender may be asked to immediately leave the venue/space.
109+
- The offender may be prohibited from continuing to attend any Python New Zealand-based
110+
events.
111+
- The incident may be reported to New Zealand Police.
112+
113+
Python New Zealand is aware of the responsibility required to ensure a successful and
114+
productive community now and in years to come, and will take appropriate measures after
115+
an incident occurs to prevent it from happening again.

‎bylaws/event_organisers/event_organisers.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
# Python New Zealand and Event Organisers
2+
3+
## Aspirations / Expectations / Responsibilities / Commitments
4+
5+
## As an Event Organiser
6+
7+
### I want to
8+
9+
- bring people together for Python-related events
10+
- be recognised for my contributions to Python New Zealand’s mission
11+
12+
### I don’t want to
13+
14+
- “start from scratch” creating an identity, framework, rules, finding participants
15+
- spend money
16+
17+
### I’m willing to commit to
18+
19+
- **spending time** organising events (e.g., finding speakers/content, chairing the
20+
events)
21+
- ensuring the events follow **Python New Zealand’s spirit and mission**
22+
- ensuring participants of the events follow **Python New Zealand’s Code of Conduct**
23+
24+
## As Python New Zealand
25+
26+
### We want to
27+
28+
- support people organising Python events
29+
- ensure that events in the charity’s name and under its banner follow the charity’s
30+
spirit, mission, and Code of Conduct
31+
32+
### We don’t want to
33+
34+
- support events that do not follow the charity’s spirit, mission, or Code of Conduct
35+
- support event organisers who are in breach of their commitments
36+
37+
### We are willing to commit to
38+
39+
- providing a framework and template for running events, including a **branded presence
40+
on meetup.com** with a co-organiser account able to create and edit events
41+
- enforcing the Python New Zealand **code of conduct** and act on any breaches reported
42+
on by an event organiser (or anyone else)
43+
- assisting event organisers in their **marketing efforts** with exposure on
44+
- other meetup groups owned by Python New Zealand
45+
- the Python New Zealand website [https://python.nz/news](https://python.nz/news)
46+
- the Python New Zealand nationwide event calendar (in preparation)
47+
- Python New Zealand social media accounts where required: Bluesky, Facebook,
48+
LinkedIn, Mastodon
49+
- the Python New Zealand (“NZPUG”) mailing list
50+
- assisting event organisers with a **communication channel** on our Slack chat
51+
platform, available for coordinating event organisation and communication with
52+
members/participants (e.g., #meetup-yourcity)
53+
- assisting event organisers with **branded material** used in running events (e.g.,
54+
laminated posters for various purposes at the venue)
55+
- assisting event organisers in the search for **venues and catering**, e.g.,
56+
approaching potential sponsors as a registered charity rather than a private
57+
individual
58+
- assisting event organisers by holding a **regular organisers meeting** online across
59+
all event organisers for the purpose of exchanging experiences and coordinating joint
60+
efforts and overlaps
61+
- assisting event organisers directly with **timely responses to enquiries** and
62+
suggestions sent to [[email protected]](mailto:[email protected]) by event
63+
organisers
64+
- being open to considering **any other type of support** that organisers may request
65+
- **recognising event organisers** and their efforts officially: on the Python New
66+
Zealand website, in newsletters and blog posts, at the Annual General Meeting.

‎bylaws/event_organisers/howto_events.md‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
# HOWTO Python New Zealand Events
2+
3+
This document describes "how we currently do things".<br> Rather than a prescriptive
4+
rulebook it is meant to be a useful reference, esp. for new organisers.
5+
6+
This is a living document. It may be incomplete and/or inaccurate. The tools we use may
7+
change. How we do things evolves.
8+
9+
**Any changes to this document will continue to reflect the expectations and commitments
10+
outlined in
11+
["Python New Zealand and Event Organisers"](https://github.com/pythonnz/event-organisers/blob/main/PythonNZ/event_organisers.md).**
12+
13+
## Monthly Meetups
14+
15+
### Other Organisers
16+
17+
- All meetup organisers are added to the mailing list [email protected]
18+
19+
- We aim to meet monthly via videoconference, for a general catchup and exchange of
20+
experiences, and to discuss matters concerning all organisers.
21+
22+
### Organising - meetup.com
23+
24+
- We use [meetup.com](https://meetup.com/) and event organisers need to join their group
25+
and then get account permissions that allow them to create and edit events.
26+
27+
- We currently have 4 groups: [Auckland](https://www.meetup.com/pythonnz-auckland/),
28+
[Wellington](https://www.meetup.com/pythonnz-wellington/),
29+
[Christchurch](https://www.meetup.com/pythonnz-christchurch/) and
30+
[Online Events](https://www.meetup.com/pythonnz-online/).
31+
32+
- Monthly Meetup Report<br> Event organisers fill out
33+
[this form](https://docs.google.com/forms/d/187tNDu20tf-vZf-hPrip3S6muMFjqYNTBebSDf16Jck/edit)
34+
after each event, to help us keep track of statistics (for the annual report to
35+
Charities Services and for ourselves).
36+
37+
### Chat
38+
39+
- The Python New Zealand
40+
[Slack instance](<(https://python.nz/get-involved/chat-with-the-community/)>) has a
41+
channel for each meetup location. These are not meant for general discussions (which
42+
should happen in `#general`), but rather to coordinate meetups, e.g. last minute
43+
announcements, pickups from venue door, discussion of a specific talk. They follow a
44+
simple naming convention `#meetup-auckland`, `#meetup-wellington`,
45+
`#meetup-christchurch`
46+
47+
### Video conferencing
48+
49+
- There are currently two options being used for running video conferences: Big Blue
50+
Button or Google Meet. The important requirements for a video conferencing platform
51+
are a) it works for all participants b) it doesn't require participants to register an
52+
account.
53+
54+
- Please note that a regular Gmail account will have a 1h limit on video conferences.
55+
Event organisers can get a [email protected] (Google Workspace) account
56+
which does not have this limitation.
57+
58+
### Video recordings
59+
60+
- When video recordings are to be published (with consent of the recorded parties), we
61+
add short intro/outro slides to the video and then upload them to the Python New
62+
Zealand [YouTube channel](https://youtube.com/@PythonNewZealand).
63+
64+
### Advertising
65+
66+
- We start all news items by creating a blog post on https://python.nz/news/ which then
67+
gets disseminated through appropriate channels such as
68+
[mailing list](https://groups.google.com/forum/#!forum/nzpug),
69+
[Slack](https://python.nz/get-involved/chat-with-the-community/),
70+
[BlueSky](https://bsky.app/profile/python.nz),
71+
[Mastodon](https://mastodon.social/@pythonnz),
72+
[Facebook](https://facebook.com/pythonnz),
73+
[LinkedIn](https://nz.linkedin.com/company/pythonnz) and
74+
[Meetup](https://python.nz/get-involved/meet-others/) group announcements. Event
75+
organisers sign up to the [python.nz](https://python.nz) Wordpress site and can then
76+
create blog posts that are then reviewed and published. The PythonNZ committee is
77+
notified when someone creates a blog post to be reviewed, and the author is notified
78+
when it is published.

0 commit comments

Comments
 (0)