Skip to content
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

Transfer jar away from unresponsive owner #618

Closed
mikelococo opened this issue Feb 6, 2017 · 7 comments
Closed

Transfer jar away from unresponsive owner #618

mikelococo opened this issue Feb 6, 2017 · 7 comments

Comments

@mikelococo
Copy link

mikelococo commented Feb 6, 2017

@Raynes (https://clojars.org/users/rayne) was a prolific contributor to the clojure community until he passed away in December 2016 (https://www.reddit.com/r/Clojure/comments/5gyyxw/clojure_open_source_contributor_anthony_grimes/). With his passing, a number of widely deployed clojure libraries are now unmaintained. To my knowledge, no one has access to either his github or clojars.org accounts anymore. Is there a process by which maintainership of these libraries can be handed-off in a way that maintains url continuity for library users?

I recognize that there may are legitimate security concerns around this sort of process, and I'm a relative novice in terms of my understanding of clojars.org processes, but I did look on clojars.org, in the maintainers mailing list, and generally searched the web for indications of an established process (or ruling forbidding such a transfer) and could not find a definitive answer.

This is related to Raynes/fs#106 which is this discussion in the concrete context of the fs library.

@mikelococo
Copy link
Author

One "easy" option if there is not a pre-existing policy might be to allow transfer if you can demonstrate control of the source-code repository linked in the clojars page. This would allow us to piggyback off the Github repository transfer process without having to craft a custom-process that could be subject to abuse or create lots of manual verification work for the clojars team.

@danielcompton
Copy link
Member

This is a pretty unusual case, so I don't think we need to create a specific policy for it. Technically it is easy to add other people to be able to deploy to Raynes libraries, the question is more about whether we should. I don't feel qualified to make a decision on this, I'd much rather some of the people that Raynes was close with are the ones to discuss and decide on this.

@tobias
Copy link
Member

tobias commented Feb 7, 2017

For the fs library specifically, @tebeka is part of the fs group (https://clojars.org/groups/fs/) so could deploy or add others to the group to allow them to deploy with out any clojars admin intervention.

@mikelococo
Copy link
Author

mikelococo commented Feb 7, 2017

It seems many of the projects uploaded by @Raynes have other group members, and it working through those co-maintainer seems to be the best option when possible. Some projects are just him, though... for example https://clojars.org/groups/conch and https://clojars.org/groups/tentacles, which both have over 10k downloads.

@tebeka
Copy link

tebeka commented Feb 8, 2017

Thanks for letting me know. I'll look into it and get back to you.

@tebeka
Copy link

tebeka commented Feb 8, 2017

I've asked for someone to step up. Once someone wolunteers I'll add them to the group.

@mikelococo
Copy link
Author

Closing. @niwinz stepped up to maintain raynes/fs and tebeka has added him to the relevant clojars project. I suspect this unresponsive maintainer question is going to come up again soon, but for raynes/fs the maintainer situation is well on its way to being sorted out. Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants