Perl 6 - the future is here, just unevenly distributed

IRC log for #pr-challenge, 2015-01-02

| Channels | #pr-challenge index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:07 neilb currently 222 people have signed up
00:08 boreas wow
00:16 G_SabinoMullane joined #pr-challenge
00:18 kentnl neilb: just fyi, I heard about it .... through gentoo before I heard about it through perl. That's weird man.
00:19 neilb heh
00:24 neilb if you’re hearing about it in other places, that might explain why I’m still getting bursts of signups
00:24 kentnl its like you replaced one end of the echo chamber with a half-silvered mirror, and it turned into a laser, and all the cats are comming out of the woodwork :D
00:29 kentnl neilb: do you have enough projects to go around?
00:30 neilb For January at least, yes :-)
00:30 neilb Have had someone emailing me asking if he should put his dists on github to help, which was awesome
00:32 neilb Next batch of assignments going out …
00:42 neilb Seen some assignments and thought “oof. doc maybe?” :-)
00:42 neilb But there are enough that hopefully one person’s “oof” is another’s \o/
00:45 neilb night
00:46 kentnl nite
00:59 BRAD joined #pr-challenge
01:10 dfluck joined #pr-challenge
01:11 exhortatory joined #pr-challenge
01:24 boreas was top post on hackernews yesterday, that may have helped.
01:34 vroom joined #pr-challenge
01:39 boreas joined #pr-challenge
01:46 athos joined #pr-challenge
01:47 daveh joined #pr-challenge
01:50 boreas joined #pr-challenge
01:58 vroom joined #pr-challenge
02:01 boreas joined #pr-challenge
02:12 boreas joined #pr-challenge
02:13 Su-Shee_ joined #pr-challenge
02:20 athos joined #pr-challenge
02:23 boreas joined #pr-challenge
02:34 boreas joined #pr-challenge
02:40 gfranks joined #pr-challenge
02:45 boreas joined #pr-challenge
03:01 boreas joined #pr-challenge
03:14 veryrusty joined #pr-challenge
03:17 vroom joined #pr-challenge
03:26 vroom joined #pr-challenge
03:26 oalders joined #pr-challenge
04:34 gfranks joined #pr-challenge
04:54 dfluck joined #pr-challenge
04:55 adelq joined #pr-challenge
05:09 adelq joined #pr-challenge
05:37 memeticpox yeah, I'm happy to be looking at contributing to the Perl community. Have been doing Perl dev off and on since the late 90s, but it's almost all been closed source stuff.
05:50 vairav joined #pr-challenge
05:53 adelq joined #pr-challenge
06:28 athos joined #pr-challenge
06:30 vairav joined #pr-challenge
07:16 LLamaRider joined #pr-challenge
07:35 tadzik glad to have you onboard :)
07:50 daveh_ joined #pr-challenge
08:18 sue joined #pr-challenge
08:21 rindolf joined #pr-challenge
08:22 rindolf Hi all.
08:23 BHS_error hi
08:24 rindolf Two things: 1. The email that was sent to me about my distribution to pull request was sent without a "Date:" field. 2. I tried to subscribe to the mailing list, but didn't get a notification that I did.
08:24 rindolf BHS_error: hi.
08:30 sue I don't understand why the google group/list is private
08:30 sue shouldn't it be readable by non-members?
08:35 sivoais ooh! quite a bit of convo here!
08:35 sivoais hmm, it should be public. That way it can be indexed. :-)
08:35 sivoais imo
08:36 sivoais I didn't even know that it was private, but we'd probably have to get everyone's assent
08:44 dfluck joined #pr-challenge
08:54 sawyer rindolf: neil could put the email script in the repo and you could submit a PR for making sure there's a Date field :)
08:54 rindolf sawyer: OK.
08:54 rindolf sawyer: :-)
08:54 rindolf sawyer: what's new?
08:55 rindolf sawyer: and thanks for the +o. :-)
09:05 sue mine had a date field. seems odd.
09:10 bjakubski joined #pr-challenge
09:20 jkg my email had a Date: header, but given it's in PST, I imagine it was added by my email provider and not the sender :-)
09:21 * jkg would not have noticed, had it not been brought up, though
09:28 lbrown joined #pr-challenge
09:31 mvuets joined #pr-challenge
09:37 sawyer rindolf: doing the PR challenge, ya know :)
09:37 sawyer how about you?
09:39 rindolf sawyer: I also did the PR challenge.
09:39 rindolf sawyer: and I went on a walk.
09:41 sawyer rindolf: that's nice
09:45 lbrown a module that tells you to run Build.PL should have Build.PL in the repo, right? Or am I just a super noob?
09:45 rindolf lbrown: maybe it uses Dist-Zilla.
09:45 rindolf lbrown: which repo is it?
09:45 lbrown Video::Xine
09:46 lbrown To install this module type the following:
09:46 lbrown perl Build.PL
09:46 lbrown ./Build
09:46 lbrown ./Build test
09:46 lbrown ./Build install
09:46 rindolf lbrown: please don't flood.
09:46 lbrown sorry
09:46 rindolf lbrown: https://github.com/stephenenelson/video-xine - this seems like a Dist-Zilla-using module.
09:47 lbrown Yeah, that's the one - probably needs its README updates
09:47 rindolf lbrown: why?
09:47 lbrown yeah, it moved to Dist::Zilla at version 0.24
09:47 moritz lbrown: cpanm Dist::Zilla; dzil test
09:47 ribasushi lbrown: often when transitioning between build systems, people leve behind emnants of the old docs or even old workflow files that have nothing to do with the current way do foing things
09:47 jkg that's a very stock looking set of installation instructions :-)
09:47 ribasushi lbrown: that indeed is a PR all by itself
09:48 rindolf lbrown: Dist-Zilla generates a Build.PL for you.
09:48 ribasushi rindolf: stop, step back, read my reply
09:48 moritz fwiw the installation instructions are probably true for the tarball
09:48 lbrown alright, installing Dist::Zilla
09:48 moritz just not doing it from git
09:48 ribasushi moritz: that is also true
09:48 rindolf ribasushi: I don't understand - when the distribution is uploaded to CPAN, it may actually have a Build.PL.
09:49 rindolf ribasushi: yes, what moritz said.
09:49 ribasushi rindolf: yes, but both cases are valid is what I was trying to point out (badly, blaming ecoffee)
09:50 lbrown yeah, there's a Build.PL in the tarball. So I guess I should add a paragraph to the readme for if you're building from git?
09:51 moritz +1
09:52 ribasushi lbrown: there is a push to standardize on some common dzil-specific verbiage for this, I do not know how far along that text is / where it is hiding
09:52 ribasushi ether would be the primary person to know this, but ETIMZONE
09:53 ribasushi lbrown: so while a couple lines in the README are perfectly fine, there may be a better way
09:53 sawyer the installation instructions are, in fact, for the tarball
09:53 LLamaRider Reading this, I'm happy I got a MakeMaker module
09:53 sawyer lbrown: that's a good change, but you need to remember to retain it for developers, not users
09:53 lbrown the Dist::Zilla repo doesn't have a README
09:54 sawyer users won't necessarily know it uses Dist::Zilla, nor need they
09:54 lbrown I guess that's one way to do it
09:54 sawyer lbrown: depending on the configuration file, it might create one
09:54 sawyer Dist::Zilla is a distribution creator - so it can create files and edit files as part of building
09:54 sawyer if you run "dzil build", you'll get both the tarball and the directory tree
09:54 ribasushi lbrown: ah I thought the repo *had* a README, ignore everything I said then ;D
09:54 sawyer then you'll see what it actually creates
09:54 sawyer you can also read the configuration file (dist.ini) which contains which plugins to run when creating it (in dzil, everything is done in plugins)
09:54 lbrown rabasushi: ??
09:54 ribasushi lbrown: +1 on what sawyer said
09:54 jkg dzil should be largely invisible to the mere mortal installing the module, right? so I guess I'm agreeing with the "instructions are fine for tarball, maybe add a line for potential-contributors installing it from git" thing :-)
09:55 sawyer jkg: yup
09:55 sawyer but some authors have information set for developers who help
09:56 jkg *nodnod* that sounds like a worthwhile thing too :-)
09:56 sawyer lbrown: but hey, you get your first experience with dzil! :)
09:56 lbrown Yeah, it looks pretty neat actually
09:56 lbrown after you get over the confusion
09:56 sawyer it's very very nice
09:56 sawyer *after you get over the confusion* :)
09:56 sawyer (i couldn't put it better myself)
09:57 lbrown ugh, modules can be so slow to build
09:57 lbrown especially on a 5 year old low-end laptop
09:58 * jashank puts his head in an eldritch, C++-shaped vice, and turns the handle
10:06 dhuzz joined #pr-challenge
10:08 * dams got JSON :)
10:09 moritz dams: sounds like a pretty useful module :-)
10:10 BHS_error lucky you !
10:10 * sivoais got Clone
10:10 sivoais I plan on using the downstream deps to test my changes :-P
10:11 rindolf moritz: JSON::MaybeXS is more recommended over JSON.pm
10:11 moritz rindolf: I know; still lots of people and projects use JSON.pm
10:11 sawyer dams++
10:11 rindolf moritz: OK.
10:11 sawyer sivoais++
10:15 BHS_error sadly, people often use JSON.pm, because when you look for a JSON-able module, that's the first one popping up in the search
10:16 moritz it takes a lot of time for such choices to change over time
10:16 BHS_error I was not even aware of alternatives for JSON.pm
10:17 BHS_error btw, what are the defects of JSON.pm so that other things should be preferred over it ?
10:17 moritz project idea: a search mode for modules on metacpan that ranks by community recommendations
10:17 dams moritz, sawyer: it's just a frontend to JSON::PP and ::XS, but still, it should provide good opportunities to hack useful stuff out of it
10:18 BHS_error moritz: or by ++
10:19 BHS_error it always bothers me when I search for moo (all smallcaps) and I get this : https://metacpan.org/pod/distribution/PerlPowerTools/bin/moo as the first result
10:20 sawyer dams: absolutely
10:20 sawyer ++ can be gamed and aren't used by many
10:20 sawyer just like github stars
10:20 sawyer just like CPAN reviews
10:20 sawyer and i've seen all three happen :/
10:21 dams sawyer: I remember the Dancer CPAN rating war :) pretty funny
10:24 sawyer dams: yeah... someone from Germany has put a horrible review under Su-Shee's name
10:24 sawyer people are terrible :/
10:24 dams sawyer: indeed. But we know who he was :)
10:25 sawyer and under Sinatra's name, which prompted them to write an official post negating it
10:25 dams I know my history, I was there :)
10:25 sawyer yeah :)
10:25 dams anyway the more time passes, the more these things make me chuckle, rather than gringe
10:25 dams I guess it's a good sign.
10:32 kentnl lbrown: its possible also that the readme in the source/build tree is generated by a plugin. That's a very common thing.
10:33 kentnl and for easy pull request points, send a pull request that gets the author to add a [MetaJSON] segment to their dist.ini (somehow), because only shipping MetaYML is so 2007.
10:33 kentnl ( neilb suffers lacking that one extensively :P )
10:44 sawyer dams: i agree
10:54 veryrusty joined #pr-challenge
10:58 sue joined #pr-challenge
11:22 sue_ joined #pr-challenge
11:29 veryrusty joined #pr-challenge
11:33 chady joined #pr-challenge
11:36 jashank All the Ruby I've written of late has changed the way I write Perl.
11:36 jashank (I'm writing a small $work project in Perl to get back up to speed, and woah...)
11:45 moritz jashank: how did it change the way our write Perl? I'm curious
11:50 sawyer jashank: BLOG POST!
11:50 sawyer :)
11:50 moritz I guess the thing that changed my p5 style most was reading HOP
12:01 LLamaRider sawyer: if you keep urging people to blog, i might just go and finish the blog I was setting up, but keep postponing ^^
12:17 jashank I'm actually really tempted to explain it now.
12:17 sawyer LLamaRider: oh my god no!
12:17 sawyer jashank: you should
12:17 sawyer LLamaRider: and you should, too :)
12:19 * jashank starts writing :P
12:28 sawyer \o/
12:31 jashank It won't be all that interesting, probably just my usual drooling about CS being a journey from concrete ideas through to abstract ideals.
12:31 jashank (This is what my CS lecturers have done to me.)
12:33 lbrown :(
12:35 jashank Well, just one of them, anyway; the other lecturer always seemed to have just logged off his PDP-7 running First Edition before coming down to each lecture.
12:55 lbrown joined #pr-challenge
12:57 lbrown joined #pr-challenge
12:58 G_SabinoMullane joined #pr-challenge
12:59 kentnl jashank: just for context, did you have Moose *before*  you started doing ruby? I
13:03 jashank kentnl: No; I learned Ruby in 2011 and Moose in mid-2012.
13:03 lbrown joined #pr-challenge
13:04 * kentnl has found moose changed my perl style slightly more than any other influence in recent memory
13:04 kentnl even when I'm not using it
13:05 jashank My Perl usage went down quite a lot after I learned Ruby, so it's possible that my brief encounter with Moose is still influencing my Perl...
13:14 lbrown I'm having some trouble building my dist... it's using distzilla but when I run dzil build it complains that an ogg file which is used for testing isn't UTF-8
13:14 vroom joined #pr-challenge
13:14 lbrown is there a different way that I should be trying to build it?
13:17 mvuets lbrown: https://github.com/rjbs/Dist-Zilla/issues/270#issuecomment-33581607 maybe?
13:20 jashank I have a draft of that blog post.  I might wait until I'm awake before I proofread and post it.
13:20 lbrown mvuets: thanks! :)
13:23 jkg jashank: you could publish and let the internet proof read it for you ;)
13:28 jashank jkg: I dunno, my preference has always been to let a blog post stew for a while before I post it.
13:29 * jashank enjoys contemplating things.
13:29 * lbrown will try to google before asking stupid questions in IRC
13:29 jkg ah, you're one of these people who only puts properly thought out things on the internet -- I didn't realise there were any left :-)
13:30 jashank I try to think about things before I spew longform prose at the Internet.
13:30 jashank That's why I use Twitter :P
13:30 jkg heh
13:31 jkg so, my assigned dist fails (many, many of) its tests in my env ... but having just poked travis-ci at it, passes them all there. I think my env might be screwed :-)
13:31 jashank jkg: Sandbox time!
13:32 lbrown jkg: yeah distzilla failed most of the tests in my env, I just used --force
13:32 jkg :)
13:32 jashank Oooh, it's a little bit too far past midnight for my liking.  Time for me to go have strange sigil dreams.  o/
13:32 lbrown it won't last the month anyway
13:33 lbrown sweet dreams, jashank
13:34 kentnl googling before IRC can have negative effects if google returns outdated wisdom
13:34 vroom joined #pr-challenge
13:34 kentnl ( not in this case, but its a general precaution =) )
13:35 lbrown that's true, but IRC before googling can have negative effects if you look stupid ;)
13:36 jkg the only way to win is not to ... wait, wrong reference.
13:36 Su-Shee good morning everyone.
13:36 kentnl looking stupid now beats looking stupid later :D
13:37 lbrown reading changelogs never has negative effects though :)
13:39 kentnl that depends more on who wrote them. Sometimes you see somebody piped git log to their changes file and the negative effect is an anyeurism
13:42 lbrown you need to stop working with such badly maintained software
13:42 kentnl I wish I wasn't talking exclusively about cpan :/
13:44 kentnl some people do it ok and its not completely atrocious, if you have a really regimented commit schedule and a good formatter you can get away  with it. But its so easy to do wrong.
13:46 lbrown alright, I'm going in for the pull request...
13:46 kentnl me can't really talk though, I make up for detailed changelogs with atrocious code :D
13:47 lbrown you don't write atrocious code unless your files end in .php
13:47 lbrown https://github.com/stephenenelson/video-xine/pull/1
13:47 kentnl I have that as an historical black mark :(
13:48 kentnl and I have this uneasy feeling I may be forced to do it again one day.
13:48 lbrown I'm writing a few PHP scripts write now
13:48 lbrown It's quite fun really, just a license to write really crappy code.
13:49 kentnl next time I do PHP, I'll probably use a lot of this: http://phpqatools.org/
13:49 jkg I've heard unsubstantiated rumours that it's possible to write good PHP
13:49 pink_mist next time I do PHP, please just shoot me
13:50 kentnl Yeah. I hear rumours of this mythical place where if you get exactly the right set of base tools you might be able to have a non-wrist-slitting experience with it.
13:50 kentnl But I'd posit there's more perl developers and perl jobs than there are php developers who do that, and php jobs where you can apply that.
13:51 sue we have a guy at work who isn't a developer but tends to come over to talk to developers from time to time about PHP and he has no idea how much nobody cares
13:52 neilb joined #pr-challenge
13:54 lbrown do we not have ChanServ in here?
13:55 kentnl lbrown: http://www.php-fig.org/psr/psr-4/ # this site may also help in some regards for $php{suck}--
13:55 jkg this network has always been a bit anti-services, although they do exist now.
13:55 lbrown I have no idea what I just read
13:56 lbrown it looks cool though, so hopefully it makes some PHP people happy
13:56 kentnl lbrown: thats basically some framework interop standards so you can actually use code from different vendors without it exploding when they all decide to do autoloading differently.
13:57 kentnl ( because PHP was born without a sane component loading system )
13:57 lbrown kentnl: yeah, I have no idea what I'm doing when I'm writing php scripts
13:58 lbrown toss a coin: heads, I use 'include', tails I use 'require', then type the name of the file, and hope that it gets loaded properly
13:58 lbrown or just copy examples from github. it's worked for me so far
13:59 kentnl yeah, theres fun cases you get when you have 2 php files in different directories both exposed on apache urls and they both require the same libraries
13:59 kentnl because each get a different value of CWD, so each gets invoked with a different relative path for require ...
14:00 kentnl The number of times you'll see that if you're behaving yourself are rare, but when you hit it, you'll bleed black from your eyeballs
14:01 lbrown and, of course, all these scripts complain that they don't have the right modules, so I search my package manager, I try to use PEAR and I can't find them. Of course, I have them installed, but commented out in the config file!
14:02 kentnl lol. :(
14:03 lbrown I only use it for a few scripts to send email, though, because I don't want to kick up a fuss about having mod_perl installed
14:04 * kentnl instantly sees in his mind all the awful you have in your code
14:05 lbrown if ($verification != "{\n  \"success\": true\n}") { // use a JSON parser? pfft, no!
14:05 kentnl Earlier, when I was talking about "Things not to google for", I was going to offer a "web contact form perl"
14:05 lbrown This is how you verify reCAPTCHA, kids
14:05 jkg kentnl: great news! MSA is only the third result when I do that search.
14:06 kentnl jkg: the bad news is there's a later result showing people how to do things the wrong way, written *recently*
14:06 jkg although, the results above it may not be better :-)
14:06 jkg in fact, the bad news is pretty much everything about this page of results.
14:06 lbrown and then we wonder why people think perl is old and dying
14:07 kentnl he does say a lot of "Don't do it this way" , but that doesn't change the fact it doesn't show how to do it right.
14:10 kentnl lbrown: though you probably don't need mod_perl if you can poke either fastcgi or a reverse proxy to something like starman in :)
14:12 lbrown kentnl: yeah, but then I have to kick up a fuss about wanting to have starman installed
14:13 neilb_ joined #pr-challenge
14:13 kentnl <?php system("perl ... ? :p
14:14 rindolf joined #pr-challenge
14:14 pink_mist hehe
14:15 lbrown but then I'd have to ask for some module for sending email to be installed from CPAN
14:15 jrhunt you could do raw SMTP...
14:15 lbrown or just bite the bullet and write it in PHP
14:15 moritz pipe to sendmail :-)
14:16 jrhunt PHP - Perl -> shell?   I like it.
14:16 jrhunt polyglot...
14:16 pink_mist reminds me of that "quine" that translated itself between about 20 or so languages to get back where it started :P
14:17 kentnl Do you need permission to "install" PHP modules? ( IE: to copy paste them into your project dir ) ?
14:17 pink_mist https://github.com/mame/quine-relay <-- ah this is the one
14:17 kentnl If "no", https://getcomposer.org/ # Could help you make PHP suck less.
14:17 pink_mist damn, it's 100 languages 0_o
14:18 kentnl 100!?. Thats just showing off.
14:18 jkg pink_mist: 100! I remember it being 50, which was plenty crazy enough
14:19 pink_mist yep, seems they expanded it since then :P
14:19 jrhunt https://github.com/mame/quine-relay/blob/master/QR.rb
14:20 jrhunt and yet i hear no end of flak about how "Perl can be made in the shape of Camels!  ewww!" from ruby devs at work
14:20 * jrhunt files that url away for future 'discussions'
14:21 pink_mist hehe, glad I could help :P
14:22 SimonAW joined #pr-challenge
14:23 jrhunt neilb, did your selection algorithm take into account familiarity/proficiency with C for XS modules?
14:24 jrhunt or did i just get lucky (i was hoping to get an XS module, fwiw)
14:24 SimonAW Good day everyone.
14:28 sawyer SimonAW: good day :)
14:29 pink_mist jrhunt: I doubt it did -- he can't really know what everyone's profficient with =)
14:29 pink_mist jrhunt: if I get an XS module, I'll just need to really try to learn XS :P
14:29 jkg if I get an XS module, I'll be writing docs :-)
14:30 jrhunt i mentioned it in my intro email; wasn't sure if he was mining that data
14:30 jrhunt (or looking at github profiles)
14:31 haarg it seems like quite a few people got xs modules
14:31 neilb jkg++
14:32 neilb jrhunt: there’s no easy (quick) way to determine if a module is XS. Hoping to have that in place for feb :-)
14:32 jkg as it is, I got a module with a maintainer who has actively looked after it for over a decade, is still going strong, and ... well I've got a 2 line doc patch so far ;)
14:32 haarg xs dists seem rather prevalent on the adoption list
14:37 neilb haarg: not that surprising really.
14:37 neilb jkg++ (doc patches are code too)
14:37 jkg neilb: I'll admit I feel better because it's /example code in the docs/ that I've changed ;)
14:38 mvuets neilb: an idea for the next send - include month in a mail subject line
14:38 haarg xs dists tend to suffer more from a lack of maintenance, and have fewer contributors
14:40 isBEKaml joined #pr-challenge
14:41 isBEKaml Good evening, PRCs!
14:41 jkg People's Republics of China? :-)
14:42 isBEKaml PR Challengers. China works too! :-)
14:46 isBEKaml My assigned module is Log4Perl. Slowly working up to it now. Any ideas I can look at?
14:47 sawyer isBEKaml: look for Github issues, RT tickets, TODO files, "TODO" or "FIXME" comments in the code itself
14:47 isBEKaml sawyer: right. RT - next place to go :-)
14:47 sawyer look for code coverage (Devel::Cover), proper documentation, major Perl::Critic issues
14:47 * isBEKaml thanks sawyer for the op-ium
14:48 sawyer :)
14:48 isBEKaml sawyer: at first brush, log4perl looks pretty well documented
14:48 sawyer it should be
14:48 SimonAW So, yesterday I saw some lines flying by regarding creating a map with all participants in this PR. Is there any news on that?
14:48 sawyer SimonAW: _Dave was working on it, but we realized that it brought into light some information which people might not be comfortable with
14:48 sawyer so whatever is on Github will appear, but not coordinates, IIRC
14:49 sawyer isBEKaml: also, maybe look for questions people had on Stack Overflow/PerlMonks - might give you ideas for documentation clarifications
14:49 SimonAW Oh, OK
14:50 isBEKaml sawyer: good idea. log4(j,perl) etc have been pretty poor in terms of external documentation. As in, documentation not easily available (but have to buy for info)
14:50 jkg sawyer++ # great suggestions, I'd thought of maybe half of those
14:50 pink_mist yeah, that's a really good idea
14:50 SimonAW isBEKaml: 17 Bugs on rt.cpan.org
14:50 mib_33ppfc joined #pr-challenge
14:50 SimonAW Lucky you ;)
14:50 SimonAW I got B::Hooks::EndOfScope
14:50 SimonAW ONE single open bug
14:50 jkg have we a wiki? I might try to capture those suggestions, before they're buried in IRC scrollback
14:51 SimonAW On Windows
14:51 isBEKaml jkg: yes, we do. CPAN-PRC/wiki
14:51 isBEKaml I'll add these to the wiki
14:51 jkg isBEKaml: doh, should probably have found that :-)
14:51 jkg ok, great, I won't then :-)
14:51 isBEKaml sawyer: push bit, please? :-)
14:51 moritz SimonAW: you could always extend the documentation, or tests
14:52 moritz isBEKaml: what's your github ID?
14:52 isBEKaml sawyer: I'm svatsan on github
14:52 mib_33ppfc hello, i am an ultra-noob...i did git clone, git init, tried create pr, but it throws error: the term 'create' is not recognized as the name of a cmdlet, function, etc...
14:52 isBEKaml moritz: ^^ svatsan on GH
14:52 SimonAW moritz: Tests are already quite exhaustive, Devel::Cover @ 94%
14:53 SimonAW moritz: This module has one single feature: Execute code at scope end.
14:53 moritz isBEKaml: invited
14:54 neilb 94 < 100!
14:54 neilb :-p
14:54 SimonAW neilb: Yes ;)
14:55 moritz mib_33ppfc: https://github.com/CPAN-PRC/resources/wiki/My-first-Pull-Request
14:56 moritz mib_33ppfc: short: on the git command line, you can create a branch, commit, and push; you have to create the pull request in the github web interface
14:56 moritz afk
14:56 isBEKaml moritz: thanks
14:57 mib_33ppfc read that...what is the order of operations, maybe i'm just retarded, but i can't create a pull request on the web interface because i want to compare master with master and there are no changes...i need to create my own branch first?
14:57 SimonAW neilb: Do you happen to know if Karen is checking her mails?
14:58 daveh jrhunt: i got an XS module. I'm assuming the C is just binding code
14:59 daveh heh, google thinks Toronto, ON, CA is in California
14:59 jrhunt daveh: which module?
14:59 daveh a crypto one
15:00 isBEKaml daveh: CA is California, you know? :P
15:00 jrhunt daveh: were you _Dave yesterday?
15:00 jrhunt lol
15:00 _Dave yes :)
15:00 jrhunt you got the RSA mod, right?
15:00 _Dave i think so
15:01 _Dave docs, critic, test coverage - that's a good start for hygeine anyhow. it's the stuff coders tend to ignore.
15:01 thrig lack of buffer overflows, etc
15:01 _Dave i got Crypt-OpenSSL-RSA BTW apparently
15:02 jrhunt yeah, that's going to be mostly binding code to OpenSSL, although it looks like there are a few helper functions in pure C that go above an beyond
15:03 thrig because OpenSSL needs helper functions (see the libressl folks, I think they're working on a new API since nobody does verifies the same or at all)
15:04 jrhunt "because OpenSSL needs help"<--- you can stop there ^_^
15:05 thrig http://www.openbsd.org/papers/eurobsdcon2014-libressl.html
15:05 chady joined #pr-challenge
15:06 neilb spent 4 hours driving home, to find blocked drains, madly baking for visitors coming later. Then relax and process all of today’s signups!
15:06 chady hello all
15:07 neilb o/
15:07 ribasushi SimonAW: she certainly is, but she is on PST
15:09 chady so I've been so far from the Perl community for so long, I have no actual idea what my assigned module is about :P
15:11 daveh joined #pr-challenge
15:11 daveh boing
15:12 jrhunt chady: what did you get?
15:12 SimonAW > perlcritic --brutal . | wc -l
15:12 SimonAW 253
15:12 SimonAW $hell->unleashed();
15:12 sawyer moritz: created "contributors" on the gh org
15:12 sawyer write permission
15:13 daveh SimonAW: -3 is good enough. then it gets silly
15:13 chady jrhunt: MooX::Types::MooseLike
15:13 sawyer SimonAW: "--brutal" is a bit overboard :)
15:13 daveh neilb: can we standardise on a perlcriticrc?
15:13 SimonAW daveh, sawyer: In anticipated that... ;)
15:14 daveh what?
15:14 ribasushi daveh: I wouldn't touch perlcritic unless a distribution already has a critic-config in its repo
15:14 jrhunt chady: are you familiar with Moose at all?
15:14 raisin joined #pr-challenge
15:14 daveh ribasushi: to me it's indicative of kwalitee
15:15 ribasushi daveh: a lot of critic rules are very subjective, and hence will invite much bikeshedding with little gain
15:15 jrhunt ribasushi++
15:15 daveh that's why we want a pgramatic rc
15:15 raisin i am going to ask a series of dumb questions, thanks in advance for your patience...
15:15 daveh and i've been there, in several companies
15:16 thrig ribasushi: two-arg opens and such might be handy to look for, though
15:16 daveh returning undef
15:16 ribasushi thrig: hence why I said "a lot" not "all" ;)
15:17 raisin so, i want to make a pull request...the noob tutorial talks about creating my own repo and then making a pull request of someone else...why can't i make a pull request of someone else regardless of whether i have my own repo, i mean, shouldn't a pull request automate that for me, e.g. make a copy of their stuff under my account and then track changes?
15:17 ribasushi daveh: see - now "return undef" *is* valid API when you need exactly that (QED ;)
15:17 rjbs I am looking forward to CPANPRC pull requests, but if they end up just being a bunch of "follow PBP guidelines," I'm gonna plotz.
15:17 neilb yeah, I wanna build up a list of such things (like indirect method notation) that no-one can disagree with, and use those to find dists to assign, and tell people about them in the email they get
15:17 daveh ribasushi: and most often don't
15:17 neilb but focus on value
15:18 ribasushi daveh: as neilb said - it can only be a list of "no one can disagree with" things, and there is precious little of these
15:18 daveh i can live with that
15:18 daveh i've been in places where critic has saved the day
15:18 sawyer i agree with ribasushi on the general idea of perl critic
15:18 daveh a single rule no-one cares about?
15:18 sawyer i have my own which lets me check for stuff that *i* find important, and i might submit fixes for some ("strict"/"warnings", etc.) but generally, i wouldn't just throw perlcritic on someone
15:19 SimonAW ribasushi: "bikeshedding"... nice one (thanks, urbandictionary ;)
15:19 sawyer i think it's a good idea to have your own Perl::Critic and get some ideas from it on possible stuff you'd like to send a PR for
15:19 ribasushi raisin: if you are working directly with the github in-browser editor - this is indeed the case (it will fork for you, behaving exactly as you described)
15:20 ribasushi raisin: the problem with doing that is that you can't test the PR you are sending - generally authors expect that contributions will pass at least some "does it compile" check, which often is `prove -lr t`
15:20 sawyer raisin: when you press "fork", it makes a copy of it on Github
15:20 sawyer but you can't code ON github, you need to code locally
15:20 sawyer so you clone locally
15:20 sawyer if you don't have write permissions to the original repo (which you probably don't), cloning that one won't help :)
15:20 oeuftete joined #pr-challenge
15:20 sawyer because you won't be able to push your changes to it
15:20 daveh you can push to clones, no?
15:21 daveh or a branched clone
15:21 sawyer so you need to create a github copy, then a local copy, then push from the local copy to the github one, then issue a pull request from the github one to the original one (on github)
15:21 raisin so i am choosing base branch of master and i need to compare it against another branch in order to create a pull request, and i guess that is my question...i would expect the pull request to create a self-owned branch
15:22 raisin ok...so i guess i'll try forking, although i feel like i should be able to edit the main branch, and let the owner choose to accept or reject my changes
15:22 sawyer raisin: i'm not sure i understand your question, can you try and rephrase? or give an example?
15:22 sawyer you're talking about both cloning and a branch - two different things
15:23 daveh raisin, what sawyer just said
15:23 isBEKaml Added some notes on PR Ideas. eyeballs appreciated https://github.com/CPAN-PRC/resources/wiki
15:24 raisin hopefully i don't annoy the owner of this cpan module, but i'm a noob and i'm just trying to learn github...so i'm going to add a hello world to his branch, commit it, and let him reject it as a nonvaluable addition, meanwhile i gain knowledge of how github works
15:24 sawyer isBEKaml++ !
15:25 cary-elvis joined #pr-challenge
15:25 raisin so i feel like i should have to have my own fork which is his code plus my hello world statement, it should just be inline with his own branch and maybe show a history that he rejected my hello world statement...no?
15:25 jkg cary-elvis: o/
15:25 sawyer raisin: let's sort some stuff out
15:25 cary-elvis jkg: hi there
15:25 raisin yes, please
15:25 raisin let's
15:25 Relequestual joined #pr-challenge
15:25 isBEKaml I couldn't push directly to the wiki using git CLI (get a 403 error) Has anyone seen this before?
15:26 sawyer first of all, you can submit pull request in two situations: 1. you have a write access to a repository (the original one), 2. you have a fork of it on github
15:26 Relequestual hey =]
15:26 sawyer raisin: so, you must have a write access to some github repo
15:26 Relequestual signed up today. Should be interesting...
15:26 sawyer because when you ask github to make a pull request, it will need you to have the authority (write access) to do it
15:27 sawyer now, i'm assuming the author did not provide you with a write access to their repo... right?
15:27 raisin correct
15:28 sawyer right, so at least we know you need to fork
15:28 raisin so now i have my fork...i clone my own fork locally to edit or i check it out?
15:28 neilb rjbs: the first version of my assignment was ready to hand out load of your dists, but I changed it so for this month at least, each author should only be “hit” once
15:28 Relequestual I thought you need to fork to make a pull request anyway?
15:28 sawyer Relequestual: not if you have write access on the original repo
15:29 sawyer raisin: so you have your fork on github, let's continue from there
15:29 sawyer you want to add a piece of code (say, "hello world" example)
15:29 raisin yes, fork on github
15:29 sawyer yeah
15:29 sawyer so what editor are you going to write it in? how are you going to commit it?
15:29 mgprot joined #pr-challenge
15:30 sawyer the fact that there's a fork on the github server doesn't help you very much :)
15:30 raisin git cli, edit it locally, then git cli to push/commit...
15:30 sawyer raisin: exactly!
15:30 sawyer so you make another copy (yup, another copy) locally
15:30 mstr joined #pr-challenge
15:30 sawyer so you clone it with git cli
15:30 raisin so walk me through...git checkout, git push, then pull request via ui which moves my version on the web to the owner's version on the web?
15:30 sawyer no no
15:31 sawyer let's go from the top, slowly
15:31 sawyer 1. go to the repo, 2. press "fork"
15:31 sawyer 3. go to your fork (which should happen automatically when you finish the "fork" operation)
15:31 sawyer 4. find the text box on the right with the link to the repo itself
15:31 sawyer 5. "git clone https://github.com/myusername/repo-name.git"
15:32 sawyer that will create a local copy (which in git terms is called "a clone" - hence the command)
15:32 sawyer so far so good?
15:33 raisin yeah, i got that and i made my edit, then i do git init so it has a .git file, and git push to update my own repo, yes?
15:33 thrig 0. recall that github password is on laptop at home
15:33 StylusEater joined #pr-challenge
15:34 jkg thrig: every. goddamn. time.
15:34 StylusEater greetings
15:34 sawyer you only run "git init" if you're creating a repo from scratch - when you do "git clone" you should have the .git directory there
15:35 sawyer raisin: how about you describe to me every step you made
15:36 sawyer because i'm not sure how you got to run "git init"
15:36 sawyer this is a command you will not have to run even once throughout the PR challenge
15:36 neilb probably
15:36 thrig ... well, unless $bad_code inspires $new_module
15:37 sawyer thrig: in which it's not part of the PR challenge :)
15:38 thrig hmm, what if you got a module that is "the legacy interface"?
15:39 sawyer what do you mean?
15:39 raisin ok, so i forked it, i did a clone of my fork, then i added a hello world to a random if statement, did a git push from my local clone, that said it succeeded / everything up-to-date, but i don't see my hello world statement on the web ui under my fork
15:39 sawyer raisin: ah okay good!
15:39 thrig "Note: This is the legacy interface, please check out Net::Amazon::S3::Client instead."
15:39 sawyer thrig: take a look at the reverse dependency
15:40 sawyer thrig: it should help you decide who uses it and how important it is
15:40 sawyer if there are other distribution using it, it might be very important to fix some bugs
15:40 sawyer raisin: when you go to the github page, it should say something like "oh hey, you just pushed a new branch"
15:40 sawyer did you do the change in a branch or in the "master" branch?
15:41 sawyer in any case, whether you made that commit in a special branch or in the master branch, you should see the message shown here: https://help.github.com/assets/images/help/pull_requests/pull-request-review-page.png
15:42 sawyer sorry, you'll see it after you press this button: https://help.github.com/assets/images/help/pull_requests/pull-request-start-review-button.png
15:43 raisin uhh...so i have to make a pull request of my own fork after i already edited it?
15:43 raisin it says there is nothing to compare
15:43 sawyer raisin: the pull request is to send a request to the original author to ask them to pull in your changes
15:44 sawyer could you paste the link to your repo?
15:45 raisin https://github.com/cpeftw/Path-Class
15:46 raisin git push seems to do nothing, i added hello world as a comment and hello world as a random print inside a random if statement
15:46 raisin no change in the web ui, although git push says everything up to date
15:46 sawyer the latest change in your fork is not yours, it's ken's change from two weeks ago
15:46 sawyer so you basically don't have new commits on your github fork - let's find out why :)
15:47 raisin right, so obviously git push is not working
15:47 cary-elvis raisin: did you make a commit before pushing?
15:47 sawyer raisin: perhaps, let's find out
15:47 raisin no...i just saved the modified file locally...
15:47 sawyer raisin: then that's why
15:47 sawyer you need commit the change in order to insert it into git
15:47 sawyer that's how git knows about changes
15:48 sawyer did you read this part of the guide? https://github.com/CPAN-PRC/resources/wiki/My-first-Pull-Request#committing-to-commit :)
15:48 sawyer clearly i had missed the part where i say "you run git commit to open the editor and write your commit message" :)
15:48 sawyer sawyer--
15:49 raisin ok, it would be nice if that part actually had an example, though, e.g. git-comment -flag "my commit message"
15:49 daveh ....if you have $EDITOR set
15:49 daveh git commit -m"comment" also works
15:49 Relequestual maybe someone could make a pull request on this... ;)
15:50 daveh is it worth setting up a separate remedial class for beginners?
15:52 sawyer raisin: i just edited the guide to include that
15:52 raisin it says my branch is up to date with origin/master and changes not staged for commit is the file that i edited
15:53 sawyer raisin: what do you see when you run "git status" in your repo directory?
15:53 sawyer you can paste it at http://pastebin.com or something
15:54 cary-elvis you need to add the modification also. either git add modified_file or git commit -a
15:55 raisin ok, so i'm good now...this is fun...i guess i just need git add, git commit, git push...
15:56 raisin for the learning impaired, this seems like it should all be one step, why would i need to separately add, i made the change so yeah i want to commit it, and then commit and push i suppose also seem like one motion...but now i know, and knowing is half the battle
15:56 sawyer raisin: yes, "git add FILES; git commit; git push"
15:56 sawyer i've revised the guide to explain that
15:57 Relequestual raisin you may want to push only some changes
15:57 sawyer raisin: per your question on multiple steps: there is a shortcut in git for it, but it will, for now, add to your confusion
15:57 sawyer once you're familiar with add -> commit -> push, you could learn the shortcuts :)
15:57 ptc raisin: you often want to make more than one commit before you push.
15:57 Relequestual that too!
15:58 ptc this is a great thing about git: it's possible to work offline and then push changes a soon as one has internet access again
15:58 isBEKaml sawyer: moritz: seems like I was added to contributors team with no repositories to commit to on CPAN-PRC org. Perhaps that's why I couldn't push from CLI...
15:58 sawyer isBEKaml: let me see
15:58 * thrig mentions http://justinhileman.info/article/git-pretty/full/
15:58 ptc pushing is seen as publishing your commits, so this is something one doesn't do as often as commiting
15:59 sawyer isBEKaml: my bad, fixed!
15:59 isBEKaml sawyer: awesome!
15:59 sawyer raisin: also what ptc just said :)
15:59 sawyer isBEKaml: NP :)
16:00 sawyer raisin: you successfully pushed your change :)
16:00 Relequestual wooo!
16:00 sawyer when you pick "submit pull request", if you want the author to ignore it, you can just write it in the description
16:00 sawyer BUT, they might still get a little annoyed that you opened a pull request for no reason
16:00 sawyer you can also close it yourself
16:01 sawyer it will, however, survive forever in the repo's pull request history
16:01 sawyer you will also now have a local branch which has a commit that needs to be deleted, because it's useless
16:01 sawyer (that's one reason to do stuff like that in branches, not in "master")
16:02 sawyer raisin: https://github.com/kenahoo/Path-Class/pull/38 - you submitted it
16:02 sawyer and you can also close it yourself
16:05 mstr i would have a question too-- i forked a repo. i want to make some changes. some of them i want to get into upstream, some of them are my pure private pleasure (since i'm gonna use it myself only). how would i do this? my guess is:
16:05 mstr fork. make a branch for every change i want done.
16:06 jkg well, you can do it in fewer branches than "one per change", but that is the crux of it, yes.
16:06 sawyer mstr: my answer will depend on your answer to this question: what kind of changes are you making for your "pure personal pleasure"? :)
16:07 mstr i forked a pelican blog theme. some changes are of common interest (new feature, bug fix) some are because i want my blog to look exactly like that. others won't care for that change.
16:07 sawyer mstr: you can maintain your own branch of your changes
16:08 sawyer you will have to make sure you keep it up-to-date with the changes in the pelican upstream
16:08 sawyer which is where "git rebase" comes in
16:08 mstr as i didn't know anything about github when i started i made all changes in the master branch. now i cannot send PR for certain commits only. i guess i will have to start over.
16:09 sawyer mstr: not necessarily
16:09 ptc mstr: have you pushed the changes to your github fork?
16:09 mstr yes. all is up there already.
16:09 sawyer ptc: that won't matter either with enough git foo :)
16:09 sawyer mstr: is it in separate commits or one big commit?
16:10 mstr separate commits
16:10 sawyer can you say "these commits yes, those commits no" ?
16:10 mstr yes
16:10 mstr and every commit is perfectly clean within itself
16:10 ptc sawyer: I was thinking of moving the commits between branches before pushing...
16:11 sawyer so, in theory (the practice i can't explain now because i gotta pee, merge a PR on Dancer2 and head home) is creating clean branches, cherry-picking the relevant commits, then resetting the master branch back and then force pushing it to github
16:11 sawyer ptc: yup
16:11 mstr so create a branch, revert all my commits, cherry pick one commit from the master branch and push followed by PR?
16:11 sawyer no, it's cleaner than that
16:11 sawyer i'll describe the steps when i'm back from peeing, okay? :)
16:11 sawyer brb
16:11 mstr sure
16:12 ribasushi sawyer: UNACCEPTABLE!
16:12 ptc hehe
16:12 ptc $sawyer->go('pee');
16:12 ribasushi I think that code can cause a leak...
16:12 mstr but considering that i could just start over my question is rgd. how it should be done cleanly from beginning on.
16:13 ptc mstr: generally one can separate different threads of development into different branches
16:13 mstr would i create a branch from a clean master for each change i want to PR later on - plus having one "private" branch where i merge all changes of the PR-branches into so i can use that private branch for my blog?
16:14 ptc yup, that sounds good
16:14 sawyer mstr: first you'll need to find the parent of the first commit you made
16:14 sawyer that is, the last commit *before* you started committing
16:14 mstr yeah
16:15 sawyer then you create a new branch from that commit (git checkout -b fix/foo abcd889)
16:15 sawyer you then cherry-pick the commits that are relevant to that branch
16:15 StylusEater are we just opening a ticket in github asking the maintainer if they need help with something in particular?
16:15 * jkg plans to email the maintainer direct about that.
16:15 sawyer you keep doing that (opening a branch from that commit, cherry-picking commits on it) for any PR you want to serve and once again for your local changes
16:16 sawyer StylusEater: that's not how you usually do it
16:16 daveh jkg: i've emailed several to no avail so far...
16:16 sawyer you can email them or find them on IRC
16:16 sawyer but it's best to look at these first: https://github.com/CPAN-PRC/resources/wiki/Pull-Request-Ideas
16:17 sawyer mstr: then, once all the commits from master are on some branch (which should have started from the last commit *before* you made any commits), you can go back to master and reset it to that commit
16:17 jkg daveh: about the PR challenge?
16:17 sawyer this means that your master is back to where it was before you committed and your commits are on proper branches
16:17 daveh arr
16:17 sawyer then you can sync github with it by pushing force
16:17 daveh jkg: let's see next week when people might be back at work
16:17 sawyer this is a delicate process (should take about a minute or two tops if you know what you're doing) and could yield damage if you don't :)
16:18 StylusEater @sawyer ... got it
16:18 sawyer so i'm explaining the theory, but also, take this warning to heart: if you do it wrong, you lose data :)
16:18 mstr :)
16:18 ptc sawyer: that's why I was going to avoid git push --force earlier :-)
16:18 sawyer my first few times i simply made a patch, killed the repo, forked it again and applied the patch
16:18 sawyer it was wayyyy easier for me than to worry about screwing up, until i understood the process and how it works
16:19 ptc practice makes perfect :-)
16:19 Relequestual interesting to know =] thanks for sharing sawyer
16:19 mstr i get that. luckily nobody cares for my forked repo so i can just start over and do it right.
16:19 sawyer Relequestual: NP :)
16:19 Relequestual it's easy to forget there was a time before you understood stuff like that =]
16:19 Relequestual I probably cheated, in that I a GUI
16:19 sawyer mstr: i've done that plenty of times when i started :)
16:19 Relequestual use*
16:19 daveh jkg: and in a cloud of smoke...I just got mail!
16:20 daveh gonna read Rankin now. Or watch TNG
16:20 daveh fuck Javascript
16:20 mstr thanks for the help!
16:20 Relequestual TNG! =D
16:20 daveh at least I've made a little progress
16:20 isBEKaml ah yeah
16:21 isBEKaml I got something else to do first before hitting the logger doldrums. github gists are blocked. So gotta hit up those APIs....
16:21 daveh WTF is a gist?
16:21 sawyer daveh: gist.github.com
16:22 isBEKaml gist, you know.. it's a gist
16:22 daveh pastebin, basically
16:22 daveh versioned
16:22 daveh that's cute
16:22 thrig Gist vs. the Gazebo
16:22 daveh i also don't know that :)
16:26 daveh does someone want to spam the perl groups on Linkedin?
16:29 rindolf neilb: here?
16:30 neilb ish
16:30 rindolf neilb: OK.
16:30 neilb 'sup?
16:30 rindolf neilb: I want to join the Google Group.
16:30 * daveh &
16:30 rindolf neilb: but I didn't get the acknowledgement.
16:31 daveh rindolf: little of substance there
16:31 rindolf daveh: what?
16:31 neilb I didn’t get any request
16:31 neilb what’s your email and i’ll send an invite
16:31 rindolf neilb: hmmmm... I sent one.
16:31 rindolf neilb: my email is shlomif@shlomifish.org and you told me I opted out of invites.
16:33 ben joined #pr-challenge
16:33 rindolf neilb: ah , I see I'm subscribed as shlomifish.org@gmail.com
16:34 daveh sawyer: possibly worth adding your git process to the docs
16:34 rindolf OK, I set it to shlomif@shlomifish.org - thanks.
16:36 neilb rindolf: you’ve opted out of invites to groups :-p
16:36 rindolf neilb: ah, don't remember why I did so.
16:36 rindolf neilb: that's OK - I sorted out the problem.
16:36 sawyer daveh: i think that's a very specific situation i wouldn't try beginners to even try
16:36 sawyer risky unless you understand it
16:39 ribasushi daveh: what sawyer said, most advanced git usage is very "personal". For instance I wouldn't expect anyone to work the way I do, while at the same time I can't work any other way: http://paste.debian.net/plain/78121
16:40 rjbs the joy of git: nobody knows what steps you took before you pushed
16:40 ribasushi in essence I take ptc's "pushing is seen as publishing" a very long way ;)
16:41 isBEKaml ribasushi: wow, that's a lot of rebasing.
16:41 neilb “I wouldn't expect anyone to work the way I do” — RIBASUSHI
16:41 ribasushi isBEKaml: looking at one's reflog is always entertaining ;)
16:42 sawyer neilb: and you can take that to the bank!
16:43 isBEKaml ribasushi: it sure is - now we can all use that as a productivity rubric ;-)
16:44 ribasushi isBEKaml: it's also a good idea to set (in your global git config) `gc.auto=0`
16:44 isBEKaml ribasushi: stuff like this, especially - 'checkout: moving from fuckforward to master'
16:44 ribasushi this way the history stays with you unless you lose the repo
16:45 sawyer *gasp* gc.auto=0
16:47 isBEKaml ribasushi: wouldn't that just cause all repo sizes to explode?
16:47 jkg disk space is ever so cheap.
16:48 ribasushi isBEKaml: http://paste.scsys.co.uk/453367
16:48 ribasushi hardly
16:50 ribasushi I mean compare to a standard `top` output these days: http://paste.scsys.co.uk/453368
16:50 ribasushi .oO( web browsers suck these days )
16:51 ptc mate, aint that the truth!
16:52 thrig 5323 jmates     3    0 3628K 6120K idle      ttyin     0:00  0.00% lynx
16:52 isBEKaml chromium, you pig
16:53 isBEKaml ribasushi: I'm reading this page and it tells me it's all for space optimization. https://www.kernel.org/pub/software/scm/git/docs/git-gc.html
16:54 ribasushi isBEKaml: you missed "Prune loose objects older than date (default is 2 weeks ago, overridable by the config variable gc.pruneExpire). This option is on by default."
16:54 isBEKaml ribasushi: from what you say, I'm guessing it's all relative and doesn't vary very much either.
16:55 isBEKaml ribasushi: ah
16:55 ribasushi isBEKaml: also "he optional configuration variable gc.reflogExpire can be set to indicate how long historical entries within each branch’s reflog should remain available in this repository...It defaults to 90 days"
16:55 ribasushi but since I don't run gc at all - none of the fine tuning knobs matter
16:56 ribasushi (also this is far offtopic at this point ;)
16:56 vairav joined #pr-challenge
16:56 isBEKaml ribasushi: right, I better get back to pulling files from gists. :-)
17:21 vroom joined #pr-challenge
17:25 daveh 0519790 HEAD@{Wed, 15 Jan 2014 16:21:06 +0100}: rebase -i (pick): fuckme
17:26 daveh i've never had the need to rebase
17:26 daveh 41f699f HEAD@{Wed, 15 Jan 2014 14:35:50 +0100}: commit: argh
17:31 isBEKaml joined #pr-challenge
17:56 dfluck joined #pr-challenge
18:00 diocles joined #pr-challenge
18:24 LLamaRider joined #pr-challenge
18:31 neilb I suggest that discussions related to “doing pull requests” go on here, and meta discussion about the challenge happen in #prc-dev
18:33 diocles joined #pr-challenge
18:38 dfluck joined #pr-challenge
18:45 isBEKaml night time here, folks. g'night!
18:46 tinypig joined #pr-challenge
18:49 ether I saw someone got one of my dists as an assignment. not sure if they are here right now, but FYI I am still on holidays so not really around until next week
18:50 ether also -- if the list of assignments were public that would be awesome, as if I have any TODO items in mind for any of those dists I would happily create an RT ticket for them, so the challenger can use that as a possible thing to work on
18:51 ether (and yes, I'm on UTC-0800, which is not terribly convenient for most people.) :D
18:58 thrig I'm on UTC, local timezone be damned
19:07 diocles joined #pr-challenge
19:13 moritz +1 on making assignment lists public
19:13 mwhisenhunt joined #pr-challenge
19:15 rjbs yes, +1
19:15 lejeunerenard +1 as well
19:15 jrhunt ^^
19:15 moritz I'll ask on the mailing list
19:17 kentnl would be nice, that way I can donate a box of tissues and to the bereaved family of anyone neilb has assigned one of my dists to.
19:17 * kentnl hopes he's not that cruel
19:18 ether :D
19:19 BHS_error eheh
19:19 BHS_error moritz: +1 on making the assignments public
19:19 dfluck +1
19:20 LLamaRider +1
19:22 sawyer +1 (as long as a person is okay with it)
19:22 sawyer i wouldn't just share this automatically
19:23 pink_mist agreed to that
19:23 ptc agreed to that
19:23 sawyer in the future it should just be a field, like "do you opposite your participation and assignments made public?" (yes/no)
19:24 sawyer (and don't get me wrong, i'd be thrilled if everyone made it public)
19:24 kentnl at very least, if not public, then a/the maintainer of the distribution in question may want to be notified in advance somehow of pending interactions
19:25 adelq joined #pr-challenge
19:25 sawyer in the future, an email could be sent to authors saying "X has been assigned your project"
19:25 kentnl would be a good place for author to contact X with anything they need doing/pointers/etc.
19:25 kentnl Serfs. More Serfs!
19:26 lbrown I'm a bit late here, but +1 for that :P
19:28 mstr joined #pr-challenge
19:31 ether is there something in place to prevent the same author being given out twice in one month?
19:32 ether not sure how likely that is to happen.. how big was the pool of dists?
19:32 sawyer ether: this is tricky because it's based on the latest releaser, i think
19:32 ether *nod*
19:32 sawyer ether: which puts you in more than half of the pool of modules :)
19:32 ether the stats could be grouped by user/org in the github repo
19:32 ether since "has a github repo" is one of the main criteria
19:32 sawyer not a bad idea
19:33 ether and then I wonder if any org-based dists were handed out this month
19:33 sawyer neil is in charge of that
19:34 adelq joined #pr-challenge
19:54 dfluck joined #pr-challenge
19:56 shmoo joined #pr-challenge
20:27 vairav joined #pr-challenge
20:31 diocles joined #pr-challenge
20:42 mulander joined #pr-challenge
20:42 mulander hi all
20:43 mulander did anyone else get mail delivery errors while trying to register via email with Neil?
20:43 raisin no
20:43 popl Has everyone gotten an assignment?
20:44 mulander I just got "Your message could not be delivered for more than 6 hour(s).
20:44 mulander It will be retried until it is 1 day(s) old." 69.64.147.249]:25: Connection
20:44 mulander timed out from my mail agent
20:44 mulander trying to decide if I should wait or sent from a different mailbox
20:44 popl mulander: Did you verify that you're sending it to the correct address?
20:45 mulander jesus, not sending any more email on new years :D
20:45 mulander popl: yep looks like an email typo
20:45 popl don't drink before sending email. ;)
20:45 mulander ^ good advice
20:46 mulander though I guess there's a fail safe if you can't type the correct email address ;)
20:46 popl yeah, you'd luck out there.
20:48 mulander are the submissions manually processed or should I expect a snappy reply from a bot?
20:49 popl neilb is handling it afaik
20:49 mulander thx
20:56 dfluck So... if I'm trying to get in touch with the maintainer of a module, I'm guessing a GitHub issue is the best way to do it?
20:56 popl dfluck: traditionally, RT or emailing them.
20:57 popl IIRC neilb wrote a blog about etiquette.
20:57 popl let me find it
20:57 dfluck This one? http://neilb.org/2014/12/31/pr-etiquette.html
20:57 popl yes, does that cover contacting authors?
20:58 popl s/,/;/
20:58 dfluck Oh, there it is.
20:59 popl my brain is a sieve; I could be referring to something else and misremembering.
21:00 dfluck It does say to open a ticket for potential changes.
21:07 adelq joined #pr-challenge
21:11 choroba joined #pr-challenge
21:34 adelq joined #pr-challenge
21:41 sue joined #pr-challenge
21:48 vairav joined #pr-challenge
22:07 LLamaRider joined #pr-challenge
22:19 vroom joined #pr-challenge
22:20 sawyer i think i finally have an idea of what to contribute
22:21 popl Did neilb email individual project assignments, then?
22:21 * thrig is pondering adding instructions on how to build it, seeing as the one I got seems to use Dist::Zilla
22:22 BRAD joined #pr-challenge
22:22 popl Or rather, did his script? :)
22:27 adelq joined #pr-challenge
22:36 popl Hey, can someone tell me how they were notified of their assigned distribution?
22:36 thrig homeless dude on the bench outside allego cafe
22:36 popl s/of/about/
22:37 jrhunt popl: i got an email from neilb
22:37 popl okay
22:37 popl thank you
22:38 popl I was scouring the Google group and couldn't find anything.
22:39 popl thrig: how's granddad doing?
22:39 choroba I got the assignment when the first three PR had already been created
23:02 blg joined #pr-challenge
23:13 vairav joined #pr-challenge
23:14 bjakubski joined #pr-challenge
23:20 bjakubski http://miburl.com/Umm8P3
23:20 nbezzala joined #pr-challenge
23:22 bjakubski But I don't think we can/should do anything other than reminding everyone that in PR etiquette first point was "be polite"
23:26 Mithaldu bjakubski: i strongly recommend using something better than mibbit
23:26 Mithaldu anything is better really
23:26 Mithaldu that link for example you posted was broken by the mibbit link shortener
23:30 bjakubski yeah, sorry about that. shortening urls is still part of IRC etiquette?
23:31 Mithaldu i haven't seen that ever been etiquette anywhere and don't know honestly
23:31 Mithaldu mibbit just does it, maybe because it helps them track stuff
23:33 bjakubski I actually explicitely clicked "Minify URL", and pasted resulting link
23:33 Mithaldu and to be clear: i'm not pointing out the shortening, it's just an example for why mibbit is less good than all other offers
23:33 Mithaldu oh well then
23:35 bjakubski https://twitter.com/miyagawa/status/551153001138647040
23:37 bjakubski I don't know what MR miyagawa is talking about, but everybody please remember to be polite
23:38 bjakubski author can always be busy or gone or not interested in merge requests
23:38 Mithaldu i'm not volunteering for this because i've plenty busy, but i recommend asking miyagawa if the problem is handled or whether neil should talk to someone
23:39 vroom joined #pr-challenge
23:39 bjakubski and the challenge is to *create* merge requests, not to get them in
23:40 vroom joined #pr-challenge
23:51 neilb joined #pr-challenge
23:55 neilb ether: yeah, working on that. Need to make sure everyone’s happy for that to be shared. I’ve had some people say that they don’t want their details shared. But anything which faciltates others helping would be good, I reckon.

| Channels | #pr-challenge index | Today | | Search | Google Search | Plain-Text | summary