Move to npm org namespace

[guyfedwards]

Just thought we could move to the newer convention for this repo @weaveworks/ui-components

[foot]

Would this change consuming it?

[guyfedwards]

No just the package name so package is and imports. It would be a major version bump though

On Wed, 14 Nov 2018, 17:06 Simon <[email protected] wrote:

Would this change consuming it?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/weaveworks/ui-components/issues/420#issuecomment-438739605, or mute the thread https://github.com/notifications/unsubscribe-auth/ABtgF56ZhxmJGL7IO52cPyMYziD8sSDwks5uvE2OgaJpZM4YeJdy .

[foot]

import { Button } from '@weaveworks/ui-components'

And then we could publish scope to the same NS I guess?

[guyfedwards]

Yep exactly

On Thu, 15 Nov 2018, 09:14 Simon <[email protected] wrote:

import { Button } from '@weaveworks/ui-components'

And then we could publish scope to the same NS I guess?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/weaveworks/ui-components/issues/420#issuecomment-438970814, or mute the thread https://github.com/notifications/unsubscribe-auth/ABtgFxtfIMOJ6oYtFjJX1XiBE5Qg3wHvks5uvTBugaJpZM4YeJdy .

[guyfedwards]

Also any other packages such as promjs?

On Thu, 15 Nov 2018, 09:39 Guy Edwards <[email protected] wrote:

Yep exactly

On Thu, 15 Nov 2018, 09:14 Simon <[email protected] wrote:

import { Button } from '@weaveworks/ui-components'

And then we could publish scope to the same NS I guess?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/weaveworks/ui-components/issues/420#issuecomment-438970814, or mute the thread https://github.com/notifications/unsubscribe-auth/ABtgFxtfIMOJ6oYtFjJX1XiBE5Qg3wHvks5uvTBugaJpZM4YeJdy .

[foot]

Nice one, much easier to remember i think 👍 . What is the official process for accepting an RFC?