• Stars
    star
    492
  • Rank 89,476 (Top 2 %)
  • Language
  • Created about 11 years ago
  • Updated about 3 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

๐Ÿซ๐Ÿ’ฌ need help with nodeschool? or just wanna ask a question? open an issue on this repo!

Gitter

discussions

need help? or just wanna ask a question? open an issue on this repo!

If you're having trouble installing a workshop on Mac or Linux, check out this guide https://github.com/nodeschool/discussions/wiki/Installing-global-node-modules-(Linux-and-Mac)

NodeSchool organizers can have discussions over here. If you want to create your own NodeSchool workshop, have a look at the workshoppers repo.

TOC
When you have a problem
ย In general: 1 - Be nice, 2 - Be public, 3 - Be patient, 4 - Non-English is okay
ย Suggestions: Check your installation, Provide full command output, Use markdown, Say thanks!, Close your issue, Bikeshedding
About Labels
Answering Issues: Use links, End with a question, Reformat issues, Apply priorities, Close issues

When you have a problem:

๐Ÿ‘‰ Check out the FAQ! ๐Ÿ‘ˆ

In general

1 - Be nice

All of the workshops and all of the discussions are done by volunteers and there is no guarantee that all questions get answered. If you only provide negative feedback and not constructive criticism your issue will probably get closed with no response.

2 - Be public

Don't email workshop authors directly, use the public discussion forum (the Issues) for all communication, that way your question and any answers you get can benefit everyone else.

3 - Be patient

It may take a day or two for people to respond here. Please don't send multiple messages in a row, it won't help your question get answered any faster.

4 - Non-English is okay!

If you can't read or write english well its better to write additionally your question in your native language. There are many people on this site and maybe people can help you in your mother-tongue. It may take slightly longer for somebody to reply to your question if it's not in English, though.

Suggestions

Check your installation

Often the installation on windows makes problems. But also other systems can experience troubles. Please also check out the installation suggestions if you have problems.

Provide full command output

To help us debug your problem please include all output from the commands you ran, including any error messages you received.

It also helps to include your node, npm, git or other CLI command versions, which you can get by running node -v, npm -v etc.

Use markdown

Github offers a lot of support to format your issue. It makes it easier for other people to understand your problem.

Say thanks!

The person that helped you did it out of the kindness of her/his heart. Tell your appreciation by saying thanks ๐Ÿ˜„ !

Close your issue

If you don't close your issue another person will have to clean it up later.

Bikeshedding

Its okay to bikeshed issues but if you do it would be nice to update it every 14days or so to let people know you still have interest.

About Labels

Only owners can add labels to the dicussions issues. We added a lot of labels that makes it easier for contributors to understand the content of an issue. There are labels that correspond to each nodeschool adventure, as well as some others, here are their intended meanings:

Label Meaning
bikeshedding This issue is kept open in case someone wants to jump in. It should be updated every now and then (~14days).
chapter request This label is for issues that are chapter requests.
contains hints for improvements This contains hints on how a workshopper/tutorial/website etc. can be improved. The issue should be closed when the improvement was added to the content in question as a PR or issue.
discussion thread This label is for threads that discuss other nodeschool related business.
general node.js This is a question not specific to a content in this repository but rather to node.js in general.
installation This is an issue with the installation of node or a workshopper.
mac This is an issue specific to computers with Mac OS X.
meta For issues that have to do with the running of nodeschool.
migrated For issues that have been migrated to another relevant repository.
needs some love This issue is not simple to answer or process. More effort than average needs to be put into this issue and it needs the love and support of the greater community.
probably self resolved This label is for the case that the person that asked the question has not answered for a longer period of time (~14 days). It should be used by the person who closes an inactive thread to show that she/he thinks that the user probably resolved this issue himself. Usually only closed issues should have this label.
question This issue contains a question that is not a problem.
seems resolved This label is to indicate that the issue seems resolved but the user forgot to close the issue. Usually only closed issues should have this label.
waiting for feedback This label is to remember that the issue has been answered but is waiting on additional information or more response.
windows This is an issue specific to computers running Windows.

If you have an issue that doesn't match a label, feel free to open an issue suggesting new labels!

Answering Issues

If you have an answer to a question please don't hesitate to add a comment, even if you're never answered one before! There are people who answer issues regularily but those are also volunteers and also only try to do their best.

It is not necessary to follow this but there are some things that we found useful to keep in mind:

Use links

Many questions are similar. If you can link to other issues or web content that makes your life easier. Keep in mind that the other person still needs an explanation why you give this link.

End with a question

If you add a question at the end it puts the ball back to the initial questionee and indicates that you think that this comment should fix the issue of the person. i.e.:

  • Could you try that?
  • Does that help you?
  • Does that solve your problem?
  • Do you need more information?

Reformat issues

