Vision for 2.0: Production Users | Priority for 1.6: Merge Branches | Priority for this week: Fix partcl segfaults & PANICs, increase test coverage on Namespace and Array PMCs, prune a struct | trac.parrot.org/parrot/wiki/Propos...chProtocol | Note: This channel is only for our Tuesday status meetings; you probably want #parrot instead.
Set by moderator on 18 September 2009.
01:33 japhb joined 12:01 kid51 joined
kid51 kid51 reporting: 12:02
Done:
* Closed 3+ RT tickets
* Eliminated configuration step auto::funcptr, which was doing nothing in the absence of JIT
* Reported failures observed in my own testing and Smolder reports
* TT #989 was nominally mine once it was reopened, but I don't know how to resolve it; reassigned to nobody
Doing:
* In library_files branch, contemplating where best to define lists of test files (TT #1061)
Blocking:
* Have repeatedly requested, but not received, feedback on TT #509. Need feedback from people with non-symlinkable systems in order to apply patch from wayland
EOR
Tene Done: git and svn fetch stages for Plumage, and the start of a pure-parrot HTTP client. 14:44
Doing: More plumage work, possibly IO, maybe a Select PMC, Austin asked for import/export for NQP. 14:45
EOR 14:47
japhb Done: 16:14
* use.perl.org/~geoffrey/journal/39682
* Edit trac.parrot.org/parrot/wiki/Module...taProposal for rev 1 16:15
16:15 whiteknight joined
japhb * Review work from Tene++ and darbelo++ 16:15
Will do:
* Continued Plumage coding
Blocking on: 16:16
* Lack of sleep and surplus of headache. Bleah.
EOR
16:20 NotFound joined
mikehh What I did in the last week: 16:43
* building and full testing parrot on amd64 and i386
* fixing test failures
* testing language builds on latest parrot, mainly rakudo and partcl
* worked on make fulltest and make cover:
* they now run all tests run by make test as well as the run-core tests,
* codetest, benchmakk_tests, manifest_tests, examples_tests and distro_tests
What I intend to do in the next week:
* continue testing
* write some tests
.eor
cotto_work What I did: 16:49
* <this space intentionally left blank>
What I intend to do:
* more than this week
Blockers:
16:54 darbelo joined
whiteknight WHAT I DID: 16:55
* Looked more at JIT stuff, especially LLVM documentation
* Got a great response to a blog post, a libJIT-based NCI frame builder, looking at that to see if it's feasible to get it into trunk.
* Following along with some GC changes
* Digging into PCC refactor branch test failures. Am certain that adding support for :named and :slurpy return arguments will resolve large numbers of failures
* Tried adding said support but failed and ran out of time.
* Updated the list of TODO items for ongoing IO cleanups to make sure other people know what needs to happen there
WHAT I WANT TO DO:
* Continuing on JIT documentation-reading and planning. Especially trying to get documentation/examples for the LLVM C bindings (the main API is C++)
* Trying to get an LLVM-based NCI thunk generator set up
* Looking over some recent GC changes to see if we can do more optimization/cleanup
* Got a lead on a new memory allocator that might improve Parrot performance, going to be testing that out.
* Debugging on PCC refactors branch. Big push to get that ready.
WHAT I AM BLOCKING ON:
* Severe tuit shortage.
EOR
darbelo Did: 17:21
(decnum dynpmcs)
* Did some makefile cleanups.
* Replaced Configure.pl with Configure.pir
(parrot)
* Attempted some strstart removals. Found dragons.
* Removed _next_for_GC.
* Made pmc2c error out on PMCs with pmclass != filename.
* Opened ticket to review pmc2c tests.
(plumage)
* Got sucked into it. Wrote some code.
Will do: 17:22
(decnum dynpmcs)
* A DecQuad PMC is imminent.
* Might remove DecInt as a failed experiment.
(parrot)
* Make pmc_freeze.c stop abusing string internals.
Might block:
* Tuit shortage has been announced for next week.
.eor
q2q
17:24 pmichaud joined
NotFound What I did: 17:28
* Renamed list.c functions that conflicted with mysql client lib.
* NCI parameter handling fixes
* Moved example Mysql module out of the parrot repo.
* Deprecated Parrot_oo_get_namespace.
* Added type safe versions of mark alive.
* Miscellaneous fixes, cleaning, and test coverage.
What I will do:
* No plan.
EOR
pmichaud What I did (past two weeks): 17:29
* Had some $otherjob tasks to take care of
* Mainly working on regex engine refactors
* Rewriting the engine in pct-rx branch
* New engine is completely PAST/POST based, unlike PGE
* It should also be quicker, and with a lot less GC pressure
* Have basic operations in place for concatenation, alternation, quantifiers
What I'm doing this week: 17:30
* More grammar engine work
* Will be adding full Cursor and Match capabilities soon
* Then protoregexes
* Then parsing/compiling P6 regexes using the new engine
* Then flesh out the rest of the regex engine capabilities
* Then redesign NQP's grammar and implementation to use the new engine
* (Don't know how far I'll get with the above... I just keep plugging away at it)
What I'm blocking on:
* Insufficient usable hours per solar day
EOR
17:39 Util joined 18:08 jrtayloriv joined
jrtayloriv WHAT I DID: 18:12
-- Started working on a Scheme compiler, "phemer"
-- Bombarded Austin++ with hundreds of questions about PAST/PCT
BLOCKERS
-- Not knowing Scheme well enough
-- Just barely understanding PCT
EOF
18:14 chromatic joined
chromatic I fixed some bugs. 18:14
I helped tune the GC and clean up some of its code.
I found yet more evil in IMCC.
This week I will do as much as possible to fix IMCC's line number tracking.
I will also post some ideas on pruning some of our structs.
18:18 allison joined 18:23 barney joined
Util # Done 18:30
* TT#600 (bytecode testing framework) - Wrote up a first draft. Posted just now.
# Not Done:
* No progress on TT#994 or TT#389 (git-svn auto-props, and keeping subs with :method out of the namespace).
# Plan for next week:
* Resume work on TT#994 or TT#389.
# Blockers:
* None.
.end
chromatic Hello.
whiteknight hello
cotto_work hi
Tene HI!
barney hi
mikehh hello
pmichaud hello
allison - Created a git branch for merging trunk with pcc branch. That's done (and pushed to a github repository), but I haven't created a new subversion branch yet because I'm getting a segfault on Mac OSX (which may have been there before the merge).
- Was in Portland this past week for LinuxCon, so spent some time talking with chromatic about project blockers and roles and responsibilities.
- Gave a talk at a Bay Area Python group and met with the Unladen Swallow developers (an implementation of Python using the LLVM JIT).
EOR
and hello
darbelo Hola. 18:31
jrtayloriv greetins'
NotFound hola
chromatic Let's talk about last week's priorities. 18:32
Exception testing?
whiteknight nothing that I am aware of
chromatic MultiSub testing? 18:33
mikehh there were some additions to exception tests 18:34
18:34 dukeleto joined
chromatic I saw someone mention coverage numbers. Was that NotFound? Can whoever's done that document how to get those numbers on the wiki? 18:34
whiteknight I say we roll those two over. Need more tests on MultiSub and Exception in any case
pmichaud I vote we table them. 18:35
cotto_work didn't we get some PMC to 100% coverage?
dukeleto yes, i added some coverage for exception, but it needs more
NotFound chromatic: make cover, or tapir2.ro.vutbr.cz/cover/cover-results/
dukeleto equality of exception objects is a big chunk of coverage that is needed
NotFound We have now 100% on some Array PMCs 18:36
chromatic That's a useful link.
NotFound Don't know who does it, somone put the link on #parrot a few weeks ago 18:37
cotto_work mj41 iirc 18:38
chromatic Move on to new PMCs or keep working on these two? Votes? Suggestions?
pmichaud I'd like to see us prioritize PCC.
NotFound pmichaud: me also
chromatic Alright then, let's talk about PCC. 18:39
Allison?
allison I have a fresh trunk-applyable patch ready for a new subversion branch. 18:40
I'm doing some testing now, but could apply it to a new branch right after #parrotsketch.
darbelo Ship it!
NotFound +10
allison A show of hands who'd rather work in subversion versus git on this one?
Util +1 SVN
darbelo +1 either way. 18:41
NotFound I'm unable to work with git
pmichaud I think svn will win this one.
allison subversion it is, I'll take all the help I can get
whiteknight yay!
whiteknight giggles with excitement
NotFound Go, go, go!
pmichaud I'd prefer git, but I'm not likely to be extremely active on committing at first, and I can certainly work okay with svn.
chromatic What's the status of the patch, allison?
whiteknight Git in baby steps
pmichaud I'd rather keep the svn users (NotFound, allison, Util) productive on this one. 18:42
mikehh I can go either way
allison chromatic: cleanly applies to trunk, segfaults in the config PMC generation on OSX
whiteknight allison: I've got a lot of test failures traced back to a lack of :named and :slurpy returns
we get those added, I think we'll have a much cleaner test output
allison chromatic: haven't been able to test on Linux because my linux laptop bit the dust on the plane to London
whiteknight I'll test on Linux tonight
mikehh I can test that 18:43
whiteknight it does build there, fails lots of tests but does build
chromatic Any other discussion of that branch and our prioritization?
whiteknight nope 18:44
pmichaud +1, thanks everyone
chromatic Okay. Other priority suggestions for the week?
Tene There are several people who can provide linux boxes for testing, I'd expect, including me.
chromatic Does anyone know the status of pirc? I'm running into places I can't patch IMCC without a severe refactoring. 18:45
allison chromatic: stalled, AFAIK
whiteknight last I heard, it was having PBC problems
floating point values, mostly. Needs testing
Tene chromatic: Incomplete. What's there works okay, but it needs several more things.
whiteknight otherwise, kjs was optimistic
allison yes, mainly just blocking on his time
there may be a way to spread that work out 18:46
whiteknight I think a concerted team effort oul get it moving again
Tene It was fairly easy for me to get started on when I looked at it.
chromatic I'd like to suggest that we focus on that soon.
whiteknight agreed
chromatic Otherwise I suspect it'll slip past 2.0.
It may anyway, but I don't want IMCC to live any longer than it has to.
allison chromatic: we already said it would slip past 2.0
2.6 at the earliest
darbelo Somebody needs to check in the generated c for those of us without bison. 18:47
Tene I tried to fix some of the problems, but I ran into issues about knowledge of parrot internals and what some of the things mean.
chromatic 2.6 is the earliest supported release in which it can be the default, or the earliest any kind of release in which it can be the default?
whiteknight that's what I get blocked on too: esoteric internals details
particle tene: did you take notes, or comment the code?
cotto_work sounds like a good next target after pcc
Tene particle: I made a couple of commits, iirc... lemme check.
allison chromatic: it's the earliest any kind of release where it can be used as a full replacement for imcc
mikehh I think a concentrated effort can get it done sooner
allison mikehh: probably, but we would have to balance that against other roadmap items currently listed for 2.0 18:48
whiteknight I agree, I think we could have it as a viable alternative by 2.0 if we focused
allison (i.e., we can't do everything)
whiteknight (2.0 is a busy milestone)
Tene particle: looks like no.
chromatic My suggestion for this week: let's a couple of us figure out its current state and make a list of tasks needed to make it the default. 18:49
whiteknight I would much rather we focus on JIT, if we have to choose
allison hll interop is a higher priority than pirc, for example
particle (lost knowledge)--
mikehh I think rirc is a priority, just as jit was/is
particle tene++ for checking
allison mikehh: indeed, it is
mikehh: they're all priorities, we just have to rank them
Tene Is there any interest in starting to have regularly scheduled hackathons? "On X datetime, everyone work on Y" for items like pcc, pirc? 18:50
whiteknight Tene: I would be very much in favor of that
chromatic +1, Tene
darbelo +1
allison Tene: that could be a good motivator
pmichaud we're doing mini-hackathons here in the north Dallas area and it's worked out well.
chromatic Suggestions for a time?
whiteknight Weekends are most permissive, I think. 18:51
NotFound Did we really need pirc? If we can have a PCT based pir compiler, that may be good enough.
Tene I'm always able to be available every saturday, any time.
whiteknight I personally have a hack marathon on Saturday
allison NotFound: that has bootstrapping problems, and the fact that PCT is SLOW
chromatic PCC hackathon this Saturday, then.
whiteknight +1
pmichaud allison: what part of PCT is slow, here, ooc? 18:52
chromatic Let's move the PCT discussion to #parrot.
18:52 kurahaupo joined
allison NotFound: so, not necessarily pirc, but a low-level fast PIR/PASM compiler as an alternative to imcc 18:52
pmichaud note that if we can get POST->PBC translation in place, then the need for PIR compilation becomes much smaller. 18:53
Tene NotFound: iirc, one of the things pirc was still needing was some part of pbc generation, which any pir compiler would need.
particle tell that to the hll folks not using pct
allison pmichaud: indeed, though still needed (since PCT is written in PIR)
pmichaud: for now :)
pmichaud allison: PCT can be rewritten... :)
it's explicitly designed to be nqp-able 18:54
allison PIR or PASM will never go away though
pmichaud sure, I agree
chromatic Shall we review our milestones now?
HLL interop?
allison needs someone to focus on it for a week or two, as I understand it 18:55
as in, close to done, but not getting attention
pmichaud I'm listed at the point person for that, but I doubt I'll be the person to focus on it in October. If someone else wants to take the lead, I'm happy with that (and will help as the PCT-related issues come up)
chromatic Anyone willing and able?
whiteknight I don't understand it either 18:56
Tene Take the lead on HLL interop?
whiteknight can we get some good documentation about the outstanding tasks?
NotFound Or even not so good?
Tene I'm pretty sure I'm supposed to be the lead on HLL interop issues.
pmichaud if nobody does it I *will* get around to it before 2.0, but regex refactor has nearly all of my attention at the moment, since so much (parrot, nqp, rakudo) is blocking on that at the moment.
chromatic Tene, are you volunteering or revolunteering? 18:57
Tene chromatic: Both! 18:58
allison I'd like to see someone else working on it, even if pmichaud can come back to it later
pmichaud Tene is the logical choice.
allison (just a matter of spreading effort)
sounds like it's in good hands
Tene If anyone else wants to be brought up to speed on HLL interop, they can ask me. 18:59
chromatic dukeleto, Parrot debugger documentation?
allison Tene: if you can break the work down into simple tasks on a wiki, you may get more help fast
Tene allison: I'll look into it.
allison (it's not always possible) 19:00
dukeleto chromatic: i think if someone could tell me what they wanted to see in the debugger docs, i could 'finish' the task, but right now, it is ambiguously specc'ed
Tene AFK; I need to lunch now, before I run out of time. :P 19:01
chromatic Do you have a list of tasks you can perform in the debugger? We could brainstorm some use cases.
allison dukeleto: focus on helping people getting started in using it
dukeleto allison: ok, I think we definitely need more of a debugger "user guide" than a manual page. good idea
pmichaud dukeleto++ 19:02
chromatic japhb, seed libraries?
allison dukeleto: a short manpage is also good (so we can ship it with the distros), but that should be fast
japhb chromatic, sorry, still spending all effort on Plumage.
On the plus side, do have a couple helpers now. :-) 19:03
NotFound I moved Mysql from examples to an external repository
japhb NotFound, have you made a Plumage metadata JSON for that? 19:04
NotFound japhb: not yet, lacked the time to learn the format.
chromatic Bytecode testing, Util? 19:05
japhb NotFound, no problem. I can help you when you have spare time.
Util I put my thoughts into TT#600, but I am not claiming the ticket (yet?). The real work looks to be in answering the outstanding questions on how it should function, which I expect IRC discussion to resolve.
chromatic Can you lead a discussion of those issues on #parrot? 19:06
Util Yes
chromatic Excellent.
Finally: pruning C data structures. I'll publish some notes on that soon.
Next question: what's blocking us in the long term, either technically or socially? 19:07
allison q2qs
whiteknight A "where to start" point for JIT
although I'm getting closer to that
chromatic Other thoughts? 19:08
NotFound strings
allison whiteknight: I had a good conversation with the unladen swallow team, will send you a summary
particle chromatic: revision of roadmap/milestone items is due 19:09
whiteknight allison: awesome
chromatic Strings, NotFound?
NotFound No work in the string branch for months
chromatic Okay.
allison you mean implementing NFG?
NotFound And renaming functions, and deleting deprecated ones, and fix lack of documentation... 19:10
whiteknight I really should look into that problem more. Bit twiddling and buffer managment is right up my alley
allison NotFound: the big branch there was merged in 19:11
NotFound allison: I'll write a ticket with the main current pitfalls. 19:12
chromatic particle, what did you mean?
allison NotFound: (the renaming interface cleanup, that is)
NotFound: excellent
particle the ROADMAP developed at pds2008 has proven invaluable in setting and achieving our near-, mid-, and long-term development goals. incremental updates to the ROADMAP over the past ten months have met our near- and mid-term needs, but no longer meet our long-term needs. it's time for a full review of the ROADMAP.
chromatic Okay, good point.
Other blockers?
allison PDS 2009
pmichaud will there be a PDS 2009?
Util A "where to start" point for really hacking Parrot; e.g. understanding the Parrot and PCT subsystems. Is the .str thinking even documented anywhere?
We have a PIR book, but if all the non-book .pods were spliced together and read, would one get a coherent picture of *every* corner of Parrot and PCT? 19:13
chromatic Good one, Util.
particle pmichaud: yes, however it may be virtual, if we can't get funding to make it face-to-face.
allison pmichaud: I list it as a blocker because it needs someone to plan it. We should have one, yes.
pmichaud I was going to suggest a virtual PDS
if we can't have a f2f one
allison that works too
chromatic Anything else?
darbelo q2q
pmichaud Util: I plan to draft someone to do a PCT book when I'm done with the current set of refactors 19:14
chromatic Let's move on to questions.
Allison?
Util pmichaud: very glad to hear it
dukeleto 1q1
allison Longish first q:
NotFound BTW we have a new platform: PacoLinux has been able to build parrot on Haiku.
dukeleto or q1q rather
allison chromatic and I are both reading a book called "The E-Myth Revisited". It's about running a small business, but a lot of the concepts apply equally well to an open source project.
Talking about that and about Parrot, we hit on the idea of adding a new role in Parrot, called something like "Development Coach". The role would involve keeping an eye out for pain points and blockers in the development process, "Are there ways we could do things better, cleaner, more efficiently?" 19:15
This would be chromatic's role, he's already doing it now, but it's valuable to mark it as a specific role, both so people inside the project recognize what he's doing and why it's important, and so people outside the project see the value we place not just on good code but on good practices.
It has an added advantage that it allows me to focus more on the architectural vision role, where we're going, why we're going there, and what are the most important steps along the way.
chromatic (and so I *remember* to put on a hat and do it)
pmichaud +2
whiteknight +1
dukeleto +1 to dev coaches
allison What do others think of adding a Coach role? Does this sound like a good idea?
NotFound +1
darbelo +5
Util +1
particle *2
pmichaud and congratulations, chromatic.
dukeleto what about "new developer" coach, is that a different role? 19:16
chromatic I'd like to think anyone and everyone can coach new developers.
allison dukeleto: that's mentoring
particle dukeleto: we have individual mentors for that
allison and, we have a number of people doing it
mikehh excellent
allison but, worth recognizing them too
dukeleto mentoring++ 19:17
chromatic Next question, allison?
allison Sounds like we have general approval, excellent!
Second q: On git, chromatic and I propose to table the migration discussion for now.
Util +1 19:18
allison We can't migrate until after 2.0 or maybe even 3.0 for stability of development process anyway.
cotto_work for now long?
particle agreed, even though it's not a question :)
allison But, we have a process modification to consider as a compromise.
(the compromise is the question)
dukeleto is there a time-frame decided for when it will be de-tabled for discussion?
2.0 ?
pmichaud wait, let's hear the compromise first. 19:19
(proposed compromise)
particle ...people are jumpy today...
allison What's the general thought on opening the parrot branching strategy up, so a particular development task could be done either with an SVN branching techique, or with a pure git branching technique?
The developers involved can decide what branching strategy to use.
pmichaud I'm not quite sure how that would work (from a technical perspective) 19:20
particle whatever works, but i'd prefer all external branches become svn branches before trunk merges
cotto_work allison, immediately?
allison Git branching is quite painless if the main developer takes a branch from trunk, and the other developers fork off that main branch and collaborate directly through git.
pmichaud sure
dukeleto allison: +1 for each developer choosing svn branch or git branch. it is easy enough to provide a diff of a git branch for svn folk to test
pmichaud but how do those get back into svn?
just a diff of the branch point? 19:21
Util Having the branches be public, rather that chance them being only on someone's laptop, is worth a lot.
Tene pmichaud: I can work through a test of it with you tonight.
allison (It does mean the one developer takes responsibility to merge the main branch into trunk when the time comes)
cotto_work +1 to the proposed compromise
Util s/that/than/
particle i say create svn branch, commit git branch there, then handle svn trunk merge
dukeleto pmichaud: by creating a patch
particle it gives existing smokers something to chew on
pmichaud dukeleto: so, roll up all of the git commits into a single diff that is then applied to svn (branch or trunk)
allison But, then, we already have one person taking that responsibility to merge in the SVN branch, so it's not a big change.
particle we don't have git smoke infrastructure
dukeleto pmichaud: yes 19:22
pmichaud how does one re-sync the git branch with parrot trunk?
Tene pmichaud: or apply all of the git commits as svn commits via git-svn
allison particle: using git on an svn branch actually reduces a good bit of the usefulness of git
pmichaud Tene: I'm thoroughly unimpressed with git-svn at the moment. It took 30 minutes for people to try to explain it to me and I couldn't follow it.
chromatic We can figure out the right workflow depending on the branch. The important ideas are 1) allowing experimentation with public Git branches and 2) recommending that all committers try Git at least once or twice.
dukeleto pmichaud: git pull origin
particle allison: when it's an integration candidate with parrot trunk, i'd like to be able to take advantage of the smokers, and to have the history in one repo 19:23
dukeleto pmichaud: we should avoid git-svn if posssible
allison pmichaud: if it's used well, it's no trouble, but the current "recommended" technique for using git-svn on the parrot wiki is not ideal
pmichaud please, if I may have the soapbox for just a second
particle just dropped git-svn at $work, due to continued branch merging pain
dukeleto particle: shall I create a TT for investigating git smoking infrastructure?
pmichaud I have a very real application for this today
particle dukeleto: sure!
allison pmichaud: application for what?
pmichaud git branch versus svn branch 19:24
current I'm doing my development on the new regex engine in an svn branch
I _tried_ to do it with a git branch this last week, but was totally unable to come up with a clean way to do it
allison a git branch from trunk, or a git branch from the svn branch?
pmichaud either.
creating the git branch is easy enough 19:25
but then resync with trunk isn't obvious
allison it's worked well for me
particle the svn barrier prevents git svn merges from being very useful
allison the easiest is to format-patch and apply that to trunk
pmichaud and I wasn't sure how to get the git stuff back into svn
sure, I can format-patch and apply to svn trunk
allison though, you can commit back to trunk directly
pmichaud but I'm still not sure how to get recent trunk commits into git branch
allison git fetch 19:26
pmichaud is this assuming that we did a git-svn checkout?
chromatic Can our resident Git experts come up with a decent workflow we think will work?
allison git svn fetch
pmichaud okay.
allison it's quite clean
pmichaud I will be happy to work on a workflow with a git expert
particle no, it's not clean
when filenames change, or big hunks of code are refactored, it totally breaks down 19:27
pmichaud I'd really prefer to use git, but I kept getting conflicting advice
allison (git rebase, btw, is considered bad news by the linux devs)
particle because you can't do git hunk-based merging, you're stuck with svn file-based merging
pmichaud agreed, I tend to want to avoid "git rebase" as well.
chromatic pmichaud, dukeleto, Tene, can you come up with some workflow for us?
allison The idea at this point is just to open it up for experimentation. 19:28
It may turn out that git is no good for us.
pmichaud I'm fine with that. As I said, I have a very real case to work with.
allison But, it's worth a try.
pmichaud I disagree with "git is no good"
(for us)
particle with the understanding that you can't spell 'experimentation' without 'pain', i'm for it
allison We just don't know yet.
chromatic Okay. darbelo, question? 19:29
pmichaud (I have to leave now...back in 30)
darbelo Can I get some input on the pmc2c tests?
darbelo is searching for TT #. 19:30
chromatic I don't find them useful myself. I've changed the generator a few times and broke the tests and the tests didn't tell me anything interesting other than "you broke the tests". Parrot continued to pass the tests that mattered to me.
darbelo TT #1063 19:31
NotFound Tests that looks at minutiae of the code are plain wrong. 19:32
cotto_work I reiterate my reply to the ticket that the tests aren't generally useful and should be deleted except where they can be made agnostic of pmc2c's specific internals. 19:33
basically, +1 to clobber
allison I'm okay with ripping those tests out.
darbelo 'kay. Clobbering it is.
allison It is a good reminder how important it is to fully test our core pmcs and dynpmcs, though.
(since they are acting as the tests for the generator too) 19:34
chromatic Next question, darbelo?
darbelo I hat 2?
cotto_work better make one up then
darbelo Oh yeah. The plumage CLA thing.
f plumage is going to be (C) The PaFo, that implies that all contributors need a CLA, right? 19:35
allison darbelo: all committers would, yes
japhb darbelo, I thought we decided that was a "yes"
allison is it going to be PaFo?
japhb allison, that's what it is now ... was I wrong to do that? 19:36
I thought it would make eventual merge smoother
darbelo japhb: Just making sure. We had no 'official' answer there IIRC.
allison japhb: nope, highly welcome, and will simplify codistribution
chromatic dukeleto, one question? 19:37
dukeleto i have booked a discussion at the gsoc mentor summit called "dynamic language interoperability"
does anybody want any specific things discussed there? 19:38
particle chaired it last year, iirc
darbelo "When are y'all gonna stop playing and move to our vm?" 19:39
particle wish i could be there to do it again....
chromatic "Why do you hate America?"
dukeleto darbelo: exactly.
particle: i will get as much feedback before/during from you as I can. 19:40
japhb chromatic, "'Cause, um, ... it's America, and ... um ... you know?"
;-) 19:41
chromatic Any final questions?
dukeleto where can I get parrot stickers?
dukeleto is addicted to stickers
i have a sticker printing shop a few blocks from my house, I can look into it if this has not been researched yet 19:42
allison iirc, pmichaud was setting up a parrot cafepress shop
Util pmichaud is absent, but was working on some such
chromatic Sticker printing is likely cheaper than cafepress, with the initial inventory overhead, of course. 19:43
allison they make nice stickers, in additon to tshirts
but, would be interested in prices for printing, too
dukeleto: if you get a quote for a full-color sticker run, send it on to the foundation directors 19:44
chromatic Let's wrap this up then. Good work, everyone. 19:45
Util parrotsketchers++ 19:46
19:46 Util left 19:47 NotFound left, chromatic left 19:50 PacoLinux left 19:51 darbelo left 21:49 Whiteknight joined 22:21 cotto_w0rk joined 22:22 ascent joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!