"Tuesday at 20:30 UTC"
Set by moderator on 20 September 2010.
00:55 ash_ joined 02:09 whiteknight left 05:33 ascent_ joined, Tene_ joined 05:41 ascent left, Tene left 09:16 bacek joined 09:33 contingencyplan left 11:36 kid51 joined
kid51 kid51's report 11:36
DONE
* Opened and working on TT #1840 for RTEMS detection during configuration
* Opened and working on TT #1841 for 'osvers' setting during configuration
* Recruited one additional smolder tester (Darwin/i386)
* Will not be taking QA Manager role at this time
WILL DO
* Whatever it takes to bring off Parrot Developers Summit this Sunday, Nov 2. We need to finalize time, procedures and agenda.
EOR
12:05 kid51 left 12:45 bluescreen joined 14:13 ash_ left 16:33 mikehh joined 16:46 contingencyplan joined 16:56 whiteknight joined 17:15 atrodo joined 17:59 bluescreen left, bluescreen joined
cotto #done: 18:26
- continued work on opmap-aware packfile pmcs
- got stuck debugging, will come back later this week
- added some Lorito questions to LoritoDesignQuestions on the wiki
- will give chromatic some time to answer what he can
- help dukeleto++ with the git migration, whenever that ends up happening
#eor
whiteknight WHAT I DID: 18:36
* Working to move my blog to a new platform
* Family medical issues are still eating up free time
* Starting to put together a task force and other resourcey people to tackle the embed API
* Started a new project: embedding a Parrot interpreter into XChat. Haven't made much progress yet.
* General well-wishing for the git migration. Won't be making any commits until that's done, will help however I can
WHAT I WILL DO:
* Continue moving blog 18:37
* Try to get the XChat project working, and see what lessons I can learn about embedding Parrot
* Looking at the embed API in much more detail
EOR
19:43 Tene_ is now known as Tene 19:44 nwellnhof joined
nwellnhof what i did: 19:45
- prepared removal of charset ops
- string_checks branch
plans:
- merge remove_charset_ops
- merge string_checks
- more work strings 19:46
- maybe work on IO
eor
19:47 nwellnhof left
Util Will be absent for #ps today. 20:13
curl -s 'trac.parrot.org/parrot/timeline?day...ticket=on' | perl -wlne '/<em[^>]+\\(([^"]+)\\)">/ or next; $h{$1}++; END {printf "%7d\\t%s\\n", $h{$_}, $_ for sort keys %h}'
1 closed: fixed
1 new
( kid51++ on both! )
# Done:
* Made progress on OS X install issue.
= Will be working in branch pbc_to_exe_direct_output. 20:14
# For the record:
* I have seen the light, and support moving Parrot from SVN to Git.
# Plans^WPriority Interrupt:
* Grandchild.new; our first, on Halloween night
.end
20:16 chromatic joined
mikehh What I did since my last report: 20:19
* building and testing parrot on amd64/i386, with gcc/g++
* some fixes
* branch testing and fixing
* did some work on GCI wiki
What I intend to do in the next week:
* testing and fixing
.eor
chromatic I: branched for GC MS2 sweep-free tuning and had some success. 20:21
Except that there's a random segfault somewhere.
I could use another set of eyes on it, but there's 5-7% performance improvement.
20:26 kid51 joined 20:29 whiteknight left, nwellnhof joined 20:30 dukeleto joined
dukeleto went to the dentis this morning and is recovering. I did some git-related stuff. 20:30
dentist, even.
kid51 Hello, #parrotsketch. 20:32
mikehh hi there
chromatic afternoon
dukeleto howdy. 20:33
dukeleto also did Google Code-In related stuff. Almost forgot.
chromatic Shall we review last week? 20:34
kid51 Yes. My casual observation: Little activity in trunk. Some activity in gc-related and other branches. Lots of interest in Google Code-In. Little or no discussion about Parrot Developers Summit. 20:35
Count of new/open tickets (by me) is 637 -- a bit higher than in recent weeks, but not terribly out-of-range.
chromatic Slowed by the oncoming Git migration? 20:36
sorear discussed lorito with cotto; I'll put together a prototype reflective of my understanding in 1-2 weeks
20:36 luben joined
sorear s/in/by/ 20:36
kid51 I don't think git migration has had impact one way or another yet ...
... except in what particular things dukeleto is working on.
If anything, I'd expect a slowdown *post*-migration, as we work out kinks. 20:37
dukeleto This is mid-terms time for many students, so any of our parrot devs that are in school are probably feeling a time crunch.
I don't think git migration has anything to do with our currently activity level. 20:38
bacek aloha
dukeleto I submitted PaFO and TPF to Google Code-In. We could use a lot more tasks and improvements to the ones we currently have. 20:39
trac.parrot.org/parrot/wiki/GoogleC...n2010Tasks
Some organizations already have hundreds of tasks. I would prefer to concentrate on making a few dozen high-quality tasks that we actually care about. 20:40
kid51 I was encourged by seeing #parrot discussions where cotto (lorito) and whiteknight (api/embedding) were leading discussions that reflected a sense that we're trying to form teams or task forces around these issues.
dukeleto For instance, which languages do we want our website and core docs translated into?
I made a task for translating parrot.org to Chinese, for example. 20:41
mikehh I added a bunch of other possibilities for translation
dukeleto mikehh++ 20:42
kid51 Yes, that's a nice list of tests needing P5->PIR that mikehh put up. 20:43
If we had n>1 students working on that, it would probably double the number of people who can write PIR worldwide :-)
chromatic How is the team formation going? 20:44
kid51 see above for my impression; whiteknight not here; cotto? 20:45
dukeleto I haven't recruited anybody for the Community team, but I haven't tried very hard.
cotto has job interviews today 20:46
so everyone wish him luck
What is the point of the Parrot Developer Summit this year? Does it have an action plan? An itinerary? 20:47
dukeleto might have missed the memo
kid51 dukeleto: There was an in-person summit held at google in fall 2008. 20:48
That wasn't feasible thereafter.
so we had an online summit, I believe in Dec 2009.
dukeleto i believe i was there.
i am asking about *this* summit, that we want to hold.
kid51 And we talked about having them semiannually? quarterly?
mikehh yes me too
dukeleto what is the point of a parrot developer summit? 20:49
kid51 In any event, the last one we held was April or farther back.
chromatic To set priorities for development over the next n months.
kid51 Yes.
And to allow us more time than in #psketch.
At least as much decision-making authority as psketch 20:50
A bit more of "the long view" than we do here.
dukeleto kid51: so what you are saying, is that PDS's are for making decisions?
mikehh and more general discussion 20:51
kid51 dukeleto: Yes, at least in the sense that deciding where something goes on a roadmap is a decision.
dukeleto kid51: is that all? is there a hackathon element to them? Or outreach? Or are they purely for making decisions?
kid51 No, not a hackathon.
Not outreach (except perhaps to engaged HLL folks)
Somewhat like the *2nd* part of the agenda at the Portland gathering last month ... 20:52
... i.e., what are the major problems facing parrot right now and what's our action plan?
chromatic Exactly. 20:53
kid51 Ideally, I would have like the Lorito and API teams to be farther along than they are and to have something to present at a summit.
chromatic What would we like to accomplish and what are our priorities?
kid51 But that's probably weeks away.
dukeleto It would be nice if all parrot team leads were present at a summit. 20:54
mikehh and potential team members as well
kid51 Well, if we don't feel a compelling need to have one on Sun Nov 07, then we should reschedule 20:55
Perhaps first Sunday in December
dukeleto who picked nov 7th? 20:56
kid51 I did, but it was more in the nature of "Let's run this up the flagpole and see who salutes"
No date is going to work for everybody 20:57
dukeleto kid51: yes, everyone know that. You don't need to keep saying it.
mikehh do we need more preparation, is this Sunday too soon? 20:58
dukeleto isn't there some website that allows a bunch of people to give their schedules and then tries to pick a time that works for most people? The name will come to me.
doodle.com 21:00
We need to use doodle.com to schedule a Parrot Developer Summit.
chromatic Who's going to take that on?
dukeleto Choosing a random day is not optimal.
dukeleto raises the "Git Migration Flag", and isn't volunteering for more work right now 21:01
cotto might be interested in doing it 21:02
I can send something to parrot-dev asking for a volunteer. Does that work? 21:03
dukeleto does it already.
chromatic Anything code related to make a priority this week?
dukeleto chromatic: get gsoc_nci merged 21:04
chromatic Works for me.
dukeleto chromatic: i think plobsing made all the tests pass. just some codetests failing, methinks
chromatic: it is a tiny goal, but a worthy one
mikehh have various gc related branches and others being worked on
chromatic I need debugging help on my GC branch. 21:05
Benchmarks would be nice too.
dukeleto chromatic: other than that, all other gsoc branches should be checked for mergability
mikehh looking at it
dukeleto chromatic: if you send an email to parrot-dev about what benchmarks you want on which branches, i can do some of that later tonight
mikehh needs some coffee 21:08
chromatic Thanks.
Anything else we should discuss? 21:09
mikehh do we need to discuss git migration 21:10
dukeleto cotto and I are working it
i am doing a dry run of reconverting the repo with a proper author list
i used the slow method, not realizing how slow it would be
mikehh yeah I know, anything yo discuss on it
dukeleto it has been running >12hrs now 21:11
i need to craft the correct incantation to git filter-branch, and it would be much faster
if the output of the current dry-run is reasonable to me and cotto, i will push it to github and it will become the new "official" git repo 21:12
i can do incremental updates on it
so we will make the svn server read-only, do a final incremental update to github, and then that will be what everyone should work from
chromatic Do we need to hold commits to trunk during any migration period?
dukeleto Making the svn directory on the server read-only is a better way. 21:13
chromatic Works for me, as long as we announce it.
mikehh I would think only for the actual migration
dukeleto The actual switch-over happens when we make it read-only.
We won't have a time where svn is read-only and git is not available.
The parrot git repo will be available before the svn server goes read-only. 21:14
mikehh so you set up, make svn readonly, and we are away
dukeleto pretty much 21:16
there are things that we will need OSUOSL for 21:17
but i know where there building is in downtown Portland, so if they ignore me on IRC and I can knock on their door ;)
s/there/their/
but actually, they are amazingly responsive
our repo conversion is the simplest part of the migration 21:18
Trac needs to be converted, and then our commit emails and bunch of other little things
21:18 bluescreen left
dukeleto i will describe each task as I need it, and send it to parrot-dev and ask for help. I will be a bit burned out after the repo conversion and my git doc branches land. 21:19
the conversion is somewhere in the r36000's 21:21
it has to follow branch merges, and it currently doing some funky stuff. 21:22
mikehh BTW did anything happen re: getting dalek to respond to Trac Wiki changed 21:23
changes
dukeleto mikehh: nope, i don't know that anyone knows why it isn't working 21:24
mikehh: Infinoid usually fixes such things, but i haven't seen him around
anything else need to get discussed in #ps today? 21:25
21:26 kid51 left
chromatic I think we can wrap it up. 21:27
dukeleto goes back to #parrot 21:28
21:28 dukeleto left 21:30 luben left 21:45 nwellnhof left 22:05 donaldh joined 22:06 donaldh left 22:10 bacek left 22:38 kid51 joined 23:18 kid51 is now known as kid51_at_dinner 23:35 whiteknight 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!