Owners can edit issues. It is often not a good idea to change the issues but adding Syntax Highlighting often helps readability and increases the chances of a good response so that we consider that a good exception.

Apply priorities

In case you feel confident to answer multiple issues it might be a good idea to follow priorities. An example for priorities might be:

  1. Issues with no labels: Add labels
  2. Issues with no comments: Think of an answer
  3. Issues that are least recently updated: Add the waiting-for-response label in case its not given and ask a question in case none has been asked.
  4. Issues that need-some-love: Try to think how to resolve those because they need your love!
  5. Old Issues that are waiting-for-feedback Close them and mark as seems-self-resolved if they are more than a month old

Close issues

If you see an old issue lurking around feel free to apply labels as mentioned above and close the issue if reasonable!

More Repositories

1

nodeschool.github.io

๐Ÿซ nodeschool internet web page
JavaScript
907
star
2

organizers

A discussion repository for nodeschool organizers
250
star
3

spb

โš“ Saint Petersburg, Russia
CSS
111
star
4

sanfrancisco

repo for organizing the sanfrancisco nodeschools
Mustache
98
star
5

taiwan

The Taiwan, TW of nodeschool
CSS
77
star
6

vancouver

๐Ÿซ nodeschool: Vancouver, British Columbia flavour ๐Ÿ‡จ๐Ÿ‡ฆ
JavaScript
58
star
7

tokyo

๐Ÿซ๐Ÿ—ผ nodeschool group for Tokyo, Japan
CSS
56
star
8

berlin

๐Ÿป learn coding with nodeschool berlin (เน‘>แด—<เน‘)
JavaScript
56
star
9

oakland

Discussion for the Oakland chapter of NodeSchool
JavaScript
55
star
10

campinas

Campinas chapter of NodeSchool.
HTML
54
star
11

international-day

international nodeschool day - 2016
JavaScript
53
star
12

buenosaires

Repositorio para organizar y responder preguntas de los eventos realizados en Buenos Aires, Argentina.
CSS
47
star
13

jobs

a list of job opportunities that might be interesting for nodeschoolers
46
star
14

italy

45
star
15

saopaulo

Organizing nodeschool events in Sรฃo Paulo, SP! ๐Ÿ‡ง๐Ÿ‡ท
JavaScript
43
star
16

seattle

NodeSchool for Seattle!
HTML
42
star
17

los-angeles

nodeschool: LA Edition
41
star
18

nyc

Organizing nodeschool events in New York, NY!
HTML
40
star
19

newsletter

markdown source for the nodeschool email newsletter
36
star
20

what-is-node

Descriptions for what Node.js is
JavaScript
31
star
21

toronto

๐Ÿซ๐Ÿ•๐Ÿ nodeschool Toronto
30
star
22

dhaka

๐Ÿซ NodeSchool Dhaka
HTML
30
star
23

amsterdam

Repository for organising Amsterdam NodeSchool events.
JavaScript
27
star
24

dallas

Nodeschool Dallas chapter
Ruby
27
star
25

london

The repo for london nodeschool events
27
star
26

bratislava

๐Ÿซ ๐Ÿป ๐Ÿ• ๐Ÿš€ NodeSchool, Bratislava, Slovakia
25
star
27

montreal

๐Ÿ๐Ÿ—ป Montreal NodeSchool chapter
HTML
25
star
28

cincinnati

NodeSchool chapter for Cincinnati.
HTML
23
star
29

globe

WebGL Globe ๐ŸŒ
HTML
22
star
30

santiago

NodeSchool in Santiago, ๐Ÿ‡จ๐Ÿ‡ฑ
Mustache
22
star
31

austin

Austin NodeSchool Chapter
JavaScript
21
star
32

karachi

Repository for organizing the karachi nodeschools events
JavaScript
21
star
33

pdx

Organizing nodeschool events in Portland, OR!
20
star
34

osaka

๐Ÿซ๐Ÿ‘น NodeSchool in Osaka, Japan
20
star
35

Bengaluru

Bengaluru Nodeschool Chapter
HTML
20
star
36

mexicocity

repo for organizing the mexico city nodeschools
19
star
37

iem-kolkata

NodeSchool chapter for IEM in Kolkata, India
18
star
38

kyiv

Kyiv/Kiev, Ukraine.
17
star
39

admin

CLI tool for setting up and maintaining a nodeschool chapters and other things.
JavaScript
17
star
40

sanmiguel

Repo of El Salvador community Nodeschool San Miguel
HTML
15
star
41

barcelona

๐ŸŒ‡ NodeSchool Barcelona
JavaScript
15
star
42

baltimore

Repo for Baltimore nodeschool events, info, etc
CSS
14
star
43

vienna

repo for organizing the Viennese nodeschools http://www.nodeschool.io/vienna
CSS
14
star
44

lisbon

๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹ ๐Ÿš‹
14
star
45

boston

