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

highlight modules or dists with ADOPTME or HANDOFF or NEEDHELP #1643

Open
rjbs opened this Issue Feb 11, 2016 · 11 comments

Comments

Projects
None yet
8 participants
@rjbs

rjbs commented Feb 11, 2016

It is intolerably hard to declare that you don't want to deal with a CPAN module anymore. No matter what, it just sits there under your name, inviting bug reports, no matter how many times you say "No, I'm done." (It's even worse if you're only co-maint, but that's another matter.)

One accepted but basically unsupported solution is to use special permissions users to indicate the idea that you want to transfer permissions away, or just get more hands at work. Unfortunately, nobody benefits from this, because nobody can tell they've been assigned unless they go look in 06perms, which is far, far more than anyone should be expected to do.

It would be useful if the MetaCPAN web site would throw up a big notice like:

  • ADOPTME: This distribution is up for adoption! Contact the modules list if you want to take over.
  • HANDOFF: This distribution's maintainer is looking for someone to take over! Contact them…
@neilb

This comment has been minimized.

Contributor

neilb commented Feb 11, 2016

👍

@oalders

This comment has been minimized.

Member

oalders commented Feb 11, 2016

This can be done once metacpan/metacpan-api#338 is merged. I'll have another look at why that never made it into master.

@neilb

This comment has been minimized.

Contributor

neilb commented Feb 13, 2016

I've written up my thoughts about this.

@rjbs

This comment has been minimized.

rjbs commented Feb 13, 2016

@neilb Your blog post actually doesn't address HANDOFF or ADOPTME at all, from what I can see.

@neilb

This comment has been minimized.

Contributor

neilb commented Feb 13, 2016

@rjbs: bugger, I thought about those at one point, then forgot to factor them in. ta!

@karenetheridge

This comment has been minimized.

Contributor

karenetheridge commented Feb 14, 2016

@neilb

This comment has been minimized.

Contributor

neilb commented Feb 14, 2016

@rjbs I've updated my blog post, to talk about HANDOFF, ADOPTME, NEEDHELP, and deprecated as well.

@dolmen

This comment has been minimized.

Contributor

dolmen commented Feb 17, 2016

Just for information: there is a place where permissions are a bit more visible that in 06perms: on rt.cpan.org, above the bug list of the distribution. That's where I usually lookup perms.
Here are a few interesting links:
https://rt.cpan.org//Dist/ByMaintainer.html?Name=ADOPTME
https://rt.cpan.org/Dist/ByMaintainer.html?Name=HANDOFF
https://rt.cpan.org/Dist/ByMaintainer.html?Name=NEEDHELP

@dolmen

This comment has been minimized.

Contributor

dolmen commented Feb 17, 2016

@neilb And speaking about rt.cpan.org, 06perms gives special power on RT tickets:

  • only maintainers (or co-maint) can edit maintainer's notes.
  • only maintainers and requestors can change the state of a ticket
@neilb

This comment has been minimized.

Contributor

neilb commented Feb 17, 2016

@dolmen -- thanks, I wasn't aware of those!

I'll update my blog post.

@xdg

This comment has been minimized.

xdg commented Feb 18, 2016

My commentary on the related issue of who/why to show prominently: http://www.nntp.perl.org/group/perl.cpan.workers/2016/02/msg1400.html

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