standard seed libraries (postgres, opengl, etc)

[allison]

Improve existing libraries for Postgres, OpenGL, etc, so they are reliable, and relatively feature complete.

Explore other libraries that we should provide by default in a full Parrot install.

The goal is to provide a small set of working libraries, both as an example to other library implementors, and to make it easier for average developers to tackle everyday tasks in Parrot. The set of seed libraries can be small, and libraries already implemented in an existing HLL are reasonable to satisfy the "everyday tasks" goal.

[allison]

The suggested seed library for 1.6 is zlib. This is a non-critical task and not a blocker for release.

[coke]

Bumping milestone to 2.0; This should be reviewed in light of the recent roadmap meeting.

[whiteknight]

This ticket seems too vague to me. I suggest we break it up into the following:

• Tickets to improve existing libraries that are suffering incompleteness or bitrot
• One ticket to define a list of such seed libraries that we would like to have interfaces for
• One ticket per library on the list

Also, we should figure out whether we want to supply library wrappers in the Parrot repo directly, or if these should be externally-hosted projects.

[dukeleto]

+1 to splitting this up the way whiteknight++ has described.

+1 to making bindings/wrappers external and easily installed via Plumage.

[doughera]

Is plumage going to be part of parrot 2.0? In the parrot-1.9.0 sources, plumage is only mentioned in two files: DEPRECATED.pod and runtime/parrot/library/distutils.pir.

[jkeenan]

Allison,

Would you be able to assess where we stand in relation to this ticket, e.g., which parts have been satisfied and which have not been?

Thank you very much.

kid51