On Mon, Dec 10, 2007 at 04:37:31PM +0200, Allison Randal wrote: > >> > s[...]. It probably makes the > most sense to repeat the group drafting strategy we're using with the PIR > PDD. You and others can help pull together the draft PDD, and I'll > review/revise/approve it as it reaches a relatively solid state. We can > also also talk back and forth about ideas on the mailing list as it > solidifies. > > There are two parts of the group drafting task: documenting how the system > works now, and documenting how you would like it to work. Documenting the > functions in embed.h is a great place to start.
> At the moment, chromatic or I would start exactly where you'll be starting: > sitting down with the code, extracting a list of current > functions/features, and at the same time keeping an eye out for missing > features, misfeatures, or other places in need of improvement. So, if you > or others are willing to take a first stab at it, it would be enormously > helpful. (It's also a great way to gain experience with parrot.) I'm delighted that Jeff's offered to help. Jeff, how do you want to proceed? >> Meanwhile there's some housekeeping I can be getting on with. >> Like fixing the broken Makefile.PL (seems best to make it a wrapper for >> the working Build.PL) > > Actually, what we'd like to do is eliminate the Module::Build dependency, > and integrate the build process for Parrot::Embed into Parrot's build > process (which is all Makefiles). Okay. Will do. Tim. p.s. How do I get a commit bit? Or should I just post patches for now?
