Difference between revisions of "20090415Agenda"

From LinuxMCE
Jump to: navigation, search
(0810 Short Term Goals)
m
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:Development]]
 
==Logistics==
 
==Logistics==
This meeting will be held on IRC.
+
*This meeting happened
*Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting
+
**[[20090415Transcript|Transcript]]
*Date: TBD
+
**[[20090415Minutes|Minutes]]
*Time: TBD
+
*Agenda
*Duration: TBD
+
**It is expected that meeting participants will be familiar with this agenda and the resources it links to
*Server: irc.freenode.net
+
**Any one may add to the agenda - just put your name next to the topic
*Channel: TBD
+
*Time and Place
 +
**This meeting will be held on IRC.
 +
**'''Date:''' Wednesday, April 15
 +
**'''Time:''' 2PM GMT (4PM Berlin, 10AM New York, 7AM Los Angeles)
 +
**'''Duration:''' 1.5 hour maximum
 +
**'''Server:''' irc.freenode.net
 +
**'''Channel:''' #linuxmce-devel
  
 
==Agenda==
 
==Agenda==
Line 13: Line 20:
 
*Status review of each component (including review of defects marked at least major, or of special interest)
 
*Status review of each component (including review of defects marked at least major, or of special interest)
 
**DCERouter
 
**DCERouter
 +
***No major bugs
 
**Orbiter
 
**Orbiter
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/153 #153]: RA button on orbiters/on-screen orbiters crashes the orbiter
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/160 #160]: JavaMO.jar missing for build
 +
