<|> [Pasting today's meeting; times are EST (UTC-0500)] <|> 03:15:23 -!- Tweety [~robert@x3.develooper.com] has quit [Ping timeout: 180 seconds] <|> 04:32:28 < spinclad> [ENOTWEETY !] <|> 09:27:00 * mugwump looks strangely satisfied and belches, a feather floats to the floor <|> 09:28:13 < Nicholas> OMG he ate tweety <|> 12:08:02 -!- smash [~smash@gil.di.uminho.pt] has joined #parrotsketch <|> 12:08:26 < smash> greetings <|> 12:08:30 < smash> no bird <|> 12:52:53 < obra> I've poked robrt nd asked him to reply <|> 12:52:58 < obra> er. restart <|> 13:02:36 < smash> cool <|> 13:28:11 -!- chromatic [~chromatic@63.105.17.30] has joined #parrotsketch <|> 13:28:36 < obra> ey chromatic <|> 13:28:44 < chromatic> Morning/afternoon. <|> 13:29:03 < particle> hey there <|> 13:29:18 < chromatic> Are you going to Ignite! tonight, particle? <|> 13:29:25 < leo_> hi all <|> 13:30:07 < particle> leo! <|> 13:31:16 -!- bernhard [~bernhard@p549A1A14.dip0.t-ipconnect.de] has joined #parrotsketch <|> 13:33:20 < obra> we'll give folks a couple more minutes <|> 13:34:09 < smash> no ops for topic ? <|> 13:34:35 < obra> nope. <|> 13:35:35 -!- allison_ [~allison@sub17-30.member.dsl-only.net] has joined #parrotsketch <|> 13:35:51 < obra> hey allison <|> 13:36:10 < allison_> hi <|> 13:36:19 < obra> anyone know if patrick is likely to join us today? <|> 13:36:38 -!- allison_ is now known as allison <|> 13:37:02 < particle> just spoke to him, he won't make it <|> 13:37:11 < obra> ok. thanks <|> 13:37:32 < obra> let's get going, then. chromatic, paicle, leo, allison, me <|> 13:37:55 < obra> sorry. I'm on slightly laggy net from madrid. But at least i'm here this week <|> 13:38:07 < chromatic> Not much to report here. particle started porting my PBC bundler to PIR and I managed to get it working in pure-PIR such that it can bootstrap itself. <|> 13:38:36 < chromatic> I have an idea for a variant of Ponie that might work out, but I want to write a little more code first to see how it does. <|> 13:39:01 < chromatic> I'll announce the bug day tomorrow on ORN unless someone else beats me to it. Otherwise, spread the word. <|> 13:39:05 < chromatic> That's all. <|> 13:39:34 < particle> ~ contacted tim bunce about dbi 2 on parrot. he's responded that implementation hasn't started yet, and will likely begin on pugs, where perl 5 bridging to JDBI is available. a parrot level api def is an early goal <|> 13:39:51 < particle> ~ answered questions from kjs++, who has now gotten languages/PIR/ to output some PIR (PIR -> parse -> PAST -> POST -> PIR)! <|> 13:40:02 < particle> ~ started coding io pmcs in c, but the api is difficult to implement. switching to pir implementation for coding ease <|> 13:40:16 < particle> ~ began reviewing ops2pm coverage testing on 'buildtools' branch by kid51++. will provide feedback this week. hopefully this can be merged with trunk pre-release <|> 13:40:31 < particle> ~ *lots* of reading this past week due to jury duty. great articles on io, stm, iterators, compiler construction, parsing techniques, etc. (acm digital library)++ <|> 13:40:44 < particle> ~ currently designing test system extensions to support pre-config and pre-build tests. written notes are posted at http://nopaste.snit.ch:8001/9430. ambiguity review and design feedback are most welcome <|> 13:40:53 < particle> .end <|> 13:40:59 < leo_> * nothing to report parrot-wise <|> 13:40:59 < leo_> * else perl & C hacking $job; next week we'll go to German Perl Workshop <|> 13:41:01 < leo_> ^D <|> 13:42:17 < allison> - I spent most of the week on the Objects PDD, wrapping up some of the bits I've been working on the past few weeks. I checked in an updated version earlier today. <|> 13:42:33 < allison> - What's left to do is mainly filling in gaps, and checking the ticket queue to make sure I cover the issues. <|> 13:42:40 < allison> EOR <|> 13:44:04 < obra> Ok. my one item is that particle and allison and leo: could you please log into pause and make parrotre a comaintainer for all your parrot-distribution included modules? this will make the next release go smoother <|> 13:44:29 < particle> done <|> 13:44:30 < obra> and with that, it's question time <|> 13:44:36 < obra> who's got things they're blocking on? <|> 13:45:04 < particle> as far as perl 6 dev goes, i'm blocking on patrick <|> 13:45:17 < chromatic> Pheme's blocking on an HLLCompiler refactor. <|> 13:45:32 < chromatic> kjs is blocking on a commit bit. <|> 13:46:07 < particle> i need his pause id to be approved so i can give it to him <|> 13:46:22 < obra> when did he apply? <|> 13:46:30 < particle> yesterday <|> 13:46:44 < obra> ah. ok. <|> 13:46:53 < obra> so no cause for extra-special measures <|> 13:47:01 < particle> no <|> 13:47:21 < chromatic> Okay good. <|> 13:47:30 < obra> chromatic: who's to do that HLLCompiler refactor? <|> 13:47:40 < chromatic> Allison was working on it. <|> 13:48:08 < allison> chromatic: I'm trying to remember which change you depended on <|> 13:48:27 < allison> chromatic: it was a pretty small wone, I remember that much <|> 13:48:39 < allison> s/wone/one/ <|> 13:48:41 < chromatic> I have my own PAST. <|> 13:48:49 < allison> Ah, right. <|> 13:48:56 < allison> I can make that change tonight. <|> 13:49:17 < chromatic> Nifty. <|> 13:49:32 < chromatic> I'll probably work on Ppwnie instead though. <|> 13:49:50 < allison> ppwnie? <|> 13:50:10 < chromatic> Ponie 2 <|> 13:50:17 < allison> ah, nifty <|> 13:50:19 < obra> so. chromatic, wht is your plan for making ponie work? <|> 13:50:34 < chromatic> Port the pp ops to Parrot in stages. <|> 13:51:06 < allison> Ponie 2 is Perl 5 using the standard compiler tools <|> 13:51:14 < allison> or is this Ponie 3? <|> 13:51:17 < chromatic> That's why it's Ppwnie, not Ponie. <|> 13:51:29 < allison> aaaaggghhh! ;) <|> 13:51:34 < obra> haven't we learned our lesson about version numbers before things are done? ;) <|> 13:51:41 < chromatic> Push-Pops With New Internals Engine <|> 13:52:00 < allison> Can we call it tootsie roll? <|> 13:52:10 < obra> ok. moving on <|> 13:52:11 < obra> what else do people have? <|> 13:52:15 < chromatic> You can call it whatever you want, but its name is Ppwnie. <|> 13:52:23 < allison> er... never mind... I do have a serious question <|> 13:52:37 < obra> go ahead <|> 13:52:46 < allison> Bug squashing session this weekend? <|> 13:52:57 < chromatic> 17th <|> 13:52:58 < allison> preparing for release on the 20th? <|> 13:53:10 < particle> that's the plan <|> 13:53:18 < particle> and patrick confirmed responsibility <|> 13:53:23 < allison> excellent <|> 13:53:26 < particle> but he's been generally unavailable lately <|> 13:53:35 < particle> i expect that will change shortly <|> 13:53:44 < particle> s/expect/hope/ <|> 13:53:48 < chromatic> Have you threatened him? <|> 13:54:09 < particle> i know where he lives :) <|> 13:54:45 < smash> i have a question too if i may.. is there a way of putting up a windows box for testing ? <|> 13:55:22 < smash> there are a lot of issues linux/windows OS specific, and some of usdo not have windows boxes <|> 13:55:24 < allison> we had one in the past, dan admind it <|> 13:55:42 < allison> we need a box and someone willing to host it <|> 13:55:43 < obra> putting a remotely acccessible windows box on the net is...a difficult proposition <|> 13:55:55 < particle> vm. <|> 13:56:29 < obra> last i heard, robert and ask didn't have the tuits to sort one out <|> 13:56:36 < allison> well, it can be behind a firewall, and only accessible indirectly <|> 13:56:37 < obra> if we had a willing volunteer, that might help <|> 13:57:00 < smash> allison: ssh tunnel <|> 13:57:05 < allison> yeah, I wouldn't stick Ask and robert with the task <|> 13:57:25 < smash> obra: ou just need a box and a running free version of vmware <|> 13:57:46 < smash> vmware server, run it on linux.. and host whatever you want on virtual machines <|> 13:57:49 < obra> you also need windows licenses, and someone to admin the box. <|> 13:58:00 < smash> yeap, on licence <|> 13:58:03 < smash> *one <|> 13:58:10 < allison> yup, that's the tricky part <|> 13:58:25 < avar> What would admining involve and how would it be set up if I may barge in? You just need remote desktop setup in vmware instances that can then be cloned? <|> 13:58:27 < particle> if it's a matter of cost, that can be fixed <|> 13:58:38 < smash> i don't know if you need a special licence to do that <|> 13:58:59 < smash> you set up another linux on a virtual machine to actas a firewall for the windows vm <|> 13:59:03 < obra> particle: cost is the easier factor. willing administrators is the harder one <|> 13:59:16 < obra> technical details of how to deploy this arent' quite right for now <|> 13:59:42 < particle> maybe there's someone in perlmonks with remote admin experience for windows <|> 13:59:44 < smash> setting up the server is the easy part <|> 13:59:46 < particle> and tuits <|> 13:59:51 < obra> but if you're interested in volunteering to help make it go, stick your hand up now <|> 14:00:04 < avar> technical details have to do with how hard it is to administer for the one hosting it which has something to do with wilingness:) <|> 14:00:27 < smash> i volunteer for help with that part <|> 14:00:31 < particle> i'll help from the parrot-on-windows perspective. but admin... not my expertise <|> 14:00:41 < obra> right then. smash: perhaps you could talk to parrot-porters to see if you can find more willing victims to help? <|> 14:00:56 < obra> it may be worth ccing ask@perl.org to see if he has hardware available <|> 14:01:14 < smash> but what are we talking here ? the vm server or the windows itself ? <|> 14:01:21 < smash> or both ? <|> 14:01:30 < particle> let's do details offilne <|> 14:01:31 < obra> both, since we have neither <|> 14:01:55 < obra> but yes, #parrot or parrot-porters is a better forum for this <|> 14:02:02 < smash> sorry <|> 14:02:04 < obra> any other issues people want to bring up? <|> 14:02:13 < obra> smash: thanks for bringing it up <|> 14:02:40 < chromatic> Do we have an implementation roadmap for PDDs? <|> 14:02:50 < particle> that'd be nice. <|> 14:03:45 < chromatic> At least a list of what non-implemented things block important things, so we can divy them up into person-sized stories. <|> 14:04:10 < particle> should we put names to roles in RESPONSIBLE_PARTIES? <|> 14:04:24 < obra> particle: by all means. go for it and check it in <|> 14:04:32 < allison> particle: sure <|> 14:04:35 < particle> chromatic: a dependency matrix for parrot wolud be a good thing <|> 14:04:48 < allison> chromatic: what form would you see the stories taking? <|> 14:05:00 < allison> RT tickets? <|> 14:05:15 < allison> or something more of an overview? <|> 14:05:36 < chromatic> Whatever works best. It'd just be nice to have something more than a blob of PDD and may-or-may-not-be-tested code. <|> 14:05:45 < allison> agreed <|> 14:06:05 < allison> particle: do you want to take a stab at a dependency matrix? <|> 14:07:22 < particle> i don't have a clear head for it now <|> 14:07:31 < particle> but if nobody gets to it in a week or two... <|> 14:09:46 < allison> ok <|> 14:10:19 < obra> ok. anyone have anything else? <|> 14:10:33 < particle> allison: i'll start reviewing pdd15 tomorrow <|> 14:11:03 < particle> could folks look at the design for config/build testing and give me feedback? <|> 14:11:44 < particle> that's it for me <|> 14:11:50 < allison> particle: col <|> 14:12:25 < allison> (blasted international lag) that's cool, thanks <|> 14:12:28 -!- Tweety [~robert@x3.develooper.com] has joined #parrotsketch <|> 14:12:28 < Tweety> Hi there. I am Tweety. I am now publically logging this channel. If you don't want to be logged, please leave now. <|> 14:12:39 * obra snickers <|> 14:12:46 < obra> anyone have anything else? <|> 14:13:02 < chromatic> Cutting and pasting the whole meeting for Tweety now... <|> 14:13:10 < obra> chromatic: thanks. <|> 14:13:14 < obra> ok. catch you all next week <|> 14:15:18 < leo_> see ya, thx <|> 14:17:08 < allison> thanks jesse <|> [Done.] % | is now known as spinclad % smash has left #parrotsketch spinclad: thanks obra: glad to help