I'm organizing NodeSummit's Day 0 NodeSchool event, Monday, February 9 @ 9a-12. The room fits 100 and I'm hoping for 10+ mentors. We currently have the 4 BayNode organizers committed (myself + @generalhenry @rosskukulinski @tonypujals ). Hoping @mikeal @substack @maxogden et. al. will join.

We're planning 2-3 tracks with 3 sessions and 1 workshop per session.

Currently schedule:
9:00-9:30 - Node primer
9:30-10:20 - Session 1
10:20-11:10 - Session 2
11:10-12:00 - Session 3

Track "Beginner": javascripting + count-to-6, learnyounode, promise-it-wont-hurt or async-you
Track "Advanced": functional-javascript-workshop, expressworks or makemehapi or kick-off-koa, stream-adventure
Track "Non-web": (I'm unfamilliar with these) bug-clinic, bytewiser, goingnative

Further, we can group tracks near each other, pair people up, have a local npm mirror, have a runnable for each of the workshops, etc...

Mozilla is hosting us on July 25th from 1pm - 5pm. The address is: 2 Harrison St, San Francisco, CA 94105

As before, we'd like to stay close to a 5:1 attendee:mentor ratio. We're accepting up to 50 attendees for this workshop. So we'll need about 10 mentors.

Mentors should commit to completing (or have already completed) the core NodeSchool workshoppers before the event. Having also completed elective workshoppers is a great bonus. We also encourage mentors to review the Mentorship Guidelines and Advice wiki page.

Comment to get involved or ask questions.

Confirmed mentors:

• @LindsayElia
• @Trott
• @erikasf
• @paulgrock
• @prattsj
• @derekr
• @upekabee
• @stevengill
• @groundwater
• @negomi
• @bengl

Organizers and helpers:

• @jedireza
• @llkats

Todo issue so I don't forget! I'm planning on carving out a little time to look at this tomorrow (Sunday) afternoon (PST). I can take a first pass at getting some original content on the page; will try to find some nice open-source templates, and will always take any design help that I can get. :)

This is the url: http://nodeschool.io/sanfrancisco/

We need to edit this branch: https://github.com/nodeschool/sanfrancisco/tree/gh-pages

(☞ﾟヮﾟ)☞

Drop me a note - [email protected] or [email protected]!

I am the new coordinator for Pittsburgh NodeSchool :)

-Mitch

Please add a Code of Conduct file customized for San Francisco with contact information to this repository, so we can reference it and foster an awesome community with it. :)

For example, Berlin Node School: https://github.com/nodeschool/berlin/blob/master/codeofconduct.md

There's a bug in docs.min.js (it's trying to load the zeroClipboard SWF file from /assets/flash but since the site's docroot is a subdirectory, it doesn't find it) but it's not obvious how docs.min.js is built. No other files mention /assets/flash so the source file is quite likely not in the repo at all.

For our next session, I'd love to offer to lead a group in working through @jlord's amazing git-it workshopper, with a special focus on opening issues and contributing changes to the nodeschool workshoppers themselves.

In workshopper fashion, git-it is still self-directed, but I would also like to cover topics like: creating issues on a repository, code reviews, and other general skills on how to contribute to open source on github. Right now, I envision this as a more guided session where we all progress through the chapters of git-it together, making sure everyone is on the same page. After we have finished, then there will be a talk component where I present on how to create issues and demonstrate how a code review might work on a demo repository, and also discussion and ideas about how contributions could be made to improve Nodeschool workshoppers themselves.

This will be a special session for people who have not contributed to a project on GitHub before. It would occur at the same time as what I'm thinking of as "OG Nodeschool SF" or "OGNSF" (pronounced og-sniff). We will continue to accommodate people who want to work on javascripting or learnyounode, but because this will be a more focused session, people who interested in git-it will move to a separate area to facilitate this workshopper.

Reza and I explored an adjacent room to the room we were in at Mozilla HQ where there are desks and whiteboards and stuff that would be perfect for hosting a more focused meeting. It looked like it could accommodate maybe 20-25 people? Thus, 3-4 mentors who are interested in helping with this session as people work through the exercises would be most appreciated.

Comments? Suggestions? Want to help out? Please let me know here!

Mentors

• @llkats
• @Trott
• or you?
• maybe you?

In spirit of getting ahead of the curve let's start kicking around ideas for June.

Can you believe this month's workshop is already our 6th event?! So far we've used the stock NodeSchool hexagon sticker using different colors for each month. I'm thinking for this month we could use all the colors of our previous stickers together. Thanks @llkats for the idea about inverting the artwork.

• add sticker order
• add pizza order (June workshop)

We need to mention the time and place for the event on the website.

a single line scroll in the http://nodeschool.io/sanfrancisco web page causes an update to the back button history. after a little scrolling around the back button history is filled. the problem is in custom.js

if (window.curpage != $s.name) {
var $link = $('ul.nav > li > a[href="#' + $s.name + '"]');
$('ul.nav > li').removeClass('active');
$link.parent().addClass('active');
   history.pushState(null, null, $link.attr('href')); ??? THIS IS EXECUTED ON EVERY PAGE SCROLL**
}

at least, it is in chrome

Finesse the copy on the homepage to be engaging and welcoming for Node beginners, localized for SF. Include details about the upcoming event on February 7th. Work with anyone doing design to make new sections or organize copy.

Let's share some ideas about logo/sticker colors.

You can create them in the browser here:
http://www.finnpauls.de/nodeschool-stickerify/

I'm starting not to like having a paywall for attendees. We started charging to separate the serious from the curious and to help offset the minor costs we incur (ex: stickers/food). We've seen that even if people pay for their ticket that many (~40%) still no-show.

The costs are low to host a workshop. I'd like to try getting financial sponsors and having a free Tito registration for attendees.

Thoughts? Concerns?

I'd like to gather feedback from attendees. This would require two things: a mechanism to collect feedback, and messaging on the homepage (possibly twitter, etc.) to solicit information.

I think GitHub Issues would be a fine way to collect feedback, though maybe people think a Google Form might be more suitable? Or we could lean on GitHub Issues and designate an email address for feedback anyone feels the need to give anonymously. I prefer organizing in the open, but as always, people might be more comfortable with a form or email.

Thoughts pls 😃 🙏 🙇 👋 👯

package.json still has all the Campinas stuff.

Please let me know how it went! Any improvements, what you liked or didn't like - let me know!

We should optimize the images used on the site (reducing their size) and save them to the repo instead of pointing to flickr.com

Mozilla is hosting us on August 29th from 1pm - 5pm. The address is: 2 Harrison St, San Francisco, CA 94105

As before, we'd like to stay close to a 5:1 attendee:mentor ratio. We're accepting up to 50 attendees for this workshop. So we'll need about 10 mentors.

Mentors should commit to completing (or have already completed) the core NodeSchool workshoppers before the event. Having also completed elective workshoppers is a great bonus. We also encourage mentors to review the Mentorship Guidelines and Advice Mentor Best Practices wiki page.

Comment to get involved or ask questions.

Confirmed mentors:

• @Trott
• @paulgrock
• @wfro
• @rstormsf
• @JonAbrams
• @Fauntleroy
• @kemitchell
• @swang
• you?
• you?

Organizers and helpers:

• @jedireza
• @llkats

We'd love to hear what experiences you thought were good and what you think could be better. We prefer to organize and collaborate in the open and when you need to reach us privately you can always send emails to [email protected].

Okay.... go 💃

Adobe is hosting us on June 27th from 1pm - 5pm. The address is: 601 Townsend St SF, CA 94103

We like to stay close to a 5:1 attendee:mentor ratio. We're accepting up to 50 attendees for this workshop. So we'll need 8-9 mentors.

Mentors should commit to completing (or have already completed) the core NodeSchool workshoppers before the event. Having also completed elective workshoppers is a great bonus.

