Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Would you like to move this repo into the alexa-js organization? #18
Would you like to move this repo into the newly created alexa-js organization, https://github.com/alexa-js?
If you do want to do this, because Github requires one be admin of both source and destination, transfer the repo to me (@dblock) and I'll immediately move it to the org.
It depends on the intentions of the org. I'm all for the enabling contributors, but what I don't want to see happen is a move towards some monolithic or framework based system.
node and npm are a joy to work with because these modules follow the unix philosophy of each doing one small thing, and doing it very well (at least, the good modules follow this approach.)
I cringe at the thought of this becoming some big platform where the modules become less useful as individual units.
What does the org intend to do with this code? Is there going to be some push to move things torwards a shiny "alexajs" platform, or will the code be maintained in it's current state?
Thanks @mreinstein for replying!
There're no goals or plans for the organization at all, except reducing bus factor and creating a place for similar or related projects to make them more discoverable. There're no plans to try to make things into a bigger framework or to take over your project by any means. You still very much own your modules and manage them and do whatever you want in them, but now if a piano falls on your head (hopefully not) there're some org maintainers that can cover for you. At the most I'd encourage you to grow the list of maintainers within these projects.
So to be clear:
Hope this helps.
Welcome to the borg :)
I think you'd be a great third admin for the alexa-js org too @mreinstein as you've written two of the essential packages for alexa-app, so I made you org admin as well. LMK if you don't want the responsibility.
Consider adding me and/or @matt-kruse to npm as well, that will permanently solve the bus factor problem ;)