Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2014-03-18

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

All times shown according to UTC.

Time Nick Message
02:15 oiami joined #metacpan
02:52 klapperl_ joined #metacpan
02:53 [Sno] joined #metacpan
05:16 nado joined #metacpan
06:32 nado joined #metacpan
06:43 nbezzala how can I see a list of all the top level namespaces used in CPAN?
06:48 [Sno] joined #metacpan
07:16 [Sno]_ joined #metacpan
09:54 rashi joined #metacpan
10:24 nado oalders, rwstauner hi! I have problems with permissions while using bin/metacpan (according to this instruction https://github.com/CPAN-API/metacpan-developer/blob/master/README_API.md) : http://paste.perldancer.org/1cJVqEpaE4bGs   what can I do with it?
10:25 dipsy [ metacpan-developer/README_API.md at master · CPAN-API/metacpan-developer · GitHub ] [ bin/metacpan release - Pastedance ]
10:25 oalders nado: which user are you running the commands as?
10:26 nado metacpan
10:26 oalders nado: try running them as "vagrant" (despite what the README says)
10:26 oalders we're thinking of changing the README
10:27 oalders you'll still need to source ~/.metacpanrc
10:27 oalders but i think it's easier to run as the vagrant user
10:31 nado ok, I'll try
10:37 nado hmm, seems to work
10:50 nado oalders, thanks!
11:01 neilb joined #metacpan
11:18 nado oalders, but now I can't start metacpan-api again (
11:20 nado oalders,  "service metacpan-api restart" doesn't work as well, but I started it with "plackup"..
12:02 [Sno]_ joined #metacpan
12:24 oiami joined #metacpan
12:53 oalders nado: right, that's the tradeoff.  we need to figure that out
12:53 oalders but you're probably better off using plackup during development anyway
12:53 oalders you'll get a better sense of what is going on by watching the output on that screen
13:08 Khisanth joined #metacpan
13:46 rwstauner too much switching of the users may have gotten the dir perms out of sync
13:47 rwstauner we mount a dir on top so that the metacpan user has write permission to that var dir
14:11 nado rwstauner, oalders yes, I see..
14:44 nado oalders, rwstauner okey. I definetely have patch for https://github.com/CPAN-API/cpan-api/issues/272
14:44 nado It was pretty easy to fix, but really hard to check :)
14:44 dipsy [ "Raw" access to images delivered as MIME="text/plain" instead of "image/png" · Issue #272 · CPAN-API/cpan-api · GitHub ]
14:45 rwstauner great!
14:50 oalders nado++
14:58 oalders nado: can you send a pull request?
15:41 nado oalders, yes, here: https://github.com/CPAN-API/cpan-api/pull/305
15:41 dipsy [ Fix GH#272 by nadoshmado · Pull Request #305 · CPAN-API/cpan-api · GitHub ]
15:42 oalders excellent :)
16:10 celogeek joined #metacpan
16:22 nado_ joined #metacpan
16:50 rashi joined #metacpan
17:44 neilb joined #metacpan
18:16 nbezzala joined #metacpan
18:19 [Sno] joined #metacpan
18:23 ether joined #metacpan
18:23 oiami left #metacpan
18:32 punter joined #metacpan
19:24 DerAlex joined #metacpan
19:32 oiami joined #metacpan
19:39 oiami Hi ! I don't understand the issue with 'Closed' status but it's linked  wishlist. Do I understand correctly that if it's closed mean it has been fixed/done or we decided that we won't fix/do it ?
19:40 oiami So if it's on wishlish I think it mean we want to see it
19:40 oalders oiami: in this case, closed means that we moved it from the issues to the wishlist
19:40 oalders the issues list was getting too big
19:40 oalders and confusing
19:41 oalders so things that weren't going to get immediate attention got moved to the wishlist
19:41 oalders so if something is on the wishlist, we can always re-open the issue later
19:41 oiami ahh, I see
19:48 oiami left #metacpan
19:49 ranguard oalders: speaking of which, related =~ duplicate == close the ticket :)
19:50 oalders ranguard: you referring to D'oh?
19:50 oalders ah, you were
19:50 oalders ranguard++
19:50 ranguard :)
19:52 nado_ oalders: so, I'm planning to write an application for OPfW now. Do you have any suggestions/tips to increase possibility of acceptance?
20:04 oalders nado_: most important would be how you will schedule your time on a weekly basis and also a realistic plan of what you hope to finish
20:04 oalders ie the hours you plan to be available and on which days
20:04 oalders in general
20:05 oalders and a timeline for getting things done
20:05 oalders just keep in mind that your first weeks on the project would be the slowest and you would get more productive as you get more familiar with the project
20:06 nado_ thanks
20:08 nbezzala joined #metacpan
20:24 metacpan joined #metacpan
20:24 metacpan [metacpan-web] ranguard pushed 2 new commits to master: http://git.io/mZkwaA
20:24 metacpan metacpan-web/master 9da6b64 OiOiOiOi: Add link to this version and latest version on s.c.o
20:24 metacpan metacpan-web/master ae90742 Leo Lapworth: Merge pull request #1130 from OiOiOiOi/Add_link_to_SCO...
20:24 metacpan left #metacpan
20:24 dipsy [ Comparing a9436d430687...ae907423ba91 · CPAN-API/metacpan-web · GitHub ]
20:32 metacpan joined #metacpan
20:32 metacpan [metacpan-web] ranguard pushed 1 new commit to master: http://git.io/rCYdzw
20:32 metacpan metacpan-web/master 8f3be96 Leo Lapworth: Give SCO it's own heading and standardize links
20:32 metacpan left #metacpan
20:32 dipsy [ Give SCO it's own heading and standardize links · 8f3be96 · CPAN-API/metacpan-web · GitHub ]
20:36 metacpan joined #metacpan
20:36 metacpan [metacpan-web] ranguard pushed 1 new commit to master: http://git.io/fyyoQg
20:36 metacpan metacpan-web/master 866a397 Leo Lapworth: Update tests to match!
20:36 metacpan left #metacpan
20:36 dipsy [ Update tests to match! · 866a397 · CPAN-API/metacpan-web · GitHub ]
20:37 oalders ranguard++
20:54 DerAlex joined #metacpan
20:59 talina_ joined #metacpan
21:47 rai_ joined #metacpan
23:08 AirDisa joined #metacpan

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