Comment to get involved or ask questions.

Confirmed mentors:

• @bengl
• @paulgrock
• @smallhaxe

Organizers and helpers:

• @Trott
• @stevengill

We should remove the text/links for the previous event and replace it with something generic until we plan the next event.

Due to some great conversations at our last event, there is some movement to get a regular Oakland Nodeschool going again. If you are so inclined to pitch in, let them know at the issue in their repo!

Set up a Google Analytics account for the site so we can track engagement.

NodeSchool: NodeSummit 2015

nodeschool.io is a community driven, open source educational software that teaches various node.js and JavaScript skills in an interactive, self-guided format.

Beginner

• 09:00 - Node.js primer
• 09:30 - javascripting & count-to-6
• 10:20 - learnyounode
• 11:10 - async-you or promise-it-wont-hurt

** Don't have node.js installed yet? All the Beginner Track workshoppers are on CodeFresh!

Advanced

• 09:00 - functional-javascript-workshop
• 10:00 - expressworks or kick-off-koa or makemehapi
• 11:00 - stream-adventure

Non-web

• 09:00 - bug-clinic
• 10:00 - bytewiser
• 11:00 - goingnative

Thanks Mentors!

Ross Kukulinksi, Yodlr & BayNode
Tony Pujals, BayNode
Luca Maraschi, Joyent
Jacob Chapel, WalmartLabs
Mikeal Rogers, DigitalOcean
Meadhbh Hamrick
Oleg Polyakov, AQI
Poornima Venkat, PayPal
Richard Littauer, MIT Media Lab
Reza Akhavan, Yahoo!
Rich Trott, UCSF

International Day is May 23rd, 2015

http://nodeschool.io/international-day/

We'd love to hear what experiences you thought were good and what you think could be better. We prefer to organize and collaborate in the open and when you need to reach us privately you can always send emails to [email protected].

Okay.... go 🏃

Per discussion here, we need to track RSVPs and charge a nominal entrance fee to ensure attendance. Let's discuss which method we want to use (Meetup and/or Tito) and get those accounts created. After creation, update the site with links to the signup page(s).

Tradecraft is hosting us on March 28th from 1pm - 5pm. The address is: 855 Front Street 94111

We like to keep a 5:1 attendee:mentor ratio. We're accepting 40 attendees for this workshop. So we'll need 8 mentors.

Mentors should commit to completing (or have already completed) the core NodeSchool workshoppers before the event. Having also completed elective workshoppers is a great bonus.

Comment to get involved or ask questions.

Confirmed mentors:

• @thealphanerd
• @Trott
• @bengl
• @lizTheDeveloper
• @Rolken
• @MrBri
• @brianleroux
• @Yonet
• @100ideas

Organizers and helpers:

• @jedireza
• @llkats
• @duquet

Looks like the automatic closing of tickets isn't happening based on the "fix/resolve/close" words in PRs and issues because the default branch is master but all the action is over in gh-pages. It might be a good idea to make gh-pages the default branch and delete the master branch. People who have forked may need to adjust their remotes if you do this and/or do this in their own forks. I'm not sure. But hopefully that's a pretty small number right now of mostly power-users.

continued from nodeschool/organizers#92

it looks like we've all expressed interest in having a first NodeSchool event on Sat Feb 7th from 12-5pm at New Relic's class space. let's continue the discussion here

Had some questions about mentoring this session, which I was woefully ill-equipped to answer. This is a reminder issue to write up some mentorship guidelines in the wiki with advice for mentors attending the sessions, helpful hints, what to expect, and general reassurances. Ideas welcome!

Would love to customize our site to differentiate from Campinas, which the site was forked from. Anyone feel like taking the reins?

Things to potentially tackle:

• background images, pictures
• color scheme
• custom icons?

FYI: I'm working to get access to the Mozilla SF commons. I'll update this thread as I learn more.

UPDATE: Mozilla office confirmed.

• create attendee (Tito) registration
• create mentor (GitHub) registration

