<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://wiki.meego.com/skins/common/feed.css?270"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://wiki.meego.com/index.php?title=Special:Contributions/Tekojo&amp;feed=atom&amp;limit=50&amp;target=Tekojo&amp;year=&amp;month=</id>
		<title>MeeGo wiki - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.meego.com/index.php?title=Special:Contributions/Tekojo&amp;feed=atom&amp;limit=50&amp;target=Tekojo&amp;year=&amp;month="/>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Special:Contributions/Tekojo"/>
		<updated>2013-06-18T05:27:18Z</updated>
		<subtitle>From MeeGo wiki</subtitle>
		<generator>MediaWiki 1.16.2</generator>

	<entry>
		<id>http://wiki.meego.com/Marketing/Meego.com_1.2_update</id>
		<title>Marketing/Meego.com 1.2 update</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Marketing/Meego.com_1.2_update"/>
				<updated>2011-01-18T13:27:50Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is the meego.com related work that needs to be in place and polished before the [http://wiki.meego.com/Release_Engineering/Plans/1.2 MeeGo 1.2 release] (end of April 2011).&lt;br /&gt;
&lt;br /&gt;
== Goals ==&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=11512 Reorganization of meego.com] (Mike)- see [[Marketing/Meego.com 1.2 update/Reorganization]]&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=11510 New page for Core OS] (Quim) &lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=11503 Guidelines for content in meego.com vs wiki.meego.com]  (Dawn)&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=7882 Complete developer.meego.com] (Ronan) - see [[Application developer site]]&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=11899 Complete planet.meego.com] (Henri) - see [[Planet.meego.com]]&lt;br /&gt;
* Complete Apps (Tero) - see [[Community Application Support]] &amp;amp; [[Community Office/Task Forces/MeeGo Surrounds and Extras|MeeGo Surrounds and Extras]]&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=7072 Complete packages interface] (Niels)&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=12471 Complete Community OBS] (David) - see [[Build Infrastructure/Community Builder|Community Builder]]&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=11505 Press friendly About section] (Quim) - [[Marketing/Meego.com 1.2 update/About section]]&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=11513 Homepage refresh] (Quim) - see [[Marketing/Meego.com 1.2 update/Homepage]]&lt;br /&gt;
* Website for new MeeGo Conference (Mike)&lt;br /&gt;
&lt;br /&gt;
== Dates ==&lt;br /&gt;
Still not agreed.&lt;br /&gt;
&lt;br /&gt;
== Open items ==&lt;br /&gt;
&lt;br /&gt;
{{#bugzilla:&lt;br /&gt;
  |columns=id,priority,severity,status,summary&lt;br /&gt;
  |product=developer.meego.com,meego.com,planet.meego.com,Community Build Service&lt;br /&gt;
  |priority=high,medium&lt;br /&gt;
  |group=product&lt;br /&gt;
  |status=new,assigned,needinfo,reopened&lt;br /&gt;
  |sort=priority,severity,id&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2011-01-18T13:24:15Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
As of mid January&lt;br /&gt;
&lt;br /&gt;
* Apps to come online for testing at [http://apps-beta.meego.com/ apps-beta] January/February&lt;br /&gt;
* Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode &lt;br /&gt;
* BOSS to be used as the management system for the apps/repos - needs some work still to get stabilised and ready for use&lt;br /&gt;
* OCS interface defined - done&lt;br /&gt;
* End-user clients are there in gitorious under the name garage-client&lt;br /&gt;
* Work on OCS server interface commencing in week 48 - still ongoing&lt;br /&gt;
&lt;br /&gt;
[http://www.qaiku.com/channels/show/MeeGork/ The stream where the developers have documented progress] and &lt;br /&gt;
[http://www.qaiku.com/channels/show/MeeGork/view/d2703a0e135711e0a24633013e50078e078e/ latest comment in the Qaiku workstream by Ferenc]&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* The rules for moving packages to and from testing&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Application submission can be handled in the OBS client&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* BOSS, the logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository called 'Apps', so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated and manual quality assurance&lt;br /&gt;
&lt;br /&gt;
[http://static.qaiku.com/d30/350/f4f/d30350f4fef911dfb46fb5ad123b10f010f0.png?t=1291393478 Mock-up of Apps page] running in a test environment.&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
* Henri (bergie) - OCS, web interface&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
* Discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;br /&gt;
* Community Applications repository sprint in November 2010: [http://lists.meego.com/pipermail/meego-community/2010-November/002526.html]&lt;br /&gt;
&lt;br /&gt;
=== Old log  ===&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2011-01-18T13:23:58Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
As of mid January&lt;br /&gt;
&lt;br /&gt;
* Apps to come online for testing at [http://apps-beta.meego.com/] January/February&lt;br /&gt;
* Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode &lt;br /&gt;
* BOSS to be used as the management system for the apps/repos - needs some work still to get stabilised and ready for use&lt;br /&gt;
* OCS interface defined - done&lt;br /&gt;
* End-user clients are there in gitorious under the name garage-client&lt;br /&gt;
* Work on OCS server interface commencing in week 48 - still ongoing&lt;br /&gt;
&lt;br /&gt;
[http://www.qaiku.com/channels/show/MeeGork/ The stream where the developers have documented progress] and &lt;br /&gt;
[http://www.qaiku.com/channels/show/MeeGork/view/d2703a0e135711e0a24633013e50078e078e/ latest comment in the Qaiku workstream by Ferenc]&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* The rules for moving packages to and from testing&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Application submission can be handled in the OBS client&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* BOSS, the logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository called 'Apps', so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated and manual quality assurance&lt;br /&gt;
&lt;br /&gt;
[http://static.qaiku.com/d30/350/f4f/d30350f4fef911dfb46fb5ad123b10f010f0.png?t=1291393478 Mock-up of Apps page] running in a test environment.&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
* Henri (bergie) - OCS, web interface&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
* Discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;br /&gt;
* Community Applications repository sprint in November 2010: [http://lists.meego.com/pipermail/meego-community/2010-November/002526.html]&lt;br /&gt;
&lt;br /&gt;
=== Old log  ===&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2011-01-18T09:10:10Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
* Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode &lt;br /&gt;
* BOSS to be used as the management system for the apps/repos&lt;br /&gt;
* OCS interface defined&lt;br /&gt;
* End-user clients are there in gitorious under the name garage-client&lt;br /&gt;
* Work on OCS server interface commencing in week 48&lt;br /&gt;
&lt;br /&gt;
[http://www.qaiku.com/channels/show/MeeGork/ The stream where the developers have documented progress] and &lt;br /&gt;
[http://www.qaiku.com/channels/show/MeeGork/view/d2703a0e135711e0a24633013e50078e078e/ latest comment in the Qaiku workstream by Ferenc]&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* The rules for moving packages to and from testing&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Application submission can be handled in the OBS client&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* BOSS, the logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository called 'Apps', so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated and manual quality assurance&lt;br /&gt;
&lt;br /&gt;
[http://static.qaiku.com/d30/350/f4f/d30350f4fef911dfb46fb5ad123b10f010f0.png?t=1291393478 Mock-up of Apps page] running in a test environment.&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
* Henri (bergie) - OCS, web interface&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
* Discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;br /&gt;
* Community Applications repository sprint in November 2010: [http://lists.meego.com/pipermail/meego-community/2010-November/002526.html]&lt;br /&gt;
&lt;br /&gt;
=== Old log  ===&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2011-01-18T08:39:15Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
* Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode &lt;br /&gt;
* BOSS to be used as the management system for the apps/repos&lt;br /&gt;
* OCS interface defined&lt;br /&gt;
* End-user clients are there in gitorious under the name garage-client&lt;br /&gt;
* Work on OCS server interface commencing in week 48&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* The rules for moving packages to and from testing&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Application submission can be handled in the OBS client&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* BOSS, the logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository called 'Apps', so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated and manual quality assurance&lt;br /&gt;
&lt;br /&gt;
[http://static.qaiku.com/d30/350/f4f/d30350f4fef911dfb46fb5ad123b10f010f0.png?t=1291393478 Mock-up of Apps page] running in a test environment.&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
* Henri (bergie) - OCS, web interface&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
* Discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;br /&gt;
* Community Applications repository sprint in November 2010: [http://lists.meego.com/pipermail/meego-community/2010-November/002526.html]&lt;br /&gt;
&lt;br /&gt;
=== Old log  ===&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-11-14T10:36:20Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
* Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode &lt;br /&gt;
* BOSS to be used as the management system for the apps/repos&lt;br /&gt;
* OCS interface defined&lt;br /&gt;
* End-user clients are there in gitorious under the name garage-client&lt;br /&gt;
* Work on OCS server interface commencing in week 48&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* The rules for moving packages to and from testing&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;br /&gt;
&lt;br /&gt;
=== Old log  ===&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-11-14T10:33:20Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
* Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode &lt;br /&gt;
* BOSS to be used as the management system for the apps/repos&lt;br /&gt;
* OCS interface defined&lt;br /&gt;
* End-user clients are there in gitorious under the name garage-client&lt;br /&gt;
* Work on OCS server interface commencing in week 48&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* The rules for moving packages to and from testing&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
=== Current status  ===&lt;br /&gt;
&lt;br /&gt;
OBS up and running.&lt;br /&gt;
Authentication and authorization is an issue.&lt;br /&gt;
&lt;br /&gt;
Web end needs work (short on people to do it)&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/MeeGo_Conference_2010/Unconference/ARM</id>
		<title>MeeGo Conference 2010/Unconference/ARM</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/MeeGo_Conference_2010/Unconference/ARM"/>
				<updated>2010-10-26T05:30:56Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Like Minded Individuals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== When ==&lt;br /&gt;
&lt;br /&gt;
This will happen as a BoF at http://conference2010.meego.com/session/bof-meego-arm&lt;br /&gt;
&lt;br /&gt;
== Intents &amp;amp; Purposes ==&lt;br /&gt;
&lt;br /&gt;
I plan to get together with like minded individuals at the unconference part of the MeeGo conference 2010 and talk about [[ARM|MeeGo on ARM]]. The idea is to sit down and discuss current state of the port of the MeeGo platform to the ARM architecture, problems, lessons learnt and future directions of MeeGo ARM and everything surrounding it (tool support, ecosystem, quality, documentation, etc.)&lt;br /&gt;
&lt;br /&gt;
Chipset and SoC vendors, hobbyists, end-user product developers, OEM, ODMs, ISVs, porting engineers, toolchain engineers - everyone with an interest is more than welcome. - indicate your interest below!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Like Minded Individuals ==&lt;br /&gt;
&lt;br /&gt;
(Form: Name, IRC nickname if any, Affiliation, discussion topic)&lt;br /&gt;
&lt;br /&gt;
* Carsten Munk, Stskeeps, Imogen Software - MeeGo Nokia N900 hardware adaptation team member - Topics: The above!&lt;br /&gt;
* Tomasz Sterna, smoku, hobbyist - MSM/QSD adaptation team member&lt;br /&gt;
* Randall Arnold, texrat - General interest in broad platform support&lt;br /&gt;
* Till Harbaum, harbaum - MeeGo on Beagleboard and similar plattforms&lt;br /&gt;
* George Ioakimedes, GeorgeIoak - Mostly TI OMAP based boards but open to other ARM solutions&lt;br /&gt;
* Jeremiah C. Foster, jeremiah, Pelagicore / GENIVI - ARM and Qemu, Integrating Linaro bits, integrating MeeGo IVI, GENIVI, etc.&lt;br /&gt;
* Timo Härkönen, timoph, Digia Plc - MeeGo QA-tools team member, general interest&lt;br /&gt;
* Jari Palojärvi, jpal, Nokia, MeeGo Porting Guide&lt;br /&gt;
* Jan-Simon Möller, dl9pf, The Linux Foundation, Toolchain/Qemu/OBS, broad platform support.&lt;br /&gt;
* Christian Daudt, csdb, Broadcom, ARM &amp;amp; MeeGo overall.&lt;br /&gt;
* Sivan Greenberg, sivang - Toolchain, quality, cross OS porting and general interest.&lt;br /&gt;
* Tero Kojo, tekojo, Nokia - Community interest, general interest&lt;br /&gt;
&lt;br /&gt;
&amp;lt;add your indication of interest here&amp;gt;&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-09-22T06:33:49Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
* Community OBS is in limited testing. i.e. some users have been invited to test the system&lt;br /&gt;
* Using the meego.com login names is technically solved with LDAP&lt;br /&gt;
* BOSS to be used as the management system for the apps/repos&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting ===&lt;br /&gt;
* '''Open, Niels on vacation'''&lt;br /&gt;
* IRC channel:  #meego-cas  (community application support).  &lt;br /&gt;
* Agenda:  http://wiki.meego.com/Community_Application_Support/Meeting_Agenda&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* Package detail management interface implementation on Drupal&lt;br /&gt;
* OCS interface design&lt;br /&gt;
* OCS interface implementation (on Drupal?)&lt;br /&gt;
* BOSS integration&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
=== Current status  ===&lt;br /&gt;
&lt;br /&gt;
OBS up and running.&lt;br /&gt;
Authentication and authorization is an issue.&lt;br /&gt;
&lt;br /&gt;
Web end needs work (short on people to do it)&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-09-22T06:29:39Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Next Meeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting ===&lt;br /&gt;
* '''Open, Niels on vacation'''&lt;br /&gt;
* IRC channel:  #meego-cas  (community application support).  &lt;br /&gt;
* Agenda:  http://wiki.meego.com/Community_Application_Support/Meeting_Agenda&lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* Package management interface design&lt;br /&gt;
* Package management interface implementation&lt;br /&gt;
* OCS interface design&lt;br /&gt;
* OCS interface implementation&lt;br /&gt;
* BOSS integration&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
=== Current status  ===&lt;br /&gt;
&lt;br /&gt;
OBS up and running.&lt;br /&gt;
Authentication and authorization is an issue.&lt;br /&gt;
&lt;br /&gt;
Web end needs work (short on people to do it)&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-08-20T06:48:08Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting ===&lt;br /&gt;
* '''Proposal:  Aug 12 (Thursday) PDT 8pm == UTC 7am == PRC 11am'''&lt;br /&gt;
* IRC channel:  #meego-cas  (community application support).  &lt;br /&gt;
* Agenda:  http://wiki.meego.com/Community_Application_Support/Meeting_Agenda &lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* Package management interface design&lt;br /&gt;
* Package management interface implementation&lt;br /&gt;
* OCS interface design&lt;br /&gt;
* OCS interface implementation&lt;br /&gt;
* BOSS integration&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
=== Current status  ===&lt;br /&gt;
&lt;br /&gt;
OBS up and running.&lt;br /&gt;
Authentication and authorization is an issue.&lt;br /&gt;
&lt;br /&gt;
Web end needs work (short on people to do it)&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-08-20T06:47:45Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting ===&lt;br /&gt;
* '''Proposal:  Aug 12 (Thursday) PDT 8pm == UTC 7am == PRC 11am'''&lt;br /&gt;
* IRC channel:  #meego-cas  (community application support).  &lt;br /&gt;
* Agenda:  http://wiki.meego.com/Community_Application_Support/Meeting_Agenda &lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* Package management interface design&lt;br /&gt;
* Package management interface implementation&lt;br /&gt;
* OCS interface design&lt;br /&gt;
* OCS interface implementation&lt;br /&gt;
* BOSS integration&lt;br /&gt;
&lt;br /&gt;
=== Current status  ===&lt;br /&gt;
&lt;br /&gt;
OBS up and running.&lt;br /&gt;
Authentication and authorization is an issue.&lt;br /&gt;
&lt;br /&gt;
Web end needs work (short on people to do it)&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-08-20T06:44:07Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Current tasks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Next Meeting ===&lt;br /&gt;
* '''Proposal:  Aug 12 (Thursday) PDT 8pm == UTC 7am == PRC 11am'''&lt;br /&gt;
* IRC channel:  #meego-cas  (community application support).  &lt;br /&gt;
* Agenda:  http://wiki.meego.com/Community_Application_Support/Meeting_Agenda &lt;br /&gt;
&lt;br /&gt;
=== Current tasks that need to be taken ===&lt;br /&gt;
&lt;br /&gt;
* Package management interface design&lt;br /&gt;
* Package management interface implementation&lt;br /&gt;
* OCS interface design&lt;br /&gt;
* OCS interface implementation&lt;br /&gt;
* BOSS integration&lt;br /&gt;
&lt;br /&gt;
=== Current status (14.6.2010) ===&lt;br /&gt;
&lt;br /&gt;
Hardware arrived to Portland. OSes being installed, and the whole hardware layout being planned.&lt;br /&gt;
&lt;br /&gt;
In the mean time David (lbt) and Niels (X-Fade) have set up an OBS instance in the old maemo.org hardware. This will speed up deployment once the hardware arrives for meego.com.&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-06-17T06:49:37Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current tasks ===&lt;br /&gt;
&lt;br /&gt;
* Mike - Getting hardware up to booting in OSU&lt;br /&gt;
* David - OBS set up&lt;br /&gt;
* Niels - OBS set up&lt;br /&gt;
&lt;br /&gt;
=== Current status (14.6.2010) ===&lt;br /&gt;
&lt;br /&gt;
Hardware arrived to Portland. OSes being installed, and the whole hardware layout being planned.&lt;br /&gt;
&lt;br /&gt;
In the mean time David (lbt) and Niels (X-Fade) have set up an OBS instance in the old maemo.org hardware. This will speed up deployment once the hardware arrives for meego.com.&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-06-15T08:29:48Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Current status (25.5.2010) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status (14.6.2010) ===&lt;br /&gt;
&lt;br /&gt;
Hardware arrived to Portland. OSes being installed, and the whole hardware layout being planned.&lt;br /&gt;
&lt;br /&gt;
In the mean time David (lbt) and Niels (X-Fade) have set up an OBS instance in the old maemo.org hardware. This will speed up deployment once the hardware arrives for meego.com.&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support/Meeting_minutes_2_6_2010</id>
		<title>Community Application Support/Meeting minutes 2 6 2010</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support/Meeting_minutes_2_6_2010"/>
				<updated>2010-06-07T10:43:21Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Full log]&lt;br /&gt;
&lt;br /&gt;
* Most people in the area present (also there seems to be ~50 people all the time on meego-meeting)&lt;br /&gt;
* No hardware yet, but expecting it real soon now. (US order should arrive first)&lt;br /&gt;
* Intel employees and David (lbt) will look at the set-up needed to make the community OBS accessible but safe&lt;br /&gt;
* There is a proof of concept OBS in maemo.org set up by David and Niels (X-Fade)&lt;br /&gt;
* The SDK - OBS connection is one area that needs to be worked on too&lt;br /&gt;
* The download client projects (maemo.org and MeeGo garage) need to be merged at some point&lt;br /&gt;
* The OBS interface will need to work with the MeeGo.com userids&lt;br /&gt;
* The working assumption is that the QA process will rely on community members doing testing. We are hoping that the core QA people also help a bit in getting test automation to the community build system too.&lt;br /&gt;
* The actual testing incentives need to be considered carefully. Testing needs to take place, and it needs to be real testing.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support/Meeting_minutes_2_6_2010</id>
		<title>Community Application Support/Meeting minutes 2 6 2010</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support/Meeting_minutes_2_6_2010"/>
				<updated>2010-06-03T11:24:00Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Created page with '- Most people in the area present (also there seems to be ~50 people all the time on meego-meeting) - No hardware yet, but expecting it real soon now. (US order should arrive fir…'&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;- Most people in the area present (also there seems to be ~50 people all the time on meego-meeting)&lt;br /&gt;
- No hardware yet, but expecting it real soon now. (US order should arrive first)&lt;br /&gt;
- Intel employees and David (lbt) will look at the set-up needed to make the community OBS accessible but safe&lt;br /&gt;
- There is a proof of concept OBS in maemo.org set up by David and Niels (X-Fade)&lt;br /&gt;
- The SDK - OBS connection is one area that needs to be worked on too&lt;br /&gt;
- The download client projects (maemo.org and MeeGo garage) need to be merged at some point&lt;br /&gt;
- The OBS interface will need to work with the MeeGo.com userids&lt;br /&gt;
- The working assumption is that the QA process will rely on community members doing testing. We are hoping that the core QA people also help a bit in getting test automation to the community build system too.&lt;br /&gt;
- The actual testing incentives need to be considered carefully. Testing needs to take place, and it needs to be real testing.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-06-03T10:39:18Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: link to meeting log&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status (25.5.2010) ===&lt;br /&gt;
&lt;br /&gt;
No change in the last week, waiting for hardware.&lt;br /&gt;
&lt;br /&gt;
In the mean time David (lbt) and Niels (X-Fade) have set up an OBS instance in the old maemo.org hardware. This will speed up deployment once the hardware arrives for meego.com.&lt;br /&gt;
&lt;br /&gt;
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule</id>
		<title>MeeGo-Meeting IRC Schedule</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule"/>
				<updated>2010-06-02T18:45:59Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* June Schedule */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To avoid meeting conflicts in [http://meego.com/community/irc-channel #meego-meeting], please add your meeting here with date and UTC time until we have a more robust solution.&lt;br /&gt;
&lt;br /&gt;
== Regular Meetings ==&lt;br /&gt;
* [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]: The 1st and 3rd Tuesday alternating between 14:00 and 19:00 UTC&lt;br /&gt;
* [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]: Every other Wednesday at 19:00 UTC&lt;br /&gt;
&lt;br /&gt;
== June Schedule ==&lt;br /&gt;
* June 1, 19:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting] - CANCELED&lt;br /&gt;
* June 2, 17:30 UTC: [http://wiki.meego.com/Community_Application_Support Community Applications Team Meeting]&lt;br /&gt;
* June 3, 14:00 UTC: [http://wiki.meego.com/L10n_meeting_schedule L10N Meeting Schedule]&lt;br /&gt;
* June 9, 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;br /&gt;
* June 15, 14:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]&lt;br /&gt;
* June 16, (Preliminary, can change if hardware arrives) 17:30 UTC: [http://wiki.meego.com/Community_Application_Support Community Applications Team Meeting]&lt;br /&gt;
* June 23, 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;br /&gt;
&lt;br /&gt;
== July Schedule ==&lt;br /&gt;
* July 6 19:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]&lt;br /&gt;
* July 7 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;br /&gt;
* July 20 14:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]&lt;br /&gt;
* July 21 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/ARM/Meego_on_the_Beagle</id>
		<title>ARM/Meego on the Beagle</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/ARM/Meego_on_the_Beagle"/>
				<updated>2010-06-01T07:39:24Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: typo fix&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is dedicated to getting MeeGo running on the Beagleboard. More info on the beagleboard can be [http://beagleboard.org/ found here]&lt;br /&gt;
&lt;br /&gt;
Because the processor for the beagleboard C4 is an OMAP3530 and the N900 currently sports a similar processor, it seems wise to start with the [[ARM]] page.&lt;br /&gt;
&lt;br /&gt;
= Steps =&lt;br /&gt;
So far we've no image for beagleboard ready. But what works so far:&lt;br /&gt;
* Take the n900 [http://repo.meego.com/MeeGo/releases/1.0/core/images/meego-n900-open-armv7l/meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw.bz2 rootfs] and extract to the rootfs partition of the beagle sdcard setup. You can mount rootfs of N900 from this image on /mnt by:&lt;br /&gt;
*# bunzip meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw.bz2&lt;br /&gt;
*# sudo mount -o loop,offset=16384 meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw /mnt&lt;br /&gt;
* Then sync the contents to your SDcard by:&lt;br /&gt;
*# sudo rsync -aHx /mnt/* /media/your_sd_card&lt;br /&gt;
* [http://wiki.meego.com/images/Meego-beagle-kernel.tar.bz2 MeeGo Beagleboard kernel and modules] contains precompiled uImage and kernel modules (v2.6.34) for Beagleboard. You need copy uImage to /boot partition of your SD card, and modules to /lib/modules directory on your root file system.&lt;br /&gt;
* Since we are using rootfs tuned for N900, we can stop starting X by replacing id:5:initdefault: to id:3:initdefault: in /etc/inittab.&lt;br /&gt;
* To fine tune above kernel follow these instructions:&lt;br /&gt;
*# Copy meego-beagle-kernel.config from above archieve to your kernel compilation directory as .config&lt;br /&gt;
*# make old_config&lt;br /&gt;
*# Tune kernel options using: make xconfig&lt;br /&gt;
*# You can now compile your kernel using: make uImage&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/ARM/Meego_on_the_Beagle</id>
		<title>ARM/Meego on the Beagle</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/ARM/Meego_on_the_Beagle"/>
				<updated>2010-06-01T07:35:21Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Steps */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is dedicated to getting MeeGo running on the Beagleboard. More info on the beagleboard can be [http://beagleboard.org/ found here]&lt;br /&gt;
&lt;br /&gt;
Because the processor for the beagleboard C4 is an OMAP3530 and the N900 currently sports a similar processor, it seems wise to start with the [[ARM]] page.&lt;br /&gt;
&lt;br /&gt;
= Steps =&lt;br /&gt;
So far we've no image for beagleboard ready. But what works so far:&lt;br /&gt;
* Take the n900 [http://repo.meego.com/MeeGo/releases/1.0/core/images/meego-n900-open-armv7l/meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw.bz2 rootfs] and extract to the rootfs partition of the beagle sdcard setup. You can mount rootfs of N900 from this image on /mnt by:&lt;br /&gt;
*# bunzip meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw.bz2&lt;br /&gt;
*# sudo mount -o loop,offset=16384 meego-n900-open-armv7l-1.0.0.20100525.1-sda.raw /mnt&lt;br /&gt;
* Then sync the contents to your SDcard by:&lt;br /&gt;
*# sudo rsync -aHx /mnt /media/your_sd_card&lt;br /&gt;
* [http://wiki.meego.com/images/Meego-beagle-kernel.tar.bz2 MeeGo Beagleboard kernel and modules] contains precompiled uImage and kernel modules (v2.6.34) for Beagleboard. You need copy uImage to /boot partition of your SD card, and modules to /lib/modules directory on your root file system.&lt;br /&gt;
* Since we are using rootfs tuned for N900, we can stop starting X by replacing id:5:initdefault: to id:3:initdefault: in /etc/inittab.&lt;br /&gt;
* To fine tune above kernel follow these instructions:&lt;br /&gt;
*# Copy meego-beagle-kernel.config from above archieve to your kernel compilation directory as .config&lt;br /&gt;
*# make old_config&lt;br /&gt;
*# Tune kernel options using: make xconfig&lt;br /&gt;
*# You can now compile your kernel using: make uImage&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Devices</id>
		<title>Devices</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Devices"/>
				<updated>2010-05-31T09:04:53Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Netbooks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Below you find devices where MeeGo was used successfully (atm only user reports, the list below is compiled from [http://forum.meego.com/showthread.php?t=83 this] forum thread). The list is not complete and waits for your input. &lt;br /&gt;
&lt;br /&gt;
==Devices compatible with MeeGo==&lt;br /&gt;
''sorted alphabetically''&lt;br /&gt;
&lt;br /&gt;
===Handsets===&lt;br /&gt;
*[[Devices/N900|Nokia N900]] (see install instructions at: [[ARM]])&lt;br /&gt;
&lt;br /&gt;
===Netbooks===&lt;br /&gt;
*[[wikipedia:Acer Aspire One|Acer Aspire]]&lt;br /&gt;
** One AO532-h&lt;br /&gt;
** One D250&lt;br /&gt;
** One ZG5&lt;br /&gt;
 &lt;br /&gt;
*[[wikipedia:Asus Eee PC|Asus EeePC]]&lt;br /&gt;
** 901&lt;br /&gt;
** 901 Go (3G not supported yet)&lt;br /&gt;
** 1000&lt;br /&gt;
** 1000H &lt;br /&gt;
** 1005HA &lt;br /&gt;
** 1005PE (Intel(R) Atom(TM) N450)&lt;br /&gt;
** 1008HA ([http://forum.meego.com/showthread.php?p=1330#post1330 well tested])&lt;br /&gt;
* Dell&lt;br /&gt;
** Latitude 2100 (including optional touchscreen)&lt;br /&gt;
** Inspiron Mini 9 ([http://forum.meego.com/showthread.php?t=287 some issues])&lt;br /&gt;
** Vostro A90 (same issues as Mini 9)&lt;br /&gt;
* HP&lt;br /&gt;
** Mini 210 1022eo ([http://forum.meego.com/showthread.php?t=328 Broadcom WiFi needs to be compiled separately])&lt;br /&gt;
** Mini 5101 HD ([http://forum.meego.com/showthread.php?t=328 Broadcom WiFi needs to be compiled separately])&lt;br /&gt;
* Medion Akoya Mini E1210&lt;br /&gt;
*[[wikipedia:MSI_Wind_Netbook|MSI Wind]]&lt;br /&gt;
** U130&lt;br /&gt;
* Samsung&lt;br /&gt;
** N140&lt;br /&gt;
** [[wikipedia:Samsung NC10|NC10]]&lt;br /&gt;
* [[wikipedia:VAIO|Sony VAIO]]&lt;br /&gt;
** VPCW211AX (Intel(R) Atom(TM) N450)&lt;br /&gt;
** VGN-TX3XP (Intel(R) Core(R) Solo(R) 1.2GHz, Intel 945GMS video card)&lt;br /&gt;
* Toshiba Mini&lt;br /&gt;
** NB205&lt;br /&gt;
** NB305&lt;br /&gt;
&lt;br /&gt;
===Nettops===&lt;br /&gt;
*Acer&lt;br /&gt;
**[[wikipedia:Acer Aspire Revo|Revo]] GN40 &lt;br /&gt;
**eMachine EZ1601 and KAV60&lt;br /&gt;
*Asus&lt;br /&gt;
**[[wikipedia:ASUS Eee Box|Eeebox]] B202 &lt;br /&gt;
**[[wikipedia:ASUS Eee Top|Eeetop]] ET1602 &lt;br /&gt;
*[[wikipedia:Micro-Star International|MSI]]&lt;br /&gt;
**AE1900&lt;br /&gt;
*Samsung&lt;br /&gt;
**[[wikipedia:Samsung N130|n130]]&lt;br /&gt;
&lt;br /&gt;
===Notebooks===&lt;br /&gt;
* Asus F2F (Celeron M)&lt;br /&gt;
* Dell Inspiron 1525 (without wireless networking) [http://forum.meego.com/showthread.php?t=371]&lt;br /&gt;
* Dell Latitude D630 (Broadcomm [http://slaine.org/_slaine/Meego_1.0_Wifi.html] wifi driver needed)&lt;br /&gt;
* Lenovo IdeaPad Y450 [http://forum.meego.com/showthread.php?t=265]&lt;br /&gt;
* Lenovo T60 / T61 [http://forum.meego.com/showthread.php?t=323]&lt;br /&gt;
* Lenovo ThinkPad R500 [http://forum.meego.com/showthread.php?t=371]&lt;br /&gt;
* Toshiba L500 Satellite low-end Notebook (needs rtl8192se driver from RealTek for wireless)&lt;br /&gt;
&lt;br /&gt;
===other===&lt;br /&gt;
*[[wikipedia:Beagle Board|Beagle Board]], see [[ARM/Meego on the Beagle]]* &lt;br /&gt;
* O2 Joggler with GMA500 and touchscreen [http://www.youtube.com/watch?v=eUiSnITKeRY] - Initial Testing&lt;br /&gt;
&lt;br /&gt;
==Known problems==&lt;br /&gt;
*Netbooks requiring GMA500 drivers, see [[wikipedia:Intel GMA#GMA 500 on Linux]] and [[wikipedia:Poulsbo_(chipset)#Linux_support]]&lt;br /&gt;
** [http://en.wikipedia.org/wiki/Nokia_Booklet_3G Nokia Booklet 3G]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule</id>
		<title>MeeGo-Meeting IRC Schedule</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule"/>
				<updated>2010-05-27T12:03:29Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* June Schedule */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To avoid meeting conflicts in [http://meego.com/community/irc-channel #meego-meeting], please add your meeting here with date and UTC time until we have a more robust solution.&lt;br /&gt;
&lt;br /&gt;
== Regular Meetings ==&lt;br /&gt;
* [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]: The 1st and 3rd Tuesday alternating between 14:00 and 19:00 UTC&lt;br /&gt;
* [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]: Every other Wednesday at 19:00 UTC&lt;br /&gt;
&lt;br /&gt;
== May Schedule ==&lt;br /&gt;
* May 18, 14:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]&lt;br /&gt;
* May 20, 06:00 UTC: [http://wiki.meego.com/ARM/N900#2010-05-20 Nokia N900 Hardware Adaptation Team Meeting]&lt;br /&gt;
* May 24, 06:00 UTC: [http://wiki.meego.com/ARM/N900 Nokia N900 Hardware Adaptation Team Meeting]&lt;br /&gt;
* May 25, 06:00 UTC: [http://wiki.meego.com/ARM/N900 Nokia N900 Hardware Adaptation Team Meeting]&lt;br /&gt;
* May 26, 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;br /&gt;
&lt;br /&gt;
== June Schedule ==&lt;br /&gt;
* June 1, 19:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]&lt;br /&gt;
* June 2, 17:30 UTC: [http://wiki.meego.com/Community_Application_Support Community Applications Team Meeting]&lt;br /&gt;
* June 2, 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;br /&gt;
* June 3, 14:00 UTC: [http://wiki.meego.com/L10n_meeting_schedule L10N Meeting Schedule]&lt;br /&gt;
* June 15, 14:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]&lt;br /&gt;
* June 16, 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;br /&gt;
* June 30, 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-05-26T09:35:36Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Current status (18.5.2010) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status (25.5.2010) ===&lt;br /&gt;
&lt;br /&gt;
No change in the last week, waiting for hardware.&lt;br /&gt;
&lt;br /&gt;
In the mean time David (lbt) and Niels (X-Fade) have set up an OBS instance in the old maemo.org hardware. This will speed up deployment once the hardware arrives for meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;br /&gt;
&lt;br /&gt;
===Links===&lt;br /&gt;
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-05-18T12:17:56Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Current status (18.5.2010) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status (18.5.2010) ===&lt;br /&gt;
&lt;br /&gt;
Waiting for hardware.&lt;br /&gt;
&lt;br /&gt;
In the mean time David (lbt) and Niels (X-Fade) have set up an OBS instance in the old maemo.org hardware. This will speed up deployment once the hardware arrives for meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-05-18T12:17:33Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Current status (18.5.2010) ===&lt;br /&gt;
&lt;br /&gt;
Waiting for hardware.&lt;br /&gt;
&lt;br /&gt;
In the mean time David (lbt) and Niels (X-Fade) have set up an OBS instance in the old maemo.org hardware. This will speed up deployment once the &lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Talk:ARM/Meego_on_the_Beagle</id>
		<title>Talk:ARM/Meego on the Beagle</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Talk:ARM/Meego_on_the_Beagle"/>
				<updated>2010-05-06T13:15:19Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Created page with 'Thanks! Any chance of getting that three lines of script to keep the watchdog awake on the page?'&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Thanks!&lt;br /&gt;
Any chance of getting that three lines of script to keep the watchdog awake on the page?&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-05-06T12:53:21Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
=== Scope of this work ===&lt;br /&gt;
&lt;br /&gt;
This project is about community built open applications that would be shared through meego.com. The project outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This work is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this project relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What is the community application support ===&lt;br /&gt;
&lt;br /&gt;
==== The technical parts ====&lt;br /&gt;
&lt;br /&gt;
[[File:Community_apps_infra.jpg‎]]&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Automated quality assurance&lt;br /&gt;
&lt;br /&gt;
==== The social side ====&lt;br /&gt;
&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly&lt;br /&gt;
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?&lt;br /&gt;
&lt;br /&gt;
===  How to start ===&lt;br /&gt;
&lt;br /&gt;
Things to do first in parallel:&lt;br /&gt;
* Get hardware&lt;br /&gt;
* Build the clients&lt;br /&gt;
* Practice setting up an OBS instance&lt;br /&gt;
* Agree on the web interface for the client&lt;br /&gt;
* Work out the QA rules&lt;br /&gt;
* Work out the security aspects&lt;br /&gt;
&lt;br /&gt;
Things that need the hardware&lt;br /&gt;
* Setting up the real OBS instance&lt;br /&gt;
* Setting up the repository&lt;br /&gt;
* Setting up the management interfaces&lt;br /&gt;
&lt;br /&gt;
=== People ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
Initially the following people are looking at this:&lt;br /&gt;
* David (lbt) - OBS and repository&lt;br /&gt;
* Niels (X-Fade) - OBS, repository, management tools&lt;br /&gt;
* Bob (bspencer) - client, web interface&lt;br /&gt;
* Daniel (danielwilms) - client, web interface&lt;br /&gt;
* Carsten (Stskeeps) - OBS&lt;br /&gt;
* Mike (mrshaver) - web back-end&lt;br /&gt;
* Tero (tekojo) - co-ordination&lt;br /&gt;
&lt;br /&gt;
=== Servers for the system ===&lt;br /&gt;
&lt;br /&gt;
Some servers have been ordered, and one of those can be used to get this work going.&lt;br /&gt;
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.&lt;br /&gt;
&lt;br /&gt;
ETA for the servers is undefined.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/File:Community_apps_infra.jpg</id>
		<title>File:Community apps infra.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/File:Community_apps_infra.jpg"/>
				<updated>2010-05-06T12:27:44Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Stick figures of community app infra&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Stick figures of community app infra&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Proposal_for_Community_Application_Support</id>
		<title>Proposal for Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Proposal_for_Community_Application_Support"/>
				<updated>2010-05-06T12:26:47Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: moved Proposal for Community Application Support to Community Application Support:&amp;amp;#32;The intention is to use this page to manage the project, not just the proposal&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Community Application Support]]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-05-06T12:26:47Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: moved Proposal for Community Application Support to Community Application Support:&amp;amp;#32;The intention is to use this page to manage the project, not just the proposal&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This proposal is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this proposal ===&lt;br /&gt;
&lt;br /&gt;
This proposal is about community built open applications that would be shared through meego.com. The proposal mainly outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This proposal is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this proposal relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What are the parts that the community application infrastructure consists of ===&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
&lt;br /&gt;
=== Technical resources and how to start ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
The people that are needed are initially available&lt;br /&gt;
* Servers for the system&lt;br /&gt;
Some servers have been ordered, and one could be used for build and repository&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Technical_Steering_Group_meetings</id>
		<title>Technical Steering Group meetings</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Technical_Steering_Group_meetings"/>
				<updated>2010-05-04T13:22:02Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Backlog of Proposed Topics */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Meeting Logistics == &lt;br /&gt;
&lt;br /&gt;
Until further notice, the Technical Steering Group meets every Wednesday at 19:00 UTC for one hour.&lt;br /&gt;
&lt;br /&gt;
All TSG meetings take place in the MeeGo [http://meego.com/community/irc-channel IRC channels]:&lt;br /&gt;
* Main meeting: #meego-meeting (may be moderated)&lt;br /&gt;
* Questions only (during moderated meetings): #meego-meeting-questions &lt;br /&gt;
* Back channel &amp;amp; other discussions (optional): #meego&lt;br /&gt;
&lt;br /&gt;
Minutes and full logs of previous meetings can be found [http://trac.tspre.org/meetbot/meego-meeting/ here].&lt;br /&gt;
&lt;br /&gt;
== Next TSG meeting ==&lt;br /&gt;
Scheduled for [http://timeanddate.com/worldclock/fixedtime.html?day=5&amp;amp;month=5&amp;amp;year=2010&amp;amp;hour=19&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=0 Wednesday, 5 May 2010, 19:00:00 UTC].&lt;br /&gt;
&lt;br /&gt;
'''Agenda'''&lt;br /&gt;
&lt;br /&gt;
* Meeting Process (see below)&lt;br /&gt;
* Introductions &lt;br /&gt;
* MeeGo Project Structure and Working Groups&lt;br /&gt;
** Type: Status Update and Discussion&lt;br /&gt;
** Owners: Valtteri Halla, Imad Sousou&lt;br /&gt;
* Upcoming Release&lt;br /&gt;
** Status update&lt;br /&gt;
** Owners: Valtteri Halla, Imad Sousou&lt;br /&gt;
* All other business (Open Items and General Questions)&lt;br /&gt;
&lt;br /&gt;
'''Meeting Process'''&lt;br /&gt;
&lt;br /&gt;
We're going to start the meeting as moderated to give the TSG time to provide their updates on a topic, but when we are ready for questions, we'll turn moderation off and open it up for questions and discussion.&lt;br /&gt;
&lt;br /&gt;
Please stay on topic, keep it constructive and give the TSG time to respond before posting new questions (one question at a time, please). All questions should also be prefaced with 'QUESTION:'&lt;br /&gt;
&lt;br /&gt;
== Backlog of Proposed Topics ==&lt;br /&gt;
&lt;br /&gt;
* MeeGo Project Structure / Roles&lt;br /&gt;
** Type: Status Update&lt;br /&gt;
** Owners: Valtteri Halla, Imad Sousou&lt;br /&gt;
&lt;br /&gt;
* Working Groups - General Direction&lt;br /&gt;
** Type: Discussion&lt;br /&gt;
** Owners: Valtteri Halla, Imad Sousou&lt;br /&gt;
&lt;br /&gt;
* Garage / Community Applications (this may be 2 topics)&lt;br /&gt;
** Owners: Bob Spencer (Garage) &amp;amp; Tero Kojo ([[Proposal_for_Community_Application_Support|Community Applications]])&lt;br /&gt;
&lt;br /&gt;
* Can we have information on the existing workgroups withing MeeGo (Netbook, Handheld, In-Vehicle and Connected TV), their membership, and how one can take part, please? - Proposed by: [[User:dneary|dneary]]&lt;br /&gt;
&lt;br /&gt;
== Propose a topic ==&lt;br /&gt;
Follow these instructions and your topic will be addressed in a TSG meeting sooner or later.&lt;br /&gt;
&lt;br /&gt;
* Make sure your topic is on-topic. The TSG meetings handle project-level decisions, nominations, escalated disputes and, in general, anything the dependent teams are not able to solve themselves. Check the [http://meego.com/about/governance MeeGo governance] for more information. &lt;br /&gt;
* Your topic proposed contains a title linking to a relevant page, and the names of the team or individuals proposing that topic, linking to their meego.com pages/profiles.&lt;br /&gt;
* If the topic involves pre-agreements with teams or disputes the TSG needs to resolve, they must be detailed in the page linked.&lt;br /&gt;
* The people behind the proposal need to take part in the TSG meeting. If you can't make it on a certain scheduled meeting please specify.&lt;br /&gt;
&lt;br /&gt;
=== Resolution ===&lt;br /&gt;
* The TSG members pick the topics to be discussed in the next TSG meeting. &lt;br /&gt;
* The agenda is frozen approximately 24h before the meeting. &lt;br /&gt;
* Topics proposed might be addressed through other channels as well, being answered by TSG members through other channels or being forwarded to the right team.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-05-04T13:12:56Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This proposal is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this proposal ===&lt;br /&gt;
&lt;br /&gt;
This proposal is about community built open applications that would be shared through meego.com. The proposal mainly outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This proposal is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this proposal relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What are the parts that the community application infrastructure consists of ===&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
&lt;br /&gt;
=== Technical resources and how to start ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
The people that are needed are initially available&lt;br /&gt;
* Servers for the system&lt;br /&gt;
Some servers have been ordered, and one could be used for build and repository&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Application_Support</id>
		<title>Community Application Support</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Application_Support"/>
				<updated>2010-05-04T12:07:30Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Created page with 'This proposal is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.    === Scope of this proposal ===  This pr…'&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This proposal is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Scope of this proposal ===&lt;br /&gt;
&lt;br /&gt;
This proposal is about community built open applications that would be shared through meego.com. The proposal mainly outlines what services need to be set up for supporting application sharing through meego.com.&lt;br /&gt;
&lt;br /&gt;
This proposal is not about platform development.&lt;br /&gt;
&lt;br /&gt;
The technical parts of this proposal relate to the official MeeGo build and repositories so, that the community build and repository infrastructure load packages form the official side, but do not upload to them.&lt;br /&gt;
&lt;br /&gt;
=== What are the parts that the community application infrastructure consists of ===&lt;br /&gt;
&lt;br /&gt;
* Web front end for developers to upload their applications to&lt;br /&gt;
Later there can be a direct 'upload to service' function in the MeeGo application development IDE.&lt;br /&gt;
* Build server (OBS server), needed for building the applications&lt;br /&gt;
* Repository server, for storing the applications and catering them to the end users&lt;br /&gt;
* The logic for running the build and repository servers&lt;br /&gt;
* End user clients, for the end users of MeeGo devices to get the applications with&lt;br /&gt;
* A web front end to the repository, so that the application lists can also be browsed on the net&lt;br /&gt;
* Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler&lt;br /&gt;
&lt;br /&gt;
=== Technical resources and how to start ===&lt;br /&gt;
&lt;br /&gt;
* The people to implement all the above mentioned parts&lt;br /&gt;
&lt;br /&gt;
* Servers for the system&lt;br /&gt;
Some servers have been ordered, and one could&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Office</id>
		<title>Community Office</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Office"/>
				<updated>2010-04-27T16:02:58Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Web infrastructure */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Mission ==&lt;br /&gt;
&lt;br /&gt;
The Community working group defines the strategy for collaboration tools and processes within the MeeGo project, and observes its implementation.&lt;br /&gt;
&lt;br /&gt;
The main channel of collaboration of this working group is the [http://forum.meego.com/forumdisplay.php?f=5 MeeGo Community Matters forum].&lt;br /&gt;
&lt;br /&gt;
== Structure ==&lt;br /&gt;
'''PROPOSAL'''&lt;br /&gt;
=== Coordination ===&lt;br /&gt;
The goals of the Community working group coordination are:&lt;br /&gt;
&lt;br /&gt;
* Overall guidance on tasks and priorities.&lt;br /&gt;
* Decision-making, when needed.&lt;br /&gt;
* Appointments within the working group.&lt;br /&gt;
* Connection with the MeeGo Technical Steering Group.&lt;br /&gt;
&lt;br /&gt;
The coordinators are appointed by the TSG:&lt;br /&gt;
* [http://meego.com/users/dawnfoster Dawn Foster], since March 24, 2010. ''MeeGo community manager employed by Intel.''&lt;br /&gt;
* [http://meego.com/users/qgil Quim Gil], since March 24, 2010. ''Regular Nokia contact with the Maemo community and other free software projects. Nokia pays me to take care of open source / community matters in meego.com.''&lt;br /&gt;
&lt;br /&gt;
=== Web infrastructure ===&lt;br /&gt;
&lt;br /&gt;
[[Web infrastructure]] coordination: Mike Shaver &amp;amp; Tero Kojo. See [[Single_sign-on]].&lt;br /&gt;
&lt;br /&gt;
* [[meego.com]] team - Coordination: Mike Shaver (sysadmin) &amp;amp; [http://meego.com/users/qgil Quim Gil] (content). Volunteers: . See [[News_and_Planet]].&lt;br /&gt;
* [[Bugzilla]] team - Coordination: [http://meego.com/users/wanshuang Wan Shuang] (sysadmin) &amp;amp; [http://meego.com/users/mshaver Mike Shaver] (content). Volunteers: [http://meego.com/users/lm lm]&lt;br /&gt;
* [[Extras/Downloads]] team - Coordination: Bob Spencer. Volunteers: &lt;br /&gt;
* [[Forum]] team - Coordination: [http://meego.com/users/reggie Reggie Suplido] (sysadmin) &amp;amp; [http://meego.com/users/qgil Quim Gil] (content). See [http://forum.meego.com/showgroups.php forum moderators]. Volunteers: [http://meego.com/users/revdkathy Kathy Smith]&lt;br /&gt;
* [[Gitorious]] team - Coordination: [http://meego.com/users/ibrahim Ibrahim Haddad] (contracts) &amp;amp; [http://meego.com/users/mshaver Mike Shaver] (content). Volunteers: &lt;br /&gt;
* [[IRC]] team - Coordination: [http://meego.com/users/dawnfoster Dawn Foster]. Volunteers: [http://meego.com/users/w00t Robin Burchell], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/termana Bradley Smith/Termana]&lt;br /&gt;
* [[OBS]] team - Coordination: [http://meego.com/users/ibrahim Ibrahim Haddad]. Volunteers: [http://meego.com/users/Jeremiah Jeremiah Foster].&lt;br /&gt;
* [[Mailman]] team - Coordination: [http://meego.com/users/dawnfoster Dawn Foster]. Volunteers:  [http://meego.com/users/lm lm]&lt;br /&gt;
* [[MediaWiki]] team - Coordination: Quim Gil. See [http://wiki.meego.com/index.php?title=Special%3AListUsers&amp;amp;username=&amp;amp;group=sysop&amp;amp;limit=50 wiki administrators]. Volunteers:&lt;br /&gt;
* [[Transifex]] team - Coordination: Dimitris Glezos (sysadmin), Margie Foster (content), [http://meego.com/users/ibrahim Ibrahim Haddad] (Contract). Volunteers:&lt;br /&gt;
&lt;br /&gt;
=== Marketing === &lt;br /&gt;
[[Marketing]] - Coordination: Quim Gil.&lt;br /&gt;
&lt;br /&gt;
* [[Brand and Design]] - Coordination: Claire? '''FIXME'''. Volunteers:  [http://meego.com/users/amfidiusz Adrian Marcinkowski]&lt;br /&gt;
* [[Trademark]] - Coordination: [http://meego.com/users/ibrahim Ibrahim Haddad]. Volunteers: &lt;br /&gt;
* [[Merchandising]] - Coordination: '''FIXME'''. Volunteers: [http://meego.com/users/texrat Randall Arnold/Texrat]&lt;br /&gt;
* [[Campaigns]] team - Coordination: '''FIXME'''. Volunteers:  [http://meego.com/users/freppas Fredrik Öqvist]&lt;br /&gt;
&lt;br /&gt;
=== Events ===&lt;br /&gt;
[[Events]] - Coordination: Dawn Foster.&lt;br /&gt;
&lt;br /&gt;
* [[MeeGo Summit 2010]] - Coordination: Dawn Foster &amp;amp; Quim Gil. Volunteers: [http://meego.com/users/dneary Dave Neary/dneary], [http://meego.com/users/texrat Randall Arnold/Texrat]&lt;br /&gt;
* See also [http://meego.com/community/events other events]&lt;br /&gt;
&lt;br /&gt;
=== Metrics ===&lt;br /&gt;
* [[Metrics]] - Coordination: Dawn Foster. Volunteers: [http://meego.com/users/texrat Randall Arnold/Texrat], [http://meego.com/users/dneary Dave Neary/dneary]&lt;br /&gt;
&lt;br /&gt;
== Process ==&lt;br /&gt;
&lt;br /&gt;
'''PROPOSAL'''&lt;br /&gt;
&lt;br /&gt;
=== Meetings ===&lt;br /&gt;
&lt;br /&gt;
[[Community Working Group Meeting]] logistics for regular weekly (or bi-weekly) meetings for the CWG. Specific meeting details are still TBD.&lt;br /&gt;
&lt;br /&gt;
The purpose of this meeting is to coordinate tasks by moving proposed tasks to committed tasks with clear owners and prioritization. We hope that this meeting will make it easier for us to get more organized about how we accomplish work in the CWG, and avoid the duplicated / wasted effort that we have been seeing at least in these early days of the project while we merge the two communities.&lt;br /&gt;
&lt;br /&gt;
=== Tasks ===&lt;br /&gt;
&lt;br /&gt;
Work and tasks will be broken down into '''Committed Tasks''' and '''Proposed Tasks'''.&lt;br /&gt;
&lt;br /&gt;
Committed tasks will have a clear owner and have been approved in a [[Community Working Group Meeting]]. The list of committed tasks may also include prioritization to make sure that we are working actively on the most important tasks. &lt;br /&gt;
&lt;br /&gt;
Proposed tasks includes all other work that we would someday like to do, but that has not yet been approved by the CWG. If you have a proposed topic that you are ready to start working on, please put together a proposal and request a spot on an upcoming [[Community Working Group Meeting]] agenda.&lt;br /&gt;
&lt;br /&gt;
==== Committed Tasks ====&lt;br /&gt;
&lt;br /&gt;
* Complete the Community WG structure and process with people in charge for each area: [http://meego.com/users/qgil Quim] and [http://meego.com/users/dawnfoster Dawn] - Must&lt;br /&gt;
* [http://wiki.meego.com/Metrics Metrics] - [http://meego.com/users/dawnfoster Dawn] - Must&lt;br /&gt;
* Planning for the [http://wiki.meego.com/MeeGo_Summit_2010 MeeGo Conference]: [http://meego.com/users/qgil Quim] and [http://meego.com/users/dawnfoster Dawn] - Must&lt;br /&gt;
* Decision on MeeGo marketing budget 2010: [http://meego.com/users/qgil Quim] - Should&lt;br /&gt;
* MeeGo presentations, processes and other ''internal'' materials published: [http://meego.com/users/qgil Quim] - Could&lt;br /&gt;
* MeeGo trademark and logo usage guidelines - [http://meego.com/users/ibrahim Ibrahim] - Must&lt;br /&gt;
* License to adopt for MeeGo documentation - [http://meego.com/users/ibrahim Ibrahim] - Must&lt;br /&gt;
* MeeGo Compliance Program at the Linux Foundation - [http://meego.com/users/ibrahim Ibrahim] - Must&lt;br /&gt;
* Article on MeeGo for the Linux Journal - [http://meego.com/users/ibrahim Ibrahim] - Must&lt;br /&gt;
&lt;br /&gt;
==== Proposed Tasks: not committed yet ====&lt;br /&gt;
&lt;br /&gt;
* Defining the basics of the Maemo Conference: core organizers, date, location, audience.&lt;br /&gt;
* Clear landing page for developers visible at meego.com.&lt;br /&gt;
* forum.meego.com released.&lt;br /&gt;
* [http://bugs.meego.com/show_bug.cgi?id=1303 MeeGo brand and trademark guidelines]&lt;br /&gt;
* Community WG way of working.&lt;br /&gt;
* Plan for Extras repository.&lt;br /&gt;
* Web Content team with identified owners.&lt;br /&gt;
* May release marketing campaign.&lt;br /&gt;
* [[News and Planet]]. See the [http://news.meego.nemein.net/ proof-of-concept]&lt;br /&gt;
* Karma decision?&lt;br /&gt;
* [[Single sign-on|SSO]] decision - needs clarification.&lt;br /&gt;
* Mail/Forum integration. See [http://talk.maemo.org/showthread.php?t=28924 maemo.org test].&lt;br /&gt;
* How to handle company endorsements at meego.com.&lt;br /&gt;
* MeeGo job market (not sure this makes sense on it's own - combine with bigger [http://www.linuxfoundation.org/node/5716 Linux Foundation] effort?)&lt;br /&gt;
* MeeGo marketplace (combined with Linux.com market, maybe)&lt;br /&gt;
* Project Management (recommend Bugzilla integration; see [https://wiki.mozilla.org/Bugzilla:Addons#Project_management_software_integration PM Options].&lt;br /&gt;
* MeeGo document templates - priority on OpenOffice.org &amp;amp; MS Office presentation slides.&lt;br /&gt;
* Something along the lines of http://djangopeople.net/ (note that although that implementation has job-market features the idea is to have an easy-access &amp;quot;Who's Who&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
== How to contribute ==&lt;br /&gt;
&lt;br /&gt;
See the Process section above for current approved work and proposed tasks.&lt;br /&gt;
&lt;br /&gt;
=== Contributors looking for a team ===&lt;br /&gt;
&lt;br /&gt;
MeeGo members interested in taking an active role in this working group. Please move your names to the team(s) where you want to contribute regularly. Better to choose one than many.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Jeremiah Jeremiah C. Foster] - maemo.org's current debmaster. Recently I've taken on a role in the [http://genivi.org/ GENIVI Alliance] as Core Integration team lead. I would like to participate actively in helping develop MeeGO, keeping it open with a thriving community.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/xfade Niels Breet] - maemo.org webmaster and long time maemo.org community member. Liberated by Nokia to work on community infra and community repository infrastructure for maemo.org. Interested in doing the same for meego.com.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/lbt David Greaves/lbt] - Mer build guy and maemo.org member. Introduced OBS to Maemo and working on Nokia build infrastructure.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Jaffa Andrew Flegg/Jaffa] - Long term Maemo community member and developer and twice Maemo Community Council member. Interested in bringing the best of the Maemo and Moblin communities together in the nascent MeeGo community and ensuring that cross-community facilitation happens.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/ksanjeet Sanjeet Kumar] Willing to contribute as server admin.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Elliot Elliot Smith/townxelliot] - meego.com websites techie, worked on moblin.org Moblin SDK materials, contributor to Moblin SDK tools. Intel pays me. Can get time to rework content from moblin.org for this site.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/bergie Henri Bergius] - contributor to the [http://bergie.iki.fi/blog/maemo-s_community_involvement_infrastructure_is_what_meego_needs/ maemo.org community infrastructure], behind services like Brainstorm, Karma and Social News. Working on maemo.org projects through Nemein, and interested in doing the same for meego.com&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/amby Gabor Ambrozy/amby] - recently joined maemo.org community member; would like to contribute to transition, community infrastructure and community marketing. Can bring virtual project mgmt and organization transition experience; IT system integration, sw development and learning projects practices. And a lot of end-user enthusiasm ;)&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/lm Lucas Maneos/lm] - member of the maemo.org bugsquad, happy to contribute in any way to the bugzilla transition.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/tekojo Tero Kojo] - One of the Nokia people involved in the Maemo community and maemo.org. My area has been working with the liberated community members and the infrastructure for maemo.org. Interested in making sure that MeeGo.com provides the necessary tools and services to both developers and active users. I work in Nokia Maemo developer platform team as project manager responsible for communities.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/margie Margie Foster] - I am the localization project manager for Moblin and also work on the MeeGo website. I am an Intel employee. I am really looking forward to helping create and maintain a vibrant MeeGo localization community using Transifex.&lt;br /&gt;
[[Category:Community]]&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/revdkathy Kathy Smith] - maemo.org community member, non-technical end user. Special interest in community building, project management and channeling the input of end users.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/qole Qole] - Two-term Maemo Community Council member, enthusiastic hacker and Linux user, primary maintainer of the Easy Debian project, and very active in the Maemo forums. Interested in helping out where I can to make MeeGo have the kind of powerhouse community that has made Maemo so special.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/vdvsx VDVsx] - Maemo Community member and developer, willing to keep helping everybody inside this new community from developers to end users.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member, former Nokia QA engineer for Maemo devices, originator of maemo.org community outreach efforts, maemo.org forum moderator and best practices blogger.  Ready to translate lessons learned from maemo.org to whatever develops here!&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/generalantilles Ryan Abel] - Long-term Maemo Community member and former two-term Maemo Community Council member. Interested in leveraging the strengths of the large maemo.org community into the growing MeeGo community. Also interested in helping to develop strong web infrastructure and tooling.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/mshaver Mike Shaver/mshaver] - Moblin.org webmaster and developer behind the current meego.com site. I am an Intel employee. Would love to see this list of people contributing and directing what we build and support for the meego.com community.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/sulamita Sulamita Garcia] - MeeGo Technical Marketing Engineer. I work at Open Source Technology Center at Intel and I've involved with Moblin from the beginning. I produce documentation, training and support for costumers and developers.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/sjgadsby Stephen Gadsby/sjgadsby] - Maemo community member, poster of weekly Bugzilla activity reports, and forum moderator. Interest in community building and communication channels between users and developers.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/reggie Reggie Suplido] - [http://wiki.maemo.org/Maemo.org_team#Talkmaster maemo.org Talkmaster], primary administrator of [http://talk.maemo.org/ talk.maemo.org]. Founded [http://www.internettablettalk.com/ Internet Tablet Talk] where it's forum later on became talk.maemo.org. Can help run the forums section of MeeGo, or perform integration with talk.maemo.org if the need arises.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/timeless timeless] - regular Nokia Browser contact with the Maemo community, contributor to Maemo, Mer, Mozilla.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/danielwilms danielwilms] - working in Nokia on the maemo.org community developer support. Taking over community tasks, working on documentation and support. Interested in helping out, by working on MeeGo.com services, support developers and users, and documentation.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/th0br0 Andreas Osowski/th0br0] - Interested in helping with infrastructure and community marketing. Currently working in Fedora as Ambassador and packager. ~4 years of C++ experience (with some Qt), RoR and Java experience&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/timsamoff Tim Samoff / timsamoff] - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/gadgety Gadgety] - maemo.org community member, business end user; I'd like to contribute to making the MeeGo community an easy place to join for newbies, fans, enthusiasts and creating a community where everyone feels welcome to contribute regardless of technical skill level&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/mikael Mikael Söderberg/mksoderberg] - I am Chair of the [http://genivi.org/ GENIVI Alliance] Reference System Work Group. I would like to contribute by assisting in development of the MeeGo Platform Infrastructure.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org community developer support with a specific documentation slant. Experienced community development consultant, event organiser &amp;amp; general busybody. I want to make sure that MeeGo makes the right strategic decisions related to transparency and participation guidelines at the project inception to avoid major issues later.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/solt Marcin Sołtysiak/solt] - Open to help with community. Aligned with l10n efforts I would see a place for language/country sub sections. Also, have experience with Midgard. I could help with geek-to-human relations :)&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/vilvo Ville Ilvonen/vilvo] - Nokia's Maemo Test Tools - responsible for advocating and coordinating development of test tools and test automation inside Maemo. Looking forward to continue with MeeGo. I can help with tools contribution and evangelism within this working group. Nokia pays me to spend time with this.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/dannybe Danny Bennett] - maemo.org community member, Nokia application architect for maemo sw. I'm interested in architecture and the technology components that make up the MeeGo distro. This is where and how I can contribute.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/auke Auke Kok] - Intel MeeGo developer, working on releases, fastboot, l10n project.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/glezos Dimitris Glezos] - [http://www.transifex.net/ Transifex] developer, [http://www.indifex.com/ Indifex] employee, working on L10n engineering. I'm interested in developing the L10n infrastructure of MeeGo.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/freppas Fredrik Öqvist] - Swedish/Finnish tech-loving marketing guy currently studying some MBA classes in China. Hoping to add a lot to the marketing and marketing strategy for Meego.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/mitsutaka Mitsutaka Amano] - Moblin community member from Moblin 1.x, [http://git.moblin.org/cgit.cgi/moblin-image-creator Moblin Image Creator] maintainer, MeeGo/Moblin contributor, l10n(Japanese), Japanese evangelist, MIRACLE LINUX CORPORATION.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/gaveen Gaveen Prabhasara / gaveen] - a DevOps guy. Planning to become a Fedora packager soon. FOSS / Linux / Ruby advocate&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/baloo Jamie Bennett] - Ubuntu Mobile developer for Canonical, long-term Maemo user/contributor/promoter looking to help develop, advocate and ensure that the whole mobile ecosphere benefits from the MeeGo initiative.&lt;br /&gt;
&lt;br /&gt;
== History ==&lt;br /&gt;
The creation of the Community working group was approved by the Technical Steering Group on March 24, 2010. See the [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-24-19.58.html meeting minutes] for more details.&lt;br /&gt;
&lt;br /&gt;
There was a first [[Community_website_meeting_2010_2_24|Community website meeting]] on February 24, 2010. &lt;br /&gt;
&lt;br /&gt;
The role of working groups in the MeeGo project are explained at http://meego.com/about/governance.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Metrics</id>
		<title>Metrics</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Metrics"/>
				<updated>2010-03-10T18:47:40Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Server error metrics&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Having good metrics and reporting is important for any community. We'll use this page to start to build out a plan for gathering the right metrics that we can use to report on the health of the community.&lt;br /&gt;
&lt;br /&gt;
== Metrics to capture ==&lt;br /&gt;
&lt;br /&gt;
* Software packaging&lt;br /&gt;
** New packages added to repository&lt;br /&gt;
** Updates to existing packages&lt;br /&gt;
** Number of developers/maintainers uploading packages&lt;br /&gt;
* Server performance metrics&lt;br /&gt;
** Server use levels&lt;br /&gt;
** Network bandwidth&lt;br /&gt;
** Downtime and error reports&lt;br /&gt;
* bugzilla reports (Intel has some of this already from Moblin that we can re-use).&lt;br /&gt;
** New bug reports&lt;br /&gt;
** Fixed bug reports&lt;br /&gt;
** Unfixed closed bugreports (dups, not a bug, etc)&lt;br /&gt;
** Upstreamed bug reports (MeeGo bug matched with upstream bug report)&lt;br /&gt;
* various open source aspects&lt;br /&gt;
** Activity of Intel &amp;amp; Nokia developers vs activity of &amp;quot;NIN&amp;quot; (Not Intel/Nokia) developers&lt;br /&gt;
** Number of NIN committers, number of MeeGo specific modules with NIN committers.&lt;br /&gt;
** Not sure what you might want to quantitatively measure here - qualitative is hard to automate. See Siobhan O'Mahony's reports for Eclipse &amp;amp; various Eclipse Foundation reports for inspiration [[User:Dneary|Dneary]] 10:00, 10 March 2010 (UTC)&lt;br /&gt;
* membership / user accounts&lt;br /&gt;
** member satisfaction&lt;br /&gt;
** member recognition&lt;br /&gt;
** Not sure what you might want to quantitatively measure here - qualitative is hard to automate. [[User:Dneary|Dneary]] 10:00, 10 March 2010 (UTC)&lt;br /&gt;
* mailing list subscriptions / participation&lt;br /&gt;
** Number of subscribers&lt;br /&gt;
** New subscriptions&lt;br /&gt;
** Departing subscribers&lt;br /&gt;
* contributor activity&lt;br /&gt;
** Wiki edits&lt;br /&gt;
** Talk posts&lt;br /&gt;
** Mailing list posts&lt;br /&gt;
** Code commits&lt;br /&gt;
** Bugzilla comments, bugs opened, bugs closed&lt;br /&gt;
* Monitoring (not exactly metrics, but related)&lt;br /&gt;
** Tracking press / blog / analyst mentions (more qualitative data)&lt;br /&gt;
** Dawn is working with Intel to get access to Radian6 for this data and plan to publish the output to the community.&lt;br /&gt;
&lt;br /&gt;
== Points to consider ==&lt;br /&gt;
&lt;br /&gt;
* Reporting solution&lt;br /&gt;
** [http://www.slideshare.net/OpenLogic/open-source-reporting-tool-comparison A comparison of open source solutions]&lt;br /&gt;
* Report sharing methods&lt;br /&gt;
** Dashboard(s) for ongoing data reports (server health, member stats, bugs, app stats, etc) --[[User:Texrat|Texrat]] 18:15, 10 March 2010 (UTC)&lt;br /&gt;
** Voluntary subscriptions (ie, RSS) for periodic public reports --[[User:Texrat|Texrat]] 18:16, 10 March 2010 (UTC)&lt;br /&gt;
* Public vs Private data&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* [http://dash.eclipse.org/dash/commits/web-app/ Eclipse Foundation dashboards]&lt;br /&gt;
* [http://www.artofcommunityonline.org The Art of Community] - Chapter 7: Measuring community&lt;br /&gt;
* [http://www.gitorious.org/mining-tools/gitdm gitdm] - Git data miner&lt;br /&gt;
* [http://www.horsepigcow.com/2007/10/metrics-for-healthy-communities/ Metrics for healthy communities] - Tara Hunt&lt;br /&gt;
* [http://spreadloveproject.pbworks.com/CommunityMeasurements Collection of metrics]&lt;br /&gt;
* [http://tools.libresoft.es/ Tools] for analysing CVS/SVN, mailing lists, social networks and more. Community metrics tools mecca.&lt;br /&gt;
&lt;br /&gt;
== Contributors ==&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Intel's MeeGo community manager. I'm interested in helping out on a variety of community activities. I have past experience managing open source, developer and other types of online communities.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member, former Nokia QA engineer for Maemo devices, Data Analyst and best practices blogger.  Ready to translate lessons learned from maemo.org and employment experience to whatever develops here!&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/dneary Dave Neary/dneary] - Maemo docmaster, free software community &amp;quot;expert&amp;quot; (hate that word).&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_website_meeting_2010_2_24</id>
		<title>Community website meeting 2010 2 24</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_website_meeting_2010_2_24"/>
				<updated>2010-02-24T19:38:00Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Actions to be taken */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Reason for the meeting ===&lt;br /&gt;
&lt;br /&gt;
We need to see what services MeeGo.com needs to run, to be a good home to the MeeGo community. To get the ball rolling we need to see who can do what.&lt;br /&gt;
&lt;br /&gt;
The outcome of this meeting should be an ordered list of things that need to be done to the site and an understanding who can and will do those things.&lt;br /&gt;
&lt;br /&gt;
=== Time and place ===&lt;br /&gt;
&lt;br /&gt;
Time: [http://www.timeanddate.com/worldclock/fixedtime.html?day=24&amp;amp;month=2&amp;amp;year=2010&amp;amp;hour=20&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=0Wednesday 2010-2-24 20:00 (UTC)]&lt;br /&gt;
&lt;br /&gt;
Place: Freenode.net irc channel #meego-meeting&lt;br /&gt;
&lt;br /&gt;
=== Topics to be covered ===&lt;br /&gt;
&lt;br /&gt;
1. List of current, ongoing and potential web services + people with current responsibilities in each service or volunteering to be involved.&lt;br /&gt;
Yes, this can be started already now in the wiki. The more complete the list is before the meeting the less time we need to spend there.&lt;br /&gt;
&lt;br /&gt;
2. Project priorities. What are the services more relevant for MeeGo now, and in which order do we want to prioritize them?&lt;br /&gt;
&lt;br /&gt;
3. Objective of MeeGo community? (-Amby)&lt;br /&gt;
&lt;br /&gt;
=== Decisions ===&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
=== List of services on MeeGo.com ===&lt;br /&gt;
&lt;br /&gt;
At this point first thing is to decide what the services are, and who the people who will take then further are.&lt;br /&gt;
&lt;br /&gt;
Service / persons volunteering&lt;br /&gt;
* Blogs on site / &lt;br /&gt;
* Blog aggregation / &lt;br /&gt;
* Forums / &lt;br /&gt;
* Garage / &lt;br /&gt;
* Bugzilla / &lt;br /&gt;
* Wiki /&lt;br /&gt;
&lt;br /&gt;
== Open issues ==&lt;br /&gt;
&lt;br /&gt;
(suggested to keep a list for open issues, where the solution actions are not fully defined - Amby)&lt;br /&gt;
&lt;br /&gt;
[[Category:Community]]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_website_meeting_2010_2_24</id>
		<title>Community website meeting 2010 2 24</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_website_meeting_2010_2_24"/>
				<updated>2010-02-22T11:00:04Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Reason for the meeting ===&lt;br /&gt;
&lt;br /&gt;
We need to see what services MeeGo.com needs to run, to be a good home to the MeeGo community. To get the ball rolling we need to see who can do what.&lt;br /&gt;
&lt;br /&gt;
The outcome of this meeting should be an ordered list of things that need to be done to the site and an understanding who can and will do those things.&lt;br /&gt;
&lt;br /&gt;
=== Time and place ===&lt;br /&gt;
&lt;br /&gt;
Time: Wednesday 2010-2-24 20:00 (UTC) -&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Place: Freenode.net irc channel #meego-meeting&lt;br /&gt;
&lt;br /&gt;
=== Topics to be covered ===&lt;br /&gt;
&lt;br /&gt;
1. List of current, ongoing and potential web services + people with current responsibilities in each service or volunteering to be involved.&lt;br /&gt;
Yes, this can be started already now in the wiki. The more complete the list is before the meeting the less time we need to spend there.&lt;br /&gt;
&lt;br /&gt;
2. Project priorities. What are the services more relevant for MeeGo now, and in which order do we want to prioritize them?&lt;br /&gt;
&lt;br /&gt;
=== Decisions ===&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
=== Actions to be taken ===&lt;br /&gt;
&lt;br /&gt;
Action/person&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Community]]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Office</id>
		<title>Community Office</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Office"/>
				<updated>2010-02-22T10:59:07Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Updated the irc meeting link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The role of MeeGo working groups are explained at http://meego.com/about/governance&lt;br /&gt;
&lt;br /&gt;
This is a request to the Technical Steering Group to approve the creation of a Community working group. There is no procedure defined but we can can improvise with some common sense.&lt;br /&gt;
&lt;br /&gt;
To discuss and plan the MeeGo community, subscribe to the MeeGo community mailing list: http://lists.meego.com/listinfo/meego-community. You can also subscribe from your account page on meego.com.&lt;br /&gt;
&lt;br /&gt;
There is an upcoming meeting on http://meego.com/community/irc-channel as well. The scheduled time is Wednesday, February 24th 2010 at 20:00 UTC. Please note that the channel chosen for this meeting is #meego-meeting. An agenda for the meeting is here: [http://wiki.meego.com/Community_website_meeting_2010_2_24 meeting agenda]&lt;br /&gt;
&lt;br /&gt;
=== Mission ===&lt;br /&gt;
The Community working group defines the strategy for collaboration tools and processes within the MeeGo project, and observes its implementation.&lt;br /&gt;
&lt;br /&gt;
=== Areas ===&lt;br /&gt;
The main areas within the scope of the working group are (in no particular order):&lt;br /&gt;
&lt;br /&gt;
* '''Maemo/Moblin transition''': bringing the best from maemo.org and moblin.org to meego.com (urgent now, until the mission here is fulfilled).&lt;br /&gt;
* '''Web administration''': server maintenance, team of admins and other users with special permissions.&lt;br /&gt;
* '''Platform infrastructure''': selection and administration of online tools for collaborative software development: build infrastructure, code repositories, bugzilla, localization...&lt;br /&gt;
* '''Community infrastructure''': selection and administration of online tools for non-technical community collaboration: planet, wiki, forum, brainstorm, downloads...&lt;br /&gt;
* '''Community marketing''': merchandising, events, evangelism...&lt;br /&gt;
&lt;br /&gt;
=== Contributors ===&lt;br /&gt;
MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/qgil Quim Gil] - regular Nokia contact with the Maemo community, and maemo.org contributor myself. One of the people responsible of the maemo.org transition from Nokia's hands to a fully community-driven site. Submitter of this proposal and happy to take an active role. Full disclosure: Nokia pays me to take care of open source / community matters in maemo.org and now meego.com. I can put time here.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Jeremiah Jeremiah C. Foster] - maemo.org's current debmaster. Recently I've taken on a role in the [http://genivi.org/ GenIVI Alliance] as Core Integration team lead. I would like to participate actively in helping develop MeeGO, keeping it open with a thriving community.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/xfade Niels Breet] - maemo.org webmaster and long time maemo.org community member. Liberated by Nokia to work on community infra and community repository infrastructure for maemo.org. Interested in doing the same for meego.com.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/lbt David Greaves/lbt] - Mer build guy and maemo.org member. Introduced OBS to Maemo and working on Nokia build infrastructure.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Jaffa Andrew Flegg/Jaffa] - Long term Maemo community member and developer and twice Maemo Community Council member. Interested in bringing the best of the Maemo and Moblin communities together in the nascent MeeGo community and ensuring that cross-community facilitation happens.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/ksanjeet Sanjeet Kumar] Willing to contribute as server admin.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Elliot Elliot Smith/townxelliot] - meego.com websites techie, worked on moblin.org Moblin SDK materials, contributor to Moblin SDK tools. Intel pays me. Can get time to rework content from moblin.org for this site.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/bergie Henri Bergius] - contributor to the maemo.org community infrastructure, behind services like Brainstorm, Karma and Social News. Working on maemo.org projects through Nemein, and interested in doing the same for meego.com&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/amby Gabor Ambrozy/amby] - recently joined maemo.org community member; would like to contribute to transition, community infrastructure and community marketing. Can bring virtual project mgmt and organization transition experience; IT system integration, sw development and learning projects practices. And a lot of end-user enthusiasm ;)&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/lm Lucas Maneos/lm] - member of the maemo.org bugsquad, happy to contribute in any way to the bugzilla transition.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/tekojo Tero Kojo] - One of the Nokia people involved in the Maemo community and maemo.org. My area has been working with the liberated community members and the infrastructure for maemo.org. Interested in making sure that MeeGo.com provides the necessary tools and services to both developers and active users. I work in Nokia Maemo developer platform team as project manager responsible for communities.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/margie Margie Foster] - I am the localization project manager for Moblin and also work on the MeeGo website. I am an Intel employee. I am really looking forward to helping create and maintain a vibrant MeeGo localization community using Transifex.&lt;br /&gt;
[[Category:Community]]&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/revdkathy Kathy Smith] - maemo.org community member, non-technical end user. Special interest in community building, project management and channeling the input of end users.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/w00t Robin Burchell] - maemo fan as of n900, wide variety of technical skills from C++ (yes, including Qt)/PHP to server administration. happy to help the community, however I can.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/qole Qole] - Two-term Maemo Community Council member, enthusiastic hacker and Linux user, primary maintainer of the Easy Debian project, and very active in the Maemo forums. Interested in helping out where I can to make MeeGo have the kind of powerhouse community that has made Maemo so special.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/vdvsx VDVsx] - Maemo Community Council member and developer, willing to keep helping everybody inside this new community from developers to end users.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/texrat Randall Arnold] - Maemo Community Council member, former Nokia QA engineer for Maemo devices, originator of maemo.org community outreach efforts, maemo.org forum moderator and best practices blogger.  Ready to translate lessons learned from maemo.org to whatever develops here!&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/generalantilles Ryan Abel] - Long-term Maemo Community member and former two-term Maemo Community Council member. Interested in leveraging the strengths of the large maemo.org community into the growing MeeGo community. Also interested in helping to develop strong web infrastructure and tooling.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/mshaver Mike Shaver/mshaver] - Moblin.org webmaster and developer behind the current meego.com site. I am an Intel employee. Would love to see this list of people contributing and directing what we build and support for the meego.com community.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/sulamita Sulamita Garcia] - MeeGo Technical Marketing Engineer. I work at Open Source Technology Center at Intel and I've involved with Moblin from the beginning. I produce documentation, training and support for costumers and developers.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/sjgadsby Stephen Gadsby/sjgadsby] - Maemo community member, poster of weekly Bugzilla activity reports, and forum moderator. Interest in community building and communication channels between users and developers.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/reggie Reggie Suplido] - [http://wiki.maemo.org/Maemo.org_team#Talkmaster maemo.org Talkmaster], primary administrator of [http://talk.maemo.org/ talk.maemo.org]. Founded [http://www.internettablettalk.com/ Internet Tablet Talk] where it's forum later on became talk.maemo.org. Can help run the forums section of MeeGo, or perform integration with talk.maemo.org if the need arises.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/timeless timeless] - regular Nokia Browser contact with the Maemo community, contributor to Maemo, Mer, Mozilla.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/danielwilms danielwilms] - working in Nokia on the maemo.org community developer support. Taking over community tasks, working on documentation and support. Interested in helping out, by working on MeeGo.com services, support developers and users, and documentation.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/th0br0 Andreas Osowski/th0br0] - Interested in helping with infrastructure and community marketing. Currently working in Fedora as Ambassador and packager. ~4 years of C++ experience (with some Qt), RoR and Java experience&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/niqt Nicola De Filippo] - maemo Qt4 contributor; technical skills: Qt (from 1997), C++, Javascript, Php, Java, Python&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/timsamoff Tim Samoff / timsamoff] - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/gadgety Gadgety] - maemo.org community member, business end user; I'd like to contribute to making the MeeGo community an easy place to join for newbies, fans, enthusiasts and creating a community where everyone feels welcome to contribute regardless of technical skill level&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/mikael Mikael Söderberg] - I am Chair of the [http://genivi.org/ GenIVI Alliance] Reference System Work Group. I would like to contribute by assisting in development of the MeeGo Platform Infrastructure.&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_website_meeting_2010_2_24</id>
		<title>Community website meeting 2010 2 24</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_website_meeting_2010_2_24"/>
				<updated>2010-02-22T10:56:39Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Category: Community&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Reason for the meeting ===&lt;br /&gt;
&lt;br /&gt;
We need to see what services MeeGo.com needs to run, to be a good home to the MeeGo community. To get the ball rolling we need to see who can do what.&lt;br /&gt;
&lt;br /&gt;
The outcome of this meeting should be an ordered list of things that need to be done to the site and an understanding who can and will do those things.&lt;br /&gt;
&lt;br /&gt;
=== Time and place ===&lt;br /&gt;
&lt;br /&gt;
Time: Wednesday 2010-2-24 20:00 (UTC) -&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Place: Freenode.net irc channel #meego-meeting&lt;br /&gt;
&lt;br /&gt;
=== Topics to be covered ===&lt;br /&gt;
&lt;br /&gt;
* Access to the site: who can do what&lt;br /&gt;
* What services are to be run:&lt;br /&gt;
** What is the overall set of services&lt;br /&gt;
** What are the basic assumptions (SSO, ...)&lt;br /&gt;
** What should it look like from an architecture point of view&lt;br /&gt;
** How to make it future-proof&lt;br /&gt;
** What is the priority order for things&lt;br /&gt;
* Service administration: who has the right to do what&lt;br /&gt;
* Bugzilla: what does it contain, which products, components and so forth&lt;br /&gt;
* Wiki: access, structure and gardeners&lt;br /&gt;
* Planet/Blogs: How to do the aggregation&lt;br /&gt;
* Bulletin board: what, how and what is the relation to talk.maemo.org&lt;br /&gt;
* The OBS build infra, is there a direct link to the site&lt;br /&gt;
* Repositories, there is a working group, but here we need to see what is the relation&lt;br /&gt;
* Other services that are needed&lt;br /&gt;
&lt;br /&gt;
=== Decisions ===&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
=== Actions to be taken ===&lt;br /&gt;
&lt;br /&gt;
Action/person&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Community]]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_website_meeting_2010_2_24</id>
		<title>Community website meeting 2010 2 24</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_website_meeting_2010_2_24"/>
				<updated>2010-02-22T10:55:39Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Reason for the meeting ===&lt;br /&gt;
&lt;br /&gt;
We need to see what services MeeGo.com needs to run, to be a good home to the MeeGo community. To get the ball rolling we need to see who can do what.&lt;br /&gt;
&lt;br /&gt;
The outcome of this meeting should be an ordered list of things that need to be done to the site and an understanding who can and will do those things.&lt;br /&gt;
&lt;br /&gt;
=== Time and place ===&lt;br /&gt;
&lt;br /&gt;
Time: Wednesday 2010-2-24 20:00 (UTC) -&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Place: Freenode.net irc channel #meego-meeting&lt;br /&gt;
&lt;br /&gt;
=== Topics to be covered ===&lt;br /&gt;
&lt;br /&gt;
* Access to the site: who can do what&lt;br /&gt;
* What services are to be run:&lt;br /&gt;
** What is the overall set of services&lt;br /&gt;
** What are the basic assumptions (SSO, ...)&lt;br /&gt;
** What should it look like from an architecture point of view&lt;br /&gt;
** How to make it future-proof&lt;br /&gt;
** What is the priority order for things&lt;br /&gt;
* Service administration: who has the right to do what&lt;br /&gt;
* Bugzilla: what does it contain, which products, components and so forth&lt;br /&gt;
* Wiki: access, structure and gardeners&lt;br /&gt;
* Planet/Blogs: How to do the aggregation&lt;br /&gt;
* Bulletin board: what, how and what is the relation to talk.maemo.org&lt;br /&gt;
* The OBS build infra, is there a direct link to the site&lt;br /&gt;
* Repositories, there is a working group, but here we need to see what is the relation&lt;br /&gt;
* Other services that are needed&lt;br /&gt;
&lt;br /&gt;
=== Decisions ===&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
=== Actions to be taken ===&lt;br /&gt;
&lt;br /&gt;
Action/person&lt;br /&gt;
*&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_website_meeting_2010_2_24</id>
		<title>Community website meeting 2010 2 24</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_website_meeting_2010_2_24"/>
				<updated>2010-02-22T10:50:51Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Page started&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Topics to be covered ===&lt;br /&gt;
&lt;br /&gt;
* Access to the site: who can do what&lt;br /&gt;
* What services are to be run:&lt;br /&gt;
** What is the overall set of services&lt;br /&gt;
** What are the basic assumptions (SSO, ...)&lt;br /&gt;
** What should it look like from an architecture point of view&lt;br /&gt;
** How to make it future-proof&lt;br /&gt;
** What is the priority order for things&lt;br /&gt;
* Service administration: who has the right to do what&lt;br /&gt;
* Bugzilla: what does it contain, which products, components and so forth&lt;br /&gt;
* Wiki: access, structure and gardeners&lt;br /&gt;
* Planet/Blogs: How to do the aggregation&lt;br /&gt;
* Bulletin board: what, how and what is the relation to talk.maemo.org&lt;br /&gt;
* The OBS build infra, is there a direct link to the site&lt;br /&gt;
* Repositories, there is a working group, but here we need to see what is the relation&lt;br /&gt;
* Other services that are needed&lt;br /&gt;
&lt;br /&gt;
=== Decisions ===&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
=== Actions to be taken ===&lt;br /&gt;
&lt;br /&gt;
Action/person&lt;br /&gt;
*&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Who%27s_who</id>
		<title>Who's who</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Who%27s_who"/>
				<updated>2010-02-19T08:53:30Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Maemo community stakeholders */  Changed my title a bit&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Technical Steering Group ==&lt;br /&gt;
''Members of the [http://meego.com/about/governance TSG]''&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/imad Imad Sousou/imad] - benevolent dictator&lt;br /&gt;
* [http://meego.com/users/valhalla Valtteri Halla] - benevolent dictator&lt;br /&gt;
* ???&lt;br /&gt;
&lt;br /&gt;
== Maemo community stakeholders ==&lt;br /&gt;
'' Official representatives of the Maemo community''&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/qgil Quim Gil/qgil] - Nokia's Maemo Community Manager&lt;br /&gt;
* [http://meego.com/users/tekojo Tero Kojo/tekojo] - Nokia's Maemo Technical Project Manager&lt;br /&gt;
* [http://meego.com/users/xfade Niels Breet/X-Fade] - maemo.org webmaster&lt;br /&gt;
* Dave Neary/dneary - maemo.org docmaster&lt;br /&gt;
* [http://meego.com/users/andre André Klapper/andre_] - maemo.org bugmaster&lt;br /&gt;
* [http://meego.com/users/jeremiah Jeremiah Foster/jeremiah] - maemo.org debmaster &lt;br /&gt;
* [http://meego.com/users/reggie Reggie Suplido] - maemo.org talkmaster&lt;br /&gt;
* [http://meego.com/users/stskeeps Carsten Munk/Stskeeps] - maemo.org distmaster &amp;amp; Mer project lead&lt;br /&gt;
* [http://meego.com/users/bergie Henri Bergius/bergie] - maemo.org web/Midgard developer&lt;br /&gt;
* [http://meego.com/users/vdvsx Valerio Valerio/VDVsx] - Maemo Community Council chair&lt;br /&gt;
* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member&lt;br /&gt;
* [http://meego.com/users/qole Alan Bruce/qole] - Maemo Community Council member&lt;br /&gt;
* [http://meego.com/users/penguinbait Matthew Lewis/penguinbait] - Maemo Community Council member&lt;br /&gt;
* Graham Cobb - Maemo Commnunity Council member&lt;br /&gt;
&lt;br /&gt;
== Moblin community stakeholders ==&lt;br /&gt;
''Representatives of the Moblin community''&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/dirkhh Dirk Hohndel/dirkhh], chief Linux and open source technologist at Intel&lt;br /&gt;
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - moblin.org &amp;amp; meego.com website techy&lt;br /&gt;
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - moblin.org webmaster &amp;amp; meego.com website developer&lt;br /&gt;
* [http://meego.com/users/margie Margie Foster/mlfoster] - localization project manager for Moblin &amp;amp; meego.com website developer&lt;br /&gt;
&lt;br /&gt;
== MeeGo developers ==&lt;br /&gt;
'' People paid to contribute to MeeGo and/or have commit rights''&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/nashif Anas Nashif/anaZ] - Random developer&lt;br /&gt;
* [http://meego.com/users/hbons Hylke Bons/hbons] - User Experience Designer&lt;br /&gt;
* [http://meego.com/users/auke Auke Kok/auke] - developer&lt;br /&gt;
* [http://meego.com/users/jku Jussi Kukkonen/jku] - developer&lt;br /&gt;
* [http://meego.com/users/quang Quang Pham/quang] - developer&lt;br /&gt;
&lt;br /&gt;
== MeeGo community ==&lt;br /&gt;
''Anyone not in the above sections''&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/jaffa Andrew Flegg/Jaffa] - long term gadget freak &amp;amp; Maemo community member&lt;br /&gt;
* [http://meego.com/users/generalantilles Ryan Abel/GeneralAntilles] - long term Maemo community member&lt;br /&gt;
* [http://meego.com/users/lbt David Greaves/lbt] - Mer OBS build guy.&lt;br /&gt;
* [http://meego.com/users/zerojay Jason Carter/zerojay] - long term Maemo community member&lt;br /&gt;
* [http://meego.com/users/debernardis Ernesto de Bernardis/debernardis] - Maemo community member, mobile device tinkerer&lt;br /&gt;
* [http://meego.com/users/timeless timeless/timeless] - Mozilla contributor, Nokia employee.&lt;br /&gt;
* [http://meego.com/users/lpotter Lorn Potter/lpotter/ljp] - QDF, Mobility, Nokia,&lt;br /&gt;
* [http://meego.com/users/corsac Yves-Alexis Perez / Corsac] - Debian developer, Maemo community member, security engineer&lt;br /&gt;
* [http://borasky-research.net M. Edward (Ed) Borasky] - Linux capacity planning / audio / openSUSE / Twitter geek&lt;br /&gt;
__NOTOC__ &amp;lt;!-- disable the table of contents from ever being shown --&amp;gt;&lt;br /&gt;
[[Category:Community]]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Packaging</id>
		<title>Packaging</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Packaging"/>
				<updated>2010-02-19T06:55:00Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Removed RPM vs. Deb part, what is necessary is said in the first section of this page. If you want to discuss use the discussion pages&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Creating Packages for MeeGo =&lt;br /&gt;
&lt;br /&gt;
The build infrastructure is not announced yet, so information here is speculative.&lt;br /&gt;
&lt;br /&gt;
What is known:&lt;br /&gt;
&lt;br /&gt;
*The package format used by MeeGo is RPM.&lt;br /&gt;
&lt;br /&gt;
* MeeGo build tools and Infrastructure will probably derive from Moblin's (see [http://moblin.org/documentation/moblin-distro-developers-guide/moblin-infrastructure] and [http://moblin.org/documentation/moblin-distro-developers-guide/build-system]) with hopefully better support for ARM targets.&lt;br /&gt;
&lt;br /&gt;
* MeeGo uses [[Build_System| openSUSE Build Services (OBS)]].&lt;br /&gt;
&lt;br /&gt;
= Upstream =&lt;br /&gt;
&lt;br /&gt;
As Maemo has had an old version of Debian as an upstream distribution, there have been lots of questions on what will be MeeGo's upstream, and why Maemo's relationship with Debian will be dropped. The answer is that MeeGo is an independent distribution : the only upstream is the projects included into MeeGo such as : kernel.org, X.org, Qt, etc. MeeGo policy is to push all bug fixes to upstream projects.&lt;br /&gt;
&lt;br /&gt;
Why not be Debian-based ? Having an upstream distribution has advantages and disadvantages.&lt;br /&gt;
Advantages : you benefit from all the packaging, QA and maintenance done in the upstream distribution, thus there is a large selection of available ported software.&lt;br /&gt;
Disadvantages : you have to align your build infrastructure with your upstream. You are dependent on the release cycle and architecture choices of upstream.&lt;br /&gt;
&lt;br /&gt;
The choice is to have no upstream for MeeGo. It makes it easier to tailor MeeGo for its target devices, which is quite specific compared to Debian's. Maybe the Debian rhythm of updates would also be inadequate for MeeGo (smartphone OSs are currently evolving at a very rapid pace, but there is more up-to-date Ubuntu and Debian is working on more frequent updates). The Moblin build tools would also not have been compatible with Debian as upstream (this is mostly nonsense, see Mer and OBS). Nonetheless MeeGo will be Linux Standard Base (LSB) compliant and its specific components will probably be available in Debian at some point.&lt;br /&gt;
&lt;br /&gt;
= Packaging Guidelines =&lt;br /&gt;
&lt;br /&gt;
Evolving [[Packaging/Guidelines|packaging guidelines]]...&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
*[http://lists.meego.com/pipermail/meego-dev MeeGo-dev mailing list]&lt;br /&gt;
*[http://www.allmeegodevices.com/2010/02/17/meego-a-whole-new-linux-ballgame/ A nice article about why no upsteam - Meego Devices]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Talk:Packaging</id>
		<title>Talk:Packaging</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Talk:Packaging"/>
				<updated>2010-02-18T11:36:50Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: Created page with 'Could this page be moved to another location? Right now if I come and read the wiki, it says:  Developer documentation  - Packing  So I think to myself: &amp;quot;great, this will tell me…'&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Could this page be moved to another location?&lt;br /&gt;
Right now if I come and read the wiki, it says:&lt;br /&gt;
 Developer documentation&lt;br /&gt;
 - Packing&lt;br /&gt;
&lt;br /&gt;
So I think to myself: &amp;quot;great, this will tell me how to package my app for Meego&amp;quot;&lt;br /&gt;
Which the page doesn't.&lt;br /&gt;
&lt;br /&gt;
tekojo&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	<entry>
		<id>http://wiki.meego.com/Community_Office</id>
		<title>Community Office</title>
		<link rel="alternate" type="text/html" href="http://wiki.meego.com/Community_Office"/>
				<updated>2010-02-16T16:10:57Z</updated>
		
		<summary type="html">&lt;p&gt;Tekojo: /* Contributors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The role of MeeGo working groups are explained at http://meego.com/about/governance&lt;br /&gt;
&lt;br /&gt;
This is a request to the Technical Steering Group to approve the creation of a Community working group. There is no procedure defined but we can can improvise with some common sense:&lt;br /&gt;
&lt;br /&gt;
=== Mission ===&lt;br /&gt;
The Community working group defines the strategy for collaboration tools and processes within the MeeGo project, and observes its implementation.&lt;br /&gt;
&lt;br /&gt;
=== Areas ===&lt;br /&gt;
The main areas within the scope of the working group are (in no particular order):&lt;br /&gt;
&lt;br /&gt;
* '''Maemo/Moblin transition''': bringing the best from maemo.org and moblin.org to meego.com (urgent now, until the mission here is fulfilled).&lt;br /&gt;
* '''Web administration''': server maintenance, team of admins and other users with special permissions.&lt;br /&gt;
* '''Platform infrastructure''': selection and administration of online tools for collaborative software development: build infrastructure, code repositories, bugzilla, localization...&lt;br /&gt;
* '''Community infrastructure''': selection and administration of online tools for non-technical community collaboration: planet, wiki, forum, brainstorm, downloads...&lt;br /&gt;
* '''Community marketing''': merchandising, events, evangelism...&lt;br /&gt;
&lt;br /&gt;
=== Contributors ===&lt;br /&gt;
MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/qgil Quim Gil] - regular Nokia contact with the Maemo community, and maemo.org contributor myself. One of the people responsible of the maemo.org transition from Nokia's hands to a fully community-driven site. Submitter of this proposal and happy to take an active role. Full disclosure: Nokia pays me to take care of open source / community matters in maemo.org and now meego.com. I can put time here.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Jeremiah Jeremiah C. Foster] - maemo.org's current debmaster. Recently I've taken on a role in the [http://genivi.org/ GenIVI consortium] as Core Integration team lead. I would like to participate actively in helping develop MeeGO, keeping it open with a thriving community.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/xfade Niels Breet] - maemo.org webmaster and long time maemo.org community member. Liberated by Nokia to work on community infra and community repository infrastructure for maemo.org. Interested in doing the same for meego.com.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/lbt David Greaves/lbt] - Mer build guy and maemo.org member. Introduced OBS to Maemo and working on Nokia build infrastructure.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/Jaffa Andrew Flegg/Jaffa] - Long term Maemo community member and developer and twice Maemo Community Council member. Interested in bringing the best of the Maemo and Moblin communities together in the nascent MeeGo community and ensuring that cross-community facilitation happens.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/ksanjeet Sanjeet Kumar] Willing to contribute as server admin.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/elliot Elliot Smith/townxelliot] - meego.com websites techie, worked on moblin.org Moblin SDK materials, contributor to Moblin SDK tools. Intel pays me.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/bergie Henri Bergius] - contributor to the maemo.org community infrastructure, behind services like Brainstorm, Karma and Social News. Working on maemo.org projects through Nemein, and interested in doing the same for meego.com&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/amby Gabor Ambrozy/amby] - recently joined maemo.org community member; would like to contribute to transition, community infrastructure and community marketing. Can bring virtual project mgmt and organization transition experience; IT system integration, sw development and learning projects practices. And a lot of end-user enthusiasm ;)&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/lm Lucas Maneos/lm] - member of the maemo.org bugsquad, happy to contribute in any way to the bugzilla transition.&lt;br /&gt;
&lt;br /&gt;
* [http://meego.com/users/tekojo Tero Kojo] - One of the Nokia people involved in the Maemo community and maemo.org. My area has been working with the liberated community members and the infrastructure for maemo.org. Interested in making sure that MeeGo.com provides the necessary tools and services to both developers and active users. I work in Nokia Maemo developer platform team as project manager responsible for communities.&lt;br /&gt;
&lt;br /&gt;
[[Category:Community]]&lt;/div&gt;</summary>
		<author><name>Tekojo</name></author>	</entry>

	</feed>