Skip to content

Latest commit

 

History

History
81 lines (62 loc) · 6.02 KB

STRUCTURE.md

File metadata and controls

81 lines (62 loc) · 6.02 KB

Structure

Ownership

All projects of the workshopper organization are OSS projects. Licensed either under the ISC License (preferred) or the compatible MIT license. As such the direction of every project is of the authors/contributors. There is no legal body and no BDFL that exercises control over the projects.

Purpose

This organization exists to unite the effort of the creation of OSS learning material, workshoppers. It should help in answering questions such as "How do I specify dependencies?", "Where can I find translators?", "How should I test my work?", "How can I retire as maintainer?". "What way are others interested to go?". etc.

Goal

Better OSS learning materials.

This organization is built around the Node.js platform and has its roots with the NodeSchool. As a result a lot of the material is related to Node.js and as of March 2017 all of the code is published on NPM. This doesn't mean though that the door is necessarily closed for material in or for other languages.

Membership

Membership is not required for contribution or attribution. Each project/repository maintains a list of contributors and anyone is free to improve or build on the work here. For managing issues or if you want to transfer some work to this organization it might be better if you become a member. In that case please create an issue mentioning which repo you need access for. One of the leads of the project/repository has to confirm your appointment.

Hierarchy

Core Team

The core team exists to limit complete access to the organization. The core team has full write permission to the organization. This distinction exists for safety reasons only.

Lead maintainers

Lead maintainers are individuals that stepped up and declared themselves as maintainers/person-answering-questions for a project. Except for the Deploy Team, the lead maintainers are the only group that definitely has admin access to the repository in question and the related npm project.

Repository Lead
adventure ※¹ @substack ※²
browserify-adventure @substack ※²
goingnative @AnshulMalik
how-to-markdown @denysdovhan
how-to-npm @watilde, @EmmaRamirez, @pnn
i18n-it-all @martinheidegger
javascripting @sethvincent, @SomeoneWeird, @AnshulMalik, @itzsaga, @AVGP, @sauban
learn-sass @claudiopro
learnyounode @AnshulMalik
learnyoureact @kohei-takata
levelmeup @martinheidegger
list @linclark ※²
org @martinheidegger
regex-adventure @substack ※²
scope-chains-closures @jesstelford, @SomeoneWeird
stream-adventure @kalinchernev
workshopper ※¹ @martinheidegger
workshopper-adventure @martinheidegger
workshopper-adventure-storage @kid-icarus
workshopper-adventure-test @martinheidegger
workshopper-boilerplate @rvagg ※²
workshopper-exercise @martinheidegger
workshopper-more ※¹ @rvagg ※²
workshopper-wrappedexec @rvagg ※²

※¹ = Legacy project or likely to be deprecated in future.
※² = Original maintainer. No active, current maintainer. Open for people to step up.

Generally there is always a vacancy for maintainers unless specifically mentioned by the maintainer. Post an issue in the org repository if you want to become an maintainer.

Deploy Team

The Deploy team (link only works if you are an org member) are members that have access to write access to all repos and the permission to deploy every repo to NPM.