We would like the attendee:mentor ratio to be at 5:1.

At present we've @groundwater, @linclark and @RichardLitt confirmed as mentors.

@maxogden @jedireza @tlhunter @cantremember @johnmarkos @bengl your names have all come up at as being interested in mentoring. Are you available Saturday, February 7 from 1-5pm? If not that's a-ok :)

Confirmed mentors:

• @jedireza
• @johnmarkos
• @cantremember
• @bengl
• @wraithan
• @Trott
• @tlhunter

Organizers and helpers:

• @llkats
• @RichardLitt
• @agminusthev

@llkats and I are big fans of organizing in the open. During the last meeting we posted a wiki page of the Announcements Script which are just some notes for that day's organizers to make sure proper shout outs are given and that important info is covered (like the Code of Conduct) 🙏.

We've been charging a $5 cover for attendees to help separate the serious from the curious and also help cover costs of things like stickers.

Some details on how things are currently setup... I setup a Stripe account that we linked to a Tito account for ticket sales. That Stripe account is linked to my personal Simple bank account. When we've needed to make purchases, I paid for it with whatever card or cash available and kept the receipts.

You may wonder what happens with all those bags of money 💰💰💰 from the ticket sales.

To keep things transparent and make it easy for any future organizers to follow suit, we created a new branch on our repo called ledger where we can keep track of this stuff: https://github.com/nodeschool/sanfrancisco/tree/ledger

Feel free to ask questions or talk about related ideas. I plan to close this thread after a few days of inactivity.

Hey peeps, here are some pics and the videos from the event. Could someone please edit the videos to only the necessary parts and then figure out where to submit them? Thanks!

https://dl.dropboxusercontent.com/u/37968874/nodeschool%20sf%20may%202015.zip
https://dl.dropboxusercontent.com/u/37968874/nodeschool-1.MOV
https://dl.dropboxusercontent.com/u/37968874/nodeschool-2.MOV

• next event should be updated
• students and mentors section links need to be updated

Folks,

I was referred to nodeschool from a recent event attendee and, after learning about the program, I'd like to explore hosting an event at our coding bootcamp program.

Location: 633 Folsom Street, San Francisco, CA 94107

We have a lot of space here and believe it to be a good fit for your needs. Please contact me at [email protected]. I'll happily show a scout around the space, if you'd like.

Thanks!

Andrew Fitch
781-812-5465
[email protected]

Tradecraft was a great location and @lizTheDeveloper mentioned that they'd be happy to have us again. It's also fun to see new locations so if you know of a place please share in the discussion.

Just like before, we need to choose a date, time and location. 🌈

Tradecraft is hosting us on March 28th from 1pm - 5pm. The address is:

855 Front Street
San Francisco, 94111

Attendees may register here: https://ti.to/nodeschoolsf/march-28th-2015
Mentors may register here: #50

We have a bunch of photos to add to the website. I think we could do better than the wide horizontal images we currently have. Maybe something more like a carousel could serve us better long term and not limit us to just one photo per event.

selfexplanatory :)

Blizzard(!!!) is hosting us on May 23rd from 1pm - 5pm. This is International Day, so it's sure to be a special event!

We will continue with the 5:1 attendee:mentor ratio and accept 40 attendees as before, which requires 8 mentors.

Mentors should commit to completing (or have already completed) the core NodeSchool workshoppers before the event. Having also completed elective workshoppers is a great bonus.

Comment to get involved or ask questions.

Confirmed mentors:

• @thealphanerd
• @cantremember
• @Trott
• @stevengill
• @wfro
• @bdeanindy
• @derekr
• ?

Organizers and helpers:

• we'll miss you @jedireza!!
• @llkats
• @paulgrock

https://ti.to/jquerysf/2015/discount/jquerySF-appeciates-nodeschoolSF

👷 💪

At the last event some people said a monthly event was a reasonable goal. Should we shoot for round 2 in March?

Next Event: In planning stage

Join the conversation (links to #56)