Open tunnckoCore opened 9 years ago
Its not sure/guaranteed 1) that all org members would have repos in the org; 2) all org members would have npm packages!! 3) or even npm accounts Strategy Two (better?) provide option for giving json/cson/yaml/xml (config) containing all org member's npm accounts could be possible option to give url to this config should have one default path/repo/config (AUTHORS/MAITAINERS, etc) e.g github.com/orgName/meta/owners.json e.g github.com/regexps/meta/owners.txt (per line basis or comma-separated?) or npm package returning module.exports = [user, names, here] loop over this config download package with tunnckoCore/gitclone (github) or tunnckoCore/package-clone (npm) run npm owner add <username> - for every in loop delete package Signature
Its not sure/guaranteed 1) that all org members would have repos in the org; 2) all org members would have npm packages!! 3) or even npm accounts
module.exports = [user, names, here]
tunnckoCore/gitclone
tunnckoCore/package-clone
npm owner add <username>
packageOwnership(String, String|Array, Object) packageOwnership(pkg, userOrOrg, options)
username/repo
CLI signature package user/repo 'description here'
package user/repo 'description here'
Goal
Features
Possible strategies/approaches
Strategy One (very bad, many possible issues)