A discussion repository for nodeschool organizers
First, open an issue on this repo asking to get added as an Owner
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 <name of company or project>. 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.
Once you are an owner follow these instructions to set up your NodeSchool chapter:
Chapter owner should create a repo for their chapter, e.g. https://github.com/nodeschool/berlin
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. If you are covering multiple cities, consider creating multiple repos.
Also the repo name should be short and all lowercase (since this will also be your chapter url, see step 4).
Chapter owner should make a new Team on the nodeschool org with the same name. The owner then has to go into the chapter org and specifically add the chapter team as a collaborator:
Everyone who ever attends a nodeschool event by that chapter should added as a member of the chapter team by the Owner (so they can open/close issues and push to the chapter org but can't e.g. delete repos). People can obviously decline the invitation to get added.
A note on github orgs: Only Owners can add new team members. The original Owner can add other trustworthy people from the chapter to the Owners team so that they can also add NodeSchool attendees to your chapter's team. Please use good judgment when adding new Owners, as Owners also have the ability to delete other chapter's repositories.
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 repos now, and I made corresponding teams
@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.
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": "http://nodeschool.io/baltimore",
"twitter": "bmorenodeschool",
"repo": "http://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:
Fill out this form to add your event to the website.
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.
- 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
- chapters can start quantifying their membership
- chapters can get pinged using
@nodeschool/<teamname> - 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