repo for organizing the Boston nodeschools
13
star
46

bogota

NodeSchool Bogota
13
star
47

fortaleza

NodeSchool Fortaleza chapter
12
star
48

seoul

repo for organizing the seoul nodeschools
12
star
49

hamburg

Hamburg chapter of NodeSchool
HTML
12
star
50

wellington

๐Ÿซ โ›ฒ ๐Ÿ’จ NodeSchool chapter in Wellington, New Zealand
JavaScript
11
star
51

chernivtsi

๐Ÿซ๐Ÿ‡บ๐Ÿ‡ฆ NodeSchool chapter for Chernivtsi, Ukraine
CSS
11
star
52

rio

Organizing NodeSchool events in Rio de Janeiro, RJ!
CSS
11
star
53

belo-horizonte

Nodeschool chapter for Belo Horizonte, Brazil
10
star
54

paris

Chapitre parisien de NodeSchool
CSS
10
star
55

singapore

Stay connected with the JS / NodeJS in Singapore
CSS
10
star
56

munich

NodeSchool chapter for Munich
HTML
10
star
57

chiang-mai

NodeSchool in Chiang Mai
10
star
58

medellin

NodeSchool Medellรญn
10
star
59

montevideo

๐Ÿซโšฝ Learn Coding with NodeSchool Montevideo
HTML
10
star
60

hanoi

๐ŸŒ‡ Hanoi chapter
10
star
61

lyon

๐Ÿซ๐Ÿฏ Learn Coding with NodeSchool Lyon
JavaScript
9
star
62

bainbridge

Bainbridge Island repository for Nodeschool
JavaScript
9
star
63

discussions-ja

nodeschool ใงใฎ่ณชๅ•ใ‚’ๆ—ฅๆœฌ่ชžใงใ—ใ‚ˆใ†!!
9
star
64

moscow

NodeSchool Chapter: Moscow, Russia
9
star
65

helsinki

๐Ÿซ๐Ÿšฃ Helsinki NodeSchool chapter
9
star
66

silesia

๐Ÿซ๐Ÿญ Repository for organizing the Polish nodeschool.io in the Silesia region.
CSS
8
star
67

khulna

Nodeschool chapter for Khulna
8
star
68

oc

Orange County, CA Chapter
8
star
69

denver-boulder

The official NodeSchool.io repository for the Denver/Boulder Node.js meetup
CSS
8
star
70

edmonton

nodeschool chapter for Edmonton, Alberta
8
star
71

philadelphia

NodeSchool chapter for Philadelphia, PA
8
star
72

belfast

Repo for the Belfast chapter of Node School
HTML
8
star
73

write-ups

A place for putting write-ups of past NodeSchool events
8
star
74

bali

Bali, Indonesia nodeschool chapter
CSS
8
star
75

madison

NodeSchool Madison, WI
JavaScript
8
star
76

puertorico

Coordination and discussion for the Puerto Rico nodeschool
7
star
77

haarlem

๐Ÿซ ๐Ÿป ๐Ÿ• Repository for organizing the Haarlem NodeSchools
JavaScript
7
star
78

stanford

Stanford University nodeschool meetup
7
star
79

algiers

A nodeschool for javascript and Node.js around algiers
7
star
80

atlanta

Atlanta chapter.
7
star
81

raleigh-durham

Raleigh-Durham NodeSchool
CSS
7
star
82

email

MX server management for nodeschool.io
JavaScript
6
star
83

lima

Chapter for Lima, Peru
JavaScript
6
star
84

workbook

6
star
85

cluj

repo for organizing the cluj nodeschools
HTML
6
star
86

okinawa

Repo for organizing the okinawa nodeschools https://nodeschool.github.io/okinawa
CSS
6
star
87

pune

Nodeschool India - Pune
6
star
88

sandiego

Chapter: San Diego, California, US
JavaScript
6
star
89

istanbul

๐Ÿซ๐ŸŒท NodeSchool chapter for Istanbul, TR
HTML
6
star
90

pereira

NodeSchool Pereira, Colombia
5
star
91

augsburg

NodeSchool chapter for Augsburg, DE
JavaScript
5
star
92

orlando

Orlando NodeSchool Chapter
5
star
93

mombasa

Nodeschool Mombasa
5
star
94

usac.gt

๐Ÿซ Nodeschool USAC Guatemala
5
star
95

lahore

NodeSchool, Lahore chapter
JavaScript
5
star
96

washingtondc

Repo for the DC Nodeschool and nodejs community
5
star
97

hradec-kralove

Repo for organizing nodeschools in Hradec Krรกlovรฉ, Czech Republic
5
star
98

costarica

๐ŸŒ‹ NodeSchool Costa Rica
5
star
99

chicago

NodeSchool Chicago
HTML
4
star
100

normal

repo for organizing the Normal nodeschools
4
star