Repository files navigation

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

If you are an existing organizer, or intend to become one in the futureplease read and abide by ourcode of conduct.

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 willbe held. Alternatively the area should be small, but yet meaningful, e.gprinceton instead ofnew-jersey orusa. 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:

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

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

For example we haveOakland andBerlin.

@finnp forked the csvconf website and set upa 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 usethis template as a starting point. Make sure to makeall people feel welcome at your event.

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

This step is important for discoverability!

Once your chapter is up and running, make a pull request to theNodeSchool website to add a chapter JSON file to the /chapters directory. When your request is accepted, your chapter will get auto-added tohttp://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:

*required

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

Fill out thisform to add your event to the website.

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

• 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 areopen 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