Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2013-11-09

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:03 trs ether: IIRC, it's any permission from 06perms for at least one of the modules in the dist.
00:03 trs ether: re: rt.cpan.org's heuristic.
00:03 trs ether: also, I think that rjbs and dagolden proposed adding a project/dist concept to PAUSE on cpan-workers
00:06 ether trs: are you sure? I recall a situation where I was missing perms on one module (that had been recently added), and I wasn't listed as maintainer until I'd been given permission
00:07 trs ether: not 100% positive...
00:08 trs hold please
00:10 trs yup: https://github.com/bestpractical/cpan2rt/blob/master/lib/CPAN2RT.pm#L374
00:10 dipsy [ cpan2rt/lib/CPAN2RT.pm at master · bestpractical/cpan2rt · GitHub ]
00:11 trs lines in 06perms are mapped to distributions via 02packages which are mapped to RT queues via CPAN::DistnameInfo->new(...)->dist
00:11 trs and you don't need to have perms on all modules in dist.
00:17 ether eeck, it's parsing 06params manually
00:17 ether there's a module for that :)
00:18 haarg given that dist names don't need to relate to module names in any way, you can get rt perms for any dist you want
00:19 * ether nods, iirc xdg and BinGOs concocted some Acme dists to demonstrate "stealing" permissions
00:19 haarg yeah.  i know they filed a bug about it somewhere, but i don't remember where.
00:19 ether the whole dist vs. module thing is a big mess
00:20 ether if there was some canonical code that resolved the issues, that everything else could hook into, it would save everyone else trying to reimplement, badly
00:22 trs ether: well, part of the issue is also that PAUSE _doesn't_ have a concept of permissions on distribution/project names, but that they are immensely practical.
00:24 trs haarg: there's an issues.bestpractical.com ticket for rt.cpan and a cpan-workers thread.
00:24 trs the issues.bps ticket isn't public (unfortunately; there's been talk of making that queue public, but it hasn't happened)
00:25 trs ether: also, I don't think it's so wrong to parse 06perms manually?  all the NNfoo files are meant to be easy to parse :)
00:25 trs ether: see also: written before there was a module for that probably
00:25 trs :)
00:27 ether hmm perhaps! :)
00:35 trs http://www.nntp.perl.org/group/perl.cpan.workers/2013/03/msg1047.html
00:35 dipsy [ Distribution names are not unique. We need to figure out what to doabout it. - nntp.perl.org ]
00:36 trs I think there's code against PAUSE for (c)
00:39 leont left #metacpan
02:51 klapperl joined #metacpan
04:22 preflex_ joined #metacpan
08:32 jwang joined #metacpan
09:06 [Sno] joined #metacpan
10:05 jwang joined #metacpan
10:09 Farow joined #metacpan
10:27 Farow|2 joined #metacpan
11:49 Farow|2 joined #metacpan
12:29 tobyink joined #metacpan
12:47 alh joined #metacpan
13:10 Farow|2 joined #metacpan
13:21 Farow|2 joined #metacpan
13:31 bowtie_ joined #metacpan
13:58 Farow|2 joined #metacpan
14:07 Farow|2 joined #metacpan
14:19 tobyink joined #metacpan
14:23 Farow|2 joined #metacpan
16:06 Farow|2 joined #metacpan
16:14 klapperl_ joined #metacpan
16:49 b_jonas so this maintainership is all a mess. I see. :(
16:54 mst well, also, people try and use it for things it isn't designed for
16:54 mst I mean, what do you mean by 'current maintainers of a dist' and why do you want to know?
17:57 b_jonas mst: I want to know it to quickly guess which modules are worth to check when I'm trying to find new modules. Checking the owner is very useful for this, but sometimes a dist doesn't have just one author.
18:01 mst a good trick is to pull up the drop down for releases - that'll show you who did the last few
18:08 b_jonas mst: that can show past maintainers, sure
18:08 b_jonas but when there are two maintainers at the present but one does the releases, it won't help
18:09 b_jonas plus sometimes the docs tells who the maintainers are, which also helps
18:10 mst right, but 'the maintainers' often doesn't correspond to the PAUSE perms
18:10 mst you're treating 'the people who can upload' as 'the maintainers'
18:10 mst the useful information is (a) who's releasing stuff (b) who's credited in the docs/changelog
18:11 b_jonas ok
18:11 b_jonas I guess I don't know what I want
18:12 mst well, I'm giving you the heuristics -I- use for spotting authors to keep an eye on
18:26 tobyink joined #metacpan
19:14 Mike-PerlRecruiter_ joined #metacpan
19:26 ether looking at the names behind a dist is certainly useful for assessing its probable quality though; I do that all the time
19:27 ether e.g. when looking at two similar dists, one by an unknown and one by a prolific author who is responsive to issues, I'll always pick the latter unless I need a specific feature only in the former (and often then, I'll send a patch to the latter to add that feature) ;)
19:27 ether does that encourage an old boys' club? perhaps
19:28 ether but reputation does matter
19:28 mst right, but the point I'm making is that "the names behind a dist" and "the list of people with co-maint" don't necessarily intersect as much as b_jonas appeared to think
20:14 Farow|2 joined #metacpan
20:50 Farow|2 joined #metacpan
21:46 Farow joined #metacpan

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary