http://wiki.linuxmce.org/api.php?action=feedcontributions&feedformat=atom&user=JimbodudeLinuxMCE - User contributions [en]2026-07-21T21:12:04ZUser contributionsMediaWiki 1.44.0http://wiki.linuxmce.org/index.php?title=Known_Issues&diff=22761Known Issues2010-04-01T23:47:33Z<p>Jimbodude: </p>
<hr />
<div>[[Category: Known Issues]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
== Known issues with LinuxMCE 0810 ==<br />
*[[LinuxMCE-0810_beta|Known issues with 0810 Beta]]<br />
<br />
== Known issues with LinuxMCE 0710 ==<br />
*[[Known_Issues_0710|Known issues with 0710 RC2]]<br />
*[[Known_Issues_0710_RC1|Known issues with 0710 RC1]]<br />
*[[Known_Issues_0710_Beta4|Known issues with 0710 Beta4]]<br />
*[[Known_Issues_0710_Beta3|Known issues with 0710 Beta3]]<br />
<br />
== Known issues with LinuxMCE 0704 ==<br />
<br />
*[[Known_Issues_0704|Known issues with 0704]]<br />
<br />
== Known issues with LinuxMCE 1.1 ==<br />
<br />
*[[Known_Issues_11Beta|Known issues with LinuxMCE 1.1 Beta]]<br />
<br />
== Known issues with LinuxMCE 1.0 ==<br />
<br />
*[[Known_Issues_LinuxMCE10|Known issues with LinuxMCE 1.0]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=LinuxMCE&diff=22760LinuxMCE2010-04-01T23:45:03Z<p>Jimbodude: /* Telecom */</p>
<hr />
<div>[[Category: Documentation]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
==Core==<br />
<br />
The '''Core''' is the heart and brain of the LinuxMCE system. The [[Core]] is a single PC acting as a dedicated server and interface for all the sub-components. The Core includes a plug-and-play back-end, so it listens for and auto configures all sorts of devices, like network audio players (e.g. Squeeze Box), IP phones and cameras. The Core can automatically provide a network boot for thin-client PCs (which can then be used as [[Media Directors]]). A Media Director is hooked up to your TV or stereo and becomes an integrated media player, PVR, video conferencing, intercom and portal to monitor and control everything in the home. All Media Directors work together seamlessly as a whole-house solution. <br />
<br />
[[Core|More about the Core]]<br />
<br />
==Orbiters==<br />
<br />
'''Orbiters''' are high-tech remote controls. LinuxMCE allows a wide variety of devices to function as Orbiters. Ordinary laptops, wireless tablet PCs, PDAs, mobile phones running Symbian or Microsoft Mobile, or any PC with a web interface that is able to connect to your LinuxMCE LAN can be used as an Orbiter.<br />
<br />
[[Orbiters|More about Orbiters]]<br />
<br />
==Media Directors==<br />
<br />
A '''Media Director''' (also known as a '''Media Station''') is a dedicated PC that streams music and video from the Core to your TV and speakers for an awesome multimedia experience. You can even use it as a Kubuntu PC, right on your TV!<br />
<br />
[[Media Directors|More about Media Directors]]<br />
<br />
==Network Attached Storage (NAS)==<br />
<br />
You can extend your Core's storage with an NAS device. LinuxMCE can recognize it and automatically integrate it into the system. Use the NAS for file storage, including your music and video collection, or for PVR functions.<br />
<br />
[[Network Attached Storage|More about NAS]]<br />
<br />
==Security==<br />
<br />
'''Security''' is a big part of LinuxMCE. Functions include light control, surveillance camera monitoring, and motion detection. Events can be triggered based on detected motion. It can send alerts to your mobile phone. It can set your alarm based on different schedules and scenarios. It can even lock the door when you leave your home.<br />
<br />
[[Security|More about Security]]<br />
<br />
==Telecom==<br />
<br />
'''Telecom''' is integrated into LinuxMCE in a sophisticated fashion. The VoIP system provides great flexibility. Each member of your family may have his/her own personal voice mailboxe. The system can keep track of where you are in your home and route incoming calls to the nearest phone (or to your mobile phone when you're not at home). Incoming calls automatically pause media, allowing you to take calls without interrupting your relaxation time.<br />
<br />
[[Telecom|More about Telecom]]<br />
<br />
==Home Automation==<br />
<br />
The '''Home Automation''' features of LinuxMCE are convenient and energy-efficient. With Home Automation you can control lights, climate and even the whereabouts of music or video played in your home. Mobile phones can also be turned into remote controls for your entire house.<br />
<br />
[[Home Automation|More about Home Automation]]<br />
<br />
==Multimedia==<br />
'''Multimedia''' in LinuxMCE is always available throughout your house. If you have more than one home, you can even join the homes together into a single multimedia/home automation system. Your media will follow you everywhere you go. It will even show your video files on the device closest to you, even if you go from one room or home to another!<br />
<br />
[[Usage_Intro#Managing_your_media|More about Multimedia]]<br />
<br />
==Personal Computing==<br />
'''Personal Computing''' can be done in LinuxMCE. After all, there's an ordinary PC with Kubuntu Linux running in the background, complete with Office suites and all the programs you need for everyday use.<br />
<br />
[[Personal Computing|More about Personal Computing]]<br />
<br />
==Building a new Home around LinuxMCE==<br />
Linux MCE is the ultimate '''smart home'''. With proper planning, a new construction home can integrate LinuxMCE as the brains of the house. <br />
<br />
In the past, a Home Entertainment Center would house a Home Theater PC. With LinuxMCE, the Core server and all communications hubs can be kept in a separate area. This makes home construction easier, allows centralization of data services, and allows for updating the home automation and multimedia system without altering the Home Entertainment Center in your living room.<br />
<br />
[[Building_a_new_Home_around_LinuxMCE|More about Home Construction using LinuxMCE]]<br />
<br />
==What can I do with LinuxMCE?==<br />
<br />
[[What_can_I_do_with_LinuxMCE%3F|What can I do with LinuxMCE?]]<br />
<br />
Also see: [[:Category:Tutorials|Tutorials Category]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=Main_Page&diff=22759Main Page2010-04-01T23:41:36Z<p>Jimbodude: </p>
<hr />
<div>[[Category: Main]]<br />
__NOTOC__ __NOEDITSECTION__<br />
<div align="center"><br />
<div style="font-size:175%; font-weight:bold">The '''[http://linuxmce.org LinuxMCE]''' wiki</div><br />
'''Your guide to a smarter home!'''<br />
</div><br />
<br />
<br />
{| style="clear: both; border: 1px solid #aaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.5em; float: right; text-align:center"<br />
|'''Screenshots'''<br />
[[Image:MainMenu2.jpg|200px]]<br/><small>Main menu with media in the background<br>(high resolution [[Selecting_the_Right_UI#UI2_with_alpha_blending|UI2B]])</small><br/><br/><br />
|-<br />
|[[Image:FileBrowserUI1.jpg|200px]]<br/><small>Browsing media files<br>(low resolution [[Selecting_the_Right_UI#UI1|UI1]])</small><br/><br/><br />
|-<br />
|[[Image:DialNumberUI1.jpg|200px]]<br/><small>Telephone dial pad<br>(low resolution [[Selecting_the_Right_UI#UI1|UI1]])</small><br/><br/>[[Screenshots|More screenshots and videos]]<br />
|}<br />
'''LinuxMCE is the only all-in-one open source solution that seamlessly combines:'''<br />
* ''Media & entertainment'' with a server for music and video, plus a [[PVR]] (like TiVo or Sky+)<br />
* ''Home automation'' to control everything from lights to heating with a touch-screen tablet or your mobile phone<br />
* VoIP based ''Phone system''<br />
* ''Security system'' that feeds live video to your mobile device during a security breach<br />
<br />
LinuxMCE builds on the superior networking capabilities of Linux to create a home automation/multimedia/communication network. No other operating system has this capability.<br />
<br />
[[LinuxMCE|Read more]] to see all the possibilities that LinuxMCE offers.<br />
<br />
See [[FAQ|the FAQ]] for quick answers to common questions about LinuxMCE.<br />
<br />
Watch the [[Video|LinuxMCE Video]] showing a detailed hardware and installation walk-through.<br />
<br />
=Download=<br />
Please take a moment to read about '''[[Known_Issues|known issues]]''' before downloading our ''Quick Install DVD'' or the ''Two-CD Installer''.<br />
<br />
{| cellspacing=5 cellpadding=5 border=0<br />
|width=48|{{Click || image=Globe.gif | link=Download_Instructions | width=48px | height=48px }}<br />
|'''[[Download_Instructions|Download LinuxMCE]] or buy [[LinuxMCE Products]]'''<br><small>After checking known issues please download from an appropriate mirror</small><br />
|}<br />
<br />
You may then want to check out the [[DVD Installation]] guide for a step by step walk through of setting up and configuring LinuxMCE.<br />
<br />
=Project News=<br />
*[[LinuxMCE-0810 beta]] (for testing) is released ''(16-Oct-09)''<br />
*[[LinuxMCE-0810 alpha2]] (for testing) is released ''(18-Feb-09)''<br />
*[[LinuxMCE-0810 alpha1]] (for testing) is released ''(1-Dec-08)''<br />
*[[LinuxTag 2008]] a resounding success ''(28-May-08)''<br />
*[[Mirrors_0710|LinuxMCE Version 0710 (RC2)]] is released ''(07-May-08)''<br />
*[[Logo|LinuxMCE Logos]] are now available for download ''(09-Apr-08)''<br />
*[[Insteon_-_Setting_Up_PLM_Template|RC1 Insteon Support]] ''(20-Feb-08)''<br />
*[http://www.osweekly.com/index.php?option=com_content&task=view&id=2664 Linux Media Center PCs Review Roundup] ''(4-Oct-07)''<br />
<br />
<br />
{| cellspacing=5 cellpadding=5 border=0 width=100%<br />
|width=48|{{Click || image=Newspaper.gif | link=LinuxMCE_media_coverage | width=48px | height=48px }}<br />
|'''[[LinuxMCE media coverage|More LinuxMCE media coverage]]'''<br><small>Third party media and blog coverage</small><br />
|}<br />
<br />
=Wiki Site News=<br />
* A new [[LinuxMCE.Org 2.0|scratch-pad area]] is being set up to help document a new front end website.<br />
* LinuxMCE Wiki was updated to the latest version which includes an RSS feed extension. Instructions about how to use it can be found [http://www.mediawiki.org/wiki/Extension:WikiArticleFeeds here], or take a look at a [[Test RSS]] ''(31-Jan-08)''<br />
<br />
=Documentation Access=<br />
This Wiki has many hierarchical [[:Category:Main|categories]] of articles. There are also developer maillists, [[Source_Code|source code]] repositories (with attached discussions), [http://trac.linuxmce.org/ bug/issue report mangement] and [http://forum.linuxmce.org/index.php forums] for discussion among users, developers and other members of the LinuxMCE community.<br />
<br />
== User Setups ==<br />
{| cellspacing=5 cellpadding=5 border=0 <br />
|width=48|{{Click || image=pcwork.gif | link=User Setups | width=48px | height=48px }}<br />
|'''[[:Category:User_Setups | User Setups]]'''<br><small>LinuxMCE User Setups/Configurations<br />
|}<br />
<br />
==Support==<br />
{| cellspacing=5 cellpadding=5 border=0 <br />
|width=48|{{Click || image=Manual.gif | link=User Manual | width=48px | height=48px }}<br />
|'''[[User Manual]]'''<br><small>LinuxMCE User Manual<br />
|width=48|{{Click || image=Guides.gif | link=:Category:Tutorials | width=48px | height=48px }}<br />
|'''[[:Category:Tutorials|Tutorials/Guides]]'''<br><small>HOWTO guides describing common scenarios<br />
|-<br />
|width=48|{{Click || image=FAQ.gif | link=Frequently Asked Questions | width=48px | height=48px }}<br />
|'''[[Frequently Asked Questions]]'''<br><small>Responses to the most common questions<br />
|width=48|{{Click || image=Hardware.gif | link=Hardware | width=48px | height=48px }}<br />
|'''[[Hardware]]'''<br><small>Hardware documentation<br />
|-<br />
|width=48|{{Click || image=Troubleshooting.gif | link=Troubleshooting | width=48px | height=48px }}<br />
|'''[[Troubleshooting]]'''<br><small>Help with common problems<br />
|width=48|{{UrlClick || image=Mail.gif | link=Developers | width=48px | height=48px }}<br />
|'''[http://www.charonmedia.org/mailman/listinfo Mailing List]'''<br><small>Stay up to date with regular emails<br />
|-<br />
|width=48|{{UrlClick || image=Forum.gif | link=kjh | width=48px | height=48px }}<br />
|'''[http://forum.linuxmce.com Forum]'''<br><small>Support forum<br />
|width=48|{{Click || image=Forum.gif | link=Chat | width=48px | height=48px }}<br />
|'''[[Chat]]'''<br><small>Support chat<br />
|}<br />
<br />
==Development==<br />
{| cellspacing=5 cellpadding=5 border=0<br />
|width=48|{{Click || image=Contacts.gif | link=Contacts | width=48px | height=48px }}<br />
|'''[[Contacts|Contact Information]]'''<br><small>Contact people involved with the project<br />
|width=48|{{Click || image=Manual.gif | link=Programmer's Guide | width=48px | height=48px }}<br />
|'''[[Programmer's Guide]]'''<br><small>A guide for software developers<br />
|-<br />
|width=48|{{Click || image=Software.gif | link=Software components | width=48px | height=48px }}<br />
|'''[[Software components|Software Components]]'''<br><small>Open source software used by LinuxMCE<br />
|width=48|{{Click || image=Bug.gif | link=Bug Reports | width=48px | height=48px }}<br />
|'''[[Bug Reports]]'''<br><small>Help improve the software by reporting bugs<br />
|-<br />
|width=48|{{Click || image=Binary.gif | link=Source Code | width=48px | height=48px }}<br />
|'''[[Source Code]]'''<br><small>Access the LinuxMCE source code<br />
|width=48|{{UrlClick || image=CDR.gif | link=Versions | width=48px | height=48px }}<br />
|'''[[Versions]]'''<br><small>View version histories and changes<br />
|}</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=User:Jimbodude&diff=21929User:Jimbodude2009-12-30T17:25:50Z<p>Jimbodude: </p>
<hr />
<div>==Setup==<br />
===Theater===<br />
*Core/Hybrid<br />
**ASUS M2NPV-VM<br />
**On-board audio, using fiber output (using digital I/O expansion card) to A/V switch<br />
**On-board video, using DVI output into HDMI cable, directly connected to Projector<br />
**USB-UIRT<br />
**Hauppage PVR-500<br />
*Projector<br />
**Epson Home Cinema 720<br />
**RS-232 control (template available in SqlCVS - you're welcome)<br />
*Speakers<br />
**Cambridge Sounworks DTT3500 (old-school multi-media speakers)<br />
**'''Uncontrollable!''' I have not been able to find ''ANY'' device capable of learning this thing's IR codes... Luckily, the receiver part is small, so I just put it near my couch.<br />
**It plays multiple inputs simultaneously, so I don't need to switch inputs.<br />
**LinuxMCE uses the internal volume, so once the speakers are on, I'm all set.<br />
*Cable box<br />
**Scientific Atlanta Explorer 2200 (Charter)<br />
**IR Control (template available in SqlCVS)<br />
**Connected directly to projector using S-video (too cheap to pay for HD... Besides, Charter doesn't have Discovery HD, so what's the point)<br />
**Connected directly to speakers with RCA to 1/8" cable<br />
*Sony Play Station 3<br />
**Video connected to component input on Projector<br />
**Fiber audio connected to A/V switch<br />
**Will be controlled via IR using [http://www.schmartstuff.com/ps3ir1k.html Schmartz Ps3IR-1000] (it's in the mail now)<br />
*A/V Switch<br />
**IMPACT 3-Play A/V switch (S-Video, fiber/coax digital audio, RCA audio, 3 inputs, 1 output, discrete input selection via IR, toggle power via IR, powered by external DC source)<br />
**Controlled via IR<br />
**Used for fiber switch only - input from Core and PS3 are switched, since the DTT3500 only has one fiber input<br />
===Bedroom===<br />
*MD<br />
**[[ASUS_P2-M2A690G]] ('''DO NOT BUY THIS THING''' - it's a piece of crap)<br />
*Monitor<br />
**Samsung 730B (standard 17" monitor)<br />
*Speakers<br />
**Klipsch stereo multi-media speakers<br />
**Excellent sound, but not controllable<br />
==LinuxMCE Projects==<br />
*MythTV commercial skip and playback menu - Allowing us to use these great features<br />
*[[User:Jimbodude/Standalone_Mode|Standalone Mode]] - Making one-NIC LinuxMCE possible<br />
*[[User:Jimbodude/Orbiter_Phone|Orbiter Phone]] - making it possible to use the Mic and speakers on the Orbiter to run simplephone</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=User:Jimbodude/Orbiter_Phone&diff=21928User:Jimbodude/Orbiter Phone2009-12-30T17:03:51Z<p>Jimbodude: </p>
<hr />
<div>This project has been abandoned due to lack of time and knowledge. Images for DT360 with SimplePhone installed are available upon request.<br />
<br />
==Plan==<br />
#Modify template 1759 to be "controlled by" template 8-Orbiter<br />
#Add 1759 as a child device to an orbiter<br />
#Find out if Orbiter starts simplephone, or if it must be started manually<br />
#Look at the buttons on the telecom screens for "answer on this orbiter" - see how that works<br />
#*Does this cause the phone to be answered on the MD? or the orbiter?<br />
<br />
==Progress==<br />
*Template 1759 updated to be controlled by Orbiter (in addition to On-Screen Orbiter - which was already there)<br />
*Started SoftPhone install on WebDT<br />
**SimplePhone lives at ''/usr/pluto/bin/SimplePhone<br />
**ldd output is:<br />
<pre><br />
linuxmce@dcerouter:/usr/pluto/bin$ ldd SimplePhone <br />
linux-gate.so.1 => (0xffffe000)<br />
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb7fcf000)<br />
librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7fc6000)<br />
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7fc1000)<br />
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7fbd000)<br />
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7f00000)<br />
liblinphone.so.1 => /usr/lib/liblinphone.so.1 (0xb7ebf000)<br />
libSerializeClass.so => /usr/pluto/lib/libSerializeClass.so (0xb7ea4000)<br />
libDCECommon.so => /usr/pluto/lib/libDCECommon.so (0xb7dc1000)<br />
libPlutoUtils.so => /usr/pluto/lib/libPlutoUtils.so (0xb7d62000)<br />
libmysqlclient_r.so.15 => /usr/lib/libmysqlclient_r.so.15 (0xb7b77000)<br />
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7b5f000)<br />
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7a6c000)<br />
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7a47000)<br />
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7a3c000)<br />
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb78f1000)<br />
/lib/ld-linux.so.2 (0xb7fe6000)<br />
libquickstream.so.0 => /usr/lib/libquickstream.so.0 (0xb78eb000)<br />
libosip2.so.3 => /usr/lib/libosip2.so.3 (0xb78d4000)<br />
libosipparser2.so.3 => /usr/lib/libosipparser2.so.3 (0xb78a9000)<br />
libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0xb7891000)<br />
libcrypt.so.1 => /lib/tls/i686/cmov/libcrypt.so.1 (0xb7862000)<br />
libz.so.1 => /usr/lib/libz.so.1 (0xb784d000)<br />
libmediastreamer.so.0 => /usr/lib/libmediastreamer.so.0 (0xb7828000)<br />
libavcodec.so.1d => /usr/lib/libavcodec.so.1d (0xb73cd000)<br />
libortp.so.5 => /usr/lib/libortp.so.5 (0xb73b6000)<br />
libasound.so.2 => /usr/lib/libasound.so.2 (0xb72ef000)<br />
libspeex.so.1 => /usr/lib/libspeex.so.1 (0xb72cf000)<br />
libtheora.so.0 => /usr/lib/libtheora.so.0 (0xb7296000)<br />
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0xb719d000)<br />
libraw1394.so.8 => /usr/lib/libraw1394.so.8 (0xb7197000)<br />
libavutil.so.1d => /usr/lib/libavutil.so.1d (0xb718d000)<br />
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0xb7164000)<br />
libogg.so.0 => /usr/lib/libogg.so.0 (0xb715f000)<br />
libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0xb70c8000)<br />
libgsm.so.1 => /usr/lib/libgsm.so.1 (0xb70b8000)<br />
libartsc.so.0 => /usr/lib/libartsc.so.0 (0xb70b2000)<br />
libesd.so.0 => /usr/lib/libesd.so.0 (0xb70a7000)<br />
libaudiofile.so.0 => /usr/lib/libaudiofile.so.0 (0xb7085000)<br />
libaudio.so.2 => /usr/lib/libaudio.so.2 (0xb706f000)<br />
libXt.so.6 => /usr/lib/libXt.so.6 (0xb701e000)<br />
libdirectfb-0.9.so.25 => /usr/lib/libdirectfb-0.9.so.25 (0xb6fc7000)<br />
libfusion-0.9.so.25 => /usr/lib/libfusion-0.9.so.25 (0xb6fc1000)<br />
libdirect-0.9.so.25 => /usr/lib/libdirect-0.9.so.25 (0xb6fb1000)<br />
libaa.so.1 => /usr/lib/libaa.so.1 (0xb6f96000)<br />
libSM.so.6 => /usr/lib/libSM.so.6 (0xb6f8e000)<br />
libICE.so.6 => /usr/lib/libICE.so.6 (0xb6f76000)<br />
libX11.so.6 => /usr/lib/libX11.so.6 (0xb6e85000)<br />
libncurses.so.5 => /lib/libncurses.so.5 (0xb6e40000)<br />
libslang.so.2 => /lib/libslang.so.2 (0xb6d7f000)<br />
libgpm.so.1 => /usr/lib/libgpm.so.1 (0xb6d79000)<br />
libXau.so.6 => /usr/lib/libXau.so.6 (0xb6d76000)<br />
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6d71000)<br />
</pre><br />
*Installed using deb packages<br />
**Created an apt repository with all LMCE packages on a USB flash drive<br />
**Removed some extra packages (including gdb)<br />
**Got it to fit - with 4.7MB free...<br />
**Initial install did NOT work - packages that had newer versions were taken from Debian apt repository instead of the LMCE repository on the USB drive. Several libraries were not compatible.<br />
**Had to remove Debian repository except for packages that were not in LMCE repository<br />
*Added SimplePhone child device<br />
**Confirmed functionality of child device's extension using Ekiga<br />
*Attempted to run SimplePhone on the DT<br />
**Console output was:<br />
<pre><br />
1.<br />
orbiter:~# /usr/pluto/bin/SimplePhone -d 86<br />
2.<br />
SimplePhone, v.2.0.0.44.0804112200<br />
3.<br />
Visit www.plutohome.com for source code and license information<br />
4.<br />
<br />
5.<br />
10 12/04/08 16:07:10.957 Device: 86 starting. Connecting to: dcerouter <0xb73c06c0><br />
6.<br />
10 12/04/08 16:07:10.968 Setting timeout for socket 3 to 20 <0xb73c06c0><br />
7.<br />
05 12/04/08 16:07:11.073 Server IP: dcerouter <0xb73c06c0><br />
8.<br />
10 12/04/08 16:07:11.074 Socket::SendMessage type 5 id 88 from 86 to -1000 <0xb73c06c0><br />
9.<br />
10 12/04/08 16:07:11.116 MD Audio Settings: ERR Parameter not found <0xb73c06c0><br />
10.<br />
10 12/04/08 16:07:11.116 Flag unprocessed: 'E' <0xb73c06c0><br />
11.<br />
10 12/04/08 16:07:11.117 Flag unprocessed: 'R' <0xb73c06c0><br />
12.<br />
10 12/04/08 16:07:11.117 Flag unprocessed: 'R' <0xb73c06c0><br />
13.<br />
10 12/04/08 16:07:11.117 Flag unprocessed: ' ' <0xb73c06c0><br />
14.<br />
10 12/04/08 16:07:11.118 Flag unprocessed: 'P' <0xb73c06c0><br />
15.<br />
10 12/04/08 16:07:11.118 Flag unprocessed: 'a' <0xb73c06c0><br />
16.<br />
10 12/04/08 16:07:11.118 Flag unprocessed: 'r' <0xb73c06c0><br />
17.<br />
10 12/04/08 16:07:11.119 Flag unprocessed: 'a' <0xb73c06c0><br />
18.<br />
10 12/04/08 16:07:11.119 Flag unprocessed: 'm' <0xb73c06c0><br />
19.<br />
10 12/04/08 16:07:11.119 Flag unprocessed: 'e' <0xb73c06c0><br />
20.<br />
10 12/04/08 16:07:11.119 Flag unprocessed: 't' <0xb73c06c0><br />
21.<br />
10 12/04/08 16:07:11.119 Flag unprocessed: 'e' <0xb73c06c0><br />
22.<br />
10 12/04/08 16:07:11.120 Flag unprocessed: 'r' <0xb73c06c0><br />
23.<br />
10 12/04/08 16:07:11.120 Flag unprocessed: ' ' <0xb73c06c0><br />
24.<br />
10 12/04/08 16:07:11.120 Flag unprocessed: 'n' <0xb73c06c0><br />
25.<br />
10 12/04/08 16:07:11.120 Flag unprocessed: 'o' <0xb73c06c0><br />
26.<br />
10 12/04/08 16:07:11.121 Flag unprocessed: 't' <0xb73c06c0><br />
27.<br />
10 12/04/08 16:07:11.121 Flag unprocessed: ' ' <0xb73c06c0><br />
28.<br />
10 12/04/08 16:07:11.121 Flag unprocessed: 'f' <0xb73c06c0><br />
29.<br />
10 12/04/08 16:07:11.121 Flag unprocessed: 'o' <0xb73c06c0><br />
30.<br />
10 12/04/08 16:07:11.122 Flag unprocessed: 'u' <0xb73c06c0><br />
31.<br />
10 12/04/08 16:07:11.122 Flag unprocessed: 'n' <0xb73c06c0><br />
32.<br />
10 12/04/08 16:07:11.122 Flag unprocessed: 'd' <0xb73c06c0><br />
33.<br />
10 12/04/08 16:07:11.125 Socket::SendMessage type 5 id 31 from 86 to -1000 <0xb73c06c0><br />
34.<br />
10 12/04/08 16:07:11.136 SimplePhone::GetConfig: Starting with extension '203' <0xb73c06c0><br />
35.<br />
sh: /usr/pluto/bin/SoundCards_SetupAudioCapture.sh: No such file or directory<br />
36.<br />
10 12/04/08 16:07:11.149 Requesthandler 0x9b27b58 (device: 86) runThread now running <0xb6bafb90><br />
37.<br />
10 12/04/08 16:07:11.150 Connect OK <0xb73c06c0><br />
38.<br />
10 12/04/08 16:07:11.150 LS_InitProxy - called <0xb63afb90><br />
39.<br />
10 12/04/08 16:07:11.151 LS_InitProxy -- Proxy: sip:dcerouter; Extension: 203; Identity: sip:203@dcerouter <0xb63afb90><br />
40.<br />
10 12/04/08 16:07:11.152 LS_InitProxy - exited <0xb63afb90><br />
41.<br />
10 12/04/08 16:07:11.152 Started SIP/Linphone thread <0xb63afb90><br />
42.<br />
10 12/04/08 16:07:11.153 LS_RegisterWithAsterisk - called <0xb63afb90><br />
43.<br />
ortp-message-oRTP-0.13.1 initialized.<br />
44.<br />
ortp-message-Registering all filters...<br />
45.<br />
ortp-message-Registering all soundcard handlers<br />
46.<br />
ortp-message-Card ALSA: default device added<br />
47.<br />
ortp-message-Card ALSA: CS5535 Audio added<br />
48.<br />
ortp-message-Loading plugins<br />
49.<br />
ortp-message-Cannot open directory /usr/lib/mediastreamer/plugins: No such file or directory<br />
50.<br />
ortp-message-ms_init() done<br />
51.<br />
ortp-message-Adding new codec PCMU/8000<br />
52.<br />
ortp-message-Adding new codec GSM/8000<br />
53.<br />
ortp-message-Adding new codec PCMA/8000<br />
54.<br />
ortp-message-Adding new codec theora/90000<br />
55.<br />
ortp-message-Adding new codec H263-1998/90000<br />
56.<br />
ortp-message-Adding new codec MP4V-ES/90000<br />
57.<br />
ortp-message-Adding new codec speex/8000<br />
58.<br />
ortp-message-Adding new codec speex/16000<br />
59.<br />
| INFO1 | <eXutils.c: 159> Outgoing interface to reach 15.128.128.93 is 192.168.80.194.<br />
60.<br />
<br />
61.<br />
| INFO1 | <eXosip.c: 333> eXosip: Reseting timer to 15s before waking up!<br />
62.<br />
10 12/04/08 16:07:11.165 SimplePhone: lib message: 'Ready' <0xb63afb90><br />
63.<br />
| INFO1 | <eXutils.c: 159> Outgoing interface to reach dcerouter is 192.168.80.194.<br />
64.<br />
<br />
65.<br />
| INFO2 | <osip_transaction.c: 131> allocating transaction ressource 1 408561296<br />
66.<br />
| INFO2 | <nict.c: 34> allocating NICT context<br />
67.<br />
| INFO2 | <eXutils.c: 237> Not an IPv4 or IPv6 address: dcerouter<br />
68.<br />
| INFO2 | <eXutils.c: 267> DNS resolution with dcerouter:5060<br />
69.<br />
| INFO1 | <jcallback.c: 148> Message sent:<br />
70.<br />
REGISTER sip:dcerouter SIP/2.0<br />
71.<br />
Via: SIP/2.0/UDP 192.168.80.194:5061;rport;branch=z9hG4bK1841486180<br />
72.<br />
From: <sip:203@dcerouter>;tag=463549899<br />
73.<br />
To: <sip:203@dcerouter><br />
74.<br />
Call-ID: 408561296@192.168.80.194<br />
75.<br />
CSeq: 1 REGISTER<br />
76.<br />
Contact: <sip:203@192.168.80.194:5061><br />
77.<br />
Max-Forwards: 70<br />
78.<br />
User-Agent: Linphone-1.7.1/eXosip<br />
79.<br />
Expires: 600<br />
80.<br />
Content-Length: 0<br />
81.<br />
<br />
82.<br />
(len=16 sizeof(addr)=128 28)<br />
83.<br />
| INFO1 | <jcallback.c: 525> cb_sndregister (id=1)<br />
84.<br />
| INFO1 | <eXosip.c: 340> eXosip: timer sec:0 usec:498189!<br />
85.<br />
10 12/04/08 16:07:11.187 LS_RegisterWithAsterisk - exited <0xb63afb90><br />
86.<br />
10 12/04/08 16:07:11.187 LS_Main_Loop - called <0xb63afb90><br />
87.<br />
| INFO1 | <udp.c: 2210> Received message:<br />
88.<br />
SIP/2.0 100 Trying<br />
89.<br />
Via: SIP/2.0/UDP 192.168.80.194:5061;branch=z9hG4bK1841486180;received=192.168.80.194;rport=5061<br />
90.<br />
From: <sip:203@dcerouter>;tag=463549899<br />
91.<br />
To: <sip:203@dcerouter><br />
92.<br />
Call-ID: 408561296@192.168.80.194<br />
93.<br />
CSeq: 1 REGISTER<br />
94.<br />
User-Agent: Asterisk PBX<br />
95.<br />
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY<br />
96.<br />
Supported: replaces<br />
97.<br />
Contact: <sip:203@192.168.80.1><br />
98.<br />
Content-Length: 0<br />
99.<br />
<br />
100.<br />
<br />
101.<br />
| INFO3 | <osip_event.c: 89> MESSAGE REC. CALLID:408561296<br />
102.<br />
| INFO1 | <jcallback.c: 601> cb_rcv1xx (id=1)<br />
103.<br />
| INFO1 | <eXosip.c: 340> eXosip: timer sec:0 usec:480877!<br />
104.<br />
| INFO1 | <udp.c: 2210> Received message:<br />
105.<br />
SIP/2.0 401 Unauthorized<br />
106.<br />
Via: SIP/2.0/UDP 192.168.80.194:5061;branch=z9hG4bK1841486180;received=192.168.80.194;rport=5061<br />
107.<br />
From: <sip:203@dcerouter>;tag=463549899<br />
108.<br />
To: <sip:203@dcerouter>;tag=as0947acc2<br />
109.<br />
Call-ID: 408561296@192.168.80.194<br />
110.<br />
CSeq: 1 REGISTER<br />
111.<br />
User-Agent: Asterisk PBX<br />
112.<br />
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY<br />
113.<br />
Supported: replaces<br />
114.<br />
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6ce374da"<br />
115.<br />
Content-Length: 0<br />
116.<br />
<br />
117.<br />
<br />
118.<br />
| INFO3 | <osip_event.c: 89> MESSAGE REC. CALLID:408561296<br />
119.<br />
| INFO1 | <jcallback.c: 1442> cb_rcv4xx (id=1)<br />
120.<br />
| INFO1 | <eXosip.c: 340> eXosip: timer sec:4 usec:999989!<br />
121.<br />
ortp-message-REGISTRATION_FAILURE<br />
122.<br />
<br />
123.<br />
ortp-message-cfg= sip:dcerouter, cfg->rid=1, rid=1<br />
124.<br />
10 12/04/08 16:07:11.209 callback: auth_requested - called <0xb63afb90><br />
125.<br />
10 12/04/08 16:07:11.209 SimplePhone: Authorisation requested, realm: '"asterisk"', username '203' <0xb63afb90><br />
126.<br />
10 12/04/08 16:07:11.210 callback: auth_requested - exited <0xb63afb90><br />
127.<br />
Segmentation fault<br />
</pre><br />
**GDB stack trace:<br />
<pre><br />
#0 0x41383a15 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<br />
() from /usr/lib/libstdc++.so.6<br />
#1 0x08057e66 in DCE::SimplePhone::GetExtension (this=0x0) at SimplePhone.cpp:397<br />
#2 0x08064c79 in LS_SetupAuth () at SIP_Thread.cpp:148<br />
#3 0x08064d72 in LS_Main_Loop () at SIP_Thread.cpp:90<br />
#4 0x08064f54 in LS_Thread (arg=0x9612b58) at SIP_Thread.cpp:174<br />
#5 0x41191f3b in start_thread () from /lib/libpthread.so.0<br />
#6 0x410e8b6e in clone () from /lib/libc.so.6<br />
</pre></div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=User:Jimbodude/Standalone_Mode&diff=21927User:Jimbodude/Standalone Mode2009-12-30T17:02:15Z<p>Jimbodude: </p>
<hr />
<div>This project has been abandoned, but the instructions to get this functionality probably still work. There is significant resistance against integrating this into the system because:<br />
* Features are disabled<br />
* The setup becomes more complex, allowing for greater variation, which creates technical support requests that are difficult to solve<br />
* Many people do not understand the networking concepts<br />
* There are other more important features in the works<br />
* There are "simpler" ways to get a similar result, such as installing 2 NICs, but leaving the internal NIC disconnected<br />
<br />
==Intro==<br />
<br />
'''Standalone Mode''' or '''Standalone Configuration''' (name is up for debate) is a proposed new feature for LinuxMCE that would allow people to have a LinuxMCE Core exist as a new system on an existing network. The goal is to encourage more people to try to use the system by allowing them to run LinuxMCE without altering their current network setup at all, and to allow the system to be used in environments where the user is not able (or willing) to alter the network configuration for some reason. This configuration would allow users to build trust with the system and learn the important concepts before doing a full scale implementation or to use a limited subset of features in a permanent solution.<br />
<br />
Ideally, this feature would be integrated into the install. The user would be able to select "Normal Mode" or "Standalone Mode" - this option would probably replace the current "disable DCHP server" option. If standalone mode is selected, the user should be warned about all the features of LinuxMCE that will be disabled.<br />
<br />
The key point of this article is that we don't need to edit any code (outside of the installer) to make this happen. We also can test and find out exactly what features are disabled by running LinuxMCE in this manner, so it is not a serious support burden.<br />
<br />
==Standalone Mode Use Cases==<br />
*A user is interested in trying LinuxMCE, and isn't ready to invest in any additional hardware just to experiment<br />
*A user is interested in trying LinuxMCE, but doesn't want to reconfigure their network just to experiment<br />
*A user is interested in trying LinuxMCE, but doesn't trust the system to run their network (yet)<br />
*A user wants to use LinuxMCE, but isn't ready to replace their current solution without further testing, or would like to run the systems in parallel<br />
*A user wants to use LinuxMCE, but only requires a subset of the features LinuxMCE offers (for example: home automation and event response service, or stand alone media appliance)<br />
*A user wants to use LinuxMCE, starting with existing hardware, and plans to build up to a full featured system over time<br />
*Any combination of the above<br />
<br />
==Using Standalone Mode==<br />
To get from normal mode to standalone mode, a few things need to happen:<br />
*Disable network management, especially DHCP, so we don't conflict with the management solution that is in place (i.e. consumer grade routers)<br />
*Reconfigure network adapter so that PnP still works and the network acts as expected<br />
<br />
In one install of LinuxMCE, I hacked up the configuration files manually to achieve the desired behavior. Using a bit more knowledge about the LinuxMCE system, I've found that there is a much simpler and cleaner way to do this.<br />
<br />
===The clean way===<br />
#Disable DHCP (uncheck the box in Web Admin --> Advanced --> Network --> Network Settings)<br />
#Disable the Firewall, because we expect that we are already behind a firewall (check box in Web Admin --> Advanced --> Network --> Firewall Rules)<br />
#Disable the following boot scripts for both Core and Hybrid (uncheck in Web Admin --> Advanced --> Software --> Boot Sequence)<br />
#*DHCP_config.sh<br />
#*Network_Firewall.sh<br />
#*Restart_DHCP.sh<br />
#Reboot the system<br />
<br />
If there's only one NIC, eth0 and eth0:0 will still both exist and have different IPs, but that's ok. Whichever one we decide to talk to will do just fine, since the firewall is off.<br />
<br />
If you want PnP to work, you'll have to configure the internal adapter's address to be part of your network's subnet. If your internal and external adapter are on the same network, the core will detect itself - be sure to ignore the core. Ideally, the external adapter should be disabled, or directed to some other subnet, where it won't actually do anything.<br />
<br />
===The gross way===<br />
'''DO NOT do this. EVER.'''<br />
#Disable DHCP<br />
#Disable the firewall<br />
#Hack the hell out of ''interfaces'' so that eth0 and eth0:0 have the same IP<br />
#Hack the hell out of the pluto properties file to get the desired IP addresses for both internal and external network<br />
<br />
This basically breaks LinuxMCE's auto configuration, and makes it a totally manual setup. This is not desirable, and you should never do it.<br />
<br />
==Feature Loss==<br />
Confirmed Lost:<br />
*Automatic netboot of MDs (no DHCP to push out the image automatically)<br />
<br />
Confirmed Not Lost:<br />
*All media functionality related to hybrid core<br />
*Network media spider<br />
*Home automation features (not dependent on DHCP)<br />
<br />
Unconfirmed Probably Lost:<br />
*Telecom<br />
*Network device PnP<br />
<br />
Probably could work with external configuration:<br />
*Manual netboot of MDs (supply boot image information referencing the Core from a DHCP server which is not the Core)<br />
<br />
==Integrating this into the install==<br />
'''Abandoned'''<br />
<br />
Things that need to be done:<br />
*Add new options to the installer to activate standalone mode<br />
*Document the loss of functionality caused by using standalone mode</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=User:Jimbodude/Standalone_Mode&diff=21926User:Jimbodude/Standalone Mode2009-12-30T17:01:02Z<p>Jimbodude: </p>
<hr />
<div>This project has been abandoned, but the instructions to get this functionality probably still work. There is significant resistance against integrating this into the system because:<br />
* Features are disabled<br />
* The setup becomes more complex, allowing for greater variation, which creates technical support requests that are difficult to solve<br />
* Many people do not understand the networking concepts<br />
* There are other more important features in the works<br />
<br />
==Intro==<br />
<br />
'''Standalone Mode''' or '''Standalone Configuration''' (name is up for debate) is a proposed new feature for LinuxMCE that would allow people to have a LinuxMCE Core exist as a new system on an existing network. The goal is to encourage more people to try to use the system by allowing them to run LinuxMCE without altering their current network setup at all, and to allow the system to be used in environments where the user is not able (or willing) to alter the network configuration for some reason. This configuration would allow users to build trust with the system and learn the important concepts before doing a full scale implementation or to use a limited subset of features in a permanent solution.<br />
<br />
Ideally, this feature would be integrated into the install. The user would be able to select "Normal Mode" or "Standalone Mode" - this option would probably replace the current "disable DCHP server" option. If standalone mode is selected, the user should be warned about all the features of LinuxMCE that will be disabled.<br />
<br />
The key point of this article is that we don't need to edit any code (outside of the installer) to make this happen. We also can test and find out exactly what features are disabled by running LinuxMCE in this manner, so it is not a serious support burden.<br />
<br />
==Standalone Mode Use Cases==<br />
*A user is interested in trying LinuxMCE, and isn't ready to invest in any additional hardware just to experiment<br />
*A user is interested in trying LinuxMCE, but doesn't want to reconfigure their network just to experiment<br />
*A user is interested in trying LinuxMCE, but doesn't trust the system to run their network (yet)<br />
*A user wants to use LinuxMCE, but isn't ready to replace their current solution without further testing, or would like to run the systems in parallel<br />
*A user wants to use LinuxMCE, but only requires a subset of the features LinuxMCE offers (for example: home automation and event response service, or stand alone media appliance)<br />
*A user wants to use LinuxMCE, starting with existing hardware, and plans to build up to a full featured system over time<br />
*Any combination of the above<br />
<br />
==Using Standalone Mode==<br />
To get from normal mode to standalone mode, a few things need to happen:<br />
*Disable network management, especially DHCP, so we don't conflict with the management solution that is in place (i.e. consumer grade routers)<br />
*Reconfigure network adapter so that PnP still works and the network acts as expected<br />
<br />
In one install of LinuxMCE, I hacked up the configuration files manually to achieve the desired behavior. Using a bit more knowledge about the LinuxMCE system, I've found that there is a much simpler and cleaner way to do this.<br />
<br />
===The clean way===<br />
#Disable DHCP (uncheck the box in Web Admin --> Advanced --> Network --> Network Settings)<br />
#Disable the Firewall, because we expect that we are already behind a firewall (check box in Web Admin --> Advanced --> Network --> Firewall Rules)<br />
#Disable the following boot scripts for both Core and Hybrid (uncheck in Web Admin --> Advanced --> Software --> Boot Sequence)<br />
#*DHCP_config.sh<br />
#*Network_Firewall.sh<br />
#*Restart_DHCP.sh<br />
#Reboot the system<br />
<br />
If there's only one NIC, eth0 and eth0:0 will still both exist and have different IPs, but that's ok. Whichever one we decide to talk to will do just fine, since the firewall is off.<br />
<br />
If you want PnP to work, you'll have to configure the internal adapter's address to be part of your network's subnet. If your internal and external adapter are on the same network, the core will detect itself - be sure to ignore the core. Ideally, the external adapter should be disabled, or directed to some other subnet, where it won't actually do anything.<br />
<br />
===The gross way===<br />
'''DO NOT do this. EVER.'''<br />
#Disable DHCP<br />
#Disable the firewall<br />
#Hack the hell out of ''interfaces'' so that eth0 and eth0:0 have the same IP<br />
#Hack the hell out of the pluto properties file to get the desired IP addresses for both internal and external network<br />
<br />
This basically breaks LinuxMCE's auto configuration, and makes it a totally manual setup. This is not desirable, and you should never do it.<br />
<br />
==Feature Loss==<br />
Confirmed Lost:<br />
*Automatic netboot of MDs (no DHCP to push out the image automatically)<br />
<br />
Confirmed Not Lost:<br />
*All media functionality related to hybrid core<br />
*Network media spider<br />
*Home automation features (not dependent on DHCP)<br />
<br />
Unconfirmed Probably Lost:<br />
*Telecom<br />
*Network device PnP<br />
<br />
Probably could work with external configuration:<br />
*Manual netboot of MDs (supply boot image information referencing the Core from a DHCP server which is not the Core)<br />
<br />
==Integrating this into the install==<br />
'''Abandoned'''<br />
<br />
Things that need to be done:<br />
*Add new options to the installer to activate standalone mode<br />
*Document the loss of functionality caused by using standalone mode</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=Frequently_Asked_Questions&diff=21263Frequently Asked Questions2009-09-17T17:29:40Z<p>Jimbodude: Someone put the section about digital cable in the wrong place...</p>
<hr />
<div>[[Category:Documentation]]<br />
This '''frequently asked questions''' (FAQ) section outlines solutions to the most common queries for initial/potential users. See also [[troubleshooting]] for solutions to problems experienced with the system.<br />
==Before Installing LinuxMCE==<br />
===What Does LinuxMCE Do For Me?===<br />
'''LinuxMCE is a whole home automation suite. It includes full featured solutions for:'''<br />
*Media<br />
**Organize media with [[Catalog_media_with_attributes|special metadata tags]]<br />
**View/Listen to media in any room<br />
**Media automatically [[Have_my_media_follow_me|follows you]] through your home<br />
**New media is automatically detected - even if it's on other devices like another computer on your network or Network Attached Storage (NAS)<br />
**Control all your A/V gear through LinuxMCE (using [[Control_regular_A/V_equipment|IR]], [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB, Ethernet, or RS-232]]) including automatically powering everything on and setting the proper inputs on each device<br />
*[[Security]]<br />
**Monitor sensors and [[Have_LinuxMCE_notify_me_of_security_alerts|trigger events]]<br />
**[[Monitor_surveillance_cameras|Monitor security cameras]]<br />
*[[LinuxMCE_telecom_features|Telecomunication]]<br />
**Use VoIP phones anywhere in your home with minimal setup<br />
**Voicemail, call forwarding, advanced caller ID<br />
*Network Management<br />
**Take the place of a standard home router<br />
**Advanced [[Firewall_Rules|firewall]]<br />
**Advanced Quality of Service (QoS) to make sure your bandwidth is used effectively (especially important for VoIP)<br />
**Manage networked storage (such as [[Network_Attached_Storage|NAS devices]]<br />
*[[Automation|Home Control and Automation]]<br />
**Control climate and lighting throughout your entire home<br />
<br />
'''LinuxMCE provides all this functionality by controlling [[:Category:Hardware|all kinds of devices]] throughout the home including:'''<br />
*LinuxMCE [[Core]] Computer<br />
*LinuxMCE [[Media_Directors|Media Director]] Computers<br />
*LinuxMCE [[Orbiters|Orbiters]] (Fancy remotes)<br />
**Nokia [[Nokia 770|770]]/[[Nokia N800|N800/N810]]<br />
**Various PDAs (such as IPAQ 5550 and IPAQ hx2410)<br />
**Various Bluetooth capable mobile phones (including Nokia [[Nokia E65|E65]], [[Nokia N70|N70]], [[Nokia N73|N73]], [[Nokia 6620|6620]], [[Nokia 7650|7650]]) <br />
**The [[Web Orbiter]]<br />
**Various [[:Category:Orbiters|other devices]]<br />
*Networked storage (including [[:Category:Network_Attached_Storage|Network Attached Storage]] (NAS) Devices)<br />
*A/V Equipment (TVs, Receivers, Cable Boxes, etc)<br />
**Using [[:Category:Infrared|Infrared]] (IR)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|RS-232]] (Serial)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|Ethernet]] (Network)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB]]<br />
*TV [[:Category:TV_Cards|Capture Devices]]<br />
*Lighting [[:Category:Automation|Automation]]<br />
**Using [[X10_LinuxMCE_Configuration|X10]]<br />
**Using [[:Category:ZWave|Z-Wave]]<br />
**Using [[:Category:Insteon|Insteon]]<br />
**Using [[:Category:Automation|various other protocols]]<br />
**See also: [[Automation]]<br />
*HVAC (Climate Control)[[:Category:Automation|Automation]]<br />
*Security [[:Category:Security|Systems or Individual Sensors]]<br />
*Surveillance [[:Category:Cameras|Cameras]] (IP, Firewire, [[:Category:Video_Capture_Boards|video capture board]], etc)<br />
*VoIP [[:Category:Phones|Phones]] and [[VOIP Service Providers|Service Providers]]<br />
<br />
For more, see [[What can I do with LinuxMCE?]]<br />
<br />
===Is LinuxMCE an appliance or software solution?===<br />
Until now there have been two options for a smarthome+media system:<br />
# Low cost '''software''' based PC solutions, including home automation software like [http://www.homeseer.com HomeSeer], [http://www.premisesystems.com Premise] and [http://www.misterhouse.com Mr. House], also media software like [http://www.microsoft.com/windowsxp/mediacenter/default.mspx Microsoft Windows XP Media Center].<br />
# '''Appliance''' solutions, like [http://www.crestron.com Crestron], [http://www.amx.com AMX], [http://www.kaleidescape.com Kaleidescape] and [http://www.escient.com Escient].<br />
<br />
High-end systems are always appliance based, preferred for their simplicity, reliability and lack of hassle; no worry about missing the football game because your PC-based PVR got a virus. But appliance systems cost a lot &mdash; for one that includes automation, media, telephony, etc., like LinuxMCE. Even though those "appliances" are normally PC's inside special cases, often running Linux plus some proprietary software, you can never get the software separately to build your own &mdash; until now.<br />
<br />
LinuxMCE is an appliance solution. The Core becomes a self-configuring, self-maintaining black box appliance. Since the Core automatically offers a network boot image to any PC's you want to use as media directors, they too become appliances. You can still use them as a PC, of course, but you can crash the hard drive, install a virus, delete system files, and it doesn't matter. When you hit 'LinuxMCE' on the remote control, the Core sends it a network boot, the hard drive turns off, it doesn't use your operating system, and you'll never see a PC prompt. And when you hit the PC button, it goes back to being a PC like normal. LinuxMCE is a 'family friendly' solution--you can use the PC for kernel-level coding, knowing the kids can always hit 1 button and still use it to watch cartoons.<br />
<br />
LinuxMCE offers the best of both worlds: an appliance solution at the price of a software solution, and the the power and versatility of a software solution with the ease of use of an appliance. We offer the software for free as open source because our business is licensing LinuxMCE to hardgoods manufacturers who embed it in their products.<br />
<br />
===What do commercial appliance solutions similar to LinuxMCE cost?===<br />
Appliance solutions are normally quite expensive. The most popular combinations are:<br />
# [http://www.crestron.com Crestron] system to do all the home automation. The cost varies depending on what you want to do with it, but a whole-house solution including touch-screen panels will set you back at least $25,000 for an entry-level system, and can easily hit 6 figures.<br />
# [http://www.kaleidescape.com Kaleidescape] for the DVD movie server, costing $27,000 for the main server, and $4,000 for each TV where you want to watch movies.<br />
# [http://www.escient.com Escient] Fireball for the music server, costing $5,000 for the central music server.<br />
# A PBX phone system with voicemail, like [http://www.panasonic.com Panasonic] will cost another 5 grand or so.<br />
<br />
All of those products require professional installation and setup, particularly the home automation devices. LinuxMCE was designed with simple web-based wizard so even non-techies can get a whole solution up within a few hours. But our competitors' products are different. Smart home dealers will require a trained programmer to set them up. For example, it can take weeks of programming to set up a Crestron system in a good-sized house. Programming fees can be over $10,000, plus re-programing fees every time you make a change. '''Bottom line: around $100,000''' for an appliance solution that does what LinuxMCE does.<br />
<br />
Appliance solutions are typically PCs, running an Linux OS with custom, proprietary software, placed inside custom cases. The software is not available separately, so there's no way to economize or build your own.<br />
<br />
LinuxMCE has taken a different approach. LinuxMCE is also an appliance solution, but we have made the software available separately. In fact, it is free, so techies and software programmers can build their own high-end appliance systems. Competing PC hardware manufacturers can license the LinuxMCE platform to use in standard, low-cost PCs. LinuxMCE brings down the cost by offering all the functionality of several systems in 1 system: whole house media & entertainment, home automation, telecom, security, and personal computer.<br />
<br />
===I've heard LinuxMCE is just a bunch of projects merged together. Is that true? What is special about LinuxMCE?===<br />
<p>LinuxMCE includes a lot of other open source projects, like Xine, Asterisk, MythTV, VideoLan, etc. So we are often asked, "Why do I need LinuxMCE, can't I just use those other projects by themselves?"</p><br />
<p>LinuxMCE has a lot of its own software; it's not just a collection of other projects. In fact, LinuxMCE's own software is bigger than most of the key outside projects combined. LinuxMCE includes its own messaging platform. Most of the logic and functionality, such as how to handle home security, media, etc., is in LinuxMCE's plug-in's--not the other projects. Plus LinuxMCE includes a GUI that runs on Linux, Windows, Windows CE and Symbian. There are already thousands of DCE Devices for various smart home components. And LinuxMCE includes lots of development tools, like the GUI Designer, code generators like DCEGen and sql2cpp. There are also some fairly substantial stand-alone projects with LinuxMCE, like sqlCVS. sqlCVS has essentially all the same features as CVS or SVN, but it works with databases--not source code. It is what ensures that when one user translates a screen on the GUI, or learns an infrared code, or creates a new GSD device, that this is committed to a central repository, reviewed by our staff, then propagated to all other users.</p><br />
<p>Additionally LinuxMCE has its own "wrappers" for all the outside open source projects we integrate. This is what allows them to work together seamlessly.</p><br />
<p><b>Example #1: LinuxMCE's wrappers allow open source projects to be interchangeable modules.</b> For example, on one media director un-check the box for the 'Xine' media player, but leave 'VideoLan' checked. Do the opposite for another media director. And for the rest, leave both checked (the default). Now start watching a movie in 1 room. As you move from room to room the movie will seamlessly move from Xine to VideoLan and back. If you leave both checked, Xine will be used when the movie is playing in 1 room only, and VideoLan when it is playing in multiple rooms. This interoperability is not possible outside of LinuxMCE.</p><br />
<p><b>Example #2: LinuxMCE allows a bunch of disparate projects to work together as a seamless whole</b> For example, if there's a security breach in your house, the lights and TV's in the house come on automatically using our home automation DCE device interfaces, and the security pin pad appears on all the Windows webpads and PDA's. After 30 seconds a menacing video plays for the burglar using Xine, while the surveillance cameras monitored by Motion feed a live video to your mobile phone over GPRS. Hit 'Talk' on the phone and Xine suspends, passing control to Linphone which makes a call using Asterisk to your mobile phone with the audio piped through the stereo so you can shout at the intruder and let him know you're watching him from a remote location and calling. To the end-user, it works seamlessly, like 1 cohesive whole, but in reality, what LinuxMCE did is enable a bunch of existing applications to work together.</p><br />
<br />
===Which hardware is known to work?===<br />
See the [[:Category:Hardware|Hardware category]].<br />
<br />
===Can LMCE record digital television?=== <br />
Yes, as long as it is unencrypted. Please [[Understanding_digital_cable|see this article]]<br />
<br />
===Is LinuxMCE a distribution or a package?===<br />
Strictly speaking LinuxMCE is a package. A very big package. The distribution it runs on is standard Kubuntu Linux.<br />
<br />
Only the PC running as the Core is required to run Kubuntu and use the LinuxMCE package.<br />
<br />
Any PC used as a Media Director can [[netboot]] from the Core, without the requirement for an OS at all. Of course, you can always boot whatever OS is already stored on the hard drive of each Media Director PC and use that PC separately from the LinuxMCE system. Play the games (or whatever) that are stored on the hard drive (using whichever OS is already installed there) there, and when you're ready to use that PC as a Media Director again, you just go back to netbooting from the Core.<br />
<br />
For the Core, you should use Kubuntu and our packages.<br />
<br />
LinuxMCE is based on the standard Kubuntu Linux distribution. While you could try to run LinuxMCE on another distribution, it's not recommended. LinuxMCE has lots of scripts and utilities to facilitate various tasks. Plus, LinuxMCE embeds many other open source projects, like Xine, Asterisk, etc., with our own "wrappers" that allows them to work together seamlessly. These wrappers are only tested against the versions we maintain in our Ubuntu mirror.<br />
<br />
Before we upgrade anything on our mirror, we thoroughly test the new packages in our system to be sure it still works.<br />
<br />
We didn't take any modules away from the Kubuntu distribution, we only added some. You can still use your Core as a normal Kubuntu Linux PC. In fact, our additions can be bypassed if they get in your way, as is explained below. But in general, DCERouter and other devices, like the home automation modules, all run in the background and won't interfere in screen sessions.<br />
<br />
''Here's what we changed:''<br />
<br />
====Configuration scripts====<br />
LinuxMCE includes a lot of scripts that automate all aspects of maintaining a Linux system. For example, when you add a new user from the LinuxMCE Admin site, it automatically creates a new media directory, exports a samba share, creates an email and voicemail accounts, and so on. There's also scripts to do lots of low-level things like setup ip network prioritizing, so your VOIP calls are always clear. By default, LinuxMCE overwrites and re-creates many Linux config files at each boot. In this regard LinuxMCE acts like a black box appliance. However, once you install LinuxMCE you can go to the [[LinuxMCE Admin Website]]-->Advanced-->Boot Scripts and disable any or all of these scripts. Then you can still maintain your LinuxMCE Core like any other Linux PC and it won't overwrite your config files.<br />
<br />
====Our Ubuntu mirror====<br />
We maintain our own mirror based on Ubuntu. The reason is that we have "wrappers" for many open source projects like Xine, Asterisk, etc., allowing them to work together seamlessly. Whenever updates are posted to Ubuntu's repository, we test the new versions to be sure the changes did not break anything in our wrappers and that the auto-configuration scripts still work. In very rare cases, we need to make our own version of a package that replaces the one in Ubuntu. We avoid that whenever possible, and instead re-work our wrappers so that we can stay current with the "stock" version. Such changes are generally trivial, and you should see no difference between LinuxMCE's Ubuntu mirror and the official one.<br />
<br />
====Window manager====<br />
The Media Directors use our own modified version of the Ratpoison window manager. All applications appear as full-screen, with no borders. Our Orbiter GUI becomes the XWindows desktop. This is the desired behavior in an appliance-like set-top box; we completely isolate the user from anything computer-like. However, you will likely not want this as your main desktop. It is possible to run 2 versions of X on separate terminals: one with LinuxMCE's window manager, and the other with your own preferred choice of desktop.<br />
<br />
====Software Module Overview====<br />
<br />
[[Overview of the software modules]]<br />
<br />
===Ok, I'm sold - what do I need to run LinuxMCE?===<br />
LinuxMCE components include:<br />
*'''''The Core''''' - The computer that acts as the "server" for LinuxMCE. It is responsible for coordinating all the other components and managing your network. This system '''REQUIRES TWO NETWORK CARDS'''. Read the next question for an explanation.<br />
*'''''Media Directors''''' - The computers that are connected to your TV's and allow you to view your media. The Core can also act as a Media Director; this configuration is called a '''''Hybrid'''''. Any system that is to be used as a Media Director should have '''an nVidia graphics card, 6200 or better'''. Read the question after the next for an explanation.<br />
*'''''Orbiters''''' - Small devices used as advanced remote controls. Some possible devices include:<br />
**Bluetooth mobile phones (with OBEX capabilities)<br />
**Nokia Internet tablets (N770/800/810)<br />
**Windows PCs<br />
**Any device with a web browser<br />
<br />
You must have exactly one Core. You may have as many Media Directors and Orbiters as you please. For a more detailed explanation, including hardware recommendations, see [[User_Manual#Hardware|this section]] of the User Manual.<br />
<br />
You will also need additional hardware for certain functionality. Here are some examples:<br />
*Recording/Watching TV - PCI or Ethernet based TV tuner<br />
*Security - Sensors, device to connect sensors to the system, IP-cameras<br />
*Home control and automation - Home automation computer adapter, control system compatible devices (switches, thermostats, etc)<br />
*A/V equipment control - IR Transceiver, RS-232 cabling<br />
*Telecommunication - VoIP provider, VoIP phones (or at least some microphones attached to Media Directors)<br />
<br />
You don't have to buy everything at once - you can expand your system as you please.<br />
<br />
===Why do I need two network cards in my Core?===<br />
LinuxMCE is built to automate as many tasks as possible. In order to do this, it monitors new connections to your network. This allows LinuxMCE to immediately react and automatically configure new networked hardware. This includes setting up VoIP phones and adding media from other systems or Network Attached Storage (NAS) devices. <br />
<br />
The LMCE or "internal" network hosts all of your LMCE devices and media sources, and is connected to the "internal" or second NIC on your core server. The first or "external" NIC can simply connect to your existing network. You can keep any existing routers and DHCP servers you wish on your "external" existing home network. The LMCE core server will connect to that network via the external NIC, and if configured that way, will receive a DHCP lease IP address like any other device. Thus your LMCE core server effectively sits between your "external" and "internal" networks using NICs 1 and 2 respectively.<br />
<br />
I basic diagrammatic guide is [[Network_Setup|here.]]<br />
<br />
But note - anything on your existing network that you want to interact with LMCE, such as NAS devices, wireless APs, PCs that may contain media, VoIP phones, ethernet based security or home automation equipment, should be moved onto the LMCE internal network. From that point it will provide DHCP services and Internet routeing to those devices.<br />
<br />
For that reason, it is important not to put any DHCP servers on your internal network. LMCE must provide that. Any existing DHCP servers on your external network are perfectly fine and can remain, as these do not effect the internal network.<br />
<br />
Ideally, you will eventually (or immediately) move all your devices onto the LMCE internal network, for simplicity. This is highly recommended. This would leave your external network as nothing but a simple link from the core's external NIC to your Internet connection device. <br />
<br />
Some (most?) people have an ADSL modem that also provides routeing functionality - thus your LMCE core will route all Internet bound traffic to this modem, and it will route the traffic on to your ISP. <br />
<br />
Others use broadband modems as a "bridge", typically with a PPPoE dialer, and bridge their public IP address directly to the LMCE core server, thus the core is effectively directly on the Internet and performs all the routing to your ISP itself. This approach is equally valid as the core has a full firewall making it secure. This configuration can be a little trickier to set up, but has the advantage of making VoIP setup much easier.<br />
<br />
Still others have both an ADSL/cable modem and a separate router device on the external network. The LMCE core server routes to the router device, and it routes either to or through the broadband device to your ISP. Again, this is valid, but often unnecessarily complicated.<br />
<br />
===Why does LinuxMCE Require nVidia graphics cards? Why can't I use my ATI card?===<br />
Any system that is going to be used as a Media Director (including a hybrid Core) should have an nVidia graphics card, 6200 or better. This is technically not a requirement, but it is a very strong suggestion. Here's why:<br />
<br />
*ATI's Linux drivers do not properly support all the features LinuxMCE needs to run the graphical overlay<br />
*Because the drivers don't support LinuxMCE's feature set, we haven't done enough refinement of the ATI device templates to make it work without lots of manual intervention<br />
*Even with proper setup - which takes an extreme amount of effort - the results are not all that good.<br />
<br />
The bottom line, nVidia has better support in Linux than ATI, allowing LinuxMCE to do a lot more stuff. Using an nVidia card will save a lot of manual configuration and give a better user experience. For these reasons, LinuxMCE only recommends nVidia cards.<br />
<br />
''LinuxMCE developers will NOT help you configure graphics cards that do not meet this requirement. You are more than welcome to use other hardware, but do so at your own risk.''<br />
<br />
For more information see [[Display Drivers]].<br />
<br />
===How do I install LinuxMCE?===<br />
There are two ways to install LinuxMCE. Both are detailed in the [[Installation Guide]], here's a short summary of each. '''Be sure to read the [[Installation Guide]] in its entirety''' before installing LinuxMCE - it contains '''very important''' information.<br />
<br />
No matter which you choose, it's important to realize that LinuxMCE is not a Linux distribution - it's actually built upon Kubuntu. The most recent version of LinuxMCE is 0710, which installs on top of Kubuntu 7.10. Do not attempt to install LinuxMCE 0710 on Kubuntu 8.04 or 8.10 - it will not work. (LinuxMCE version 0810 is under development - [[LinuxMCE-0810_alpha2|alpha versions]] are available for testing - these should not be used by new users. Not all features are complete, and not all features are stable.)<br />
====DVD Method====<br />
This method will use the entire hard drive and will setup LinuxMCE with default settings. If you want more control over the installation, use the CD method. Booting from the DVD will start the install process.<br />
<br />
Default settings include:<br />
*Automatically install Kubuntu 7.10<br />
*Use the whole hard drive - wiping anything on it<br />
*Start a DHCP server on boot<br />
<br />
====CD Method====<br />
This is a two step process. First, you must install Kubuntu 7.10. '''Do not apply any Kubuntu updates.''' Doing so may cause issues with the LinuxMCE install. Then, start the CD installation from within Kubuntu (not as a boot disc). Details about this process are in the [[Installation Guide]].<br />
<br />
Additional configuration options include:<br />
*Custom partition setup<br />
*Run installation from ISO images (instead of actual discs)<br />
<br />
==First Boot==<br />
===Nothing came up on my TV! What's wrong?===<br />
Probably nothing serious. See [[AVWizard#What_to_do_if_A.2FV_Wizard_does_not_start|this page]].<br />
===My Network Card Doesn't Work! Now What?===<br />
There are some devices that don't work out of the box. [[Unrecognized_NIC|This page]] has more information on getting NICs to work.<br />
===How do I login to a LinuxMCE system?===<br />
In order to do certain things - like system configuration, or general computing - you will need to provide login information. See [[Logging_In]] for details.<br />
===How do I configure LinuxMCE?===<br />
Much of the initial configuration is handled in the installation. The remaining system setup is handled by the [[AVWizard|A/V Wizard]], which automatically launches on the first boot.<br />
<br />
For additional configuration options, see the [[LinuxMCE Admin Website]] (http://dcerouter/ or http://192.168.80.1/) or re-run the A/V Wizard.<br />
<br />
==General Information==<br />
===How are media files organized?===<br />
====General use====<br />
<p>For windows users, you can access the files on the core in Windows explorer's network neighborhood, or by choosing 'Start' 'Run' and typing \\ plus the ip of your core. You will need to login with your user-name and password; it's the same one you use with LinuxMCE Admin. You will see 2 folders: 'public' and 'john', assuming your name is 'John'. Any files that you want everyone in the House to have access to go into the public folder. The folder with your name, John in this case, is your private folder where you can put files that only that only you will have access to. Often times when you choose to save media using the orbiter it will ask you if you want the media to be public or private. If you choose public the media will be saved under the public folder, and if you choose private it will be saved under the private folder with your name. Within those folders you will find some folders called: 'music' (where all ripped cd's go), 'movies' (where all ripped DVD's go), 'videos' (where videos recorded from tv or camcorders go), pictures (where your pictures go), and 'documents' (where your documents go). When you go to play some media in the orbiter by choosing the buttons music, movies, videos, pictures or documents, you will see combined together all the media from the family's public folder as well as the media from your own personal private folder.</p><br />
<br />
<p>So, for example, if you rip a CD 'Madonna' and make it public, and rip a CD 'Rolling Stones' and make it private, and your spouse rips a CD 'Fleetwood Mac' and makes it private, then when you touch music on the orbiter you will see 'Madonna' and 'Rolling Stones', and when your spouse touches music your spouse will see 'Fleetwood Mac' and 'Madonna'. Assuming your name is john and your spouse is susan, then if you browse the network share, you will find 'Madonna' in the folder public\music and you will find 'Rolling Stones' in the folder john\music. If, in LinuxMCE admin your user has 'can modify configuration' checked, then that means you are also able to browse everybody else's private folders too. So in addition to 'public' and 'john', you will also see a folder 'susan', which contains 'music' which contains 'Fleetwood Mac'. If that option is not checked for Susan, then she will only see the folder 'public' and 'susan' and will not see your private folder 'john'.</p><br />
<br />
<p>Note that even if you check that option giving yourself access to everyone's private folders, when you go to browse media on the orbiter you will still only see public files plus your own private files, just so you're not bothered with everyone else's.</p><br />
<br />
<p>To maintain the media files, including copying deleting and renaming, you can either use another PC and a network share, such as a Windows PC with Windows Explorer, or in the LinuxMCE admin web site you can choose Media & Files, Browse.</p><br />
<br />
<p>Note that LinuxMCE maintains an internal database of all your media, including various attributes such as the actors in a movie or the composer of a song. This makes searching very comfortable. For example if you touch the music button, then start typing, you will see all attributes. For example after you touch 'G', you may see 'Geffen Studios (studio)', 'Get You Back (song)', 'GNR Live (album)', and 'Guns N Roses (performer)'. You can continue typing to narrow your entries down further, and touch any entry then 'view' to see all the music that matches. The resulting screen even does cross matching and shows pictures for each attribute.</p><br />
<br />
<p>When you rip media within LinuxMCE the attributes are created automatically. You can view attributes or change them in the LinuxMCE admin site. LinuxMCE also monitors any media that you may add or change outside of LinuxMCE, such as using Windows Explorer. For example if you copy files over in Windows Explorer, LinuxMCE will automatically scan the files and add the attributes to its internal database so you can still search. Also if you rename or delete files, LinuxMCE will automatically update your database accordingly.</p><br />
<br />
<p>If you add a plug-and-play network attached storage device, within each media folder you will see a subfolder for that device and you will be able to move files to and from it.</p><br />
<br />
====Technical explanation====<br />
<p>The public directory maps to /home/public/data, and each user's private directory maps to /home/user_xxxx/data, where xxxx is the internal user ID. The name 'john' is a symlinc to user_xxxx for convenience. The program /usr/pluto/bin/UpdateMedia uses INotify to monitor all /home/public/data and /home/user_xxxx/data folders, so it can rescan whenever the directory is changed. All attributes are stored in the MySql database pluto_media. Each file is a record in the 'File' table. UpdateMedia creates an extended attribute called 'ID' for each file with the primary key of each file. That way if you move or rename a file UpdateMedia will see the extended attribute and your attributes will not be lost--it just updates the database. If you want to add more storage you can map drives under those directories. For example, if you have another 2TB drive array that you want to use for both public music and your private movies, create 2 directories on that array, let's say: public_music and john_movies. Using a network mount, or a symlinc to a network mount, create a folder such as /home/public/data/music/my_2TB_nas that maps to public_music and /home/user_xxxx/data/movies/my_2TB_nas that maps to john_movies. Then when you browse music or movies in the orbiter you will see a folder 'my_2TB_nas' to access the files on that new drive. When you add a plug-and-play network attached storage, LinuxMCE automatically adds a folder within every single directory, such as /home/public/data/music/new_nas, /home/public/data/movies/new_nas, /home/user_xxxx/data/videos/new_nas, and these are automatically mapped to corresponding folders on the NAS. This makes it very easy for a novice to just plug in a NAS and immediately use it without any technical knowledge. However if you want to change this behavior, just remove the symlincs our plug and play script created.</p><br />
<br />
===What are scenarios?===<br />
[[Scenarios]] (aka activities) are the buttons that appear on the main menu of every controller, such as Web pads, PDAs, mobile phones, and Media Director PCs. They trigger any number of actions which can include anything from changing lighting to starting media playback to changing climate settings. Scenarios are specific to rooms. A scenario can affect any device anywhere in the house, but certain scenarios will only be displayed in certain rooms. This is so that when you are in a particular room, you will only see the scenarios that you are likely to use from that room.<br />
See [[What_scenarios_are_created_automatically?|this page]] to learn about what scenarios are created automatically.<br />
===Does LinuxMCE support encrypted DVD's?===<br />
The short answer: yes - if it is legal in your area. You will have to add optional software to enable the features. See [[Encrypted_DVD's| this page]] for more information.<br />
===How can I use additional mouse buttons for LinuxMCE?===<br />
See [[Use_Additional_Mouse_Buttons|this page]]<br />
===How should I format additional hard drives?===<br />
From "blog gelusi: Linux Tuning Guide" (http://gelusi.blogspot.com/2008/02/linux-tuning-guide.html)<br />
<br />
1. Filesystem<br />
Block sizes<br />
<br />
For filesystems dedicated to serving fairly large files, adopting a larger than default 1024 byte block size may yield significant<br />
performance gains.<br />
<br />
Recent transactions on the linux kernel list suggest that setting the block sizein an ext2 file system to 4096 instead of the <br />
default 1024 will result in less file fragmentation, faster fsck's, faster deletes and faster raw read speed, due to the reduced <br />
number of seeks.<br />
<br />
Unfortunately this cannot be changed on the fly. Only a reformat will make this so. The command to format a file system with 4096 <br />
byte blocks is:<br />
<br />
mke2fs -b 4096 /dev/whatever<br />
<br />
Additionally, on any filesystems except those used for logfiles, the default of 5% reserved for root use is excessive for large <br />
file systems, so the command to make the filesystem can be augmented to<br />
<br />
mke2fs -b 4096 -m 1 /dev/whatever<br />
<br />
to set the reserved fraction to 1 percent.<br />
<br />
Then if you want a journaling (ext3) filesystem:<br />
<br />
mke2fs -b 4096 -m 1 -j /dev/whatever<br />
<br />
Note, no further configuration should be necessary as new drives will be auto-discovered.<br />
<br />
==Fixing Problems==<br />
===What if I forget my web admin password?===<br />
[[Reset_the_password_for_the_LinuxMCE_Admin_site|See this article]]<br />
===What if I forget my linuxmce/upgrade account password?===<br />
[[Resetting_Account_Passwords|See this article]]<br />
===I can't access my media files over the network!===<br />
[[I can't access my media files over the network|See this article]].<br />
===What if you don't have a driver for my home automation device?===<br />
[[What if you don't have a driver for my home automation device|See this article]].<br />
===What if my problem isn't listed here?===<br />
It may be listed on the [[Troubleshooting]] page.<br />
<br />
If not, it's time to do some research on your own. [[Main_Page|The LinuxMCE wiki]] is full of information - try using the search feature or browsing categories. See if anyone else has had the same issue by searching on [http://forum.linuxmce.org/ the forum].<br />
<br />
When all else fails, maybe someone else has the answer for you. Try posting on [http://forum.linuxmce.org/ the forum] or our IRC channel (irc.freenode.net #linuxmce).<br />
<br />
Remember, LinuxMCE doesn't have any paid employees, so don't get annoyed if no one gets back to you right away. We're all very busy people who have lives outside of LinuxMCE.</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090519Minutes&diff=1920320090519Minutes2009-05-28T01:51:45Z<p>Jimbodude: /* Topics and Discussion */ typo</p>
<hr />
<div>Meeting chair: jimbodude<br />
<br />
Minutes prepared by: jimbodude<br />
<br />
==Attendance==<br />
Active participants<br />
*dlewis<br />
*jimbodude<br />
*jondecker76<br />
*possy<br />
*tkmedia<br />
*totallymaxed<br />
*TSCHAK<br />
*Zaerc<br />
<br />
==Topics and Discussion==<br />
*Meeting began at 10:04 EDT<br />
*The agenda from the previous meeting were informally accepted<br />
*Creation of a standardized testing methodology has been deferred until after the 0810 release<br />
*A formal 0810 release date was not chosen<br />
**This release will have many blockers and pitfalls<br />
**The discussion of a formal release date is deferred until 0810 Beta release<br />
*The [[Bug Reporting]] article will be made more LinuxMCE specific by '''jimbodude'''<br />
*'''possy''' is managing release milestones - no major news there<br />
*Critical defects<br />
**IR/GSD Bugs<br />
***'''jondecker76''' is working on these<br />
**MythTV instability (Trac #195)<br />
***Causes are being investigated by '''jondecker76'''<br />
*Critical outstanding features<br />
**Re-enable Remote Assistance<br />
**Create a deb package for Orbiter<br />
**DVD Installer<br />
***It was decided that this feature is a '''''blocker for beta''''' - mostly because of the need to test thoroughly before release<br />
***The current DVD installer method, which involves VMWare, is not acceptable for 0810<br />
***A new method using packages cached on DVD should be created<br />
***'''totallymaxed''' will be heading up this effort<br />
*PVR Recording File Structure<br />
**All recordings (MythTV or VDR) will be stored in ''/home/public/data/pvr'' - the usual symlinks will be created for each storage device<br />
**MythTV will have storage groups for each user's directory (including 'public') on each storage device<br />
**'''jondecker76''' is heading up this effort<br />
*LinuxMCE-specific Installation Numbers<br />
**Currently, installation numbers are generated by a script running on Pluto's website<br />
**A new installation number generation script will be created and run from a server controlled by LinuxMCE<br />
**New installation numbers will be assigned starting at "1000000"<br />
*LinuxMCE 501c3 Status<br />
**After a few additional signatures, the form will be sent for filing<br />
**'''dlewis''' and '''TCSHAK''' are following up with this<br />
*LinuxFund<br />
**In order to be considered, we must pick focus areas<br />
***Orbiter alternatives<br />
***Media Plug-in debugging/improvements<br />
**'''dlewis''' will follow up with this<br />
*Google Summer of Code<br />
**'''dlewis''' will look into getting LinuxMCE on the list for next summer<br />
*Future meeting scheduling<br />
**A mailing list will be created to facilitate asynchronous communication<br />
**This will help in both meeting scheduling and general communication<br />
**Contact '''jimbodude''' on the forum, IRC, or by wiki-e-mail with your e-mail address if you want to be on it<br />
*Meeting ended at 11:48 EDT</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090519Minutes&diff=1920220090519Minutes2009-05-28T01:47:34Z<p>Jimbodude: New page: Meeting chair: jimbodude Minutes prepared by: jimbodude ==Attendance== Active participants *dlewis *jimbodude *jondecker76 *possy *tkmedia *totallymaxed *TSCHAK *Zaerc ==Topics and Disc...</p>
<hr />
<div>Meeting chair: jimbodude<br />
<br />
Minutes prepared by: jimbodude<br />
<br />
==Attendance==<br />
Active participants<br />
*dlewis<br />
*jimbodude<br />
*jondecker76<br />
*possy<br />
*tkmedia<br />
*totallymaxed<br />
*TSCHAK<br />
*Zaerc<br />
<br />
==Topics and Discussion==<br />
*Meeting began at 10:04 EDT<br />
*The agenda from the previous meeting were informally accepted<br />
*Creation of a standardized testing methodology has been deferred until after the 0810 release<br />
*A formal 0810 release date was not chosen<br />
**This release will have many blockers and pitfalls<br />
**The discussion of a formal release date is deferred until 0810 Beta release<br />
*The [[Bug Reporting]] article will be made more LinuxMCE specific by '''jimbodude'''<br />
*'''possy''' is managing release milestones - no major news there<br />
*Critical defects<br />
**IR/GSD Bugs<br />
***'''jondecker76''' is working on these<br />
**MythTV instability (Trac #195)<br />
***Causes are being investigated by '''jondecker76'''<br />
*Critical outstanding features<br />
**Re-enable Remote Assistance<br />
**Create a deb package for Orbiter<br />
**DVD Installer<br />
***It was decided that this feature is a '''''blocker for beta''''' - mostly because of the need to test thoroughly before release<br />
***The current DVD installer method, which involves VMWare, is not acceptable for 0810<br />
***A new method using packages cached on DVD should be created<br />
***'''totallymaxed''' will be heading up this effort<br />
*PVR Recording File Structure<br />
**All recordings (MythTV or VDR) will be stored in ''/home/public/data/pvr'' - the usual symlinks will be created for each storage device<br />
**MythTV will have storage groups for each user's directory (including 'public') on each storage device<br />
**'''jondecker76''' is heading up this effort<br />
*LinuxMCE-specific Installation Numbers<br />
**Currently, installation numbers are generated by a script running on Pluto's website<br />
**A new installation number generation script will be created and run from a server controlled by LinuxMCE<br />
**New installation numbers will be assigned starting at "1000000"<br />
*LinuxMCE 501c3 Status<br />
**After a few additional signatures, the form will be sent for filing<br />
**'''dlewis'' and '''TCSHAK''' are following up with this<br />
*LinuxFund<br />
**In order to be considered, we must pick focus areas<br />
***Orbiter alternatives<br />
***Media Plug-in debugging/improvements<br />
**'''dlewis''' will follow up with this<br />
*Google Summer of Code<br />
**'''dlewis''' will look into getting LinuxMCE on the list for next summer<br />
*Future meeting scheduling<br />
**A mailing list will be created to facilitate asynchronous communication<br />
**This will help in both meeting scheduling and general communication<br />
**Contact '''jimbodude''' on the forum, IRC, or by wiki-e-mail with your e-mail address if you want to be on it<br />
*Meeting ended at 11:48 EDT</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=19200DeveloperMeetings2009-05-28T00:37:31Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Tuesday, May 19, 14:00 GMT/UTC, 10:00AM New York, 16:00 Berlin Time, 15:00 London Time)<br />
**[[20090519Agenda|Agenda]]<br />
**[[20090519Transcript|Transcript]]<br />
**[[20090519Minutes|Minutes]]<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=19110DeveloperMeetings2009-05-19T14:29:38Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Tuesday, May 19, 14:00 GMT/UTC, 10:00AM New York, 16:00 Berlin Time, 15:00 London Time)<br />
**[[20090519Agenda|Agenda]]<br />
**[[20090519Transcript|Transcript]]<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090519Agenda&diff=1910920090519Agenda2009-05-19T14:08:30Z<p>Jimbodude: </p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Tuesday, May 19<br />
**'''Time:''' 14:00 GMT/UTC, 10:00AM New York, 16:00 Berlin Time, 15:00 London Time<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' #linuxmce-meeting<br />
**'''In case anyone is reading this: I am strongly opposing changing the meeting from an IRC meeting to an audio meeting''' - To many disadvantages in an audio meeting, like ability to understand people, ability to mark specific things for feature reference, to name just a few.<br />
<br />
==Agenda==<br />
<br />
===Items from previous meeting===<br />
*Standardized testing procedures (hari)<br />
*0810 Release Scheduling ('''NO ONE''')<br />
*Improved defect tracking (jimbodude)<br />
**http://wiki.linuxmce.org/index.php/Bug_Reporting<br />
<br />
===Milestones===<br />
I propose to better take care of the milestones in trac, and move all open tickets to milestone beta or further out. (and I will take care of it, if there is a consent [[User:Posde|posde]])<br />
<br />
===0810 Progress Review===<br />
*Review of major bugs<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===High Level Design Discussions===<br />
*Is DVD Install a blocker for Beta? (posde)<br />
*MythTV recording directory structure (jondecker)<br />
Items deferred from previous meeting<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural===<br />
*LinuxFund<br />
*501(c)(3)<br />
*Schedule next meeting<br />
**Asynchronous scheduling communication</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=New_In_0810&diff=18705New In 08102009-04-30T21:15:59Z<p>Jimbodude: </p>
<hr />
<div>Here's a list of new features and bug fixes in the 0810 release. This list is not exhaustive - it is meant to highlight the features most users will notice.<br />
<br />
==Media==<br />
===New Features===<br />
*[http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21 Upgrade MythTV to 0.21]<br />
**Add ability to use myth's player from Video scenario, enabling some of myth's playback features such as commercial skipping (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/131 131])<br />
**Added ability to choose where to save recordings - including private recordings (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/124 124])<br />
*Media Metadata<br />
**[http://forum.linuxmce.org/index.php?topic=6571.0 Media metadata import feature] (SVN: [http://svn.linuxmce.org/trac.cgi/changeset/21538 21538], [http://svn.linuxmce.org/trac.cgi/changeset/21543 21543])<br />
**[http://forum.linuxmce.org/index.php?topic=6919.0 Pull metadata from IMDB] (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/53 53], [http://svn.linuxmce.org/trac.cgi/ticket/52 52])<br />
**Added button to clear all missing media files from the database (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/6 6])<br />
**Added ability to filter out all media with cover art from media sync (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/47 47])<br />
*[http://forum.linuxmce.org/index.php?topic=5677.0 On-Orbiter TV Guide]<br />
*[http://forum.linuxmce.org/index.php?topic=5803.0 Play list export feature]<br />
*[http://forum.linuxmce.org/index.php?topic=4083.0 MAME (Arcade Game emulator) game support] (Trac [http://svn.linuxmce.org/trac.cgi/ticket/40 40] SVN: [http://svn.linuxmce.org/trac.cgi/changeset/21567 21567], [http://svn.linuxmce.org/trac.cgi/changeset/21568 21568], [http://svn.linuxmce.org/trac.cgi/changeset/21569 21569], [http://svn.linuxmce.org/trac.cgi/changeset/21570 21570], [http://svn.linuxmce.org/trac.cgi/changeset/21573 21573], [http://svn.linuxmce.org/trac.cgi/changeset/21574 21574], [http://svn.linuxmce.org/trac.cgi/changeset/21597 21597], [http://svn.linuxmce.org/trac.cgi/changeset/21598 21598], [http://svn.linuxmce.org/trac.cgi/changeset/21599 21599], [http://svn.linuxmce.org/trac.cgi/changeset/21603 21603], [http://svn.linuxmce.org/trac.cgi/changeset/21620 21620], and probably others)<br />
*Infrared repeats parameter can now be edited in the web admin<br />
*The playlist editor has been redone, and a Vertical mode added as well<br />
*Playlist export to .m3u and .pls functionality<br />
*New Unmanaged room type allows you to designate a room where no automatically generated scenarios appear. This give you total control over scenarios for that room.<br />
*Added ability to grow ext2/ext3 Software RAIDs from the web admin (SVN: [http://svn.linuxmce.org/trac.cgi/changeset/21687 21687], [http://svn.linuxmce.org/trac.cgi/changeset/21685 21685])<br />
*Added new ability to fix the most common software RAID problem from the web admin. When a drive is kicked from the array, it can be re-added now from the web admin instead of having to fix it with the command line. (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/108 108] SVN: [http://svn.linuxmce.org/trac.cgi/changeset/21694 21694])<br />
*Media files on CD's or DVD's are automatically detected and imported into the media database (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/141 141])<br />
*Auto-tagging rules are available on a per-directory basis (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/158 158])<br />
<br />
===Bug Fixes===<br />
*Media attribute import from Amazon/IMDB is now smarter (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/52 52])<br />
*Fixed path/filename escaping in web admin (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/57 57])<br />
*"Docs" scenario removed - no supporting player (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/56 56], SVN: [http://svn.linuxmce.org/trac.cgi/changeset/21572 21572],)<br />
*Fixed mounting of shares with special characters in their names (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/55 55])<br />
*Fixed mounting of "non-browsable" samba shares (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/38 38])<br />
* *.dvd.keys.tar.gz, *mpg.png, and *.mpg.png.tnj are no longer displayed in the web admin<br />
* accompanying *.dvd.keys.tar.gz will follow source file when renaming/deleting from the web admin<br />
* fixed a bug where deleting a performer's picture would delete the file entirely from the system. Now the picture is only deleted if nothing else references it<br />
* fixed similar bug that would permanently delete a picture when disassociating it from a file.<br />
* changing privacy settings via web admin now flags the orbiters to regenerate<br />
<br />
==Hardware Support==<br />
*USB Microphone Support (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/39 39], [http://svn.linuxmce.org/trac.cgi/ticket/161 161])<br />
*[http://forum.linuxmce.org/index.php?topic=6210.0 New Z-Wave driver] (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/44 44], SVN: [http://svn.linuxmce.org/trac.cgi/changeset/21621 21621], [http://svn.linuxmce.org/trac.cgi/changeset/21622 21622], [http://svn.linuxmce.org/trac.cgi/changeset/21623 21623], [http://svn.linuxmce.org/trac.cgi/changeset/21624 21624], [http://svn.linuxmce.org/trac.cgi/changeset/21648 21648])<br />
*Better support for CM11 X-10 module (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/8 8])<br />
*Mobile orbiter support for S60 v3 devices (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/43 43])<br />
*Initial support for EnOcean devices (Trac: http://svn.linuxmce.org/trac.cgi/ticket/100)<br />
<br />
==Other==<br />
===New Features===<br />
*Updated base distribution to Kubuntu 0810 (with standard 2.6.27 kernel - updating as Kubuntu updates)<br />
*Cleaned up many packages so they're as close as possible to (if not the same as) Ubuntu's Apt repository versions<br />
*LinuxMCE can now be installed without an active Internet connection (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/26 26])<br />
*Cleaned out a lot of hard coded stuff from scripts (SVN: [http://svn.linuxmce.org/trac.cgi/changeset/21582 21582], and others)<br />
*Dutch language support (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/34 34], [http://svn.linuxmce.org/trac.cgi/ticket/35 35])<br />
*Enhancements to Climate Control (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/127 127])<br />
*New Launch Manager (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/48 48])<br />
*Interactive tool tips in the web admin (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/155 155])<br />
*New web orbiter option - iOrbiter (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/16 16])<br />
<br />
===Bug Fixes===<br />
*Scenario Sorting works more reliably (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/140 140])<br />
*Dynamic DNS now obtains actual external address (Trac: [http://svn.linuxmce.org/trac.cgi/ticket/154 154])<br />
<br />
==LinuxMCE Dev Tools==<br />
===Bug Fixes===<br />
*SqlCVS has been fixed and now works<br />
==LinuxMCE Project Infrastructure==<br />
*Bug tracking now managed by [http://svn.linuxmce.org/ Trac] (formerly Mantis)<br />
*[http://linuxmce.org/news.php?id=28 New 12-month release schedule]<br />
*[http://linuxmce.org/news.php?id=28 New servers]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090426Agenda&diff=1867220090426Agenda2009-04-26T15:03:17Z<p>Jimbodude: </p>
<hr />
<div>==Logistics==<br />
*This meeting was '''CANCELED'''<br />
**Attendance was poor - only jimbodude, jondecker, and uplink-lmce were active<br />
**Those in attendance waited for one hour after the start time before canceling<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Sunday, April 26<br />
**'''Time:''' 14:00 GMT/UTC, 10:00AM New York, 16:00 Berlin Time, 15:00 London Time<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' #linuxmce-meeting<br />
**'''In case anyone is reading this: I am strongly opposing changing the meeting from an IRC meeting to an audio meeting''' - To many disadvantages in an audio meeting, like ability to understand people, ability to mark specific things for feature reference, to name just a few.<br />
<br />
==Agenda==<br />
<br />
===Items from previous meeting===<br />
*Standardized testing procedures (hari)<br />
*0810 Release Scheduling ('''NO ONE''')<br />
*Improved defect tracking (jimbodude)<br />
**http://wiki.linuxmce.org/index.php/Bug_Reporting<br />
<br />
===Milestones===<br />
I propose to better take care of the milestones in trac, and move all open tickets to milestone beta or further out. (and I will take care of it, if there is a consent [[User:Posde|posde]])<br />
<br />
===0810 Progress Review===<br />
*Review of major bugs<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===High Level Design Discussions===<br />
Items deferred from previous meeting<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural===<br />
*Schedule next meeting<br />
**Asynchronous scheduling communication</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_alpha2&diff=18664LinuxMCE-0810 alpha22009-04-25T23:41:43Z<p>Jimbodude: added direct links to mirrors, since ubuntu page no longer links to 810.</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==Installation==<br />
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. (download Kubuntu 8.10 release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany])<br />
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.<br />
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.<br />
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.<br />
# Reboot, wait for the activity to stop (see progress on console 8).<br />
<br />
In other words, after installing Kubuntu and upgrading it etcetera:<br />
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.<br />
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz<br />
tar xvf new-installer-alpha-latest.tar.gz<br />
cd new-installer<br />
./pre-install-from-repo.sh<br />
./mce-install.sh<br />
./post-install.sh<br />
reboot<br />
=== nVidia Restricted Driver ===<br />
Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results<br />
<br />
=== MythTV ===<br />
Remove reference to hardy in /etc/apt/sources.list<br />
<br />
from terminal<br />
<pre><br />
sudo apt-get install pluto-mythtv-player<br />
</pre><br />
<br />
Install updated version of pluto-mythtv-plugin<br />
<br />
=== Setup Diskless MD ===<br />
Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].<br />
<br />
=== Upgrading kernel ===<br />
There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.<br />
<br />
== Updates ==<br />
Check if there is no junk like references to hardy in /etc/apt/sources.list then:<br />
sudo apt-get update<br />
sudo apt-get dist-upgrade<br />
Or use a package manager on the KDE desktop for more convenience.<br />
<br />
=== 20090218 (alpha-2.1) ===<br />
*lmce-datalog-db_2.0.0.44.0902180810<br />
*lmce-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-src-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-lmce-datalog_2.0.0.44.0902180810<br />
*pluto-dcerouter_2.0.0.44.0902180810<br />
*pluto-dhcpd-plugin_2.0.0.44.0902180810<br />
*pluto-hald-src_2.0.0.44.0902180810<br />
*pluto-hald_2.0.0.44.0902180810<br />
*pluto-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-dcerouter_2.0.0.44.0902180810<br />
*pluto-src-hal-device-finder_2.0.0.44.0902180810<br />
*pluto-src-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-src-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-updatemedia_2.0.0.44.0902180810<br />
*pluto-updateentarea_2.0.0.44.0902180810<br />
*pluto-updatemedia_2.0.0.44.0902180810<br />
*pluto-zwave-lighting_2.0.0.44.0902180810<br />
*lmce-game-player_2.0.0.44.0902180810<br />
*lmce-game-plugin_2.0.0.44.0902180810<br />
*lmce-src-game-player_2.0.0.44.0902180810<br />
*lmce-src-game-plugin_2.0.0.44.0902180810<br />
<br />
==== 20090222 (alpha-2.1.1) ====<br />
*pluto-dcerouter_2.0.0.44.0902220810<br />
*pluto-bluetooth-dongle_2.0.0.44.0902220810<br />
<br />
=== 20090301 (alpha-2.2) ===<br />
SVN revision: 21746<br />
<br />
To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:<br />
dpkg -r --force-all pluto-storage-devices<br />
apt-get update<br />
apt-get install -f<br />
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!<br />
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql<br />
*pluto-boot-scripts_2.0.0.44.0903010810<br />
*pluto-network-storage_2.0.0.44.0903010810<br />
*pluto-skins-basic_2.0.0.44.0903010810<br />
*pluto-src-network-storage_2.0.0.44.0903010810<br />
*pluto-src-std-plugins_2.0.0.44.0903010810<br />
*pluto-src-updatemedia_2.0.0.44.0903010810<br />
*pluto-std-plugins_2.0.0.44.0903010810<br />
*pluto-storage-devices_2.0.0.44.0903010810<br />
*pluto-system-database_2.0.0.44.0903010810 <br />
*pluto-updatemedia_2.0.0.44.0903010810<br />
*pluto-website-admin_2.0.0.44.0903010810<br />
<br />
=== 20090308 (alpha-2.3) ===<br />
SVN revision: 21765<br />
<br />
Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead. <br />
Also remove the pluto-storage-devices, hopefully for the last time. <br />
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things. <br />
<br />
*pluto-asterisk_2.0.0.44.0903080810<br />
*pluto-src-asterisk_2.0.0.44.0903080810<br />
*pluto-src-text-to-speech_2.0.0.44.0903080810<br />
*pluto-src-updatemedia_2.0.0.44.0903080810<br />
*pluto-storage-devices_2.0.0.44.0903080810<br />
*pluto-system-database_2.0.0.44.0903080810<br />
*pluto-text-to-speech_2.0.0.44.0903080810<br />
*pluto-updatemedia_2.0.0.44.0903080810<br />
*pluto-website-admin_2.0.0.44.0903080810<br />
<br />
=== 20090315 (alpha-2.4) ===<br />
SVN revision: 21798<br />
<br />
The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]<br />
<br />
<br />
The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:<br />
sudo apt-get install libsox-fmt-all <br />
cd /usr/pluto/bin<br />
sudo rm generate_users_voicemenu.pl<br />
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw<br />
sudo chmod 755 generate_users_voicemenu.pl<br />
sudo ./generate_users_voicemenu.pl<br />
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.<br />
<br />
<br />
<br />
*pluto-asterisk_2.0.0.44.0903150810<br />
*pluto-boot-scripts_2.0.0.44.0903150810<br />
*pluto-makerelease_2.0.0.44.0903150810<br />
*pluto-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-orbitergen_2.0.0.44.0903150810<br />
*pluto-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-asterisk_2.0.0.44.0903150810<br />
*pluto-src-makerelease_2.0.0.44.0903150810<br />
*pluto-src-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-src-orbitergen_2.0.0.44.0903150810<br />
*pluto-src-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-std-plugins_2.0.0.44.0903150810<br />
*pluto-src-text-to-speech_2.0.0.44.0903150810<br />
*pluto-std-plugins_2.0.0.44.0903150810<br />
*pluto-system-database_2.0.0.44.0903150810<br />
*pluto-text-to-speech_2.0.0.44.0903150810<br />
*pluto-updateentarea_2.0.0.44.0903150810<br />
*pluto-website-admin_2.0.0.44.0903150810<br />
<br />
=== 20090322 (alpha-2.5) ===<br />
SVN revision: 21827<br />
<br />
*freepbx_0+2.3.1-2<br />
*pluto-asterisk_2.0.0.44.0903220810<br />
*pluto-dhcpd-plugin_2.0.0.44.0903220810<br />
*pluto-install-scripts_2.0.0.44.0903220810<br />
*pluto-raid-tools_2.0.0.44.0903220810<br />
*pluto-skins-basic_2.0.0.44.0903220810<br />
*pluto-src-asterisk_2.0.0.44.0903220810<br />
*pluto-website-admin_2.0.0.44.0903220810<br />
<br />
=== 20090401 (alpha-2.6) ===<br />
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:<br />
I'm not sure on this, but you may have to manually install LM via apt-get<br />
After you upgrade, reboot your core <br />
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished<br />
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)<br />
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).<br />
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.<br />
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.<br />
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed<br />
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.<br />
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)<br />
<br />
* lmcevdr_1.1-10_all.deb<br />
* pluto-website-admin_2.0.0.44.0904010019_i386.deb<br />
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb<br />
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb<br />
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb<br />
* pluto-system-database_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb<br />
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbiter_2.0.0.44.0904010019_i386.deb<br />
<br />
=== 20090405 (alpha 2.7) ===<br />
From now on, the SVN version will part of the deb name.<br />
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me. <br />
* lmce-game-player_2.0.0.44.090405.21873_i386.deb<br />
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb<br />
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb<br />
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb<br />
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)<br />
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb<br />
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb<br />
* pluto-system-database_2.0.0.44.090405.21873_i386.deb<br />
* pluto-website-admin_2.0.0.44.09040521873_i386.deb<br />
<br />
=== 20090412 (alpha 2.8) ===<br />
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic). <br />
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups<br />
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.<br />
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org<br />
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.<br />
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename<br />
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)<br />
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template<br />
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template<br />
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes<br />
<br />
=== 20090413 (alpha 2.9 jondecker special) ===<br />
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo<br />
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support<br />
<br />
=== 20090419 (alpha 2.10 pbr) ===<br />
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb<br />
* pluto-website-admin_2.0.0.44.09041921897_i386.deb<br />
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb<br />
* pluto-system-database_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-player_2.0.0.44.09041921897_i386.deb<br />
* pluto-asterisk_2.0.0.44.09041921897_i386.deb<br />
<br />
=== 20090426 (upcoming...) ===<br />
With this release, MythTV now takes advantage of storage groups. Do some recordings, and try recording to a few different storage groups. <br />
Please test this out and report any problems such as duplicate attributes appearing in pluto_media, icon image not showing up, recordings failing to record, etc. Also, if you do have problems, try a reboot and see if it fixes the problem, then please let me know if the reboot fixed your problem. - jondecker76<br />
<br />
* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD<br />
* pluto-boot-scripts (234) - small fix to get rid of a warning on DCERouter startup re missing dir., New MythTV directory structure stuff<br />
* pluto-asterisk - Added Support for Cisco 7910 phone<br />
* pluto-dhcpd-plugin - Added support for Cisco 7910 phone<br />
* pluto-system-database (211) - '''If new devices are added, the pluto-system-database needs to be updates as well'''<br />
* pluto-storage-devices (533) - Adds new tv_shows_* directories. Generates MythTV storage groups<br />
* pluto-std-plugin (134,153) - adds some useful debugging snippets that helped trace down the problem of mythtv attributes not adding to pluto_media<br />
* pluto-mythtv-plugin (134,153) - lots of changes to facilitate the new storage groups<br />
* pluto-network-storage (503,508) - small changes to work with new tv_shows_* directories<br />
<br />
== Previous alpha releases ==<br />
* Notes about [[LinuxMCE-0810 alpha1]]<br />
* Notes about [[LinuxMCE-0810 alpha0]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090426Agenda&diff=1865020090426Agenda2009-04-24T23:09:12Z<p>Jimbodude: New page: ==Logistics== *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 t...</p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Sunday, April 26<br />
**'''Time:''' 14:00 GMT/UTC, 10:00AM New York, 16:00 Berlin Time, 15:00 London Time<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' #linuxmce-meeting<br />
<br />
==Agenda==<br />
<br />
===Items from previous meeting===<br />
*Standardized testing procedures (hari)<br />
*0810 Release Scheduling ('''NO ONE''')<br />
*Improved defect tracking (jimbodude)<br />
**http://wiki.linuxmce.org/index.php/Bug_Reporting<br />
<br />
===0810 Progress Review===<br />
*Review of major bugs<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===High Level Design Discussions===<br />
Items deferred from previous meeting<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural===<br />
*Schedule next meeting<br />
**Asynchronous scheduling communication</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Minutes&diff=1864920090415Minutes2009-04-24T23:08:51Z<p>Jimbodude: </p>
<hr />
<div>Meeting chair: jimbodude<br />
<br />
Minutes prepared by: jimbodude<br />
<br />
==Attendance==<br />
*colinjones<br />
*dlewis<br />
*hari<br />
*jimbodude<br />
*tkmedia<br />
*totallymaxed<br />
*TSCHAK<br />
*Zaerc<br />
<br />
==Topics and Discussion==<br />
*Several bug reports were covered<br />
**Nothing conclusive came out of the discussion<br />
**About 3 bug tickets in, focus was shifted to the next agenda items to keep interest<br />
<br />
*Standardized testing procedures (presented by '''hari''')<br />
**Goal: locate all bugs in a systematic way<br />
**Method:<br />
**#Develop standardized tests for each component (DCERouter, Web Admin, Orbiter, etc...)<br />
**#Assign 2+ people to each component<br />
**#Run tests over 2-3 days<br />
**#Combine results, create new tickets<br />
**If other test procedures are already available, use those to augment<br />
**'''No one has taken direct responsibility for these tasks.'''<br />
<br />
*Release Scheduling<br />
**Goal: focus development efforts in key areas on a flexible, but documented, schedule such that important issues are not overlooked for long periods of time.<br />
**Method:<br />
**#Find things that don't work<br />
**#Assign them to a milestone<br />
**#Pick a date for each milestone's completion<br />
**Things that are broken or need attention: (in no particular order)<br />
***MD booting<br />
***KDE Desktop on MD<br />
***Getting back to Orbiter from KDE<br />
***the desktop is incorrectly sized on TV's at HD resolutions<br />
***login problem on MD<br />
***Auto detect of USBUIRT<br />
***ir codes in sqlcvs<br />
***serial detection<br />
***cisco 7070 wrong room problem<br />
***making more devices PnP<br />
***work on upgrading telecom<br />
***issue with the sony changer<br />
**'''No one has taken responsibility for these tasks'''<br />
<br />
*Update scheduling discussion is deferred until there is a release schedule<br />
*Installation number generation design discussion is deferred in the interest of time and higher priority issues<br />
<br />
*Defect Tracking<br />
**Goal: Improve defect tracking in order to:<br />
***Communicate issues to a team that is distributed<br />
***Bring attention to issues that may otherwise be ignored<br />
***Focus developer efforts on key tasks<br />
***Assist in release scheduling<br />
**Method: Encourage testers to submit bug reports. Draft a defect reporting policy specific to LinuxMCE<br />
**A LinuxMCE policy will be presented at the next meeting for discussion<br />
**'''jimbodude had taken responsibility for these tasks'''<br />
<br />
*Future Meetings<br />
**This meeting was helpful - future meetings are expected to be just as useful, and should be scheduled<br />
**Since the topics at this meeting require significant follow-up work the next meeting will be in one week<br />
**Meetings thereafter may be weekly or bi-weekly - this decision is deferred to the next meeting<br />
**'''jimbodude has taken responsibility for creating an agenda for the next meeting'''<br />
**'''No one has taken responsibility for scheduling the next meeting'''</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18640DeveloperMeetings2009-04-22T22:29:13Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Sunday, April 26, 14:00 GMT/UTC, 10:00AM New York, 16:00 Berlin Time, 15:00 London Time)<br />
**[[20090426Agenda|Agenda]]<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18637DeveloperMeetings2009-04-22T20:47:43Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Date/Time TBD)<br />
**Two times have been proposed - please note if you are unavailable for one time or the other.<br />
***Thursday, April 23, 21:30 GMT/UTC (17:30 New York)<br />
****Cant attend: hari, uplink<br />
***Sunday, April 26, 14:00 GMT/UTC (10:00AM New York)<br />
****Cant attend: hari, jondecker<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18636DeveloperMeetings2009-04-22T16:58:14Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Date/Time TBD)<br />
**Two times have been proposed - please note if you are unavailable for one time or the other.<br />
***Thursday, April 23, 9:30PM GMT/UTC (5:30 New York)<br />
****Cant attend: hari<br />
***Sunday, April 26, 2PM GMT/UTC (10AM New York)<br />
****Cant attend: hari, jondecker<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18635DeveloperMeetings2009-04-22T16:51:48Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Date/Time TBD)<br />
**Two times have been proposed - please note if you are unavailable for one time or the other.<br />
***Thursday, April 23, 9:30PM GMT/UTC (5:30 New York)<br />
****Cant attend: hari<br />
***Sunday, April 26, 2PM GMT/UTC (10AM New York)<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18630DeveloperMeetings2009-04-21T21:07:31Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Date/Time TBD)<br />
**Two times have been proposed - please note if you are unavailable for one time or the other.<br />
***Thursday, April 23, 9:30PM GMT/UTC (5:30 New York)<br />
***Sunday, April 26, 2PM GMT/UTC (10AM New York)<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18609DeveloperMeetings2009-04-17T04:35:25Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*Follow-up to April 15th Meeting (IRC #linuxmce-meeting - Date/Time TBD)<br />
**Place availability [http://www.when2meet.com/?16360-k9rRx here] if interested<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=Bug_Reporting&diff=18545Bug Reporting2009-04-15T20:39:31Z<p>Jimbodude: </p>
<hr />
<div>==Introduction==<br />
In oder to focus the efforts of a software project, it is essential to have a clear understanding of the current status of all defects. This document outlines LinuxMCE's policies on bug reporting.<br />
<br />
==Importance of Reporting Bugs==<br />
There are several reasons to track defects strictly:<br />
*If a bug is not tracked, it may be overlooked and never fixed<br />
*If a bug is not tracked, members of the development team may not know it exists<br />
*Tracking bugs provides a way to determine the functional status of the project<br />
*The bug list provides development team members a place to look for things to contribute<br />
*The bug list provides users a place to formally report issues<br />
*The bug tracking system provides a way to divide up work among the development team<br />
*The bug tracking system provides a way for people to check the status of particular issues and present workarounds or fixes in an organized and manageable way<br />
<br />
==What Bugs Should Be Reported==<br />
Follow these steps:<br />
===Step 1: Determine if the issue is worth reporting===<br />
If the answer to any of these questions is '''"yes"''', then this issue probably '''does not warrant a bug report''':<br />
*Can the issue be phrased as a support request? (for examples: "How do I...", "Is it possible to...", "How do I configure...", "Where is documentation on..."<br />
*Is the issue related to future development? (for examples: "Add a feature for...", "Restructure system so...")<br />
*Is the issue caused by an unrelated software package that doesn't directly affect our project? (for example, say we are making a phone system based in Linux that has a Gnome desktop. Our issue is: "I cannot open text documents in gedit because the Gnome project has provided a broken package". This would not be a bug for our phone system at all, as it doesn't affect our project - though it may be an annoyance to people using our applications)<br />
<br />
If the answer to any of the following questions is '''"yes"''', then it may be time to '''consider reporting a bug''':<br />
*Is a feature completely unusable?<br />
*Is a feature that used to work not working as expected?<br />
*Is an important feature missing that is hindering the usefulness of another feature?<br />
<br />
===Step 2: Determine if the bug is actually expected behavior===<br />
In many cases, software is designed to do things that the user doesn't expect. To avoid reporting bugs when no bug exists, a thorough check of the functionality of the affected component is required. Make sure you have answered the following questions before reporting a bug:<br />
*Do I have a complete understanding of what is happening to produce the bug? (consider checking documentation)<br />
*Have other people experienced this issue and been shown that it is by design? (consider checking forums, IRC channels)<br />
*Is this component under heavy development right now? Perhaps there has been a change in how it works.<br />
<br />
===Step 3: Determine if the bug has already been reported===<br />
Reporting duplicate bugs wastes everyone's time. The reporter takes time to compile their thoughts, the reviewer takes time to mark it as a duplicate, future bug investigators take time to redirect to the proper bug, and the list goes on. To maintain everyone's efficiency, duplicate bugs should be avoided. Make sure you have followed the previous two steps and done significant searching in the bug database before reporting a new bug.<br />
<br />
If a bug ticket already exists for the issue you are trying to report, make sure there is enough information in the ticket. Add any new information you have. Useful information is discussed in the next section.<br />
<br />
===Step 4: Report the bug===<br />
Assuming all of the previous steps have suggested the issue is worth reporting, it's time to make a bug report. The details that go into the report are discussed in the next section.<br />
<br />
==What Data Should Be In The Report==<br />
An uninformative bug report is a waste of time. To make a good bug report, the following items are essential:<br />
*'''A clear title/subject''' - describe what is broken and in what way. This goes in the "Short summary" field in LinuxMCE Trac tickets.<br />
**''Good example'': Unable to adjust screen brightness using hotkeys - works otherwise<br />
**''Bad example'': Brightness doesn't work<br />
*'''Clear description of the issue''' - describe all symptoms of the issue in the body of the report without trailing off into other features. Be sure to explain exactly what you expect to happen, exactly what is happening, and exactly how to make it happen.<br />
**''Good example'': When the hotkeys associated with screen brightness are pressed, the screen brightness should change, but the screen brightness does not change. The expected brightness notification appears in the top right of the screen, but it displays the wrong brightness level.<br />
**''Bad example'': I push the hotkey and nothing happens.<br />
*'''If there is more than one way to perform a task, state exactly which way you did it, and whether the other way works'''<br />
**''Good example'': (taking a break from the brightness examples) Select File --> Load to load the file. Loading the file by double clicking in the file explorer works.<br />
**''Bad example'': Load the file.<br />
*'''When was the last time it worked the way you expected?''' - Is this something that broke recently? When, precisely, did it stop working?<br />
**''Good example'': This worked out of the box in versions 7.04 through 8.10. Using the most recent development packages, it does not work<br />
**''Bad example'': It used to work, now it doesn't.<br />
*'''Step by step instructions to reproduce the issue''' - the more detailed, the better. Do not leave steps out, do not assume any prior knowledge of the issue, even if it is widely known<br />
**''Good example'': While logged into Gnome in an X session, press Fn+F5 or Fn+F6 several times. Notice that the brightness doesn't change, but the brightness notification appears<br />
*'''Note any configuration that may impact this issue''' - If you have configured something differently than expected, be sure to note this.<br />
**''Good example'': I am using the out-of-the box configuration.<br />
**''Good example'': I have changed xorg.conf to try to increase my screen resolution. The lines I changed were...<br />
*'''Hardware description''' - If hardware could affect the issue, be sure to include all relevant information<br />
**''Good example'': I am using a Sony VGN-S480 with nVidia 6200Go graphics card<br />
*'''Workarounds''' - If you've found a way around the issue, add that in to help people who are suffering the same issue and to provide a better picture of what is actually broken<br />
**''Good example'': It is possible to adjust screen brightness using the ''smartdimmer'' command<br />
*'''''MOST IMPORTANTLY: RE-READ THE REPORT BEFORE YOU SEND IT''''' - Re-reading gives you a chance to collect your thoughts, make sure you haven't missed anything, correct typographical errors that make reading difficult, and clarifying your ideas. Be sure your writing is clear and concise. Read the report as if you know nothing about the issue. Look for places where you may have assumed certain knowledge or a certain process.<br />
<br />
When writing your report, be mindful of the following:<br />
*'''Avoid the use of general terms like "it" or "the window".''' Instead, use specifics like "the brightness notification dialog at the top right of the screen"<br />
*'''Give any information that could be related.''' It is generally acceptable to provide too much information, but leaving something out will make the issue harder to address<br />
*This can't be stressed enough: '''''RE-READ THE REPORT BEFORE YOU SEND IT''''' for all the reasons stated above.<br />
<br />
==Fill in Additional Bug Report Fields==<br />
This information is specific to LinuxMCE and the Trac ticket system.<br />
===Your email or username===<br />
Put something here so we know who you are! If we can't identify you as the original reporter, we can't follow up to make sure the bug is fixed.<br />
===Type===<br />
Pick a type so we know what this bug is all about.<br />
*''defect'' - There is a feature in the version you are using that is not working properly<br />
*''defect_patch'' - There is a feature in the version you are using that is not working properly, and you are providing a patch that fixes it. '''This is the standard way to submit a fix patch''' (see also - [[Bug_Reporting#Submitting a Patch|Submitting a Patch]])<br />
*''feature_request'' - Something is missing from the version you are using that should be added<br />
*''feature_patch'' - Something is missing, and you are providing a patch that adds it. '''This is the standard way to submit a feature patch''' (see also - [[Bug_Reporting#Submitting a Patch|Submitting a Patch]])<br />
*''task'' - Something needs doing, but nothing is broken<br />
===Priority===<br />
Pick a priority so we know how serious the issue is.<br />
*''blocker'' - LinuxMCE cannot exist without this bug being addressed<br />
*''critical'' - Functionality of the whole system or a critical component is significantly impaired by this bug<br />
*''major'' - Functionality of a specific component is significantly impaired by this bug<br />
*''normal'' - Functionality of a specific component is slightly impaired by this bug<br />
*''minor'' - Functionality is impaired, but not significantly<br />
*''trivial'' - Functionality may slightly affected, or this bug may simply cause user confusion<br />
===Component===<br />
Determine what area of LinuxMCE is most directly affected.<br />
===Milestone===<br />
When is a reasonable target time for this bug to be addressed? (Most people who are not involved with the development process will leave this blank)<br />
===Version===<br />
What is the most recent version of LinuxMCE that is affected by this bug?<br />
===Keywords===<br />
Key words and phrases to allow others to search for this bug easier. Keywords are important to avoid bug duplications.<br />
===Cc===<br />
Names of people who should be notified of this bug. (Most people who are not involved with the development process will leave this blank)<br />
<br />
==Attaching Files to the Bug Report==<br />
*Log files are essential to understanding issues. Attach any log files that may be interesting.<br />
*The output of certain programs may demonstrate the issue well. Attach any interesting output in text files if more than a few lines to avoid filling the bug report with complex text.<br />
<br />
==Submitting a Patch==<br />
If you're attaching a patch, be sure to mention it in the report. Attach it as a separate file - not inline.<br />
*Explain how the patch addresses the problem and any other components that the changes might affect.<br />
*Explain the procedure you went through to test the functionality of the patch<br />
*Explain what you've done to make sure the patch does not break other functionalities.<br />
*Make sure the ''type'' field is set to ''feature_patch'' if your patch is adding a new feature or ''defect_patch'' if your patch is fixing a defect<br />
<br />
==Following Bug Progress==<br />
If you are the original reporter of the bug you have a responsibility to make sure it is addressed. Check the bug ticket regularly. If more information is requested, you should provide it in a timely manner.<br />
<br />
It is generally not acceptable to post additional comments on a bug report asking for the bug to be fixed faster, so do not do that. Only post additional comments if you have come up with new information that will help resolve the bug.<br />
<br />
==References==<br />
*This page originally adapted from [http://jimbodude.net/wiki/Bug_Reporting jimbodude's wiki]<br />
*[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Simon Tatham, "How to Report Bugs Effectively"]<br />
*[http://www.debian.org/Bugs/Reporting Debian BTS, "reporting bugs"]<br />
*[https://help.ubuntu.com/community/ReportingBugs Ubuntu Community Documentation, "Reporting Bugs"]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=Bug_Reporting&diff=18540Bug Reporting2009-04-15T20:08:49Z<p>Jimbodude: initial import</p>
<hr />
<div>==Introduction==<br />
In oder to focus the efforts of a software project, it is essential to have a clear understanding of the current status of all defects.<br />
<br />
==Importance of Reporting Bugs==<br />
Software defects are commonly tracked using specialized databases. There are several reasons to track defects strictly:<br />
*If a bug is not tracked, it may be overlooked and never fixed<br />
*If a bug is not tracked, key members of the development team may not know it exists<br />
*Tracking bugs provides a way to determine the functional status of the project<br />
*The bug list provides development team members a place to look for things to contribute<br />
*The bug list provides users a place to formally report issues<br />
*The bug tracking system provides a way to divide up work among the development team<br />
*The bug tracking system provides a way for people to check the status of particular issues and present workarounds or fixes in an organized and manageable way<br />
<br />
==What Bugs Should Be Reported==<br />
Follow these steps:<br />
===Step 1: Determine if the issue is worth reporting===<br />
If the answer to any of these questions is "yes", then this issue probably does not warrant a bug report:<br />
*Can the issue be phrased as a support request? (for examples: "How do I...", "Is it possible to...", "How do I configure...", "Where is documentation on..."<br />
*Is the issue related to future development? (for examples: "Add a feature for...", "Restructure system so...")<br />
*Is the issue caused by an unrelated software package that doesn't directly affect our project? (for example, say we are making a phone system based in Linux that has a Gnome desktop. Our issue is: "I cannot open text documents in gedit because the Gnome project has provided a broken package". This would not be a bug for our phone system at all, as it doesn't affect our project - though it may be an annoyance to people using our applications)<br />
<br />
If the answer to any of the following questions is "yes", then it may be time to consider reporting a bug:<br />
*Is a feature completely unusable?<br />
*Is a feature that used to work not working as expected?<br />
*Is an important feature missing that is hindering the usefulness of another feature?<br />
<br />
===Step 2: Determine if the bug is actually expected behavior===<br />
In many cases, software is designed to do things that the user doesn't expect. To avoid reporting bugs when no bug exists, a thorough check of the functionality of the affected component is required. Make sure you have answered the following questions before reporting a bug:<br />
*Do I have a complete understanding of what is happening to produce the bug? (consider checking documentation)<br />
*Have other people experienced this issue and been shown that it is by design? (consider checking forums, IRC channels)<br />
*Is this component under heavy development right now? Perhaps there has been a change in how it works.<br />
<br />
===Step 3: Determine if the bug has already been reported===<br />
Reporting duplicate bugs wastes everyone's time. The reporter takes time to compile their thoughts, the reviewer takes time to mark it as a duplicate, future bug investigators take time to redirect to the proper bug, and the list goes on. To maintain everyone's efficiency, duplicate bugs should be avoided. Make sure you have followed the previous two steps and done significant searching in the bug database before reporting a new bug.<br />
<br />
If a bug ticket already exists for the issue you are trying to report, make sure there is enough information in the ticket. Add any new information you have. Useful information is discussed in the next section<br />
<br />
===Step 4: Report the bug===<br />
Assuming all of the previous steps have suggested the issue is worth reporting, it's time to make a bug report. The details that go into the report are discussed in the next section.<br />
<br />
==What Data Should Be In The Report==<br />
An uninformative bug report is a waste of time. To make a good bug report, the following items are essential:<br />
*'''A clear title/subject''' - describe what is broken and in what way<br />
**''Good example'': Unable to adjust screen brightness using hotkeys - works otherwise<br />
**''Bad example'': Brightness doesn't work<br />
*'''Clear description of the issue''' - describe all symptoms of the issue in the body of the report without trailing off into other features. Be sure to explain exactly what you expect to happen, exactly what is happening, and exactly how to make it happen.<br />
**''Good example'': When the hotkeys associated with screen brightness are pressed, the screen brightness should change, but the screen brightness does not change. The expected brightness notification appears in the top right of the screen, but it displays the wrong brightness level.<br />
**''Bad example'': I push the hotkey and nothing happens.<br />
*'''If there is more than one way to perform a task, state exactly which way you did it, and whether the other way works'''<br />
**''Good example'': (taking a break from the brightness examples) Select File --> Load to load the file. Loading the file by double clicking in the file explorer works.<br />
**''Bad example'': Load the file.<br />
*'''When was the last time it worked the way you expected?''' - Is this something that broke recently? When, precisely, did it stop working?<br />
**''Good example'': This worked out of the box in versions 7.04 through 8.10. Using the most recent development packages, it does not work<br />
**''Bad example'': It used to work, now it doesn't.<br />
*'''Step by step instructions to reproduce the issue''' - the more detailed, the better. Do not leave steps out, do not assume any prior knowledge of the issue, even if it is widely known<br />
**''Good example'': While logged into Gnome in an X session, press Fn+F5 or Fn+F6 several times. Notice that the brightness doesn't change, but the brightness notification appears<br />
*'''Note any configuration that may impact this issue''' - If you have configured something differently than expected, be sure to note this.<br />
**''Good example'': I am using the out-of-the box configuration.<br />
**''Good example'': I have changed xorg.conf to try to increase my screen resolution. The lines I changed were...<br />
*'''Hardware description''' - If hardware could affect the issue, be sure to include all relevant information<br />
**''Good example'': I am using a Sony VGN-S480 with nVidia 6200Go graphics card<br />
*'''Workarounds''' - If you've found a way around the issue, add that in to help people who are suffering the same issue and to provide a better picture of what is actually broken<br />
**''Good example'': It is possible to adjust screen brightness using the ''smartdimmer'' command<br />
*'''''MOST IMPORTANTLY: RE-READ THE REPORT BEFORE YOU SEND IT''''' - Re-reading gives you a chance to collect your thoughts, make sure you haven't missed anything, correct typographical errors that make reading difficult, and clarifying your ideas. Be sure your writing is clear and concise. Read the report as if you know nothing about the issue. Look for places where you may have assumed certain knowledge or a certain process.<br />
<br />
When writing your report, be mindful of the following:<br />
*'''Avoid the use of general terms like "it" or "the window".''' Instead, use specifics like "the brightness notification dialog at the top right of the screen"<br />
*'''Give any information that could be related.''' It is generally acceptable to provide too much information, but leaving something out will make the issue harder to address<br />
*This can't be stressed enough: '''''RE-READ THE REPORT BEFORE YOU SEND IT''''' for all the reasons stated above.<br />
<br />
==Attaching Files to the Bug Report==<br />
*Log files are essential to understanding issues. Attach any log files that may be interesting.<br />
*The output of certain programs may demonstrate the issue well. Attach any interesting output in text files if more than a few lines to avoid filling the bug report with complex text.<br />
<br />
==Submitting a Patch==<br />
If you're attaching a patch, be sure to mention it in the report. Attach it as a separate file - not inline.<br />
*Explain how the patch addresses the problem and any other components that the changes might affect.<br />
*Explain the procedure you went through to test the functionality of the patch<br />
*Explain what you've done to make sure the patch does not break other functionalities.<br />
<br />
==Additional Bug Report Fields==<br />
Be sure to fill out as many of the additional fields on the report as you can as accurately as you can. Fields like "version" should be pretty easy. Fields like "component" or "package" might be more difficult - use your judgment. Be sure to categorize the bug properly - is this a feature request, a defect, a security risk...? If you have a patch to fix the bug, be sure to indicate that in the report and in any field that allows it.<br />
<br />
==Following Bug Progress==<br />
If you are the original reporter of the bug you have a responsibility to make sure it is addressed. Check the bug ticket regularly. If more information is requested, you should provide it in a timely manner.<br />
<br />
It is generally not acceptable to post additional comments on a bug report asking for the bug to be fixed faster, so do not do that. Only post additional comments if you have come up with new information that will help resolve the bug.<br />
<br />
==References==<br />
*This page originally adapted from [http://jimbodude.net/wiki/Bug_Reporting jimbodude's wiki]<br />
*[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Simon Tatham, "How to Report Bugs Effectively"]<br />
*[http://www.debian.org/Bugs/Reporting Debian BTS, "reporting bugs"]<br />
*[https://help.ubuntu.com/community/ReportingBugs Ubuntu Community Documentation, "Reporting Bugs"]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=Bug_Reports&diff=18539Bug Reports2009-04-15T20:06:07Z<p>Jimbodude: adding bug reporting link</p>
<hr />
<div>Bugs may be reported via http://svn.linuxmce.org/trac.cgi/report, the bug/issue tracking system.<br />
<br />
Before reporting bugs, be sure to read [[Bug Reporting]]<br />
<br />
[[Category:Development]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18538DeveloperMeetings2009-04-15T19:57:52Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[20090415Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=Meeting1Agenda&diff=18537Meeting1Agenda2009-04-15T19:57:34Z<p>Jimbodude: Meeting1Agenda moved to 20090415Agenda: move to proper date</p>
<hr />
<div>#REDIRECT [[20090415Agenda]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1853620090415Agenda2009-04-15T19:57:34Z<p>Jimbodude: Meeting1Agenda moved to 20090415Agenda: move to proper date</p>
<hr />
<div>==Logistics==<br />
*This meeting happened<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Wednesday, April 15<br />
**'''Time:''' 2PM GMT (4PM Berlin, 10AM New York, 7AM Los Angeles)<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' #linuxmce-devel<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
***No major bugs<br />
**Orbiter<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/153 #153]: RA button on orbiters/on-screen orbiters crashes the orbiter<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/160 #160]: JavaMO.jar missing for build<br />
***[Compile error in Orbiter_Plugin #9]: Compile error in Orbiter_Plugin<br />
**Media Playing<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/40 #40]: MAME Integration (blocker/defect)<br />
***[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)<br />
**Xine<br />
***No major bugs<br />
**MPlayer<br />
***No major bugs<br />
**MythTV<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/124 #124]: MythTV Plugin needs to use the new MythTV Storage Groups<br />
**VDR<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/54 #54]: Initial vdr config errors<br />
**Lighting,Climate<br />
***No major bugs<br />
**Setup and AV Wizard<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/27 #27]: Create Diskless Boot Image (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/166 #166]: Automatic MD creation (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/150 #150]: hardy entry ends up in the sources.list<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/167 #167]: pluto-blutooth-dongle does not automatically install when USB dongle inserted<br />
**Web Admin<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/119 #119]: IR / GSD codes bugs<br />
**Telephony<br />
***No major bugs<br />
**Other<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/26 #26]: New installer (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/101 #101]: cleancore script bugs (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/48 #48]: Launch Manager rewrite to be CLI only (no QT dependancy)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/107 #107]: Backup system does not backup all relevant parts<br />
*Review of other topics as they arise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**[http://www.freeaudioconferencing.com/services.php Voice chat]? - (Cylon7)<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18530DeveloperMeetings2009-04-15T19:39:41Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*General Organizational Meeting (IRC #linuxmce-meeting - 15 April 2009, 2PM GMT)<br />
**[[Meeting1Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18529DeveloperMeetings2009-04-15T19:38:31Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*General Organizational Meeting (IRC - time and channel TBA)<br />
**[[Meeting1Agenda|Agenda]]<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Minutes&diff=1852820090415Minutes2009-04-15T19:36:30Z<p>Jimbodude: New page: Meeting chair: jimbodude Minutes prepared by: jimbodude ==Attendance== *colinjones *dlewis *hari *jimbodude *tkmedia *totallymaxed *TSCHAK *Zaerc ==Topics and Discussion== *Several bug ...</p>
<hr />
<div>Meeting chair: jimbodude<br />
<br />
Minutes prepared by: jimbodude<br />
<br />
==Attendance==<br />
*colinjones<br />
*dlewis<br />
*hari<br />
*jimbodude<br />
*tkmedia<br />
*totallymaxed<br />
*TSCHAK<br />
*Zaerc<br />
<br />
==Topics and Discussion==<br />
*Several bug reports were covered<br />
**Nothing conclusive came out of the discussion<br />
**About 3 bug tickets in, focus was shifted to the next agenda items to keep interest<br />
<br />
*Standardized testing procedures (presented by '''hari''')<br />
**Goal: locate all bugs in a systematic way<br />
**Method:<br />
**#Develop standardized tests for each component (DCERouter, Web Admin, Orbiter, etc...)<br />
**#Assign 2+ people to each component<br />
**#Run tests over 2-3 days<br />
**#Combine results, create new tickets<br />
**If other test procedures are already available, use those to augment<br />
**'''No one has taken direct responsibility for these tasks. jimbodude has taken responsibility to see that something happens.'''<br />
<br />
*Release Scheduling<br />
**Goal: focus development efforts in key areas on a flexible, but documented, schedule such that important issues are not overlooked for long periods of time.<br />
**Method:<br />
**#Find things that don't work<br />
**#Assign them to a milestone<br />
**#Pick a date for each milestone's completion<br />
**Things that are broken or need attention: (in no particular order)<br />
***MD booting<br />
***KDE Desktop on MD<br />
***Getting back to Orbiter from KDE<br />
***the desktop is incorrectly sized on TV's at HD resolutions<br />
***login problem on MD<br />
***Auto detect of USBUIRT<br />
***ir codes in sqlcvs<br />
***serial detection<br />
***cisco 7070 wrong room problem<br />
***making more devices PnP<br />
***work on upgrading telecom<br />
***issue with the sony changer<br />
**'''No one has taken responsibility for these tasks'''<br />
<br />
*Update scheduling discussion is deferred until there is a release schedule<br />
*Installation number generation design discussion is deferred in the interest of time and higher priority issues<br />
<br />
*Defect Tracking<br />
**Goal: Improve defect tracking in order to:<br />
***Communicate issues to a team that is distributed<br />
***Bring attention to issues that may otherwise be ignored<br />
***Focus developer efforts on key tasks<br />
***Assist in release scheduling<br />
**Method: Encourage testers to submit bug reports. Draft a defect reporting policy specific to LinuxMCE<br />
**A LinuxMCE policy will be presented at the next meeting for discussion<br />
**'''jimbodude had taken responsibility for these tasks'''<br />
<br />
*Future Meetings<br />
**This meeting was helpful - future meetings are expected to be just as useful, and should be scheduled<br />
**Since the topics at this meeting require significant follow-up work the next meeting will be in one week<br />
**Meetings thereafter may be weekly or bi-weekly - this decision is deferred to the next meeting<br />
**'''jimbodude has taken responsibility for creating an agenda for the next meeting'''<br />
**'''No one has taken responsibility for scheduling the next meeting'''</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Transcript&diff=1851520090415Transcript2009-04-15T15:38:44Z<p>Jimbodude: </p>
<hr />
<div><pre><br />
10:02 jimbodude alright. lets get this show on the road shall we?<br />
10:02 totallymaxed Anyone got remote accexx to Thom's system...maybe put on some loud music ;-)<br />
10:02 jimbodude hehe<br />
10:02 Zaerc fine with me<br />
10:03 jimbodude first order of business - lets nominate someone to run this thing.<br />
10:03 jimbodude I'll volunteer if there's no interest...<br />
10:04 jimbodude going... going... gone.<br />
10:04 tkmedia_2 i 2nd that<br />
10:04 Zaerc ok<br />
10:04 totallymaxed fine with me<br />
10:05 jimbodude ok, so quick logistical items. before we move on to a different topic, I'll make sure there's no other comments - any text and we'll stop and wait for you to speak your mind.<br />
10:05 Zaerc sounds fair<br />
10:06 Zaerc maybe we should move to a different channel<br />
10:06 jimbodude Zaerc: sure. your pick.<br />
10:07 Zaerc how about #linuxmce-meeting<br />
[10:08] --> You have joined the channel #linuxmce-meeting (n=tkmedia@c-75-69-169-56.hsd1.ct.comcast.net).<br />
[10:08] *** Channel modes: secret, no messages from outside<br />
[10:08] *** This channel was created on 04/15/2009 10:06:47 AM.<br />
[10:08] --> totallymaxed has joined this channel (i=51892222@gateway/web/ajax/mibbit.com/x-f5a21145926c5205).<br />
[10:08] *** Zaerc gives channel operator privileges to you.<br />
[10:08] *** Zaerc gives channel operator privileges to totallymaxed.<br />
[10:08] <jimbodude> alright, I think we're back to where we were with attendance.<br />
[10:10] <jimbodude> so, from time to time it may be nice to have a straw-poll vote. there will be a question followed by options in (). pick an option, say that. if you'd like to talk about your choice, also say "with rights" and we'll let you talk some more before moving on.<br />
[10:10] <jimbodude> this keeps the vote quick.<br />
[10:10] <tkmedia_2> hang on<br />
[10:10] <jimbodude> with that, on to status.<br />
[10:10] <jimbodude> go ahead.<br />
[10:10] <tkmedia_2> are we exlcuding people who planned to log this<br />
[10:11] <tkmedia_2> or should we post a log for them<br />
[10:11] <jimbodude> I'm not sure what you mean... I was planning on posting a transcript when we're done anyway.<br />
[10:11] <jimbodude> yes.<br />
[10:11] <tkmedia_2> ok<br />
[10:11] <jimbodude> all set then?<br />
[10:11] <jimbodude> perfect.<br />
[10:11] <Zaerc> yes<br />
[10:12] <jimbodude> First component is DCERouter - there are no major bugs listed. Any status report needed here?<br />
[10:12] <jimbodude> ok. Orbiter. 3 major bugs.<br />
[10:13] <jimbodude> http://svn.linuxmce.org/trac.cgi/ticket/153 RA button on orbiters/on-screen orbiters crashes the orbiter - anyone have eyes on this one and want to talk about where it is?<br />
[10:13] <jimbodude> (status wise)<br />
[10:14] <jimbodude> jondecker reported it... seems pretty well explained.<br />
[10:14] <Zaerc> seems more like an obsolete feature to me<br />
[10:14] <jimbodude> ok, would you mind commenting on the ticket with that note?<br />
[10:14] <Zaerc> not really tbh<br />
[10:15] <jimbodude> ok then.<br />
[10:15] <jimbodude> http://svn.linuxmce.org/trac.cgi/ticket/160 JavaMO.jar missing for build<br />
[10:16] <jimbodude> looks like its fixed, just not marked. true?<br />
[10:16] <Zaerc> no idea<br />
[10:16] <hari> re #153, we don't even have RA active at the moment<br />
[10:16] <jimbodude> I mean in the comments - it says "everything compiles now"<br />
[10:17] <hari> so until we re-enable RA from the web interface i'd say we remove the button from the UI<br />
[10:17] <jimbodude> ok, thanks hari.<br />
[10:17] --> TSCHAKeee has joined this channel (n=TSCHAKee@c-65-96-166-204.hsd1.ma.comcast.net).<br />
[10:17] <TSCHAKeee> erf<br />
[10:17] <jimbodude> morning TSCHAKeee. :)<br />
[10:17] <hari> jimbodude: autossh might be another option<br />
[10:17] <hari> to replace the old scripts<br />
[10:17] <dlewis> TSCHAKeee: got my text? lol<br />
[10:17] <hari> technically RA is quite simple, it just logs onto the central server with ssh/pubkey and forward some ports back to the local installation<br />
[10:18] <hari> works through NAT, we just need a mechanism to assign tcp ports on the server<br />
[10:18] <hari> if sb wants to take on that for 0810, fine, server and such is there. If not, let's deactivate the buttons in the web admin and orbiter UI<br />
[10:18] <jimbodude> ok, sounds like we have some discussion needed about RA - remind me to bring it up when we get to design discussions. for now - lets plow through the bugs really fast.<br />
[10:19] <TSCHAKeee> dlewis: yup thanks<br />
[10:19] <hari> re #160, the build works on linux with some dependencies<br />
[10:19] <hari> it will be integrated into the external add-on build system soonish<br />
[10:19] <jimbodude> ok. are you working on that hari?<br />
[10:19] <hari> till then, there is a place where sambuca drops the jar<br />
[10:20] <hari> jimbodude: yes, also the symbian v2 and v3 build<br />
[10:20] <hari> will automate those three builds<br />
[10:20] <jimbodude> alright - could you note that status on the ticket?<br />
[10:21] <Zaerc> doesn't seem like a "blocker" to me<br />
[10:21] <hari> there is no ticket for the auto build system yet<br />
[10:21] <hari> worst case i'll do a manual run for the v2 and v3 orbiters for the beta/release<br />
[10:21] <jimbodude> Zarec: yes, it could probably be downgraded to somewhere around major.<br />
[10:21] <hari> and the actual jar for the javamo resides on download<br />
[10:22] <hari> jimbodude: we shall ask sambucca if he wants to document place of the jar in the ticket<br />
[10:22] <jimbodude> ok. so 160 is being addressed well. perfect. any other comments on 160?<br />
[10:22] <TSCHAKeee> nope.<br />
[10:22] <hari> i think the worst bugs are the ones we have no tickets for yet ;-p<br />
[10:22] <jimbodude> hari: sure... I have no idea what's going on there... I just wrote the agenda... :P<br />
[10:23] <jimbodude> hari: getting to that... ;)<br />
[10:23] *** dlewis gives channel operator privileges to TSCHAKeee.<br />
[10:23] <hari> jimbodude: my most important thing for this conference<br />
[10:23] <hari> we need to find and nail down outstanding bugs<br />
[10:23] <hari> and isolate non-finished features<br />
[10:23] <hari> but it is too much for a single person to test all things at a time<br />
[10:23] <hari> ppl would get crazy<br />
[10:24] <hari> and not everybody has all stuff in his installation<br />
[10:24] <jimbodude> so the drift I'm getting is that visiting individual bugs is not doing it for you guys - sound correct? shall we just skip into the meat? (yes | no)<br />
[10:24] <hari> there was a status page, i think it is in our wiki, derived from pluto, with 1-5 for implementation status<br />
[10:24] <hari> jimbodude: i'm fine reviewing individual bugs first<br />
[10:24] <hari> but i really want that topic adressed today, too<br />
[10:25] <Zaerc> jimbodude: yes<br />
[10:25] <dlewis> i'm with Zaerc<br />
[10:25] <jimbodude> alright - well lets just go to the interesting stuff then. I'm bored with bugs too...<br />
[10:25] <Zaerc> ok<br />
[10:26] <hari> so, that overview gave nice sections<br />
[10:26] <hari> for ha, telephony, media, ...<br />
[10:26] <hari> we need to enrich it, with specific test cases<br />
[10:26] <hari> and then assign at least 2 ppl for each test case/group<br />
[10:26] <hari> does that sound reasonable?<br />
[10:26] <jimbodude> yes, I like it a lot.<br />
[10:26] <hari> so we would be able to do a "full" test run in say 2-3 days<br />
[10:26] <hari> and have every subsystem checke<br />
[10:27] <hari> we do 2 or 3 iterations of that over the next weeks<br />
[10:27] <hari> that should (*hope*) give us a clear picture where we are and what needs to be fixed first<br />
[10:27] <Zaerc> fiire claimed they had developed all these wonderful test cases... but I guess they took them to their grave<br />
[10:28] <hari> Zaerc: what i've seen from aaron for now, i really appreciate his genius, but testing seems to be the same like sales for him<br />
[10:28] <hari> :-p<br />
[10:28] <hari> and when we look at the regression numbers in the 0710 betas...<br />
[10:28] --> uplink-lmce has joined this channel (n=uplink-l@host81-137-34-33.in-addr.btopenworld.com).<br />
[10:28] <hari> btw, the mantis is available as www/mantis-deact<br />
[10:29] <hari> i pulled it from public as it is exploitable<br />
[10:29] <totallymaxed> I think the 'test cases' were more Pluto driven than Fiire to be franks<br />
[10:29] <jimbodude> hari: have you started putting any of this together yet? in written form?<br />
[10:29] <tkmedia_2> my production system mostly 0810 now and have lots to test<br />
[10:29] <hari> jimbodude: yup, in this channel :-)<br />
[10:29] <jimbodude> good start. :)<br />
[10:29] <Zaerc> fiire != aaron<br />
[10:30] <Zaerc> but as we've never even seen them there is little point in beating adead horse<br />
[10:30] <totallymaxed> sure...but Fiire was just a marketing front ;-)<br />
[10:31] <hari> brb<br />
[10:31] <jimbodude> alright, so we need to write up some tests.<br />
[10:31] <Zaerc> I'll just have to take your word for that<br />
[10:31] --> fido has joined this channel (n=fido@cpc2-glen1-0-0-cust693.belf.cable.ntl.com).<br />
[10:31] <-- fido has left this channel.<br />
[10:32] <tkmedia_2> 1. squeezeboom tested sucessfully on 0810 this AM<br />
[10:32] <jimbodude> everyone agree with the basics of hari's plan?<br />
[10:32] <tkmedia_2> pnp<br />
[10:32] <Zaerc> fine with me<br />
[10:33] <totallymaxed> sure<br />
[10:33] <dlewis> I agree<br />
[10:33] <tkmedia_2> sure<br />
[10:33] <jimbodude> hari: want to take the lead on that? I'm available to help as you see fit.<br />
[10:34] <jimbodude> he'll answer when he gets back...<br />
[10:34] <jimbodude> next agenda topic is release scheduling.<br />
[10:34] <TSCHAKeee> whoa, we have a schedule?<br />
[10:35] <jimbodude> basically, I see a release schedule as a way to focus developer efforts - even if it changes all the time.<br />
[10:35] <TSCHAKeee> *walks-around-all-dazed*<br />
[10:35] <jimbodude> TSCHAKeee: nope. that's why I put it on there.<br />
[10:35] <TSCHAKeee> ;)<br />
[10:35] <Zaerc> TSCHAKeee: http://wiki.linuxmce.org/index.php/Meeting1Agenda<br />
[10:35] <TSCHAKeee> I know, i was being sarcastic. ;)<br />
[10:35] <Zaerc> oh you meant release-schedule<br />
[10:36] <jimbodude> generally speaking, if software projects want to be successful, they have a schedule - even if it's fairly vague.<br />
[10:36] <hari> jimbodude: want, yes, can, no<br />
[10:36] <jimbodude> what do you guys think about pulling together some milestones and dates for 0810 - even if we don't tell anyone about them?<br />
[10:36] <Zaerc> heh, I remember setting a rough date for the beta a few months ago<br />
[10:37] --> colinjones has joined this channel (i=9665c9a9@gateway/web/ajax/mibbit.com/x-cfa01ade4796ad9b).<br />
[10:37] <jimbodude> ok hari - I'll take point on it for now then. we can move it around later.<br />
[10:37] <Zaerc> since then I feel we've only been moving away from the beta<br />
[10:37] *** Zaerc gives channel operator privileges to colinjones.<br />
[10:38] <colinjones> :) ignore me, just catching up on the dev thread... too tired and drunk to contribute!<br />
[10:38] <jimbodude> I'm not sure "moving away" is quite right - a lot has come up, and a lot of new features are being added.<br />
[10:38] <Zaerc> well, that's what I call moving away<br />
[10:38] <totallymaxed> my feeling is that we need some kind of schedule...<br />
[10:38] <jimbodude> it seems, to me, that a lot of the issues we're having we've had for quite a while and they just aren't getting addressed.<br />
[10:39] <TSCHAKeee> the big one right now is getting media directors to boot<br />
[10:39] <jimbodude> If there were some milestone targets - for instance "release alpha 3, fixing the following issues: blah blah blah, on such and whatever date"<br />
[10:40] <jimbodude> we might be able to focus development power towards the ultimate goal.<br />
[10:40] <totallymaxed> without a schedule we're just drifting...jimbodude seems like a good idea<br />
[10:41] <jimbodude> any further thoughts?<br />
[10:41] <Zaerc> TSCHAKeee: I was working on that<br />
[10:41] <TSCHAKeee> ok<br />
[10:42] <tkmedia_2> why isn't /Diskless_BuildDefaultImage.sh run in the post_install ?<br />
[10:42] <jimbodude> do you guys want to pull something together here, delegate for later work, or not have a schedule?<br />
[10:42] <Zaerc> but apparently we need a launch-manager instead of figuring the bootscripts out properly, so I kind of dropped it<br />
[10:43] <Zaerc> (or whatever it's supposed to be called these days)<br />
[10:43] <hari> Zaerc: i think both are way important<br />
[10:43] <TSCHAKeee> jimbodude: I know what I need to do from my perspective. my big one is getting mame to work, since the other big ones that were initially on my plate are dealt with.<br />
[10:44] <hari> Zaerc: otherwise we'd end up using dcewhisperer in the launchcore script ;-)<br />
[10:44] <TSCHAKeee> but anything else anybody decides to put on my plate is cool, just let me know<br />
[10:44] <totallymaxed> hari: great idea :-)<br />
[10:44] <hari> but the actual qt/dce interwoven mess had to be cleaned up<br />
[10:44] <jimbodude> well, I don't think the problem is people not doing their work - I think the problem is that tasks are getting overlooked because they don't have deadlines.<br />
[10:44] <hari> totallymaxed: i knew you'd like it<br />
[10:44] <Zaerc> dcewhisperer?<br />
[10:44] <hari> totallymaxed: really, why not, everything is better than the crap we had (and nobody understood)<br />
[10:44] <totallymaxed> :-)<br />
[10:44] <jimbodude> can you guys stay on topic for me please? we can deal with design stuff later. we're talking about scheduling now.<br />
[10:45] <TSCHAKeee> and it was. We now have a stable launching system again<br />
[10:45] <Zaerc> ok<br />
[10:45] <jimbodude> do you guys want to pull something together here, delegate for later work, or not have a schedule?<br />
[10:45] <TSCHAKeee> and one that can have the necessary UI attached to it.<br />
[10:45] <TSCHAKeee> I do.<br />
[10:46] <hari> Zaerc: the bits that could not be implemented in bash to do dce communications<br />
[10:46] <hari> so a bit of a GSD for bash :-p<br />
[10:46] <totallymaxed> :-)<br />
[10:46] <Zaerc> I don't see a need for it, but let's stay on topic<br />
[10:47] <Zaerc> and maybe discuss that later<br />
[10:47] <TSCHAKeee> i'm all for it, just give me stuff to do. I'll balance it with the remote work.<br />
[10:47] <hari> yeah, schedule is important<br />
[10:47] <hari> i always do stuff when approaching the deadline :-p<br />
[10:47] <jimbodude> I don't think we're at the point of assigning work... but if we all agree that we want to get certain things done by a certain date, we can make sure nothing gets overlooked at least.<br />
[10:48] <totallymaxed> agreed<br />
[10:48] <jimbodude> is that the general consensus? no major objections?<br />
[10:48] <Zaerc> none here<br />
[10:48] <jimbodude> shall we start hashing something out now, or assign it as a task to someone?<br />
[10:48] <TSCHAKeee> i'm cool<br />
[10:49] <jimbodude> alright... so let's look into it a bit now.<br />
[10:50] <jimbodude> let's talk about big things that don't work - not about why they don't work, just that they don't.<br />
[10:50] <tkmedia_2> MD booting<br />
[10:50] <jimbodude> what are the biggest broken things - with special focus on things that worked on 0710?<br />
[10:51] <tkmedia_2> KDE desktop on MD<br />
[10:51] <tkmedia_2> or lack there of<br />
[10:51] <totallymaxed> How to get back to Orbiter from KDE<br />
[10:51] <totallymaxed> ...if the LM is cli<br />
[10:51] <Zaerc> click workspace 3 for now<br />
[10:52] <TSCHAKeee> now that we have LM, I just make a plasmoid<br />
[10:52] <TSCHAKeee> which will reorder the workspace correctly<br />
[10:52] <jimbodude> ok, lets keep this out of fixes and design for a bit though.<br />
[10:52] <jimbodude> just broken things.<br />
[10:52] <hari> do we want/need kde?<br />
[10:52] <Zaerc> is the KDE bar still visible through UI2?<br />
[10:52] <jimbodude> Zaerc: I never see it.<br />
[10:52] <hari> i mean do ppl use the desktop feature on the living room tv?<br />
[10:52] <totallymaxed> desktop oversizing at HD resolutions...<br />
[10:52] <tkmedia_2> i use my MD as daily computer using kde<br />
[10:52] <TSCHAKeee> (the LM keeps track of the on screen orbiter, and can be used to reorder to the right places<br />
[10:53] <TSCHAKeee> hari: I do.<br />
[10:53] <totallymaxed> yes we do use the desktop on living room TV's<br />
[10:53] <Zaerc> hari: yes amongst other things to use ktorrent<br />
[10:53] <TSCHAKeee> all I need to do is talk to jondecker76 on the client socket protocol<br />
[10:53] <TSCHAKeee> and I can make a plasmoid to do this correctly<br />
[10:53] <jimbodude> ok, back to broken things - KDE stuff gets added to the list<br />
[10:54] <TSCHAKeee> once i know what to do, it's only an hour or so of work.<br />
[10:54] <totallymaxed> ...at HD resolutions like 720p or 1080i... the desktop is incorrectly sized on TV's<br />
[10:54] <tkmedia_2> login problem on MD<br />
[10:54] <TSCHAKeee> totallymaxed: yeah, it's somewhat ironic, we override everything, and in the process lose any automatic DPI info we need to display desktop fonts at the right size.<br />
[10:55] <totallymaxed> correct TSCHAKeee<br />
[10:55] <tkmedia_2> Auto detect of USBUIRT<br />
[10:55] <jimbodude> how about some of the other components - like telecom... game... web admin...<br />
[10:55] <jimbodude> tkmedia_2: I like your list... keep it rolling.<br />
[10:55] <-- colinjones has left this server ("http://www.mibbit.com ajax IRC Client").<br />
[10:56] <tkmedia_2> ir codes in sqlcvs<br />
[10:56] <TSCHAKeee> i think jondecker has been steadily hacking away at that one<br />
[10:56] <tkmedia_2> yes<br />
[10:57] <tkmedia_2> just want it on the the list<br />
[10:57] <tkmedia_2> so it dont get missed<br />
[10:57] <jimbodude> exactly.<br />
[10:57] <jimbodude> it has a ticket too - which is nice. #119.<br />
[10:57] <jimbodude> (we'll talk about that later)<br />
[10:58] <jimbodude> alright, so I think that's a pretty complete list for now.<br />
[10:58] <dlewis> we definitely need to work on upgrading telecom<br />
[10:58] <tkmedia_2> serial detection<br />
[10:58] <dlewis> making more devices PnP<br />
[10:58] <jimbodude> ok, I guess we can make it more complete... :)<br />
[10:58] <TSCHAKeee> now that we have a working media director phone combo<br />
[10:58] <tkmedia_2> cisco 7070 wrong room problem<br />
[10:59] <TSCHAKeee> telecom plugin bugs are really coming out of the woodwork<br />
[10:59] <tkmedia_2> 7970<br />
[10:59] <jimbodude> you guys just keep rolling - Now. someone needs to go through this list, prioritize it, assign things to milestones, and we need to agree on dates to hit the milestones.<br />
[11:00] <dlewis> do we have a comprehensive list of telecom bugs?<br />
[11:00] <tkmedia_2> Some issue with the sony changer.... certainly not release stoppers<br />
[11:00] <jimbodude> I don't think this is the best place to do that - maybe someone could come up with a draft, and 2-3 of the lead devs could review it. does that sound reasonable? any takers?<br />
[11:01] <jimbodude> dlewis: probably not - we're going to get to bug tracking next.<br />
[11:01] <TSCHAKeee> the big show stoppers right now are media director support, and certain devices not popping up like the UIRT and ZWave devices.<br />
[11:01] <tkmedia_2> I will test and put in trac<br />
[11:01] <TSCHAKeee> (both serial devices)<br />
[11:02] <jimbodude> I'm going to try to cut this in about a half hour to 40 minutes guys - just to keep it reasonable. after that, we can break out and dig in deeper on specific issues.<br />
[11:02] <tkmedia_2> yes not sure if the pnp scripts get passed to my tv if using a usb/serial adapter<br />
[11:02] * Zaerc agrees with TSCHAKeee, the rest can be fixed during the beta<br />
[11:02] <jimbodude> so back to my previous two points on scheduling - anyone want to take the lead on that?<br />
[11:02] <TSCHAKeee> please dear god anybody but me<br />
[11:03] <jimbodude> I'm not in any position to assign a task like that... so someone is going to have to volunteer or it's going to be left.<br />
[11:04] <Zaerc> ok I guess that means nobody feels like doing that, let's move on<br />
[11:04] <jimbodude> alrighty then.<br />
[11:05] <jimbodude> there's a note on the agenda from jondecker76 about update scheduling - we'll defer that until we have a release schedule...<br />
[11:05] <jimbodude> I'm also going to jump over his points about installation number generation for now - he's documented his thoughts pretty well in the agenda.<br />
[11:05] <jimbodude> to get to bug tracking.<br />
[11:05] <TSCHAKeee> ok<br />
[11:05] <Zaerc> I'm a bit surprised that he's not here<br />
[11:06] <TSCHAKeee> probably at work<br />
[11:06] <jimbodude> so, I'm noticing a LOT of issues that people just "know about" that aren't documented in Trac.<br />
[11:06] <Zaerc> TSCHAKeee: since when is that an excuse? ;^)<br />
[11:07] * TSCHAKeee whistles <br />
[11:07] <jimbodude> I think that's a pretty bad practice with such a distributed team - we're losing track of what needs to be done.<br />
[11:07] <TSCHAKeee> I wish there was a brain dump plugin for trac<br />
[11:07] <jimbodude> it would be nice yes...<br />
[11:07] <TSCHAKeee> yeah...<br />
[11:07] <TSCHAKeee> you're right.<br />
[11:07] <Zaerc> jimbodude: tbh I gave up on using trac a long time ago<br />
[11:07] <jimbodude> and of course - I'm no angel... I just reported a bug yesterday that I've known about since I get 0810.<br />
[11:08] <jimbodude> yes, I've noticed that Zaerc.<br />
[11:08] <jimbodude> I think you're not the only one.<br />
[11:08] <tkmedia_2> should i flood it with what i have ..... i did not want to burden with my trivial bugs<br />
[11:08] <TSCHAKeee> yes please<br />
[11:08] <jimbodude> yes. that's what the priority scale is for.<br />
[11:08] <hari> we'd be lost without tracking<br />
[11:09] <totallymaxed> Well I'll commit to adding anything we have here to Trac...<br />
[11:09] <tkmedia_2> ok you asked for it<br />
[11:09] <totallymaxed> :-)<br />
[11:09] <TSCHAKeee> totallymaxed: yup, we're interested to see what you guys run into for 0810<br />
[11:09] <TSCHAKeee> and half scared too<br />
[11:09] <jimbodude> Trac can help us determine where to focus developer efforts, give newbies a place to start working on stuff, and tell us where the project stands.<br />
[11:09] <jimbodude> it is essential that we use it - in my opinion.<br />
[11:10] <tkmedia_2> ok what about working things<br />
[11:10] <tkmedia_2> like the squeezboom<br />
[11:10] <totallymaxed> well we have a full time Core dedicated to testing 0810 now... so the flow from us should be greater going forwards<br />
[11:10] <tkmedia_2> so we dont duplicate effort<br />
[11:10] <jimbodude> I suggest we draft and agree on a bug reporting policy. We also need someone to keep an eye out and make sure we're not throwing bugs under the rug and ignoring them.<br />
[11:10] <TSCHAKeee> to tell you the truth, it's fucking amazing that we've gotten this far and not checked into the looney bin.<br />
[11:11] <jimbodude> tkmedia_2: I'm not sure what you mean... there are no bug reports for things that work.<br />
[11:11] <totallymaxed> TSCHAKeee: :-)<br />
[11:11] <tkmedia_2> yes but how do know what works unless we test<br />
[11:11] <jimbodude> right, TSCHAKeee, and as more people get added to the project, we're going to go nuttier.<br />
[11:11] <tkmedia_2> and this is a new item<br />
[11:11] <jimbodude> tkmedia_2: that's where hari's testing plan comes in.<br />
[11:12] <tkmedia_2> k<br />
[11:12] <jimbodude> tkmedia_2: patches should probably go through Trac also - so we have a ticket to reference the feature implementation.<br />
[11:12] <tkmedia_2> many things have already been tested<br />
[11:12] <jimbodude> but that's part of the policy that we haven't talked about yet.<br />
[11:12] <jimbodude> tkmedia_2: right. and many things have not, or have not been tested well.<br />
[11:13] <jimbodude> which is where the test plan comes in.<br />
[11:13] <tkmedia_2> k<br />
[11:13] <jimbodude> so back to defect tracking.<br />
[11:14] <jimbodude> does that sound reasonable to everyone? report all bugs, prioritize correctly, keep the bug status up to date. do we want a written policy? something based on what I wrote earlier, something different?<br />
[11:14] <TSCHAKeee> that's fine to me<br />
[11:16] <Zaerc> fine with me too<br />
[11:16] <jimbodude> Ok, I'll volunteer to pull together a policy and wiki that. It will be based on what I've written here: http://jimbodude.net/wiki/Bug_Reporting -<br />
[11:16] <jimbodude> Any other comments on defect tracking?<br />
[11:17] <Zaerc> I thought that already was the policy<br />
[11:17] <Zaerc> yeah, anonymous users should only have read-only access<br />
[11:17] <TSCHAKeee> (1) is it broken?<br />
[11:17] <jimbodude> well, it's not really worded as a policy, and we never formally "agreed" on it. I'll reword it at bit and drop it on wiki.linuxmce.org<br />
[11:18] <TSCHAKeee> (2) Put in Trac, so we know, and wait<br />
[11:18] <TSCHAKeee> (3) or for big brownie points, hack on it and submit patch<br />
[11:18] <jimbodude> Zaerc: yes I agree.<br />
[11:19] <jimbodude> TSCHAKeee: yep, pretty much that.<br />
[11:19] <Zaerc> TSCHAKeee: (1b) is it really broken?<br />
[11:19] <jimbodude> alright. I'll pull that together. Zaerc, I can't help you with read only - you know better than I do who to talk to for that...<br />
[11:20] <Zaerc> jimbodude: tried that...<br />
[11:20] <jimbodude> any other comments here? if not, we're going to move on to the last topic - next meeting, if any - and be done here.<br />
[11:20] <Zaerc> but it's hard to talk to people who don't listen<br />
[11:21] <totallymaxed> Bi-weekly?<br />
[11:21] <jimbodude> ok. so the big question is - more meetings? was this useful?<br />
[11:21] <totallymaxed> Yes<br />
[11:21] <jimbodude> I think it was.<br />
[11:21] <Zaerc> yes<br />
[11:21] <TSCHAKeee> I am reminded of a certain Dave Barry quote.<br />
[11:22] <jimbodude> and I'll volunteer to continue pulling together agendas and such to keep them running.<br />
[11:22] <jimbodude> Ok, so how far do we want to space these? week, 2 week, month, other?<br />
[11:22] <TSCHAKeee> “If you had to identify, in one word, the reason why the human race has not achieved, and never will achieve, its full potential, that word would be "meetings” -Dave Barry<br />
[11:22] <dlewis> yes, very useful<br />
[11:23] <totallymaxed> 2 week looks good<br />
[11:23] <TSCHAKeee> yeah, 2 week is fine.<br />
[11:23] <tkmedia_2> or weekly to start<br />
[11:23] <totallymaxed> TSCHAKeee: nice quote ;-)<br />
[11:24] <jimbodude> maybe next week to pull together some of the big things we have discussed here - like testing plan, scheduling, defect policy, then bi-weekly after that?<br />
[11:24] <Zaerc> I'd say weekly, keep 'em short and to thepoint<br />
[11:25] <jimbodude> alright. next week then? and we'll decide on permanent schedule then?<br />
[11:25] <totallymaxed> ok<br />
[11:25] <Zaerc> fine with me<br />
[11:25] <TSCHAKeee> all I'd really want is just a small set of stuff to work on for the next build.<br />
[11:25] <tkmedia_2> sounds good<br />
[11:25] <jimbodude> I'll do the leg work before the meeting. I need a bit of help with scheduling - I think we missed some people this week because of how I did things.<br />
[11:26] <Zaerc> maybe sundays is better for some?<br />
[11:26] <tkmedia_2> be nice to have jondecker here<br />
[11:26] <totallymaxed> or evenings his time<br />
[11:26] <totallymaxed> what timezone is he in?<br />
[11:26] <TSCHAKeee> that's the other thing too, the one thing we DO NOT need on this project is burnout<br />
[11:27] <totallymaxed> Agreed<br />
[11:27] <Zaerc> totallymaxed: if you like having these meetings at 3am...<br />
[11:27] <TSCHAKeee> this project has the highest potential burnout and turnover rate in the history of time :P<br />
[11:27] <totallymaxed> :-)<br />
[11:27] <jimbodude> well, I think this meeting is much more intense than what we'll have going forward to begin with... I imagine a 15 minute check in every week or two once we get all the big stuff hashed out.<br />
[11:28] <totallymaxed> Zaerc: but what timezone is jondecker in? Anyone know?<br />
[11:28] <TSCHAKeee> wanna say US/Eastern<br />
[11:28] <totallymaxed> maybe we can vary the time so that people get a more agreeable slot<br />
[11:28] <Zaerc> totallymaxed: I reckon somewhere between GMT-7 and GMT-9<br />
[11:28] <jimbodude> alright - so next week. can someone schedule a time for us? someone who knows our devs a bit better than me preferably?<br />
[11:28] <Zaerc> or around<br />
[11:29] <tkmedia_2> btw good job jimbodude<br />
[11:29] <TSCHAKeee> yes<br />
[11:29] <totallymaxed> seconded<br />
[11:29] <TSCHAKeee> second that<br />
[11:29] <jimbodude> I do what I can.<br />
[11:29] <Zaerc> I think the time was good<br />
[11:29] <hari> yup<br />
[11:29] <TSCHAKeee> dlewis: thanks for the page.<br />
[11:29] <Zaerc> maybe an hour or so later<br />
[11:29] <TSCHAKeee> yeah, that way I can waaaaaaaaaaaake up<br />
[11:30] <Zaerc> so TSCHAKeee can come on time;^)<br />
[11:30] <Zaerc> heh beat me to it<br />
[11:30] <TSCHAKeee> hehehe<br />
[11:30] <totallymaxed> :-)<br />
[11:31] <jimbodude> alright. I think we're done? anything else?<br />
[11:31] <jimbodude> can one of you grab the transcript and plop it here for me - http://wiki.linuxmce.org/index.php?title=20090415Transcript&action=edit -<br />
[11:31] <Zaerc> not that I can think of atm<br />
[11:31] <jimbodude> it comes out all silly if I use mibbit...<br />
[11:31] <Zaerc> I don't have logging on...<br />
[11:32] <totallymaxed> Nope...good job jimbodude<br />
[11:32] <jimbodude> haha there's one way to avoid writing docs... :P<br />
[11:32] <Zaerc> heh, I never log irc, except for small pieces I copy/paste on occasion<br />
[11:33] <jimbodude> someone got that? yes? volunteer?<br />
[11:33] <jimbodude> should have thought of that earlier... I overran the buffer here... whoops.<br />
[11:33] <tkmedia_2> done<br />
[11:33] <jimbodude> thanks.<br />
[11:33] <tkmedia_2> just a full paste<br />
[11:34] <jimbodude> alright guys, thanks for putting up with my nagging all week - you can expect more next week ;)<br />
[11:34] <Zaerc> thank you jimbodude for organizing this<br />
[11:34] <Zaerc> it has been long overdue imo<br />
[11:34] <jimbodude> Zaerc: no problem.<br />
[11:35] <jimbodude> I'm pretty excited about this project, anything I can do to help is a plus for everyone.</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1850520090415Agenda2009-04-15T15:30:25Z<p>Jimbodude: </p>
<hr />
<div>==Logistics==<br />
*This meeting happened<br />
**[[20090415Transcript|Transcript]]<br />
**[[20090415Minutes|Minutes]]<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Wednesday, April 15<br />
**'''Time:''' 2PM GMT (4PM Berlin, 10AM New York, 7AM Los Angeles)<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' #linuxmce-devel<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
***No major bugs<br />
**Orbiter<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/153 #153]: RA button on orbiters/on-screen orbiters crashes the orbiter<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/160 #160]: JavaMO.jar missing for build<br />
***[Compile error in Orbiter_Plugin #9]: Compile error in Orbiter_Plugin<br />
**Media Playing<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/40 #40]: MAME Integration (blocker/defect)<br />
***[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)<br />
**Xine<br />
***No major bugs<br />
**MPlayer<br />
***No major bugs<br />
**MythTV<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/124 #124]: MythTV Plugin needs to use the new MythTV Storage Groups<br />
**VDR<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/54 #54]: Initial vdr config errors<br />
**Lighting,Climate<br />
***No major bugs<br />
**Setup and AV Wizard<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/27 #27]: Create Diskless Boot Image (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/166 #166]: Automatic MD creation (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/150 #150]: hardy entry ends up in the sources.list<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/167 #167]: pluto-blutooth-dongle does not automatically install when USB dongle inserted<br />
**Web Admin<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/119 #119]: IR / GSD codes bugs<br />
**Telephony<br />
***No major bugs<br />
**Other<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/26 #26]: New installer (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/101 #101]: cleancore script bugs (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/48 #48]: Launch Manager rewrite to be CLI only (no QT dependancy)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/107 #107]: Backup system does not backup all relevant parts<br />
*Review of other topics as they arise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**[http://www.freeaudioconferencing.com/services.php Voice chat]? - (Cylon7)<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1848220090415Agenda2009-04-15T14:01:42Z<p>Jimbodude: /* 0810 Progress Review */</p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Wednesday, April 15<br />
**'''Time:''' 2PM GMT (4PM Berlin, 10AM New York, 7AM Los Angeles)<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' #linuxmce-devel<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
***No major bugs<br />
**Orbiter<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/153 #153]: RA button on orbiters/on-screen orbiters crashes the orbiter<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/160 #160]: JavaMO.jar missing for build<br />
***[Compile error in Orbiter_Plugin #9]: Compile error in Orbiter_Plugin<br />
**Media Playing<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/40 #40]: MAME Integration (blocker/defect)<br />
***[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)<br />
**Xine<br />
***No major bugs<br />
**MPlayer<br />
***No major bugs<br />
**MythTV<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/124 #124]: MythTV Plugin needs to use the new MythTV Storage Groups<br />
**VDR<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/54 #54]: Initial vdr config errors<br />
**Lighting,Climate<br />
***No major bugs<br />
**Setup and AV Wizard<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/27 #27]: Create Diskless Boot Image (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/166 #166]: Automatic MD creation (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/150 #150]: hardy entry ends up in the sources.list<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/167 #167]: pluto-blutooth-dongle does not automatically install when USB dongle inserted<br />
**Web Admin<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/119 #119]: IR / GSD codes bugs<br />
**Telephony<br />
***No major bugs<br />
**Other<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/26 #26]: New installer (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/101 #101]: cleancore script bugs (blocker)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/48 #48]: Launch Manager rewrite to be CLI only (no QT dependancy)<br />
***[http://svn.linuxmce.org/trac.cgi/ticket/107 #107]: Backup system does not backup all relevant parts<br />
*Review of other topics as they arise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**[http://www.freeaudioconferencing.com/services.php Voice chat]? - (Cylon7)<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1845420090415Agenda2009-04-14T16:42:22Z<p>Jimbodude: </p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Wednesday, April 15<br />
**'''Time:''' 2PM GMT (4PM Berlin, 10AM New York, 7AM Los Angeles)<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' #linuxmce-devel<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**[http://www.freeaudioconferencing.com/services.php Voice chat]? - (Cylon7)<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1841520090415Agenda2009-04-13T13:51:10Z<p>Jimbodude: adding times</p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**'''Date:''' Wednesday, April 15<br />
**'''Time:''' 2PM GMT (4PM Berlin, 10AM New York, 7AM Los Angeles)<br />
**'''Duration:''' 1.5 hour maximum<br />
**'''Server:''' irc.freenode.net<br />
**'''Channel:''' TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**[http://www.freeaudioconferencing.com/services.php Voice chat]? - (Cylon7)<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1839020090415Agenda2009-04-11T05:22:11Z<p>Jimbodude: /* Procedural Changes */</p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
**Date: TBD<br />
**Time: TBD<br />
**Duration: TBD<br />
**Server: irc.freenode.net<br />
**Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**[http://www.freeaudioconferencing.com/services.php Voice chat]? - (Cylon7)<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1838320090415Agenda2009-04-10T19:42:39Z<p>Jimbodude: /* High Level Design Discussions */</p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
**Date: TBD<br />
**Time: TBD<br />
**Duration: TBD<br />
**Server: irc.freenode.net<br />
**Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
*Discuss possibility of running our own new_install script on www.linuxmce.org and assigning our own installation ID's - (jondecker76)<br />
**Who knows if and/or when plutohome.com will disappear along with the script that is currently used. <br />
**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. <br />
**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). <br />
**Old pluto installation ID's can be re-assigned for upgrades from 0710 with a post-upgrade script. <br />
**This change can be made in a matter of an hour.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1838220090415Agenda2009-04-10T19:41:08Z<p>Jimbodude: /* Logistics */</p>
<hr />
<div>==Logistics==<br />
*Agenda<br />
**It is expected that meeting participants will be familiar with this agenda and the resources it links to<br />
**Any one may add to the agenda - just put your name next to the topic<br />
*Time and Place<br />
**This meeting will be held on IRC.<br />
**Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
**Date: TBD<br />
**Time: TBD<br />
**Duration: TBD<br />
**Server: irc.freenode.net<br />
**Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
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.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1838120090415Agenda2009-04-10T19:38:46Z<p>Jimbodude: /* 0810 Release Scheduling */</p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
*Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
*Date: TBD<br />
*Time: TBD<br />
*Duration: TBD<br />
*Server: irc.freenode.net<br />
*Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
*Should 0810 have a "formal" release schedule?<br />
**Consider these sources as examples<br />
***[https://wiki.ubuntu.com/GutsyReleaseSchedule Ubuntu Gutsy], [https://wiki.ubuntu.com/JauntyReleaseSchedule Ubuntu Jaunty]<br />
***[http://live.gnome.org/Schedule Gnome]<br />
***[http://techbase.kde.org/Schedules/Release_Schedules_Guide KDE General Guide], [http://techbase.kde.org/Schedules/KDE_3.2_Release_Schedule KDE 3.2]<br />
**What milestones apply?<br />
***Feature Freeze?<br />
***Code Freeze?<br />
***Beta release deadline?<br />
***General release deadline?<br />
*0810 Update release schedule (jondecker76)<br />
**Discuss update scheduling for after 0810 is released, as well as the frequency of the updates. <br />
**Maybe a planned monthly build (similar to how we do the weekly's now) for bugfixes/feature enhancements wouldn't be a bad idea.<br />
<br />
===High Level Design Discussions===<br />
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.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1837920090415Agenda2009-04-10T19:30:55Z<p>Jimbodude: re-org</p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
*Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
*Date: TBD<br />
*Time: TBD<br />
*Duration: TBD<br />
*Server: irc.freenode.net<br />
*Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
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.<br />
<br />
===High Level Design Discussions===<br />
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.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**Schedule next meeting</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1837820090415Agenda2009-04-10T19:30:29Z<p>Jimbodude: /* Review of Outstanding Defects */</p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
*Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
*Date: TBD<br />
*Time: TBD<br />
*Duration: TBD<br />
*Server: irc.freenode.net<br />
*Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
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.<br />
<br />
===Procedural Changes===<br />
*Discuss efforts to improve defect tracking methods (jimbodude)<br />
**Discuss ways to make sure all defects are reported<br />
**Discuss ways to make sure all reported defects are addressed in a timely manner<br />
**Consider re-working [http://jimbodude.net/wiki/Bug_Reporting current work] into LinuxMCE/Trac specific policy<br />
*Discuss effectiveness of future meetings<br />
**Decide whether to have more<br />
**Discuss meeting frequency<br />
**Schedule next meeting<br />
<br />
===High Level Design Discussions===<br />
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.</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1837720090415Agenda2009-04-10T19:25:12Z<p>Jimbodude: /* 0810 Short Term Goals */</p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
*Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
*Date: TBD<br />
*Time: TBD<br />
*Duration: TBD<br />
*Server: irc.freenode.net<br />
*Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
*Defects to address<br />
*Features to implement<br />
<br />
===0810 Release Scheduling===<br />
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.<br />
<br />
===Review of Outstanding Defects===<br />
<br />
===High Level Design Discussions===<br />
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.</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1837620090415Agenda2009-04-10T19:23:38Z<p>Jimbodude: /* 0810 Progress Review */</p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
*Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
*Date: TBD<br />
*Time: TBD<br />
*Duration: TBD<br />
*Server: irc.freenode.net<br />
*Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
*Status review of each component (including review of defects marked at least major, or of special interest)<br />
**DCERouter<br />
**Orbiter<br />
**Media Playing<br />
**Xine<br />
**MPlayer<br />
**MythTV<br />
**VDR<br />
**Lighting,Climate<br />
**Setup and AV Wizard<br />
**Web Admin<br />
*Review of other topics as they arrise<br />
<br />
===0810 Short Term Goals===<br />
<br />
===0810 Release Scheduling===<br />
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.<br />
<br />
===Review of Outstanding Defects===<br />
<br />
===High Level Design Discussions===<br />
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.</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1837120090415Agenda2009-04-09T23:24:54Z<p>Jimbodude: </p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
*Post your availability [http://www.when2meet.com/?16114-xPiEx here] if interested in this meeting<br />
*Date: TBD<br />
*Time: TBD<br />
*Duration: TBD<br />
*Server: irc.freenode.net<br />
*Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
<br />
===0810 Short Term Goals===<br />
<br />
===0810 Release Scheduling===<br />
<br />
===Review of Outstanding Defects===<br />
<br />
===High Level Design Discussions===</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=DeveloperMeetings&diff=18370DeveloperMeetings2009-04-09T23:23:06Z<p>Jimbodude: </p>
<hr />
<div>==Purpose==<br />
This page serves as a place to keep track of discussions that happen in developer meetings and plan future meetings.<br />
<br />
==Meetings==<br />
*General Organizational Meeting (IRC - time and channel TBA)<br />
**[[Meeting1Agenda|Agenda]]<br />
**(transcript will be available after the meeting)</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1836920090415Agenda2009-04-09T23:22:16Z<p>Jimbodude: </p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
*Date: TBD<br />
*Time: TBD<br />
*Duration: TBD<br />
*Server: irc.freenode.net<br />
*Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
<br />
===0810 Short Term Goals===<br />
<br />
===0810 Release Scheduling===<br />
<br />
===Review of Outstanding Defects===<br />
<br />
===High Level Design Discussions===</div>Jimbodudehttp://wiki.linuxmce.org/index.php?title=20090415Agenda&diff=1836820090415Agenda2009-04-09T23:21:50Z<p>Jimbodude: New page: ==Logistics== This meeting will be held on IRC. Date: TBD Time: TBD Duration: TBD Server: irc.freenode.net Channel: TBD ==Agenda== ===0810 Progress Review=== ===0810 Short Term Goals===...</p>
<hr />
<div>==Logistics==<br />
This meeting will be held on IRC.<br />
Date: TBD<br />
Time: TBD<br />
Duration: TBD<br />
Server: irc.freenode.net<br />
Channel: TBD<br />
<br />
==Agenda==<br />
<br />
===0810 Progress Review===<br />
<br />
===0810 Short Term Goals===<br />
<br />
===0810 Release Scheduling===<br />
<br />
===Review of Outstanding Defects===<br />
<br />
===High Level Design Discussions===</div>Jimbodude