Gustavo Niemeyer

Indeed. The initial omission was purposeful, to wait until the feature was polished, but we can now document it openly.

Neat, thanks!

I'd prefer to have the badge being served by gopkg.in itself because that's both easy and much more convenient, but I'm not against people using something else if they wish....

Hey Alex, Indeed it should not be hard, and I wouldn't having a flag to make this a runtime option, as long as we can keep both cases clean. No...

We can have a flag to alter between two modes: 1. The default behavior: a missing user means go-[repository name] 2. A custom default user We cannot have a mix...

Thanks for cooking this, Alex. I'm trying to think about the consequences in terms of people understanding that although this looks a lot like a common gopkg.in, it actually follows...

This would be the right URL: http://gopkg.in/GlassyMedia/go-json-rest.v1/trie

Actually, I'm reopening this as it should be better documented. Thanks for bringing it up.

Sounds like a fine idea to me.

We need to consider caching of that information, and we should also pick a less populated namespace for that. We already have the potential of git and the actual repository...