New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loris Needs a New Owner #323

Closed
jpstroop opened this Issue Jul 12, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@jpstroop
Member

jpstroop commented Jul 12, 2017

I can't think of an easier way to reach all of the people who need to see this message than to start an issue--I hope nobody minds.

Loris started as a simple Python script that was meant to sit behind a webserver and dynamically respond to DZI requests, and it wasn't meant to work for anyone other than me. Around the same time, IIIF came along and the script became an application, and I put it on Github because it seemed like it might be useful to others. At the time there was no other image server that was (arguably) production-ready and implemented the IIIF Image API natively. And, importantly, Loris was, and is, hackable in a way that many other solutions are not--it's still reasonably easy to pull down the code and customize it to work for you and contribute those changes back.

A small community of developers, 24 in all, have committed to Loris since then, and in the last two years or so they have come to know the code better than me, and have made the project better than I could have. Late last fall, I added @bcail as a committer because he, in particular, had been doing a lot of value-added refactoring and seemed like a natural fit. As my career continues to trend away from hands-on software development, it's time to pass on management and ownership of Loris to others. I'm happy to stay involved, and to help organize this effort in any way that I can, but as things stand right now I no longer feel comfortable merging pull requests.

I don't want to put anyone on the spot, and I don't want to wrap this transition in a ton of process if we can avoid it. Please, drop me an email (jpstroop @ gmail) in the next week or two, and I'll consult w/ @bcail, after which we'll give you write access to the repository if we agree. For now my only requirement is that you have made at least one substantive commit to the project before expressing interest. Ideally there will be three committers, and I'll leave it to that group to make decisions and policies around how future PRs are merged and additional committers are added.

Thanks.
@jpstroop

@jpstroop

This comment has been minimized.

Show comment
Hide comment
@jpstroop

jpstroop Oct 13, 2017

Member

Closing this, thanks to @bcail and @alexwlchan! New committers still welcome (nudge nudge @azaroth42).

Member

jpstroop commented Oct 13, 2017

Closing this, thanks to @bcail and @alexwlchan! New committers still welcome (nudge nudge @azaroth42).

@jpstroop jpstroop closed this Oct 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment