Hi Neil, thanks for coming back to that.
I will do both: first write ETHER a mail, polite but clear. And as second, contact the MetaCPAN people. As I was supposed that there is an indexing issue, I contacted PAUSE Admins first (and NEILB was displayed by PAUSE as the available admin). And regarding the Block: I would really be happy if hijacking someone else namespace (even with DEV-Releases) isn't possible without COMAINT. And I would be always happy to add someone as COMAINT, when this person respects the service quality of a module and not just "it's own particular bug regardless everyone else". I do not really want an ETHER poster at anyones wall with "Must prevented to disturb Jens" :) Cheers, Jens PS: Seems a lot of people changed their primary email addresses ... > Am 06.05.2026 um 11:40 schrieb Neil Bowers <[email protected]>: > > Hi Jens, > There isn't a documented policy related to doing developer releases of > someone else's distribution. I've done this a few times in the past, but > always checking with the author first that they're happy for me to do that. > I'll discuss this with other admins, but if the PAUSE Operation Model is > updated, it would likely be to say that it's good manners to check with the > people who have indexing permissions, and particularly those who've done > recent releases. > Have you contacted ETHER directly to say that you're not happy for her to > do this? If not, then I suggest a polite email asking her to (a) delete the > recent upload, and (b) not do it again. That puts you in a stronger position > if she does it again. You could also ask her if there's a bug she was trying > to address, which you could then address in your own releases. Being polite > and trying find out what problem someone else is trying to address, often > helps diffuse a situation, I've found. > You requested "A standing block preventing ETHER from uploading into any > namespace I own". There is no mechanism for that, and I don't see us adding > one. > Due to the way PAUSE handles indexing permissions, the real problem here > seems to be MetaCPAN related, so maybe you could have a chat with that team? > Cheers, > Neil >
signature.asc
Description: Message signed with OpenPGP
