Move to the Thread GitHub

[jackfranklin]

Hey @PixelsCommander ,

Now that both @stephencookdev and myself are working on this as colleagues at @thread, I was wondering how you felt about moving this repository to there? We'd still very happily allow you to be a contributor, along with @ChristianMurphy and others who are involved, but if we were able to own the repo we could do things like set up CI, add contributors, etc, more easily without having to disturb you.

What do you think?

[PixelsCommander]

Hi, Jack. Moving to a separate organization is something we should proceed with and I am ashamed it is still not there. Moving ownership to your consultancy account does not seem to be a fair solution. However, I understand where your need is coming from and could propose to make a PR with a label "Maintained by Thread" вт, 5 мар. 2019 г. в 16:39, Jack Franklin <notifications@github.com>:

…

Hey @PixelsCommander <https://github.com/PixelsCommander> , Now that both @stephencookdev <https://github.com/stephencookdev> and myself are working on this as colleagues at @thread <https://github.com/thread>, I was wondering how you felt about moving this repository to there? We'd still very happily allow you to be a contributor, along with @ChristianMurphy <https://github.com/ChristianMurphy> and others who are involved, but if we were able to own the repo we could do things like set up CI, add contributors, etc, more easily without having to disturb you . What do you think? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#102>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAxer-QyeBGZDrfm-vGoa243OTUVNFyXks5vTo_AgaJpZM4be4-W> .

[PixelsCommander]

Should we have a roadmap on moving this to an organization? If so would it make sense to have a call or chat on this? вт, 5 мар. 2019 г. в 16:46, Denis Radin <denis.radin@gmail.com>:

…

Hi, Jack. Moving to a separate organization is something we should proceed with and I am ashamed it is still not there. Moving ownership to your consultancy account does not seem to be a fair solution. However, I understand where your need is coming from and could propose to make a PR with a label "Maintained by Thread" вт, 5 мар. 2019 г. в 16:39, Jack Franklin ***@***.***>: > Hey @PixelsCommander <https://github.com/PixelsCommander> , > > Now that both @stephencookdev <https://github.com/stephencookdev> and > myself are working on this as colleagues at @thread > <https://github.com/thread>, I was wondering how you felt about moving > this repository to there? We'd still very happily allow you to be a > contributor, along with @ChristianMurphy > <https://github.com/ChristianMurphy> and others who are involved, but if > we were able to own the repo we could do things like set up CI, add > contributors, etc, more easily without having to disturb you . > > What do you think? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#102>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAxer-QyeBGZDrfm-vGoa243OTUVNFyXks5vTo_AgaJpZM4be4-W> > . >

[jackfranklin]

@PixelsCommander I have no strong opinion about moving it to a separate org vs moving it to Thread. Happy if you just want to make a ReactiveElements org + create this repo + then invite myself, @ChristianMurphy and @stephencookdev to the organisation.

No need to have a call, feel free to create the org called whatever you like.

[PixelsCommander]

The move is going to happen in the next two weeks. If there is a PR with additional credits as discussed - you are welcome.

[ChristianMurphy]

I'd lean toward moving ReactiveElements to an independent ReactiveElements organization.

[PixelsCommander]

I just tried to make the move but see that https://github.com/ReactiveElements already exists. I submitted an abuse to Github on that since that org is not used and we d have more use of it having ownership.

[PixelsCommander]

I created reactive-elements org also but does not look like the right way to go.

[ChristianMurphy]

reactive-elements org

👍

does not look like the right way to go

How so?

[PixelsCommander]

Because repo is ReactiveElements, no dash. Does not look pro. However, GH does not reply. So I do not see another option there. Do you?

[ChristianMurphy]

the package name has a dash.
Maybe the repo could be renamed to match?
Then npm, repo, and org would be in alignment.

[PixelsCommander]

@ChristianMurphy good observation, lets move on as you proposed

[PixelsCommander]

Moved, published update with new package.json urls. LMK please if there are any issues with current setup