Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chromatic (983)

chromatic
  (email not shown publicly)
http://wgz.org/chromatic/

Blog Information [technorati.com] Profile for chr0matic [technorati.com]

Journal of chromatic (983)

Wednesday September 03, 2008
01:53 AM

Perl 6 Design Minutes for 30 July 2008

[ #37333 ]

The Perl 6 design team met by phone on 30 July 2008. Allison, Jerry, Will, Jesse, and chromatic attended.

Allison:

  • OSCON was a success
  • now I'm completely free from all responsibilities until at least December
  • launched the PIR PDD
  • now working on the last few failing language tests before I merge back the concurrency branch
  • also spent some time talking to PhD advisors at Cambridge this week
  • might start fall 2009, if I can get funding and such
  • leaving for London on Saturday
  • speaking at the BBC on Tuesday
  • may miss next week's meetings

c:

  • was very busy with OSCON
  • trying to apply a few patches
  • trying to get other people to the place where they can help with that
  • mostly I need tasks I can do in 30 minutes when I can grab an hour or two
  • fixed some small stuff at the hackathon

Allison:

  • I need to split up the MMD PDD into bite-sized tasks

Jerry:

  • OSCON was fabulous
  • our talk was successful
  • good feedback and enthusiasm
  • the lighting talks with Jeff were successful
  • most of my hacking was on mod_parrot
  • trying to refactor its configure system into something more robust and portable
  • it's just about working in the same state it was before
  • hope to reach that point this afternoon
  • met with some folks at Microsoft's open source lab on Monday
  • promising beginning to a relationship between them and the Parrot Foundation
  • the hackathon was productive as well

Jesse:

  • I talked to some Sun people about what makes CPAN tick

Will:

  • mostly absent the past couple of weeks
  • trying to resurrect Tcl, which was untouched for some time
  • making progress there on spec tests
  • identifying what's left to do

c:

  • what's our roadmap look like for the rest of the year?

Jesse:

  • I asked Patrick about that
  • he said there's a good chance to get that from the hackathon
  • if not, he said I could get his attention at YAPC and get his milestones to break down soon

Jerry:

  • he spoke on IRC about that today
  • he wants to break it down into better granularity and put dependencies between tasks
  • have a feeling it'll happen at YAPC::EU
  • Jonathan is keen to get together with Allison and Patrick there to discuss related designs

c:

  • I've noticed projects in Parrot like Reini's attempt to get installation and loading sorted out
  • seems like time to get those sorted out

Jerry:

  • it's difficult to have willing volunteers and not get them the right guidance
  • and to make "eventually" now

c:

  • thinking we should ask Reini for a list of concerns, needs, and use cases
  • then try to make a design that addresses more of those

Jerry:

  • especially as he's about to leave on a two-week business trip
  • sounds like a PDD to me

Allison:

  • sounds like several

Jerry:

  • library loading, runtime components

c:

  • does he have commit access?

Jerry:

  • we can encourage him to apply

c:

  • thinking about bindings to Prophet
  • probably client-side

Jerry:

  • we need sockets

Will:

  • we have experimental sockets
  • we need to make tickets or mark up PDDs for unimplemented things
  • I did some of that with PDD 19 today
  • stuff's deprecated and only exists in the PDD
  • just to warn people who are going to write code that docs don't match reality

Jerry:

  • that merits a CAGE task for reviewing the PDDs
  • we could spread that out among many people

Will:

  • I'll send an email

c:

  • and post it on parrotblog

Will:

  • no one reads those

c:

  • they won't if we don't publish them

Jesse:

  • I see them posted places like Reddit fairly often

Allison:

  • probably will roll that into parrot.org eventually
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.