subdomain bikeshedding

[harlantwood]

OK... about to deploy the first version of the board to

some-subdomain.ipfs.io

What subdomain? ci-status.ipfs.io you say? That's OK, but it's got a lot more than that in it now, mostly readme information:

http://ipfs.github.io/ci-status/

And more stuff coming soon, like: # of open issues / # of open PRs / # of stars.

To me, repos.ipfs.io makes most sense. Each row is a repo, after all. Other thoughts?

I'll go ahead with ci-status.ipfs.io unless we hit on something better, can always add an alias...

[jbenet]

repos.ipfs.io may be repos on ipfs. i'd do: project-repos.ipfs.io or ci-status.ipfs.io or even code-status.ipfs.io

[harlantwood]

I like project-repos.ipfs.io the best of these. Verbose but clear, and says what it is.

Reasons: lots of our repos are not code, and it's much more than ci-status already.

Going with project-repos.ipfs.io.

[jbenet]

sgtm!

On Mon, Dec 7, 2015 at 7:56 PM Harlan T Wood notifications@github.com
wrote:

I like project-repos.ipfs.io the best of these. Verbose but clear, and
says what it is.

Reasons: lots of our repos are not code, and it's much more than ci-status
already.

Going with project-repos.ipfs.io.

—
Reply to this email directly or view it on GitHub
#8 (comment).