|
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 14 May 2013. |
|||
|
02:25
Coke joined
02:43
quias joined
02:44
contingencyplan joined
03:41
jlaire joined
06:06
contingencyplan joined
08:39
quias joined
10:15
wagle joined
12:11
darbelo joined
13:04
bluescreen joined
13:07
bluescreen_ joined
18:37
darbelo joined
18:40
contingencyplan joined
19:17
bluescreen_ joined
|
|||
| Util | Pre-report: | 19:29 | |
| # Done: | |||
| * Several small improvements to the release process. | |||
| # Doing: | |||
| * Releasing Parrot 5.4.0: "Austin Parrot" | |||
| + (for Austin,TX [host of hackathon] and Austin Powers [who comes from the Summer of Love]) | |||
| # Happenings: | |||
| * GSoC: | |||
| + Today is an unofficial deadline for selecting proposals and officially matching them to mentors. Tomorrow, Google will start "deduplication", which can't work without commitment of slots and mentors. Hence the pressure to commit earlier than the official deadline of the 23rd. | |||
| + FYI: pmichaud has been alerted that he is not showing up as a mentor. If anyone else thinks that they are mentoring, but are not able to vote on proposals on the Melange system, contact me or dukeleto ASAP, because you are *not* a mentor until you sign up. | |||
| + Looking at the average scores, 3 proposals are clear front-runners. We are not yet supposed to let the students know their status, so if their is any discussion needed that is not in the private comments on Melange, then please speak up, and we will have a quick meeting in another channel. | |||
| + If there is no discussion or issue, then assume that we will give our three slots to the proposals with the highest averages (though skipping any whose for whom no Mentor can be found). | 19:30 | ||
| + In past #ps meetings, I have mentioned email-list discussion of GSoC proposals. I was later advised to use Melange instead, to restrict participant access to private comments between mentors and admins. While I prefer to "let the sun shine in", Google is hosting this party, and I have acceded to their desire. | |||
| .end | |||
| Hello! Who all are in attendance? | 19:31 | ||
| sa1 | Util: hello | 19:36 | |
| Hmm, brrt had some interest in becoming my co-mentor | |||
| I wonder if he registered as one. | 19:37 | ||
| Util | Hi, sa1. I am going to nudge the #perl6 channel, to see if GSoC discussion is needed by them. | ||
| sa1 | okay | ||
| Util | sa1: brrt was sent a Mentor request (by me from Melange), but Melange says "User Action Required", so he must now have responded yet. | 19:39 | |
| PerlJam | Util: how many mentors are there? (just curious) | ||
| (in melange) | |||
| sa1 | Util: ok | 19:40 | |
| Util | PerlJam: 4 registered mentors, plus 2 admins that might fill in for mentors, plus brrt who said he would but has not replied, plus pmichaud who said he would but was only just now informed of the need to register. | 19:41 | |
| PerlJam | And 3 slots, right? sounds like a good ratio. | 19:43 | |
|
19:43
moritz joined
|
|||
| Util | PerlJam: In general, yes, but not every mentor is automatically qualified to help in every task. | 19:44 | |
| For example, I can help with lots of areas of Parrot, but tasks involving NCI need to have a primary mentor that knows NCI. | 19:46 | ||
| sa1: Your proposal is in good shape, IMO. Has their been any update or discussion about it this past week? | 19:53 | ||
| sa1 | Util: I asked some questions about it. dukeleto asked me to forward it to the list, which I did. | ||
| dukeleto answered one question, but I am waiting for more replies. | 19:54 | ||
| Util | sa1: I see it now. Which question was answered? | 19:56 | |
| sa1 | He told me that a PMC was an object basically. | 19:57 | |
| Which I figured out, but I needed more details. | 19:58 | ||
| He told me that others on the list can answer some questions better, but I hope he does reply with more detail in a while. | 19:59 | ||
| Util | Right, Parrot has 32 machine registers for each or 4 types: Int, Num, String, and PMC. | ||
| See src/pmc/*.pmc and src/dynpmc/*.pmc for all the object types that come with Parrot. | |||
| Client languages (like Rakudo) can add their own DynPMCs. | |||
| Non-dynamic PMCs have to be built into Parrot. | 20:00 | ||
| For later readers, sa1's post to parrot-dev is Subject: Fwd: NCI questions | 20:01 | ||
| sa1 | Hmm, okay. The NCI page says "If this is a return type and the value is NULL, PMCNULL is returned, otherwise parrot will create a new UnManagedStruct PMC type, which is just a generic "pointer to something" PMC type which Parrot does no management of. " | ||
| What does this mean and how will it affect things? | 20:02 | ||
| If there is no management e.g, do I have to add destructors? | |||
| We can continue discussion on #parrot if that is more suitable. | 20:03 | ||
| I see the .pmc's now. I will have to read them. | 20:05 | ||
| Util | sa1: It would depend on what underlying C function you were calling, just like it would if you were calling from C. If the docs for the function say "use function 'release_some_git_memory()' to free the structure returned', then you have to do that, etc | ||
| sa1 | Right, makes sense | 20:06 | |
| Util | It might be that the pointer is only valid until some point in the future when other calls to Git C functions clobber it's contents, and you have to copy what you want from the pointer before it gets overlayed or reused. I just don't know the Git C API. | 20:07 | |
| Parrot can't do better that an UnManagedStruct, because Git has no notion of the internals of a Parrot PMC, and so cannot populate a PMC itself. | 20:08 | ||
| sa1 | right | 20:09 | |
| PerlJam | sa1: btw, do you know about the PDDs ? | ||
| sa1 | PerlJam: I read this: docs.parrot.org/parrot/devel/html/d...l.pod.html | ||
| PerlJam | okay, just checking. There's often useful info in the parrot design docs even if some of it is dated. | 20:10 | |
| (or considered "draft") | |||
| sa1 | I can't find any existing destructors in current parrot-libgit2. I will see the git api to see when they are required to be freed. | 20:12 | |
| Util | We are past 30 minutes, and conversation of this detail should be moved to #parrot. | ||
| (which can occur in parallel; don't let us slow you down sa1, just pick it up in #parrot). | |||
| Any other discussions? | |||
| sa1 | no | 20:13 | |
| Util | OK then, Meeting Adjourned, and Thanks to all participants! | 20:17 | |
|
21:58
darbelo joined
23:16
darbelo joined
|
|||