You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking that communicating changes in distro permissions or announcements may be beneficial.
For example, if $work depends on Acme::Useful::Module, and the sole author gets run over a bus, leading to the dist maintainer being set to HANDOFF, I think it would be good if this would be communicated in any tooling used by this business.
e.g. if cpm(1) or cpanm(1) or cpan(1) could give a notice if any modules that just were installed need adoption, and if the business finds this necessary, it could decide to volunteer taking over the dist.
To help make this easier, let's make the 06perms.txt file available. :-)
The text was updated successfully, but these errors were encountered:
Hei!
I'm thinking that communicating changes in distro permissions or announcements may be beneficial.
For example, if $work depends on Acme::Useful::Module, and the sole author gets run over a bus, leading to the dist maintainer being set to HANDOFF, I think it would be good if this would be communicated in any tooling used by this business.
e.g. if cpm(1) or cpanm(1) or cpan(1) could give a notice if any modules that just were installed need adoption, and if the business finds this necessary, it could decide to volunteer taking over the dist.
To help make this easier, let's make the 06perms.txt file available. :-)
The text was updated successfully, but these errors were encountered: