Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Code And Learn at Node Interactive in Austin #59

Closed
5 tasks
addaleax opened this issue Oct 13, 2016 · 14 comments
Closed
5 tasks

Code And Learn at Node Interactive in Austin #59

addaleax opened this issue Oct 13, 2016 · 14 comments

Comments

@addaleax
Copy link
Member

Time: December 1, 9 am – 12 am (3 pm – 6 pm UTC).

Todo:

  • Gather and pre-review tasks for participants to address
  • Prepare storage medium (Network storage seems to be the best idea) for downloading a fresh clone of the core repository + eventually needed compilers
  • Get estimates for mentor/attendee numbers
  • Solicit off-site collaborators who can start reviewing PRs while the event is happening
  • Write a proper description of the event for the Agenda
@addaleax
Copy link
Member Author

@nodejs/collaborators: Who of you is going to be at NI NA and is able to help with mentoring Code & Learn attendees? Are some of you likely going to be able to review PRs as they are being opened?

@imyller
Copy link
Member

imyller commented Oct 13, 2016

I'm available for reviewing & mentoring PRs remotely.

I suggest that new (temporary) Github Project is opened for grouping Austion C&L session PRs and special attention is given for those to make it a pleasant experience for participants.

@bengl
Copy link
Member

bengl commented Oct 13, 2016

If I'm at NINA (most likely), I'm in. If not, happy to review.

@Trott
Copy link
Member

Trott commented Oct 13, 2016

I'll be there!

@evanlucas
Copy link

I'll be there and would love to help!

@williamkapke
Copy link

I'll be there in a supportive role (like I did in Amsterdam).

@MylesBorins
Copy link
Contributor

o/

@bmeck
Copy link
Member

bmeck commented Oct 14, 2016

I can be there to help in person :)

@jasnell
Copy link
Member

jasnell commented Oct 14, 2016

I'll be there for sure.

@mcollina
Copy link
Member

I'll be there.

A couple of notes. I think we should come up with more substantial "good-first-contributions", so all mentors should probably engage in creating/tagging some issues before the event.
A massive amount of var -> const is not 100% what it needs.

I think we should also stress the fact that in OSS we triple-check each other work, and it takes a while for a contribution to land. And they need to stick with it, and follow it through till its landed.
There is the misconception that their task was just sending a PR. The amount of back-and-forth and change needed is quite high.

Regarding the fresh checkout, a couple of USB sticks and instructions can do wonders. We can also send them instructions on how to do a checkout before the event.. :)

@lrlna
Copy link

lrlna commented Oct 14, 2016

Ooo! Y'all are doing another one in Austin! I am gonna come again then ^_^

@sam-github
Copy link

I'll be there, I can help.

@addaleax
Copy link
Member Author

Okay I’m closing this in favour of @hackygolucky’s #60, that seems a bit more organized, but I’ll take the liberty to add people who raised their hand for mentoring here over there :)

@addaleax
Copy link
Member Author

(Please indicate the OS combinations you’d be able to help with over there!)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests