Would you like to move this repo into the alexa-js organization? #18

Closed
dblock opened this Issue Jan 11, 2017 · 10 comments

Comments

Projects
None yet
2 participants
@dblock
Collaborator

dblock commented Jan 11, 2017

Would you like to move this repo into the newly created alexa-js organization, https://github.com/alexa-js?

This would reduce bus factor as currently only @mreinstein can add contributors to this project. By moving org admins can at least add new people, currently that's @matt-kruse and myself.

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.

@dblock dblock changed the title from Join forces into an alexa JS org. to Would you like to move this repo into the alexa-js organization? Jan 12, 2017

@mreinstein

This comment has been minimized.

Show comment
Hide comment
@mreinstein

mreinstein Jan 12, 2017

Contributor

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?

Contributor

mreinstein commented Jan 12, 2017

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?

@mreinstein mreinstein referenced this issue in mreinstein/alexa-verifier Jan 12, 2017

Closed

Move into the alexa-js organization? #10

@dblock

This comment has been minimized.

Show comment
Hide comment
@dblock

dblock Jan 12, 2017

Collaborator

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:

  1. the org is going to do nothing with your code
  2. there will be no "push"

Hope this helps.

Collaborator

dblock commented Jan 12, 2017

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:

  1. the org is going to do nothing with your code
  2. there will be no "push"

Hope this helps.

@dblock

This comment has been minimized.

Show comment
Hide comment
@dblock

dblock Jan 12, 2017

Collaborator

Btw, I maintain two similar orgs: https://github.com/ruby-grape/ and https://github.com/slack-ruby

Collaborator

dblock commented Jan 12, 2017

Btw, I maintain two similar orgs: https://github.com/ruby-grape/ and https://github.com/slack-ruby

@mreinstein

This comment has been minimized.

Show comment
Hide comment
@mreinstein

mreinstein Jan 12, 2017

Contributor

@dblock sounds reasonable. How do I go about assimilation into this alexa borg collective? : )

Contributor

mreinstein commented Jan 12, 2017

@dblock sounds reasonable. How do I go about assimilation into this alexa borg collective? : )

@dblock

This comment has been minimized.

Show comment
Hide comment
@dblock

dblock Jan 12, 2017

Collaborator

Haha.

Transfer the repos to me and I'll immediately move them into alexa-js.

Collaborator

dblock commented Jan 12, 2017

Haha.

Transfer the repos to me and I'll immediately move them into alexa-js.

@mreinstein

This comment has been minimized.

Show comment
Hide comment
@mreinstein

mreinstein Jan 12, 2017

Contributor

should I just transfer them to alexa-js org?

Contributor

mreinstein commented Jan 12, 2017

should I just transfer them to alexa-js org?

@mreinstein

This comment has been minimized.

Show comment
Hide comment
@mreinstein

mreinstein Jan 12, 2017

Contributor

i.e., this?
screen shot 2017-01-12 at 12 25 31 pm

Contributor

mreinstein commented Jan 12, 2017

i.e., this?
screen shot 2017-01-12 at 12 25 31 pm

@dblock

This comment has been minimized.

Show comment
Hide comment
@dblock

dblock Jan 12, 2017

Collaborator

Except you aren't admin of the org and it won't let you. But I am happy to give you org admin access too, should I?

Collaborator

dblock commented Jan 12, 2017

Except you aren't admin of the org and it won't let you. But I am happy to give you org admin access too, should I?

@mreinstein mreinstein closed this Jan 12, 2017

@dblock

This comment has been minimized.

Show comment
Hide comment
@dblock

dblock Jan 12, 2017

Collaborator

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 ;)

Collaborator

dblock commented Jan 12, 2017

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 ;)

@mreinstein

This comment has been minimized.

Show comment
Hide comment
@mreinstein

mreinstein Jan 12, 2017

Contributor

I've added you and Matt to both packages on npm

Contributor

mreinstein commented Jan 12, 2017

I've added you and Matt to both packages on npm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment