Make this repo public

[prymitive]

There are a few open PRs, can we open this repo once they are merged?
Are there any other outstanding issues preventing us from making it public?

Small tasks to be done once it's open:

• Add mock data to this repo - pointless before it's marked public as we won't be able to access those files
• Setup travis - we could use CI, travis will be easy to add
• Build an official docker image and put it on docker hub ?

[prymitive]

I guess there's one issue - we should tag a release

[prymitive]

Created first milestone, if there's anything else we need please raise a ticket and attach it to this milestone.

[jamesog]

I'm happy to open this once the PRs are all merged. Your suggestions are all fine - using Travis is no problem, we already use it for many other Cloudflare repos.

[prymitive]

No more outstanding PRs, is everyone happy with making this repo public now? This will allow me to tag a release and complete at least first 2 points in this ticket (docker image isn't critical).

[jamesog]

LGTM 👍

[prymitive]

@mattbostock any objections?

[mattbostock]

No objections from me. Just one question - are we going to use the timestamp format for release tags?

IMHO it'd be more useful to use semantic versioning for a public project.

[mattbostock]

Also, minor nit, but we should definitely add a screenshot to the README. Maybe using the sample data you created?

[prymitive]

I'm happy with both version schemes, @jamesog you're needed to get a quorum
I'll add a screenshot but let me add more mocked alerts, it would look kinda sad with the current set

[prymitive]

Should we use v prefix for release tags and milestones? I think that v1.0 is more obvious as a tag name than 1.0, same for milestones.

[jamesog]

Yep, I'd prefix with v.

You have your quorum. Let the code be free.

[mattbostock]

I also agree with 'v' - I believe that's what GitHub uses by default if you create a tag manually.

[mattbostock]

I'm thinking that, rather than v1.0, we make the first version be v0.0.1. That'll allow for changes (without worrying about backwards compatibility) while the code settles a bit.

Using SemVer, there's a big difference between pre-1.0.0 and 1.0.0 onwards:
http://semver.org/#spec-item-4

[prymitive]

v0.1.0 it is, v0.0.1 sounds like a stub of a project, I think we're past that phase

[prymitive]

We're done with PRs I think, I'll open the repo and setup travis

[mattbostock]

🎉

[prymitive]

Made a PR for travis - #17
I'm going to ignore docker for now and get back to it later (will raise an internal ticket for myself)

[prymitive]

will deploy a new build internally and if all goes well we'll tag a release

[prymitive]

Repo is public so closing