[Epo-extended-core] Working Group Charter

Cory Watson jheephat at gmail.com
Wed Jan 14 15:56:54 GMT 2009


On Thu, Jan 8, 2009 at 10:13 PM, Chris Prather <perigrin at gmail.com> wrote:

>
> * List of reccomeded Modules with reviews as to *why* they're reccomeded.
> * A "Task::EPO-EC" module that defines the Extended Core Modules and
> allows one to Bootstrap off CPAN
> * A workable plan on how to build a EPO-EC Perl Distribution
> * List of secondary modules that *should* be in future EPO-EC but
> cannot yet currently for specific reasons
> * List of *specific* ways the EPO can help the secondary List be
> promoted to the EPO-EC
>

Additional item:

* Identify domains that need modules chosen and establish a process for
ongoing maintenance of these domains.

Idea being that we don't want to "pick a module for everything on CPAN".

The idea is that these "problem domains" are focused on the corporate usage
of perl.  Part of the process should be determining if the average corporate
shop cares about the problem domain and, if so, we add it to the set.  If
it's not something that we expect such shops to use, we can either leave it
be or pass it to a more specific WG (Chris' used BIOPERL as an example of a
specific offshoot of this idea).

-- =

Cory 'G' Watson
http://www.onemogin.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/epo-extended-core/attachments/20090=
114/aade1514/attachment.htm


More information about the Epo-extended-core mailing list