Skip to content
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.

Move below webpack-contrib? #48

Open
bebraw opened this issue Mar 6, 2017 · 10 comments
Open

Move below webpack-contrib? #48

bebraw opened this issue Mar 6, 2017 · 10 comments

Comments

@bebraw
Copy link

bebraw commented Mar 6, 2017

Hi,

I was wondering if you would be interested in moving the repository below webpack-contrib. It's an organization where we maintain third party loaders/plugins together. Let me know.

@sairion
Copy link
Collaborator

sairion commented Mar 7, 2017

Hello @bebraw, I'm interested, would you give me an instruction regarding how to move this repo below the org?

@bebraw
Copy link
Author

bebraw commented Mar 7, 2017

Hi,

Can you add me as a collaborator to the repository? That's enough for me to handle the move. You will still retain rights to the loader after this.

We should also make sure multiple people can publish the package after that (I'll figure out a good way to handle this).

@sairion
Copy link
Collaborator

sairion commented Mar 7, 2017

@bebraw invite sent

@bebraw
Copy link
Author

bebraw commented Mar 7, 2017

Ok, we are just figuring out the right process for this (needs to be done right once 👍 ). I'll get back to you once we have it done.

As it appears having just collab rights isn't enough. The process is more involved than that.

@bebraw
Copy link
Author

bebraw commented Mar 7, 2017

Alright, we found a way. If you move the repo below my personal account, I can move it to webpack-contrib there. GitHub added a few restrictions a couple of years ago, but that's a good way to handle it.

We'll do a more formalized process in the near future. 👍

@bebraw
Copy link
Author

bebraw commented Mar 7, 2017

Remaining steps:

  • I need you to npm add owner bebraw and npm add owner d3viant0ne. This way we can push new releases.

@d3viant0ne Feel free to comment here on the other bits (where to copy the license, how to handle CLA, etc.).

@sairion
Copy link
Collaborator

sairion commented Mar 7, 2017

@bebraw
Copy link
Author

bebraw commented Mar 7, 2017

Thanks. I think Joshua will comment on the remaining.

@joshwiens
Copy link
Member

@sairion - The rest is just a bunch of housekeeping and configuration. I can take care of it, shouldn't be anything else you need to do.

@sairion
Copy link
Collaborator

sairion commented Mar 7, 2017

ok, thanks! :) @bebraw @d3viant0ne

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants