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 31 August 2013.
08:43 denis_boyun joined 10:09 denisboyun joined 11:01 denisboyun joined 13:21 denis_boyun joined
sa1 Pre-report: 15:29
# Worked on References and Trees
## Already mentioned in last blog post
# Diff class
# Working on documentation in pencils down week
16:40 pmurias joined
pmurias GSoC prereport 16:40
Implemented serialization (nqp/t/serialization/01-basic.t nqp/t/serialization/02-types.t).
Serialization of closures still left as I need to think about some things (mainly how nqp::markcodestatic needs to behave).
Implemented nqp::radix.
16:40 lizmat joined
pmurias Wrote a test for that. 16:40
Working on getting the nqp-compiled-to-javascript to run more things. 16:41
It mainly involves fixing bugs and finding tiny things we do differently from nqp-parrot that are not tested for.
Stuff like stringifing hash iterators, nqp::unshift on an object with a positional delegate.
The big things (like the heavily tested regex engine) seem to work correctly.
There shouldn't be an serious blockers, mostly bughunting.
18:15 denis_boyun joined
denis_boyun # Done: 18:39
* hll and library templates have supported build with perl5 language
# Doing:
* done api more and more smart(clean old zip project)
.end
Util Pre-report: 19:30
Doing: GSoC end-game work.
.end
Hello! Who all is in attendance?
denis_boyun Util: hi. yes
sa1 Util: Hello
I'm meant to code worked upon till the 16th at the end of the evaluation. 19:32
So this week is just meant for documentation and tests.
Util sa1: You out-typed me. See below. 19:33
Reminder to GSoC students:
We have passed the suggested 'pencils down' date (Mon Sep 16), and are approaching the firm 'pencils down' date (Mon Sep 23).
Unless specified by your mentor, new work on features should quickly end, and all work for the rest of the week should be on tests, documentation, final refactoring, and other end-game efforts.
sa1: So, you are proceeding according to plan, yes? 19:34
sa1 Util: Hmm, github is down so I can't show you the gist, but the final deliverables mentioned there are met.. 19:35
But the diff work that I mentioned for the last week's schedule, that needs a little more work.
Util sa1: Post the gist info here after the meeting, when GH is back up. 19:36
sa1 Util: google-melange.appspot.com/gsoc/pr..._kgp/11002 19:37
Is that visible to you?
nm, I see github back up too: gist.github.com/sa1/5468408 19:39
Util sa1: The Melange post was not visible, but the Gist is. 19:40
sa1: "final deliverables mentioned there are met". This is music to my ears :^) 19:41
sa1 Util: thank you :) 19:42
So I've got my exams coming up next week. I'll spend some time on documentation. The other wrapping up stuff involves making things easier to set up. 19:43
But I need feedback on that, the problems faced on setup.
Util sa1: Does dukeleto know in detail of the feedback you need, and that you need it? 19:45
sa1 Util: I asked him whether he set up an environment, and he said that he didn't because needing another .so file installed is a good short-term solution, but a bad long-term one. 19:47
He has made some attempts at setup after that, because of one or more commits he pushed. 19:48
But I only want any problems faced to be mentioned, nothing more. 19:49
Removing the .so file currently required will take some time and insight.
Util sa1: I am not sure I completely understand, but I will leave that issue to the two of you; let me know if you need me to look into it myself. 19:50
denis_boyun: Have you fulfilled your final deliverables?
Can you stop your work on the API and shift to just cleanup, and still have accomplished what was promised? 19:51
sa1 Util: I want only general feedback, just see if you can build, install, and run a test
And if that's not possible, just mention it.
Util sa1: OK 19:52
denis_boyun Util: yes. my project have done. hll and template files are supporting all build languages and all tests. I've done tests and documentation
Util GSoC students - Some thoughts to shape your documentation:
denis_boyun: Excellent! 19:53
Util restarts my pasting
GSoC students - Some thoughts to shape your documentation:
1. Someone else may want to continue your work in the next few months.
Write what will help them know what dead-ends you have already explored, and what your next items of work would have been.
2. Someone else may continue your work during the next GSoC.
(You might have a conflicting schedule next year).
Write what will help them get "up to speed" quickly.
3. *You* may continue your work during the next GSoC.
You *will* have forgotten 95% of the knowledge that seems so fresh and permanent in your brains now.
Write what will restore all that knowledge, so you don't have to discover it all over again.
.end 19:54
sa1 hmm, makes sense
Util denis_boyun: By "done", do you mean that you have no more tests&docs to do this week, or do you mean that your have already started on them and will be finishing this week? 19:55
denis_boyun Util: I mean that I've done all work which I planed. At this week I want to add some features, which done my project more perfect 19:58
Util: It's a some change on my API, on tests and etc 19:59
Util denis_boyun: It is great that you have done all your planned work, but be careful about adding new features at this point. That should only be done with dukeleto's agreement. 20:03
The reason is that, if you try to add new features now, you have 6 days to fully implement, *and* debug, *and* document the new features.
Something could happen to you in 3 days that completely disrupts your schedule, and leaves your project in a inconsistent state.
Better to polish the existing code, tests, and documentation during this week.
After the official close of GSoC, you are *very* welcome to work more; we would love to have all three of you students all year long! (We just can't pay you ourselves)
( This is all according to Google's timeline: www.google-melange.com/gsoc/events/...e/gsoc2013 ) 20:04
sa1 Payments are not a problem. I'll be done with my exams and then do some more work on this and then see what else I can do after that. 20:05
Util sa1: We will be glad to have you. 20:06
denis_boyun Util: ok, I will take a note your advice 20:07
Util Getting new long-term participants for our projects is the best part of GSoC for all the participating organizations.
denis_boyun: Great!
I am looking forward to next week's meeting, and a 100% successful conclusion to this year's GSoC.
GSoC students: Remember to post to Parrot.org and parrot-dev!
Anything else to discuss? (GSoC or not)
sa1 no
denis_boyun no 20:08
Util Thank you all for participating!
( You too, pmurias; Great work! )
Meeting adjourned.
Coke big thanks to all the GSOC students this semester, and to Util for driving. 21:05

Powered by Cro and the Raku® Programming Language.

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

Thank you!