Transition plan

[nathany]

Will we use img.shields.io or a different subdomain? If we do, how many people are using it and how we handle API compatibility?

Do we want to transition users of other services such as http://b.adge.me/ and http://b.repl.ca to the new service, and if so, how do we go about this (assuming the API #100 may change)?

[espadrine]

Since the move is designed to put the b.adge.me code under the shields name, it should presumably be under the shields.io domain.

[nathany]

@espadrine Clarified my questions above.

[chadwhitacre]

Here's where we decided previously to use img.shields.io, fwiw: #52 (comment).

[chadwhitacre]

I think we do want to transition users of other services. This is underway for http://badgr.co/ (#63), though honestly the number of users depending on any of these services is so small in comparison to the number of users we hope to have that we shouldn't stress about it too much, I think. If we leave them running for a month or two after launch I think that'd be plenty.

[espadrine]

People are currently relying on the b.adge.me URLs and APIs. Until I can redirect them to the new domain, they will keep doing so.

How long would we wait until we use b.adge.me under img.shields.io? What prevents this from happening?

[chadwhitacre]

@espadrine Some number of people are currently using img.shields.io already as well. The b.adge.me API doesn't match the existing img.shields.io API, so if we simply CNAME img.shields.io to b.adge.me we'll break the service for those already using it. I suppose that leads back to the web API discussion (#100).

[nathany]

So b.adge.me could run a little bit of code to redirect with the new API format.

Or we could support other API formats under img.shields.io based on referrer, or have something like badgeme.shields.io and do a bit of API translation based on subdomain?

[espadrine]

Can you specify what the differences are between the current img.shields.io API and b.adge.me?

Note for instance that http://img.shields.io/gittip/jsfiddle.png will be hard to transpose, since I am case-sensitive.

[chadwhitacre]

Picking up with web API discussion at #100 (comment) ...

[olivierlacan]

We're using img.shields.io.