Take over ownership

[mattrobenolt]

How do we (Sentry) become owners of this repository on Docker Hub?

I was going to start publishing to a getsentry/sentry, but realized, it'd probably be better if we owned this instead and controlled our own releases, etc.

I was going to be publishing a new repository at https://github.com/getsentry/docker-sentry. Would we be able to point that one to the official registry? Or would it be developed in here?

Thanks.

[tianon]

That would be absolutely fantastic! 🎉

There's a little bit of info about the process we prefer over at https://github.com/docker-library/official-images#maintainership, and so if you're ready to take the torch I can add you as an admin in the https://github.com/docker-library-transitioner organization and move this repo over so you can rename/move it to the getsentry organization, assuming @yosifkit doesn't have any objections. 👍 (You haven't really been involved in this repo specifically, but you've contributed positively to others we maintain, so I'm personally a big +1! ❤️)

Sound like a good plan?

[mattrobenolt]

Let's do it. :)

[yosifkit]

LGTM!

[md5]

@tianon @yosifkit Did docker-library get opted in to GitHub's Improved Permissions beta yet? If not, it may be worth figuring out if they can add you. It would allow you to do away with this docker-library-transitioner thing and just add outside collaborators as admins directly to specific docker-library repos (which would allow them to complete the transfer).

[tianon]

Oh interesting -- nope!

[mattrobenolt]

Cool, it's transferred over just fine.

What's needed now to get builds in official-library to be coming from this repo now?

[mattrobenolt]

thx for the speedy process, btw. <3

[md5]

@tianon You might try pinging support@github.com. I think they'll be happy to add docker-library, given the nature of the org.

[md5]

Sorry for the OT comments, @mattrobenolt 👍

[tianon]

@mattrobenolt 👍

You'll probably want to familiarize yourself with https://github.com/docker-library/official-images/blob/master/README.md and generate-stackbrew-library.sh within this repo, which when run should spit out the contents of https://github.com/docker-library/official-images/blob/master/library/sentry (ready for making a PR to update the image itself).

[mattrobenolt]

Rad. Lemme do that. :)

[tianon]

@mattrobenolt you'll also want to check out https://github.com/docker-library/docs, which is where the documentation for the image lives (and there's a README.md there describing that repo's process as well)

[mattrobenolt]

@tianon @yosifkit How does this LICENSE work in this repo? Right now it's licensed to Docker, Inc, which is odd for us. I assume we can change this to be our own LICENSE?

[tianon]

Uhh, hmm. I'm not a lawyer, but I would imagine that's OK? My understanding is that right now it's copyrighted by Docker, Inc (and actually, it's really copyrighted to the individual contributors unless they explicitly signed-off their copyright), so the name in the license should be safe to change without a problem AFAIU.

[mattrobenolt]

/cc @dcramer

Going to assume it's ok to change the LICENSE here to our 3-clause BSD? Or do you want our Apache?

[md5]

@tianon Since the only contributors are you and @yosifkit and you worked on this image as part of Infosiftr under an agreement with Docker, Inc, that probably means it's a work for hire and that Docker, Inc. really does have the copyright. Assuming I understand the situation correctly (IANAL, etc).

[dcramer]

I prefer Apache. We cant really change the license but we can amend it. Legally all prior contributions are licensed under Docker, Inc. and all future contributions will additionally be licensed under Sentry.

i.e. add Copyright 2015 Sentry to the top, but keep the rest in tact

[mattrobenolt]

Thanks guys, I think everything is done here for us?

[tianon]

I think so! 👍