From Fedora Project Wiki

(Clarify purposes)
(Firm up plan)
Line 17: Line 17:


== Plan ==
== Plan ==
# Location possibilities
# '''Location:'''  Fredericksburg, VA
#* Chicago, IL
# '''Date:''' Sept 10-12 (Fri-Sun)?
#* Fredericksburg, VA
# '''Schedule'''
# Date possibilities
#* Participants arrive Day 0-1 (Thu/Fri)
#* Next to Summit, in Chicago, August 29-30 (Sat-Sun)?
#* Hack on Day 1-2 (Fri/Sat)
#* Week after, in F'burg, Sept 11-12 (Fri-Sat)?
#* Participants leave Day 3 (Sun)
# Schedule
#* Participants arrive Day 0
#* Hack on Day 1-2
#* Participants leave late Day 2 or 3
# Important skills (one or more)
# Important skills (one or more)
#* Asterisk
#* Asterisk
Line 39: Line 35:
#* John Poelstra (OR)
#* John Poelstra (OR)
#* (infrastructure person?)
#* (infrastructure person?)
#* ''others?''
#* ''others? (Ian Weller, ...)''
# Other considerations
# Other considerations
#* Jared needs as much advance notice as possible.  His October is much busier than September right now.
#* Jared needs as much advance notice as possible.  His October is much busier than September right now.
#* Jared can better do a weekend if he's out of town.
#* Jared can better do a weekend if he's out of town.
#* May need to bring this in very cheaply, meaning minimize travel costs overall: play it by the numbers.
#* May need to bring this in very cheaply, meaning minimize travel costs overall: play it by the numbers.

Revision as of 21:18, 27 July 2009

Purpose

  1. To code-sprint our way to a better Fedora Talk system, complete with the following primary goals:
    • On-demand recording and publishing (or at least dumping into a holding pen)
    • Streaming capability for live events (it completely works + documentation on exactly how to set it up and operate at a live events)
  2. In addition, we will attempt to complete the following secondary goals as time allows:
    • On-demand conference room setup and teardown
    • More control over conference room details (moderation, muting, etc.)
    • Better web interface for some limited functionality
  3. To spread knowledge and awareness of the Asterisk system's capabilities among a pool of people empowered to continue improvements in the future.
  4. Document configuration of various clients. Jared will bring a suitcase full of different phones to assist in documenting configuration of clients.

Prerequisites

  • Need at least one subject matter expert
  • Possibly a publictest instance for testing
  • A venue to host (Fredericksburg, VA!)
  • A couple O'Reilly Asterisk books sent to participants 30 days ahead, with reading recommendations

Plan

  1. Location: Fredericksburg, VA
  2. Date: Sept 10-12 (Fri-Sun)?
  3. Schedule
    • Participants arrive Day 0-1 (Thu/Fri)
    • Hack on Day 1-2 (Fri/Sat)
    • Participants leave Day 3 (Sun)
  4. Important skills (one or more)
    • Asterisk
    • Python
    • TurboGears
    • GStreamer
    • Planning/design
  5. Personnel (people who might fit the bill)
    • Jared Smith (VA)
    • Paul Frields (VA)
    • Jeff Ollie (IA)
    • John Poelstra (OR)
    • (infrastructure person?)
    • others? (Ian Weller, ...)
  6. Other considerations
    • Jared needs as much advance notice as possible. His October is much busier than September right now.
    • Jared can better do a weekend if he's out of town.
    • May need to bring this in very cheaply, meaning minimize travel costs overall: play it by the numbers.