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.
03:25 eternaleye joined 05:14 eternaleye joined 05:41 denisboyun joined 06:41 denis_boyun joined 09:52 denisboyun joined 12:10 denis_boyun_ joined 12:29 pmurias_ joined
pmurias_ What's done? 12:29
A cross compiling nqp-js (running on top of parrot) passes all tests in nqp/t/nqp with the exception of test 49 (which does an equivalent of eval, which would be really tricky do in a cross compiler).
It also passes the serialization tests in nqp/t/serialization.
It also passes the same tests as nqp-parrot in nqp/t/qregex.
We use a custom harness for those to avoid compiling regex at runtime.
A standalone nqp-js (compiled with a cross compiling nqp-js and using a setting compiled by a cross compiling nqp-js) passes most of the tests in nqp/t/nqp (it fails 5 of them).
During the program I also extended the nqp test suite, implemented nqp::shell on nqp-parrot.
What's missing?
Currently for building the nqp-js I'm keeping a nqp-compiler.nqp, which is basically the most of NQP concatenated into one file. The real nqp concatenates it files into 2 gigantic files.
My nqp-compiler.nqp doesn't currently register itself using the nqp::bindcomp ops correctly so it's failing the roles tests (url and url) as that's needed for roles.
Some bugs are making test 32 fail on the standalone compiler.
Test 49 needs loading of the compiler and runtime.
And test 55 has some problems with cloning multi methods.
As the standalone compiler had trouble with roles and multi methods I didn't get to create a bootstraped nqp-js (nqp-js compiled with standalone nqp-js). 12:30
Running in the browser is mostly a matter of figuring out how to load our pure JavaScript dependencies with RequireJS (or something similiar as I haven't got around to figuring that), and figuring out how to replace our bigint dependency.
The other none pure JavaScript dependencies are for stuff browsers don't support anyway.
What's next?
14:17 bluescreen joined 14:45 bluescreen joined 16:26 Tene joined 16:39 bluescreen joined
Util pmurias: Next, you can complete your Student Evaluation on Melange. 18:15
18:30 denisboyun joined 19:08 pmurias joined
pmurias Util: re What's next? - that was actually a title of a section of my project report ;) 19:18
Util: thanks for reminding be to do the evaluation ;)
Util pmurias: You are welcome. I came here straight from the Incomplete list on melange, so your pre-report above is all that I had read. 19:21
Oh, I see now. You were telling me that "What's next" was *not* a request for a task. 19:22
I though that you were saying that "complete your Student Evaluation on Melange" was listed by you on some other project report today (like maybe on Parrot.org).
pmurias Util: in pastie.org/pastes/8351242/text, I had a "What's next" section 19:24
Util pmurias: Thanks!
Pre-report: 19:26
# Doing:
* Prep work for GSoC end-game, and Mentor Summit.
* Resumed work on Flutter
+ github.com/Util/Flutter
.end
pmurias currently I'm creating a "trynqp" demo page (as masak++ suggested) (a page with a big textarea to compile nqp code to js and run it in your browser) 19:27
Util pmurias: Great! Please let us know when you have that working; I would love to play with it. 19:28
sa1 *Pre-report 19:30
** Minor documentation work this week.
** Work limited by ongoing exams
** Will create a final report soon.
pmurias: That's really nice work done. I admire it, and hope to take up tasks as challenging soon. 19:31
Util pmurias: FYI, ash_ had a Perl 6 version of that working a year or two ago. I think the host was run.perl6.org/ . Not working now, but maybe worth stealing from?
Notes to GSoC students: 19:32
1. This is the last time, but you still have to make posts to parrot-dev and Parrot.org today.
Please consider adding some text about your overall experience with GSoC,
and with our Parrot and Perl 6 communities.
2. Since some of you have expressed interest in continuing your work after the Pencils Down date,
your Required Code Samples may need some extra care to comply with the rules.
Please read the FAQ section of:
www.google-melange.com/gsoc/documen...guidelines
sa1 and denisboyun: Thank you for completing your student evaluations on Melange! 19:33
Hello! Who all is in attendance?
sa1 Hello
denisboyun Util: hi
Util denisboyun: Hi! Shall we give you a minute to make your report?
denisboyun Util: yes one minute please 19:34
Util OK
denisboyun # Done: 19:35
* update tests and documentation
* close a new issued from dukeleto
.end
sa1 So this was a very nice few months. Completing it successfully(I should wait for the evaluations) is very motivating for future work. 19:38
denisboyun I agree with sa1
Util I just received from your mentors that PASS evaluations are in your future for all three of you. 19:41
Assuming you finish your Parrot.org and parrot-dev posts, of course :^)
Is there anything remaining that you need help with? For example: Code Samples ?
sa1 Ah, nice to hear! :) I don't have an exam day after tomorrow, so after tomorrow's exam, I'll take out the time to write a final report. 19:42
I don't think so. I'll create a single diff file and submit. Is that okay?
Or should I submit the whole source code as a tar file? 19:43
denisboyun yes, it's cool.
Util sa1: Great! Good luck with your exam.
sa1 thanks.
Util sa1 and denisboyun: *read* the FAQ section I recommended above!
sa1 Util: I did. I was just following this: "Use your best discretion, or talk to your mentor about what's appropriate." :) 19:44
Util sa1: Ha! 19:45
denisboyun Util: what kind of faq section? What do you mean?
Util denisboyun: The FAQs of www.google-melange.com/gsoc/documen...guidelines 19:46
denisboyun Util: oook. thanks
Util sa1: Single or multiple diffs would be much better than a tarball of all the source, since you worked on pre-existing code.
sa1 Right. 19:47
Util A source tarball would be appropriate only if the whole codebase was your own work, *and* only work that you did during the GSoC period.
sa1 I was thinking that apart from a diff I should also include the code on which the diff is meant to be applied and mention it appropriately in the README. 19:48
So that they can get the code to run, if they want.
19:49 kshannon joined 19:50 Tene joined
sa1 The FAQ doesn't mention anything about ability of code sample to run independently, though. 19:50
Util sa1: I would give them the URL of the GitHub repo instead of the original codebase tarball. Part of why they need actual code submissions (I think) is for audit requirements on Work-For-Hire, a legal concept in the United States.
19:51 cotto joined
sa1 Right, I can always point them to the commit just before the program started. 19:51
Util They also probably want to examine the code *without* running it, to see the quality of your work, via your changes. Almost all of that can be perceived without the original source. 19:52
sa1 Yeah.
Util Oh, I left out a pre-report "Doing" item: 19:53
* Prepping the next release of Parrot.
.end
denisboyun Util: What is needing to write on final report? And when is the final term for that? 19:55
Util denisboyun: I am unclear on what you mean by "final report". Could you tell me more? 19:57
denisboyun sa1: said something about final report and i think that we need to write something final report:)))) 19:58
sa1 denisboyun: I just meant that it is the final time we are writing a report, and as such I will include a report of not just last week's stuff, but the project as a whole. 19:59
Util denisboyun: I think that sa1 meant that his posts to parrot-dev and Parrot.org will be much more extensive than his 3-line pre-report. 20:00
Util suffers from NetLag :(
denisboyun Util: ok, i'm sorry I misunderstood 20:01
Util denisboyun: Did that fully answer your question?
denisboyun Util: no
Util: yes
Util denisboyun: OK 20:02
Personally, I am very pleased with everyone's work this year.
This was my first year as a GSoC Org Admin; I enjoyed working with everyone (students and mentors), and I look forward to doing it again.
(or maybe mentoring next year) 20:03
I hope to see you all three back again next year,
but I also hope to work with you often between now and then!
sa1 yeah, me too
denisboyun Util: thanks and me 20:04
Util denisboyun: Thank you for all your contributions to our communities!
sa1: Thank you for all your contributions to our communities!
pmurias: Thank you for all your contributions to our communities!
pmurias thanks 20:05
Util Thanks also to Mentors dukeleto and pmichaud, and Cheerleader Coke. 20:06
sa1 also thanks Util for your extensive work here as admin.
Util You are very welcome.
Anything else to discuss? (GSoC or not)
sa1 no
denisboyun no
sa1 should get back to studying fluid mech for tomorrow. 20:07
denisboyun sa1: good luck with your exams
sa1 thanks denisboyun
Util These meetings will continue weekly for Parrot development. 20:08
It is slow right now, but I at least have a backlog of partial work and ideas,
and there are several branches that need finishing and merging of work done by people have have since left for MoarVM.
There is some very good work in those branches; we don't want to lose it. 20:09
Thank you all for participating!
Meeting adjourned.
20:09 Tene joined 21:19 bluescreen 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!