<div>Thanks to everyone who filled in their availability.</div><div><br></div>The meeting will be 9PM GMT on Sunday the 10th April. Lets keep the meeting short as most of us have work in the morning.<div><br></div><div>Agenda:</div>
<div><br></div><div>A very short summary of what's happened in each component since the last meeting (which was January sometime) from the component leaders.</div><div><br></div><div> - Contact List (mck182)</div><div>
- Chat UI (nwokeka) </div><div> - Call UI (gkaigia)</div><div> - Accounts KCM (volunteers?)</div><div> - Approver (gkiagia)</div><div> - The plasmoids (drf_____)</div><div><br></div><div>The most important thing to discuss:</div>
<div>"Release 0.1alpha"</div><div><br></div><div>The most important thing to decide with a release is "who is it for". For me the main purpose of a release is to say "We are doing stuff, look at all this". It's about publicity and getting attention within the KDE Community rather than about getting 'normal' everyday users. </div>
<div><br></div><div>I don't care about whether everything is feature complete, or if it's 100% perfect. Though it is important to have a solid stable codebase and to show the potential of the project - and ideally to try and highlight some of the application integration possible (i.e KDE Tp can be so much more than Kopete). I want people to look at it and go "ah, that's cool - that's progressing well and shows a lot of new cool ideas". </div>
<div><br></div><div>(and most importantly, look like we're doing enough for the eV to send us all to the desktop summit)</div><div><br></div><div>Does anyone disagree with this objective?</div><div><br></div><div>With these goals in mind, I want all component leads to list everything that needs doing before a release, and some kind of timeframe as to how long this will take. Please think about this _before_ the meeting. It may be worth making a list of all your outstanding tasks in bugzilla, and even listing stuff you don't intend to get done before a release and list that you think it can be deferred. Please also think about this when prioritising your coding </div>
<div><br></div><div>Also try and think about is there anything that isn't being handled by any of the above components. </div><div><br></div><div>We also need to task finding out how to deliver this as something that can be downloaded/distributed especially wrt icons and protocol files.</div>
<div><br></div><div>Wiki page: <a href="http://community.kde.org/Real-Time_Communication_and_Collaboration/Meeting_10_04_2011">http://community.kde.org/Real-Time_Communication_and_Collaboration/Meeting_10_04_2011</a></div>
<div><br></div><div>If you have anything you want to raise at the meeting please let me know.</div><div><br></div><div>For anyone who can't attend the meeting, a short summary will be published to the mailing list afterwards.</div>
<meta http-equiv="content-type" content="text/html; charset=utf-8">