├── .github └── ISSUE_TEMPLATE │ └── session-proposal.md ├── CODE_OF_CONDUCT.md └── README.md /.github/ISSUE_TEMPLATE/session-proposal.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Code&Learn Session Proposal 3 | about: Submit a session proposal for the Code&Learn event 4 | title: 'Session Topic: ' 5 | labels: Session Proposal 6 | assignees: christian-bromann, evahowe, jorydotcom, keywordnew 7 | 8 | --- 9 | 10 | 18 | 19 | **Topic of the session** 20 | 21 | 22 | **Project** 23 | 26 | 27 | 28 | **Describe the session** 29 | 30 | 31 | **Additional context (optional)** -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | The OpenJS Foundation and its member projects use the Contributor 4 | Covenant v1.4.1 as its Code of Conduct. Refer to the following 5 | for the full text: 6 | 7 | * [english](https://www.contributor-covenant.org/version/1/4/code-of-conduct) 8 | * [translations](https://www.contributor-covenant.org/translations) 9 | 10 | Refer to the section on reporting and escalation in this document for the specific emails that can be used to report and escalate issues. 11 | 12 | # Reporting 13 | 14 | ## Project Spaces 15 | 16 | For reporting issues in spaces related to a member project please use the email provided by the project for reporting. Projects handle CoC issues related to the spaces that they maintain. Projects maintainers commit to: 17 | 18 | * maintain the confidentiality with regard to the reporter of an incident 19 | * to participate in the path for escalation as outlined in 20 | the section on Escalation when required. 21 | 22 | ## Foundation Spaces 23 | For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization, use the email `report@lists.openjsf.org`. The Cross Project Council (CPC) is responsible for managing these reports and commits to: 24 | 25 | * maintain the confidentiality with regard to the reporter of an incident 26 | * to participate in the path for escalation as outlined in 27 | the section on Escalation when required. 28 | 29 | # Escalation 30 | 31 | The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. In order to escalate to the CoCP send an email to `"coc-escalation@lists.openjsf.org`. 32 | 33 | For more information, refer to the full 34 | [Code of Conduct governance document](https://github.com/openjs-foundation/cross-project-council/tree/HEAD/proposals/approved/CODE_OF_CONDUCT). -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Code And Learn 2 | ============== 3 | 4 | Code & Learn events allow you to get started (or go further) with popular open source projects from the [OpenJS Foundation](https://openjsf.org/projects). Experienced contributors help guide you through your first, second or third commit to the projects. 5 | 6 | ## Date and Times 7 | 8 | December 13th, 2019 9 | Palais des Congrès de Montréal 10 | 11 | Location: TBD 12 | 13 | Cost: free 14 | 15 | The event is free and for everyone who wants to participate. See the [How To Participate](#how-to-participate) section to see how to register. 16 | 17 | ## Format 18 | 19 | This years format is a little bit different than previous years. If you want to attend the event you can choose between multiple sessions that will take part or propose your own. Every session focuses on a specific area of one of the OpenJS Foundation projects (e.g. help contributing to the new [Node.js documentations page](https://nodejs.dev/)). You can find a list of proposed sessions [here](https://github.com/openjs-foundation/code-and-learn/labels/Session%20Proposal). Every session is hold in rather small groups and facilitated by a core member of the project. 20 | 21 | We are welcoming everyone who wants to participate and learn something! It doesn't matter if you just started with Node.js or are already using it as part of your job. 22 | 23 | ## How To Participate 24 | 25 | There is no registration necessary to attend this years Code&Learn however as orginizers we need to know who wants to participate so that we can plan accordingly. There are two ways how you can participate at Code&Learn: 26 | 27 | #### Join a Proposed Session 28 | 29 | Check out the list of already [proposed Code&Learn sessions](https://github.com/openjs-foundation/code-and-learn/labels/Session%20Proposal) and see if any of these sessions interest you. If so, give a 👍 on the issue thread so that we know you like to participate. By giving a 👍 you will be automatically registered to the event. If your plans are changing please make sure to remove it again. 30 | 31 | #### Propose Your Session 32 | 33 | If you are interested in contributing to a specific area that is not already covered in the proposed sessions you can [create a new issue](https://github.com/openjs-foundation/code-and-learn/issues/new?assignees=christian-bromann%2C+evahowe%2C+jorydotcom%2C+keywordnew&labels=Session+Proposal&template=session-proposal.md&title=Session+Topic%3A+) and we will try to find the appropiate faciliator of the project for it. Please understand that a proposed session needs to have at least 5-10 attendees that are also interested to contribute in the session. 34 | 35 | ## Participating Projects 36 | 37 | [![Node.js](https://openjsf.org/wp-content/uploads/sites/84/2019/05/NodeJS_New_Pantone_medium.png "Node.js")](https://nodejs.org) 38 | [![Appium](https://openjsf.org/wp-content/uploads/sites/84/2019/05/appium_medium.png "Appium")](http://appium.io/) 39 | [![Dojo](https://openjsf.org/wp-content/uploads/sites/84/2019/05/dojo_medium.png "Dojo")](https://dojotoolkit.org/) 40 | [![webpack](https://openjsf.org/wp-content/uploads/sites/84/2019/05/webpack_medium.png "webpack")](https://webpack.js.org/) 41 | [![jQuery](https://openjsf.org/wp-content/uploads/sites/84/2019/05/jquery_medium.png "jQuery")](https://jquery.com/) 42 |

43 | [![architect](https://openjsf.org/wp-content/uploads/sites/84/2019/05/arc_medium.png "architect")](https://arc.codes/) 44 | [![Node-RED](https://openjsf.org/wp-content/uploads/sites/84/2019/05/node-red_medium.png "Node-RED")](https://nodered.org/) 45 | [![Intern](https://openjsf.org/wp-content/uploads/sites/84/2019/05/intern_medium.png "Intern")](https://theintern.io/) 46 | [![WebdriverIO](https://openjsf.org/wp-content/uploads/sites/84/2019/05/webdriver_medium.png "WebdriverIO")](https://webdriver.io/) 47 | [![Mocha](https://openjsf.org/wp-content/uploads/sites/84/2019/05/mocha_medium.png "Mocha")](https://mochajs.org/) 48 | [![webhint](https://openjsf.org/wp-content/uploads/sites/84/2019/05/sonar_medium.png "webhint")](https://webhint.io/) 49 |

50 | [![ESLint](https://openjsf.org/wp-content/uploads/sites/84/2019/05/eslint_medium.png "ESLint")](https://eslint.org/) 51 | [![Libuv](https://openjsf.org/wp-content/uploads/sites/84/2019/05/libuv_medium.png "Libuv")](http://libuv.org/) 52 | [![Esprima](https://openjsf.org/wp-content/uploads/sites/84/2019/05/esprima_medium.png "Esprima")](https://esprima.org/) 53 | [![Lodash](https://openjsf.org/wp-content/uploads/sites/84/2019/05/lodash_medium.png "Lodash")](https://lodash.com/) 54 | [![Express](https://openjsf.org/wp-content/uploads/sites/84/2019/05/express_medium.png "Express")](https://expressjs.com/) 55 | [![Marko](https://openjsf.org/wp-content/uploads/sites/84/2019/05/marko_medium.png "Marko")](https://markojs.com/) 56 | [![Globaliize](https://openjsf.org/wp-content/uploads/sites/84/2019/05/globalize_medium.png "Globalize")](https://globalizejs.com) 57 | [![Messageformat](https://openjsf.org/wp-content/uploads/sites/84/2019/05/messageformat_medium.png "Messageformat")](https://messageformat.github.io/messageformat/) 58 | [![Grunt](https://openjsf.org/wp-content/uploads/sites/84/2019/05/grunt_medium.png "Grunt")](https://gruntjs.com/) 59 | [![Moment](https://openjsf.org/wp-content/uploads/sites/84/2019/05/moment_medium.png "Moment")](https://momentjs.com/) 60 | [![HospitalRun](https://openjsf.org/wp-content/uploads/sites/84/2019/05/hospitalrun_medium.png "HospitalRun")](https://hospitalrun.io/) 61 | [![PEP](https://openjsf.org/wp-content/uploads/sites/84/2019/05/pep_medium.png "PEP")](https://github.com/jquery/pep) 62 | [![Interledger.js](https://openjsf.org/wp-content/uploads/sites/84/2019/05/interledger_medium.png "Interledger.js")](https://interledger.org/) 63 | [![QUnit](https://openjsf.org/wp-content/uploads/sites/84/2019/05/qunit_medium.png "QUnit")](https://qunitjs.com/) 64 | [![JerryScript](https://openjsf.org/wp-content/uploads/sites/84/2019/05/jerryscript_medium.png "JerryScript")](https://jerryscript.net/) 65 | 66 | ## [Code Of Conduct](https://github.com/openjs-foundation/code-and-learn/blob/HEAD/CODE_OF_CONDUCT.md#code-of-conduct) 67 | 68 | In the interest of fostering an open and welcoming environment, we as organizers, contributors and maintainers pledge to make participation for the event, in our projects and community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. --------------------------------------------------------------------------------