make it public

[rmurphey]

@reason-bv @tnunamak these are the changes I believe necessary to make this repo public. We do not need to alter the history of the repo because it was developed with the intention of opening it.

Once I get signoff on these changes, I need to:

• make it public in github
• npm publish
• see if there's anything to change in travis
• triple-check who has write access to the repo

[reason-bv]

Currently write access is @brianarn, @rmurphey, and me. We may want more. Compare with scoutfile which is a different team with @ceejtron added.

[reason-bv]

I question the 0.12 in .travis.yml given that we're standardized on late 0.10.* with little intention of moving, and scoutfile has 0.10 in that file.

[reason-bv]

👍 Other than that.

[tnunamak]

Awesome that this is so easy to publish.

[rmurphey]

I think I'm good with leaving it 0.12 because these modules are all client-side modules; the 0.12 really just reflects the version of Node in which Karma etc. runs; these modules will/should not run in Node.

[rmurphey]

Published:

rebecca.murphey@rmurphey-retina [08:17:32] [~/code/bv-ui-core] [master]
-> % npm publish .
+ bv-ui-core@0.3.0