Fallout from transfer to org and repo rename

Question

Fallout from transfer to org and repo rename

paulyoung opened this issue 9 years ago · 10 comments

Off the top of my head the following need to be addressed:

README.md
package.json
give contributors ability to publish to npm
blesscss.com

/cc @BlessCSS/contributors

Answer 1 · 2015-07-17T15:02:00.000Z

I can't do anything about travis as I'm not an org owner, so you'll need to take care of that one. I already sent a request from approval from the travis UI.

Answer 2 · 2015-07-17T15:03:02.000Z

I don't see any concerns in the Readme at the moment, was there something specific you were concerned about?

Answer 3 · 2015-07-17T15:03:02.000Z

@mtscout6 pointed out that contributors need to be given access to publish to npm

Answer 4 · 2015-07-17T15:03:44.000Z

Looks like the package.json is ok: https://github.com/BlessCSS/Bless/blob/4.0.0-development/package.json#L2

Answer 5 · 2015-07-17T15:07:46.000Z

@mtscout6 I was referring to the old URLs in there.

Answer 6 · 2015-07-17T15:08:37.000Z

@mtscout6 the README has the old travis badge so we'd need to update that.

Answer 7 · 2015-07-17T15:15:29.000Z

Need to add a blesscss.github.io repo to the org for the docs, then change the domain to point at the new location.

Or add a permanent from blesscss.com redirect to http://blesscss.github.io and forego the domain?

Answer 8 · 2015-07-17T15:30:50.000Z

I believe everything is done for the website. I updated the DNS but it's probably still propagating.

I deleted the gh-pages branch since it's now in it's own repo and at https://blesscss.github.io

Answer 9 · 2015-07-17T21:19:44.000Z

The remaining tasks were addressed in 38e282b.

Answer 10 · 2015-07-17T21:39:48.000Z

Awesome, any reason to keep this issue open then?