Consolidate Badges as a Service under GitHub organization

[chadwhitacre]

No description provided.

[nathany]

Do we also want a https://github.com/shieldsio organization on GitHub? If we're gonna move it again, we might as well get that out of the way. /cc @jbowes @olivierlacan @bryanveloso

[chadwhitacre]

@nathany I think that should coincide with a spin-out from Gittip, which I agree should happen but I'd feel better about it if the project were a little better established first. GitHub does gives us redirects now so there's less pressure from that angle. Can we get through our milestone (land the port to Go for http://img.shields.io/ + design a new http://shields.io/) and then revisit the idea of a spin-out?

[nathany]

Sure thing.

Though I'll mention up front that the way Go's imports work, the spin-out may impact a handful of people who want to use shields.io as a library (despite having those redirects in place). Probably not a big deal.

[chadwhitacre]

[T]he way Go's imports work, the spin-out may impact a handful of people who want to use shields.io as a library (despite having those redirects in place).

Ah, due to net imports or some such, eh? I'd expect that to be a minor use case, but it could be a reason to switch organizations now. It sounds like you have the energy and interest to lead this charge, so I say go for it! :-)

[nathany]

No rush here.

[chadwhitacre]

Let's do this now, because https://github.com/gittip/buckler/pull/13/files#r8681416. I think the org name should be shields instead of shieldsio per #92 (comment).

[chadwhitacre]

@nathany Do you have all the perms you need to configure this? What do you need from me?

[chadwhitacre]

Sorry, didn't check https://github.com/shields first. I guess https://github.com/shieldsio is the next-best option. @olivierlacan?

[nathany]

@whit537 I have permissions to make the change, though I'm not entirely sure how it impacts open pull requests like badges/buckler#13. It should be fine, only people with commit access will need to update their remotes.

[nathany]

One other option is to ask @Mikulas if we can hang out under https://github.com/badges - another Retina project.

Does github.com/badges/shields.io make sense?

[Mikulas]

I am totally willing to let you use badges.github.io, I don't really have time to take it further than the current concept.

However while hi-res png is cool as it looks the same on everywhere, svg can be rendered in literally everything but IE8 (which is not an issue for GitHub users anyway). What is the plan here currently, svg or png?

I have a totally cross-browser svg with embedded Open Sans, so unlike b.adge.me the svg does not look any different than the "canonical" template Travis etc use.

[nathany]

@Mikulas If you can give me admin access to the badges organization, I'd like to shuffle all badge related repos over there. This includes shields.io, buckler, b.adge.me, etc.

We may only use a few of these in building the new shield service, but I think it would be a good start, just to collect them all together.

@whit537 My preference would be to use badges for the organization and shields for the main repo (rather than shieldsio/shields). To me, it makes sense to distinguish between the badge image (which may have one or more libraries and a CLI) and the Shields brand/service.

[Mikulas]

@nathany I actually added you as an owner as any lower privileges would hinder whatever you want to do. Feel free to replace / remove the current repo. It would be cool however if I were to remain (at least for the time being) as an owner as well.

[nathany]

Thanks @Mikulas. For now I think I'll do a core team of administrators that have full access to all repos.

We can go more granular if people prefer.

[nathany]

@whit537 Can you transfer https://github.com/gittip/badgr.co to the badges organization? https://github.com/badges

[nathany]

@jbowes We're moving buckler again, over to https://github.com/badges/buckler (sorry about all the moving).

[chadwhitacre]

@nathany I luuuuuuuuuuuv what you're doing with https://github.com/badges. I agree that it's a fantastic step in the right direction. I've moved both badgr.co and img.shields.io-old over there.

[nathany]

@cainus We are consolidating all the "badge as a service" implementations under the badges organization. If you would like to get in on the fun and move https://github.com/cainus/shielded under https://github.com/badges, that'd be swell!

[chadwhitacre]

Hey @cainus, want in on the party? You should transfer https://github.com/cainus/shielded to the badges organization. :-)

[nathany]

^_^

[nathany]

@whit537 Looks like I hijacked your thread. Shall we setup a new issue for a Shields company?

This can be closed once @espadrine and @canius are in.

[chadwhitacre]

Looks like I hijacked your thread.

Yeah, no worries. You did something awesome with it. :-)

Shall we setup a new issue for a Shields company?

Sounds good.

[cainus]

transferred!

[nathany]

@cainus Awesome! Thanks.

Would you be interested in working with @espadrine and a few others on Shields.io implementation? They have SVG badges implemented here (also Node.js): https://github.com/espadrine/gh-badges

[cainus]

What kind of help are they looking for? Those two projects I just moved under this org do basically that.

[espadrine]

@cainus Did you do work on server-side caching? I could use some help making PNG faster.

I'd assume we can achieve two things:

• Keeping phantomjs running (avoids startup time and re-computing the font's base64)
• Caching the resulting image in a fixed-sized RAM store, keeping the most used ones around.

[nathany]

@fjcaetano If you would like to move https://github.com/fjcaetano/cocoapod-badges under the https://github.com/badges organization, just let me know. Also include the handles of anyone with commit access so I can setup a new team.

[nathany]

@cainus Please refer to The Team issue #96 for a high level list of things we need to work on and the gh-badges issue list for implementation-specific enhancements.

[fjcaetano]

@nathany I guess it makes sense to join everything under the same roof, but I'm a little hesitant to give up ownership of the repo...

[nathany]

@fjcaetano Your project uses the badge generation services that these other projects are trying to provide, so it is a little different.

I can give you admin/owner access once I'm at a computer. Right now we probably have too many owners. I think we may want more granular permissions once we firm up the team. #96

[chadwhitacre]

GitHub let's you create teams and assign permissions to repos based on teams. If Cocoapods is a straight consumer of the services under badges it might be a bridge too far to move that under the badges org.

[chadwhitacre]

Now, gh-badges on the other hand ... ;-)

cc: @espadrine

[nathany]

CocoaPod Badges and @kura's PyPI Shields are certainly interesting. They are consumers of the APIs rather than badge generation implementations, bridging the gap by providing badges to another service. I don't feel like they need to be under the badges organization, but I certainly don't mind if they would like to.

[kura]

@nathany what would being under the organisation include/exclude for my service? I'm happy to chat about it, feel free to drop a mail to kura [at] kura [dot] io.

[chadwhitacre]

@nathany I think if "bridge" services come under the badges organization, we should set them up permissions-wise to be independent, as they are now (we should be able to use GitHub teams for this). Then the value to them is simply a commitment and advertisement that they're part of this overall badge standardization effort.

@fjcaetano @kura Does that sound interesting to you?

[fjcaetano]

I like it

[kura]

I'm good with that.

[nathany]

@fjcaetano @kura I've added teams for cocoapod-badges and pypipins. You are administrators of each, and everything (including issues) will transfer.

I will double check the team settings after you transfer your repositories.

[fjcaetano]

Guys, I've migrated cocoapod-badges to the org. Let me know what I have to do with its LICENSE.

Currently it's on my name. Can I leave it that way, or should I change it to the org?

[nathany]

@fjcaetano I'm glad you bring up the LICENSE. For now I see no problem with leaving it as is, but it is an important discussion to have going forward. #104

@fjcaetano and @cainus Can I encourage both of you to join Gittip? https://www.gittip.com/

Closing off this ticket. Thanks for joining us!

[nathany]

Whoops, I thought @kura had already migrated over.

[kura]

Sorry, haven't had the time. I'll do it later today.

[kura]

I've transferred ownership, can you give me my privileges over the repo please? =)

[nathany]

Sure thing. Sorry for the delay @kura.