Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Add info about expert list for vetting.

  • Loading branch information...
commit 2e15777d8c94d37b88c2782f10c5c079eca273e0 1 parent 1b9024b
Cory Watson authored
Showing with 13 additions and 9 deletions.
  1. +13 −9 documents/charter.txt
View
22 documents/charter.txt
@@ -26,14 +26,19 @@ Deliverables
------------
1. List of Domains that the EPO-EC will cover.
-2. List of recommended Modules with reviews as to *why* they're recommended.
-3. List of secondary modules that *should* be in future EPO-EC but cannot yet
-currently for specific reasons
-4. List of *specific* ways the EPO can help the secondary List be promoted to
+2. List of recommended Modules.
+3. Create list of community "leaders" (high-level positions at companies or
+major contributors to the community, experts in a domain) that can "vet" our
+lists.
+4. Validate Module list with community leader "reviews" as to *why* they're
+recommended.
+5. List of secondary Modules that *should* be in future EPO-EC but cannot yet
+currently for specific reasons.
+6. List of *specific* ways the EPO can help the secondary List be promoted to
the EPO-EC
-5. A "Task::EPO-EC" module that defines the Extended Core Modules and allows
+7. A "Task::EPO-EC" module that defines the Extended Core Modules and allows
one to Bootstrap off CPAN
-6. A workable plan on how to build a EPO-EC Perl Distribution
+8. A workable plan on how to build a EPO-EC Perl Distribution
Timeline
--------
@@ -42,11 +47,10 @@ Timeline
2. March 24: Lists of Modules, Recommendations and initial Task::EPO (2-5)
3. April 24: Update of Task EPO
4. May 24: Update of Task EPO
-5. May 30: Alpha/Beta release of EPO-Dist (6)
-6. June 24: Update of Task EPO,
+5. May 30: Alpha/Beta release of EPO-Dist (7)
+6. June 24: Update of Task EPO
7. July 24: Update of Task EPO
8. August 24: Update of Task EPO
9. September 24: Update of Task EPO
10. September 30: Release of EPO-Dist
-
Please sign in to comment.
Something went wrong with that request. Please try again.