***[Compile error in Orbiter_Plugin #9]: Compile error in Orbiter_Plugin
 
**Media Playing
 
**Media Playing
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/40 #40]: MAME Integration (blocker/defect)
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/142 #142]: Added ability to brows/play files directly from a data CD/DVD (feature with patch - Itsik)
 
**Xine
 
**Xine
 +
***No major bugs
 
**MPlayer
 
**MPlayer
 +
***No major bugs
 
**MythTV
 
**MythTV
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/124 #124]: MythTV Plugin needs to use the new MythTV Storage Groups
 
**VDR
 
**VDR
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/54 #54]: Initial vdr config errors
 
**Lighting,Climate
 
**Lighting,Climate
 +
***No major bugs
 
**Setup and AV Wizard
 
**Setup and AV Wizard
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/27 #27]: Create Diskless Boot Image (blocker)
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/166 #166]: Automatic MD creation (blocker)
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/150 #150]: hardy entry ends up in the sources.list
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/167 #167]: pluto-blutooth-dongle does not automatically install when USB dongle inserted
 
**Web Admin
 
**Web Admin
*Review of other topics as they arrise
+
***[http://svn.linuxmce.org/trac.cgi/ticket/119 #119]: IR / GSD codes bugs
 +
**Telephony
 +
***No major bugs
 +
**Other
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/26 #26]: New installer (blocker)
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/101 #101]: cleancore script bugs (blocker)
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/48 #48]: Launch Manager rewrite to be CLI only (no QT dependancy)
 +
***[http://svn.linuxmce.org/trac.cgi/ticket/107 #107]: Backup system does not backup all relevant parts
 +
*Review of other topics as they arise
  
 
===0810 Short Term Goals===
 
===0810 Short Term Goals===
Line 29: Line 59:
  
 
===0810 Release Scheduling===
 
===0810 Release Scheduling===
jondecker76 - we should also discuss update scheduling for after 0810 is released, as well as the frequency of the updates. Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.
+
*Should 0810 have a "formal" release schedule?
 
+
**Consider these sources as examples
===Review of Outstanding Defects===
+
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]
 +
***[http://live.gnome.org/Schedule Gnome]
 +
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]
 +
**What milestones apply?
 +
***Feature Freeze?
 +
***Code Freeze?
 +
***Beta release deadline?
 +
***General release deadline?
 +
*0810 Update release schedule (jondecker76)
 +
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates.  
 +
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.
  
 
===High Level Design Discussions===
 
===High Level Design Discussions===
jondecker76 - Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's (who knows if and/or when plutohome.com will disappear along with the script that is currently used). Since we are our own entity at this point and very active in changing the direction of LMCE, I'd also like to see us start all over with installtion ID #1 starting with 0810. This will cleanly separate us from pluto and provide insurance that we can continue to assign new installation ID's in the future (especially important once linking installations is possible). Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. This change can be made in a matter of an hour.
+
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)
 +
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used.  
 +
**Since we are our own entity at this point and very active in changing the direction of LMCE, I'd also like to see us start all over with installation ID #1 starting with 0810.  
 +
**This will cleanly separate us from pluto and provide insurance that we can continue to assign new installation ID's in the future (especially important once linking installations is possible).  
 +
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script.  
 +
**This change can be made in a matter of an hour.
 +
 
 +
===Procedural Changes===
 +
*Discuss 501(c)(3) filing
 +
*Discuss LinuxFund
 +
*Discuss efforts to improve defect tracking methods (jimbodude)
 +
**Discuss ways to make sure all defects are reported
 +
**Discuss ways to make sure all reported defects are addressed in a timely manner
 +
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy
 +
*Discuss effectiveness of future meetings
 +
**Decide whether to have more
 +
**Discuss meeting frequency
 +
**[http://www.freeaudioconferencing.com/services.php Voice chat]? - (Cylon7)
 +
**Schedule next meeting

Latest revision as of 14:01, 23 August 2009

Logistics

  • This meeting happened
  • Agenda
    • It is expected that meeting participants will be familiar with this agenda and the resources it links to
    • Any one may add to the agenda - just put your name next to the topic
  • Time and Place
    • This meeting will be held on IRC.
    • Date: Wednesday, April 15
    • Time: 2PM GMT (4PM Berlin, 10AM New York, 7AM Los Angeles)
    • Duration: 1.5 hour maximum
    • Server: irc.freenode.net
    • Channel: #linuxmce-devel

Agenda

0810 Progress Review

  • Status review of each component (including review of defects marked at least major, or of special interest)
    • DCERouter
      • No major bugs
    • Orbiter
      • #153: RA button on orbiters/on-screen orbiters crashes the orbiter
      • #160: JavaMO.jar missing for build
      • [Compile error in Orbiter_Plugin #9]: Compile error in Orbiter_Plugin
    • Media Playing
      • #40: MAME Integration (blocker/defect)
      • #142: Added ability to brows/play files directly from a data CD/DVD (feature with patch - Itsik)
    • Xine
      • No major bugs
    • MPlayer
      • No major bugs
    • MythTV
      • #124: MythTV Plugin needs to use the new MythTV Storage Groups
    • VDR
      • #54: Initial vdr config errors
    • Lighting,Climate
      • No major bugs
    • Setup and AV Wizard
      • #27: Create Diskless Boot Image (blocker)
      • #166: Automatic MD creation (blocker)
      • #150: hardy entry ends up in the sources.list
      • #167: pluto-blutooth-dongle does not automatically install when USB dongle inserted
    • Web Admin
      • #119: IR / GSD codes bugs
    • Telephony
      • No major bugs
    • Other
      • #26: New installer (blocker)
      • #101: cleancore script bugs (blocker)
      • #48: Launch Manager rewrite to be CLI only (no QT dependancy)
      • #107: Backup system does not backup all relevant parts
  • Review of other topics as they arise

0810 Short Term Goals

  • Defects to address
  • Features to implement

0810 Release Scheduling

  • Should 0810 have a "formal" release schedule?
  • 0810 Update release schedule (jondecker76)
    • Discuss update scheduling for after 0810 is released, as well as the frequency of the updates.
    • Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.

High Level Design Discussions

  • Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)
    • Who knows if and/or when plutohome.com will disappear along with the script that is currently used.
    • Since we are our own entity at this point and very active in changing the direction of LMCE, I'd also like to see us start all over with installation ID #1 starting with 0810.
    • This will cleanly separate us from pluto and provide insurance that we can continue to assign new installation ID's in the future (especially important once linking installations is possible).
    • Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script.
    • This change can be made in a matter of an hour.

Procedural Changes

  • Discuss 501(c)(3) filing
  • Discuss LinuxFund
  • Discuss efforts to improve defect tracking methods (jimbodude)
    • Discuss ways to make sure all defects are reported
    • Discuss ways to make sure all reported defects are addressed in a timely manner
    • Consider re-working current work into LinuxMCE/Trac specific policy
  • Discuss effectiveness of future meetings
    • Decide whether to have more
    • Discuss meeting frequency
    • Voice chat? - (Cylon7)
    • Schedule next meeting