meteor/guide

Document Meteor developer organizations

Open

#596 opened on Dec 30, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (839 stars) (323 forks)batch import
good first issue

Description

Moving this issue over from meteor/meteor#3850. I'm not sure if this should be documented in the Guide (maybe under Writing Atmosphere Packages) or in the API Docs, but I'll assume the Guide for now. One of the best references I've seen for Meteor developer organization information is the Meteor 0.9.1: Meteor developer organizations, solidified Blaze APIs blog post.

(originally reported by @rgoomar)

I have not seen anything in the docs mentioning organizations and how to manage them.

It is an important part of the package system (IMO) and should be documented so that it can more easily be utilized.

There should probably be something in the meteor admin section, writing packages because I did not see how to manage organizations. But, I did end up finding it under meteor.com/account-settings/organizations

Contributor guide

Tech stack
javascripthtml
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Meteor basicsUnderstanding of package development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Research the Meteor developer organizations feature by reading the linked blog post and any related code in the Meteor core repository. Then, determine the appropriate location in the Guide (e.g., around Writing Atmosphere Packages) and draft documentation covering how organizations work, how to create and manage them, and how they interact with package publishing. Update the API docs if necessary.