organizers

• Learn to run an event and get pro-tips from other organizers in the organizers wiki
• Ask a question or browse discussions in the organizers discussion board

If you are an existing organizer, or intend to become one in the future please read and abide by our code of conduct.

How to start a new NodeSchool chapter

First, open an issue on this repo asking to get added as a chapter organizer

Your issue should say something like this (not everything is required but it's nice to tell us a little about yourself so you don't come across as a total stranger):

Hi, I would like to start a nodeschool chapter for [name of geographic community]. I am [@your twitter name] on twitter and work at/on . I will be co-organizing this chapter with [names of other organizers]. I have been using Node.js for 6 months and would like to help others learn as well.

The chapter name should preferably be the name of the city, where the workshops will be held. Alternatively the area should be small, but yet meaningful, e.g princeton instead of new-jersey or usa. Also the repo name should be short and all lowercase.

An existing Owner will have to respond and create your Chapter repository for you

Once you are an organizer follow these instructions to set up your NodeSchool chapter:

1

You should have been added to the team called chapter-organizers and should have access to edit the new chapter repo, e.g. https://github.com/nodeschool/berlin

2

Each chapter can set up their own gh-pages branch on their org and github pages will automatically route nodeschool.io/<reponame> to it

For example we have Oakland and Berlin.

@finnp forked the csvconf website and set up a gh-pages branch for the berlin repo and thanks to the awesomeness that is GitHub Pages this url automatically works: http://nodeschool.io/berlin/

You should create a code of conduct for your website and repository. You can use this template as a starting point. Make sure to make all people feel welcome at your event.

Another bonus feature is that you can simply use gitter.im/nodeschool/<chaptername> to automatically get a chat room for your chapter.

3

This step is important for discoverability!

Once your chapter is up and running, make a pull request to the NodeSchool website to add a chapter JSON file to the /chapters directory. When your request is accepted, your chapter will get auto-added to http://nodeschool.io/chapters.html

The chapter JSON file should look something like this:

{
  "name": "Baltimore NodeSchool",
  "location": "Baltimore, MD",
  "country": "US",
  "region": "North America",
  "organizers": ["jasonrhodes"],
  "website": "https://nodeschool.io/baltimore",
  "twitter": "bmorenodeschool",
  "repo": "https://github.com/nodeschool/baltimore"
}

Chapter JSON field info:

field	description
name*	Whatever you call your event, often <location> NodeSchool
location*	This appears on the chapters.html page, often <City> or <City, State> but can be any geocode-able string
country	If your location isn't a country, list the ISO-3166 2-letter country code for consistency
region*	Choose an existing region from the chapters page if possible--if not then pick a broad, non-country region name
organizers	An array of GitHub usernames
website	URL to the main website for your chapter, if one exists besides your GitHub repo
repo*	GitHub repo URL
other?	Any other services like Twitter, Gitter, etc. that exist for the chapter (not the organizer's info)

*required

---

That's all the mandatory steps. Here are some optional steps:

Add your events to the NodeSchool webpage

Fill out this form to add your event to the website.

Make a logo

You can use this .AI/.SVG template to design your own custom nodeschool sticker/logo. There is also a design helper for the browser based on the design for sketching a simple sticker. A sticker specification can be found here.

Benefits of this approach

• chapters get their own "mailing list" (github issues). These can be in other languages as well, e.g. Spanish for Latin-American Chapters, whereas the main Discussions repo is primarily in English
• all NodeSchool attendees leave with a GitHub account and a community they can ask questions to
• chapters get their own website
• since all chapter members are open open source style contributors it means everyone gets empowered to help moderate discussions and improve the chapter website
• we can list all of the chapters on the nodeschool site