Community Application Support

Revision as of 08:39, 18 January 2011

This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.

Current status

• Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode
• BOSS to be used as the management system for the apps/repos
• OCS interface defined
• End-user clients are there in gitorious under the name garage-client
• Work on OCS server interface commencing in week 48

Current tasks that need to be taken

• The rules for moving packages to and from testing

Requirements

Scope of this work

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.

This work is not about platform development.

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.

What is the community application support

The technical parts

• Application submission can be handled in the OBS client

Later there can be a direct 'upload to service' function in the MeeGo application development IDE.

• Build server (OBS server), needed for building the applications
• Repository server, for storing the applications and catering them to the end users
• BOSS, the logic for running the build and repository servers
• End user clients, for the end users of MeeGo devices to get the applications with
• A web front end to the repository called 'Apps', so that the application lists can also be browsed on the net
• Automated and manual quality assurance

Mock-up of Apps page running in a test environment.

The social side

• Quality assurance process, initially this most likely will be human testing, but automated tools would make it much faster and simpler
• The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly
• Managing the users - is it completely free for all anonymous users or is there some form of user management in place?

People

• The people to implement all the above mentioned parts

Initially the following people are looking at this:

• David (lbt) - OBS and repository
• Niels (X-Fade) - OBS, repository, management tools
• Bob (bspencer) - client, web interface
• Daniel (danielwilms) - client, web interface
• Carsten (Stskeeps) - OBS
• Mike (mrshaver) - web back-end
• Tero (tekojo) - co-ordination
• Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI
• Henri (bergie) - OCS, web interface

Links

• Discussion about above in forum: [1]
• Community Applications repository sprint in November 2010: [2]

Old log

Raw meeting log from 2.6.2010