Post closed tickets in your report. | Note: This channel is for our weekly status meetings (Tuesdays at 19:30 UTC); you probably want #parrot instead. | irclog: irclog.perlgeek.de/
Set by moderator on 13 July 2013.
00:11 Tene_ joined 05:01 denis_boyun joined 11:05 denis_boyun joined 13:14 denisboyun joined 13:23 bluescreen joined 13:53 pmurias joined
pmurias Pre-report: 13:53
* simple protoregexes work
* simple grammars work
* we pass some grammar and protoregexes tests
* merged in my bug fix branches into main nqp branch
* stopped using a custom nqp branch instead I'm mixing a role into the QAST::Compiler
14:23 darbelo joined 14:56 denisboyun joined 15:16 denisboyun joined 17:43 darbelo joined 19:14 denis_boyun joined
denis_boyun Pre-report: 19:17
# Done:
* deployed project on GNU Compile farm
* Fixed bug with uncompress project content
* Update API for work with template file
# Doing:
* to continue work with hll template file. to provide more build and test system
.end
sa1 * Pre-report: 19:24
** Done:
*** add AttrCache class
*** Fixed other bugs with Repository and Index structures
*** Most git_repository functions and git_index are able to be called.
** Doing:
*** Dealing with repository corruption issues.
*** Working example doc remains hinged on above issue.
* end 19:25
Util Pre-report: 19:30
# Done: * Nothing (but $WORK is easing up some, so better prospects ahead)
# Doing:
* GSoC evals
* Will look at sa1's corruption issue today.
.end
Hello! Who all is attending today? 19:31
denis_boyun Util: Hi
sa1 Hello Util, denis_boyun
denis_boyun sa1: Hi
Util Glad to see pre-reports from all 3 GSoC students!
Please remember to make your mailing list and parrot.org posts as well. 19:32
sa1 Right
denis_boyun Util: Ok 19:33
Util: I have a question about evalutions on google-melange. Should we write a special report for that? 19:34
sa1 Util: I've been working on my corruption issue for the last few hours after I sent you that email.
I haven't been able to consolidate all my issues to report them, but working on it 19:35
Util denis_boyun: I don't know if the evaluations done *by* the students are supposed to be public. Maybe use a gist until we know more. Does that answer your question? 19:36
sa1: OK, I will wait until I see email or IRC message from you, before diving in.
sa1: Thanks for the warning. 19:37
sa1 Util: the mentor and organization administrator sees the melange evals, according to the FAQ
Util: One issue over the last hour was while trying to call this function(libgit2.github.com/libgit2/#v0.19.0...ory_index) 19:38
It expects two arguments, I am passing two, the nci file has two, but its expecting one. 19:39
denis_boyun Util: not really, I'm reading on public email that the student must fill the evalutions fields and mentors must do it too.
sa1 Sounds similar to my prev makefile issues.
denis_boyun Util: Should we write a special report for mentor of out work in this midterm? 19:40
sa1 Its an immature issue at the moment, I'll look more into it. 19:41
But I seriously need to talk aloud for more of my work. Getting yout thoughts out probably helps in sorting them out. 19:42
Util denis_boyun: Oh, I see. No, I don't think a special report is needed, since (as sa1 reminded me), we admins and mentors will be able to see the evaluation that you submit. On the other hand, if there is anything that you would like to tell us, that the evaluation has no place to write, then feel free to send us a email directly. 19:43
sa1: Yes, a well-known and valuable technique; see "teddy bear" in cm.bell-labs.com/cm/cs/tpop/debugging.html 19:44
denis_boyun Util: ok thanks. I understand
sa1 Ah, nice to hear to Kernighan and Pike have written on it. Have been meaning to read that book after reading the C one. 19:46
Util denis_boyun: What is the URL for your test deployment? I know I had it, but cannot find it now.
denis_boyun Util: gcc20.fsffrance.org:3000/ 19:47
Util denis_boyun: thanks
Any blockers that we might help resolve? (besides sa1's corruption issue)
denis_boyun Util: not yet 19:48
sa1 No
Util A thought: You both lost some time to problems that were recently solved, and so are slightly behind schedule. 19:50
It is mid-term now, so if you can increase your velocity of progress, you can get *ahead* of schedule, and not be vulnerable to unforseen problems close to the end-term.
sa1 True 19:51
denis_boyun Util: agree
Util Any other issues, or anything at all to discuss? (including non-GSoC) 19:52
sa1 Util: No, but try to run my code in a while and make other comments even if not directly related to my priority issue. 19:54
Util sa1: Will do 19:55
GSoC: Remember, if you do get snagged on something that you need help with, and are not getting the help you have requested, say it differently, more urgently, or just *again*!
Thank you all for participating! 19:56
Meeting adjourned.
sa1 Thanks!
20:54 bluescreen_ joined 20:56 bluescreen__ joined