Revision as of 00:08, 10 October 2011 (view source) Feri (Talk | contribs) (→Accessing Apps) ← Older edit		Revision as of 00:11, 10 October 2011 (view source) Feri (Talk | contribs) (→Community Apps Team) Newer edit →
Line 22:		Line 22:
	= Community Apps Team =		= Community Apps Team =
-	* Lead Developer: Niels Breet
	* Client Application: Martin Grimme		* Client Application: Martin Grimme
-	* Web Site: Ferenc Szekely	+	* Web Site: Niels Breet, Henri Bergius, Ferenc Szekely
-	* OCS Interface: Henri Bergius	+	* OCS Interface: Niels Breet, Henri Bergius, Ferenc Szekely
-	* Build Service: David Greaves	+	* Build Service: Niels Breet, David Greaves
		+	* Graphics, design: Istvan Jozsa
	== Community Apps Volunteer Team ==		== Community Apps Volunteer Team ==

---

Revision as of 00:11, 10 October 2011

MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the Community Office. The LF have refused to allow 'apps' in the meego.com namespace; the problem statement tries to explain more.

Contents 1 Accessing Apps 2 Process 2.1 Supporting Process References 3 Community Apps Team 3.1 Community Apps Volunteer Team 3.2 Team Communication Channels 4 Plans and Schedule

Accessing Apps

• Apps for MeeGo web interface
• Open Collaboration Services (OCS) API provider file for Apps
• Client code in Gitorious
• Server code on GitHub

Process

A developer will need to request access to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.

Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package. The Apps-testing repository is intended for stability testing and community QA. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

Supporting Process References

• Getting access to the Community OBS
• Packaging Guidelines
• QA Process
• Repository layout description

Community Apps Team

• Client Application: Martin Grimme
• Web Site: Niels Breet, Henri Bergius, Ferenc Szekely
• OCS Interface: Niels Breet, Henri Bergius, Ferenc Szekely
• Build Service: Niels Breet, David Greaves
• Graphics, design: Istvan Jozsa

Community Apps Volunteer Team

• Graphics: Tim Samoff

Team Communication Channels

• Use the MeeGo-Community Mailing List for questions and discussion.
• File bugs in the Community Apps Component
• Ask questions in the #meego IRC Channel

Plans and Schedule

Working on:

W26:

• Automatic import/delete packages in MeeGo Apps by BOSS participant signaling (niels)
• OCS interface additions: commenting and voting (ferenc/henri)
• List apps in testing queue (ferenc)
• QA result signaling to BOSS (niels/david)
• Configure Apps build targets in OBS, cleanup old build targets (niels)
• Document Apps submit process (niels)

Open issues (help appreciated):

Documentation:

• Document QA process

Design:

• Front page design (Mike?/Tim)
• Icons for App categories