meteor/guide

Document Meteor developer organizations

Open

Aperta il 30 dic 2016

Vedi su GitHub
 (0 commenti) (0 reazioni) (0 assegnatari)HTML (839 star) (323 fork)batch import
good first issue

Descrizione

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

Guida contributor

Tech stack
javascripthtml
Dominio
documentation
Tipo issue
documentation
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Meteor basicsUnderstanding of package development
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
50
Direzione di ricerca
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.