Version 28 (modified by solj, 13 years ago) (diff)

Add some tickets for upcoming sprint

Upcoming sprints

when: sometime during weekend of February 6-7, 2010 10AM CST-4PM CST (when is this in my time zone?)
where: #bcfg2 on freenode, ANL


Documentation Updates

In general, we should try and flesh out the sphinx docs as much as possible. A good start would be getting all the unsorted documents transferred over to sphinx.

Other things that are still needed:

  • Elaborate a little more on new SSL authentication options
  • bcfg2-info docs and possibly an in depth howto for developers
  • how-to for using bcfg2-info to debug
  • Ohai plugin usage and examples


  • SSL CA plugin (maybe come up with a design specification?)
  • Add support for per-plugin info/info.xml files


  • #816 - Upstart script for lucid (+ client tool if needed)
  • #733 - Packages support for modifying auto update
  • #773 - Allow for APT client tool customization
  • #819 - Add timestamp to client tool log
  • #710 - Output multiple variables from a single probe
  • #770 - Fix snapshots postgres compatibility
  • #754 - plugin for checking out code from some sort of VCS


Future sprint ideas

  • Do a pure user doc book sprint - the the Book Sprints book talks about how to go about running an "extreme book sprint" where a book is completed in around a week (the Command Line Intro book was mostly done in a weekend).