Mercurial > pylearn
diff doc/v2_planning/committees.txt @ 1006:49eea4953efe
job of each committee
author | Yoshua Bengio <bengioy@iro.umontreal.ca> |
---|---|
date | Thu, 02 Sep 2010 21:59:22 -0400 |
parents | 5753cd864356 |
children | 0ed99521bc45 |
line wrap: on
line diff
--- a/doc/v2_planning/committees.txt Thu Sep 02 18:03:25 2010 -0400 +++ b/doc/v2_planning/committees.txt Thu Sep 02 21:59:22 2010 -0400 @@ -1,11 +1,30 @@ List of committees and their members: -Python ML libraries investigation: GD, DWF, IG, DE -Dataset interface: DE, OB, OD, AB, PV -Learner: AB, PL, GM, IG, RP -Optimization: JB, PL, OD -Inference/sampling: JB, GD, AC -Job management, analysis, metrics, costs, visualization: GD, FS, PL, XM -Formulas/tags: FB, NB, RP, AC, OB -Coding style: DE, OD, DWF, FB +* Existing Python ML libraries investigation: GD, DWF, IG, DE +* Dataset interface: DE, OB, OD, AB, PV +* Learners: AB, PL, GM, IG, RP +* Optimization: JB, PL, OD +* Inference/sampling: JB, GD, AC +* Job management, analysis, metrics, costs, visualization: GD, FS, PL, XM +* Formulas/tags: FB, NB, RP, AC, OB +* Coding style: DE, OD, DWF, FB + +Issues to be tackled in the future: +* serialization & reproducibility +* job management, results analysis, metrics & costs, visualization +* GPU portability +* social engineering, code review and incentives + +Job of each committee: + +* name a leader +* create a text file in this directory associated with their discussion +* discuss the issues, write them down in this file +* come up with an interface, protocol, or recommendations +* bring up the issues and recommendations to the rest of the group, and get feedback +* make sure the recommendations fit with other committees recommendations +* update the discussion / recommendation file +* implement documentation for these conventions in python or proper doc files as appropriate +* implement one or a few examples that show what is typically expected +