├── .github ├── labeler.yml └── stale.yml ├── CONTRIBUTING.md ├── FAQ.md ├── README.md └── issue_template.md /.github/labeler.yml: -------------------------------------------------------------------------------- 1 | numLabels: 60 2 | excludeLabels: [] 3 | -------------------------------------------------------------------------------- /.github/stale.yml: -------------------------------------------------------------------------------- 1 | daysUntilStale: 30 2 | daysUntilClose: 7 3 | exemptLabels: 4 | - meta 5 | staleLabel: inactive 6 | markComment: > 7 | This issue has been automatically marked as stale because it has not had 8 | recent activity. It will be closed if no further activity occurs. Thank you 9 | for your contributions. 10 | closeComment: > 11 | This issue is being automatically closed due to inactivity. Please feel to re-open. 12 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | Search before you ask! Someone else has probably asked your question already. [Here is a search example](https://github.com/nodeschool/discussions/issues?utf8=%E2%9C%93&q=learnyounode) 2 | 3 | 4 | Table of Contents
5 | When you have a problem
 6 |  In general: 1 - Be nice, 2 - Be public, 3 - Be patient, 4 - Non-English is okay
7 |  Suggestions: Check your installation, Provide full command output, Use markdown, Say thanks!, Close your issue, Bikeshedding
8 | About Labels
 9 | Answering Issues: Use links, End with a question, Reformat issues, Apply priorities, Close issues 10 | 11 | 12 | # When you have a problem: 13 | 14 | ## In general 15 | 16 | ### 1 - Be nice 17 | 18 | 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. 19 | 20 | ### 2 - Be public 21 | 22 | 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. 23 | 24 | ### 3 - Be patient 25 | 26 | 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. 27 | 28 | ### 4 - Non-English is okay! 29 | 30 | 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. 31 | 32 | ## Suggestions 33 | 34 | ### Check your installation 35 | 36 | Often the installation on [windows](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+label%3Awindows+) makes problems. But also other systems can experience troubles. Please also check out [the installation suggestions](https://github.com/nodeschool/discussions/wiki/Installation-suggestions) if you have problems. 37 | 38 | ### Provide *full* command output 39 | 40 | To help us debug your problem please include all output from the commands you ran, including any error messages you received. 41 | 42 | 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. 43 | 44 | ### Use markdown 45 | 46 | Github offers a lot of support to [format your issue](https://help.github.com/articles/github-flavored-markdown/). It makes it easier for other people to understand your problem. 47 | 48 | ### Say thanks! 49 | 50 | The person that helped you did it out of the kindness of her/his heart. Tell your appreciation by saying thanks :smile: ! 51 | 52 | ### Close your issue 53 | 54 | If you don't close your issue another person will have to clean it up later. 55 | 56 | ### Bikeshedding 57 | 58 | Its okay to [bikeshed](http://en.wiktionary.org/wiki/bikeshedding) issues but if you do it would be nice to update it every 14days or so to let people know you still have interest. 59 | 60 | # About Labels 61 | 62 | Only [owners](https://github.com/orgs/nodeschool/teams/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. Here is their intended meaning: 63 | 64 | | Label | Meaning | 65 | | ----- | ------- | 66 | | [bikeshedding](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Abikeshedding) | This issue is kept open in case someone wants to jump in. It should be updated every now and then (~14days). | 67 | | [contains hints for improvements](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Acontains-hint-for-improvement) | 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](https://help.github.com/articles/using-pull-requests/) or issue. | 68 | | [general node.js](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Ageneral-node.js) | This is a question not specific to a content in this repository but rather to node.js in general. | 69 | | [installation](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Ainstallation) | This is an issue with the installation of node or a workshopper. | 70 | | [mac](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Amac) | This is an issue specific to computers with Mac OS X. | 71 | | [needs some love](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Aneeds-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. | 72 | | [probably self resolved](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aclosed+label%3Aprobably-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. | 73 | | [seems resolved](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aclosed+label%3Aseems-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. | 74 | | [question](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+label%3Aquestion+is%3Aopen) | This issue contains a question that is not a problem. | 75 | | [waiting for feedback](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Awaiting-for-feedback) | This label is to remember that the issue has been answered but is waiting on additional information or more response. | 76 | 77 | If you want to add labels to issues, don't be afraid to ask for permissions. Its a github restriction that only owners can add labels. 78 | 79 | If you have an issue that doesn't match a label, feel free to add a label and describe it here. 80 | 81 | # Answering Issues 82 | 83 | Owner or not: If you have an answer to a question please don't hesitate to add a comment. There are people who answer issues regularily but those are also volunteers and also only try to do their best. 84 | 85 | It is not necessary to follow this but there are some things that we found useful to keep in mind: 86 | 87 | ## Use links 88 | 89 | 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. 90 | 91 | ## End with a question 92 | 93 | If you add a question at the end it puts the ball back to the inital questionee and indicates that you think that this comment should fix the issue of the person. i.e.: 94 | 95 | - Could you try that? 96 | - Does that help you? 97 | - Does that solve your problem? 98 | - Do you need more information? 99 | 100 | ## Reformat issues 101 | 102 | Owners can edit issues. It is often not a good idea to change the issues but adding [Syntax Highlighting](https://help.github.com/articles/github-flavored-markdown/#syntax-highlighting) often helps readability and increases the chances of a good response so that we consider that a good exception. 103 | 104 | ## Apply priorities 105 | 106 | In case you feel confident to answer multiple issues it might be a good idea to follow priorities. An example for priorities might be: 107 | 108 | 1. [Issues with no labels](https://github.com/nodeschool/discussions/issues?q=is%3Aopen+is%3Aissue+no%3Alabel): Add labels 109 | 2. [Issues with no comments](https://github.com/nodeschool/discussions/issues?q=is%3Aopen+is%3Aissue+comments%3A0+): Think of an answer 110 | 3. [Issues that are least recently updated](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+no%3Alabels): Add the `waiting-for-response` label in case its not given and ask a question in case none has been asked. 111 | 4. [Issues that `need-some-love`](https://github.com/nodeschool/discussions/issues?q=is%3Aopen+is%3Aissue+label%3Aneeds-some-love): Try to think how to resolve those because they need your love! 112 | 113 | ## Close issues 114 | 115 | If you see an old issue lurking around feel free to apply labels as mentioned above and **close the issue if reasonable**! 116 | -------------------------------------------------------------------------------- /FAQ.md: -------------------------------------------------------------------------------- 1 | # FAQs 2 | 3 | ## Installation 4 | 5 | ### How do I know that Node.js installed correctly? 6 | 7 | **Windows** - Open the Start Menu and look for an icon that says "Node.js Command Prompt". Type `node` in the terminal and press Enter. If a weird greater symbol (>) appeared in your terminal with a blinking underscore, then you're able to run Node. 8 | 9 | **Linux/OSX** - Open a terminal and type `node`. If a weird greater symbol (>) appeared in your terminal with a blinking underscore, then you're able to run Node. 10 | 11 | ### I installed Node.js, now what? 12 | 13 | **Windows** - Open the Start Menu and look for an icon that says "Node.js Command Prompt". Once you open it, you could for example type `npm install javascripting -g` to install Javascripting. If you want to install other workshopper, use the same command replacing the module name. 14 | 15 | **Linux/OSX** - Open a terminal and type `npm install javascripting -g` to install Javascripting. If you want to install other workshopper, use the same command replacing the module name. 16 | 17 | ### I installed Node.js but when I type `node` in my terminal it says `'node' is not recognized` (or `node: command not found`) 18 | 19 | It's likely that you have a problem with your installation. Go through the installation steps again and if you still have the problem, open an issue telling us exactly which steps you followed to install Node. 20 | 21 | ### I have Node.js installed but when I type `javascripting` in my terminal it shows an error 22 | 23 | If you know that Node installed [correctly][node-installed-correctly], then you may have a problem with the installation of the workshopper. Try to reinstall the workshopper. After that, if you still have the problem open an issue with your error and tell us exactly what happened. 24 | 25 | ## Working on challenges 26 | 27 | ### I can't find what is wrong! 28 | 29 | Don't panic. Open an issue, give us your code, the workshopper name, the challenge name and be patient. Someone will try to help you soon. 30 | 31 | ### The challenge is wrong! 32 | 33 | All the workshoppers are Open Source. If you know how to fix it, just submit a pull request to the workshopper's repository explaining the problem. If you don't know how to fix it, open an issue with the title `Improvement - Workshopper name, challenge name` and all the aditional info you consider it's neccessary in it's content. 34 | 35 | [node-installed-correctly]: FAQ.md#how-do-i-know-that-nodejs-installed-correctly 36 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | [![Gitter](https://badges.gitter.im/nodeschool/discussions.svg)](https://gitter.im/nodeschool/discussions?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) 2 | 3 | discussions 4 | =========== 5 | 6 | need help? or just wanna ask a question? [open an issue](https://github.com/nodeschool/discussions/issues) on this repo! 7 | 8 | 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) 9 | 10 | NodeSchool organizers can have discussions [over here](https://github.com/nodeschool/organizers). If you want to create your own NodeSchool workshop, have a look at the [workshoppers repo](https://github.com/nodeschool/workshoppers). 11 | 12 | 13 | TOC
14 | When you have a problem
 15 |  In general: 1 - Be nice, 2 - Be public, 3 - Be patient, 4 - Non-English is okay
16 |  Suggestions: Check your installation, Provide full command output, Use markdown, Say thanks!, Close your issue, Bikeshedding
17 | About Labels
 18 | Answering Issues: Use links, End with a question, Reformat issues, Apply priorities, Close issues 19 | 20 | 21 | # When you have a problem: 22 | 23 | :point_right: [**Check out the FAQ!**](FAQ.md) :point_left: 24 | 25 | ## In general 26 | 27 | ### 1 - Be nice 28 | 29 | 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. 30 | 31 | ### 2 - Be public 32 | 33 | 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. 34 | 35 | ### 3 - Be patient 36 | 37 | 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. 38 | 39 | ### 4 - Non-English is okay! 40 | 41 | 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. 42 | 43 | ## Suggestions 44 | 45 | ### Check your installation 46 | 47 | Often the installation on [windows](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+label%3Awindows+) makes problems. But also other systems can experience troubles. Please also check out [the installation suggestions](https://github.com/nodeschool/discussions/wiki/Installation-suggestions) if you have problems. 48 | 49 | ### Provide *full* command output 50 | 51 | To help us debug your problem please include all output from the commands you ran, including any error messages you received. 52 | 53 | 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. 54 | 55 | ### Use markdown 56 | 57 | Github offers a lot of support to [format your issue](https://help.github.com/articles/github-flavored-markdown/). It makes it easier for other people to understand your problem. 58 | 59 | ### Say thanks! 60 | 61 | The person that helped you did it out of the kindness of her/his heart. Tell your appreciation by saying thanks :smile: ! 62 | 63 | ### Close your issue 64 | 65 | If you don't close your issue another person will have to clean it up later. 66 | 67 | ### Bikeshedding 68 | 69 | Its okay to [bikeshed](http://en.wiktionary.org/wiki/bikeshedding) issues but if you do it would be nice to update it every 14days or so to let people know you still have interest. 70 | 71 | # About Labels 72 | 73 | Only [owners](https://github.com/orgs/nodeschool/teams/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: 74 | 75 | | Label | Meaning | 76 | | ----- | ------- | 77 | | [bikeshedding](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Abikeshedding) | This issue is kept open in case someone wants to jump in. It should be updated every now and then (~14days). | 78 | | [chapter request](https://github.com/nodeschool/discussions/labels/chapter-request) | This label is for issues that are chapter requests. | 79 | | [contains hints for improvements](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Acontains-hint-for-improvement) | 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](https://help.github.com/articles/using-pull-requests/) or issue. | 80 | | [discussion thread](https://github.com/nodeschool/discussions/labels/discussion%20thread) | This label is for threads that discuss other nodeschool related business. | 81 | | [general node.js](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Ageneral-node.js) | This is a question not specific to a content in this repository but rather to node.js in general. | 82 | | [installation](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Ainstallation) | This is an issue with the installation of node or a workshopper. | 83 | | [mac](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Amac) | This is an issue specific to computers with Mac OS X. | 84 | | [meta](https://github.com/nodeschool/discussions/labels/meta) | For issues that have to do with the running of nodeschool. | 85 | | [migrated](https://github.com/nodeschool/discussions/labels/migrated) | For issues that have been migrated to another relevant repository. | 86 | | [needs some love](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Aneeds-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. | 87 | | [probably self resolved](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aclosed+label%3Aprobably-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. | 88 | | [question](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+label%3Aquestion+is%3Aopen) | This issue contains a question that is not a problem. | 89 | | [seems resolved](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aclosed+label%3Aseems-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. | 90 | | [waiting for feedback](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Awaiting-for-feedback) | This label is to remember that the issue has been answered but is waiting on additional information or more response. | 91 | | [windows](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+label%3Awindows) | This is an issue specific to computers running Windows. | 92 | 93 | If you have an issue that doesn't match a label, feel free to open an issue suggesting new labels! 94 | 95 | # Answering Issues 96 | 97 | 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. 98 | 99 | It is not necessary to follow this but there are some things that we found useful to keep in mind: 100 | 101 | ## Use links 102 | 103 | 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. 104 | 105 | ## End with a question 106 | 107 | 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.: 108 | 109 | - Could you try that? 110 | - Does that help you? 111 | - Does that solve your problem? 112 | - Do you need more information? 113 | 114 | ## Reformat issues 115 | 116 | Owners can edit issues. It is often not a good idea to change the issues but adding [Syntax Highlighting](https://help.github.com/articles/github-flavored-markdown/#syntax-highlighting) often helps readability and increases the chances of a good response so that we consider that a good exception. 117 | 118 | ## Apply priorities 119 | 120 | In case you feel confident to answer multiple issues it might be a good idea to follow priorities. An example for priorities might be: 121 | 122 | 1. [Issues with no labels](https://github.com/nodeschool/discussions/issues?q=is%3Aopen+is%3Aissue+no%3Alabel): Add labels 123 | 2. [Issues with no comments](https://github.com/nodeschool/discussions/issues?q=is%3Aopen+is%3Aissue+comments%3A0+): Think of an answer 124 | 3. [Issues that are least recently updated](https://github.com/nodeschool/discussions/issues?q=is%3Aissue+is%3Aopen+no%3Alabels): Add the `waiting-for-response` label in case its not given and ask a question in case none has been asked. 125 | 4. [Issues that `need-some-love`](https://github.com/nodeschool/discussions/issues?q=is%3Aopen+is%3Aissue+label%3Aneeds-some-love): Try to think how to resolve those because they need your love! 126 | 5. [Old Issues that are `waiting-for-feedback`](https://github.com/nodeschool/discussions/issues?q=is%3Aopen+is%3Aissue+label%3Awaiting-for-feedback+sort%3Acreated-asc) Close them and mark as `seems-self-resolved` if they are more than a month old 127 | 128 | ## Close issues 129 | 130 | If you see an old issue lurking around feel free to apply labels as mentioned above and **close the issue if reasonable**! 131 | -------------------------------------------------------------------------------- /issue_template.md: -------------------------------------------------------------------------------- 1 | 2 | ### Notes 3 | 4 | - If you have a question about the NodeSchool organization: Please open an issue in [nodeschool/organizers](https://github.com/nodeschool/organizers/issues/new) 5 | - If you want to improve or contribute to workshoppers: Please open an issue in [workshopper/org](https://github.com/workshopper/org/issues/new) 6 | - Did you see the guide for questions? https://github.com/nodeschool/discussions#when-you-have-a-problem 7 | 8 | **Please delete this section after reading it** 9 | 10 | ### If you have a problem with an error message: 11 | 12 | * node version: 13 | * npm version: 14 | * os: windows 7/windows 10/mac/linux 15 | 16 | ### Error output 17 | ``` 18 | // copy your error output here 19 | ``` 20 | 21 | ### My Code 22 | ```js 23 | // copy your code here 24 | ``` 25 | --------------------------------------------------------------------------------