Meego Wiki
Views

Community Application Support

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
m
(added disclaimer about content)
 
(7 intermediate revisions not shown)
Line 1: Line 1:
 +
'''IMPORTANT - this page to be updated or merged with or as a subpage under [[MeeGo Apps]]''' - please move or delete the content and redirect the page.
 +
This project is about enabling the community to create open applications and share them through a channel that is hosted in meego.com.
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 ===
=== Current status ===
 +
As of mid January
 +
 +
* Apps to come online for testing at [http://apps-beta.meego.com/ apps-beta] January/February
* Community OBS is in limited testing. Request for access from X-Fade or lbt on #meego on Freenode  
* 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
+
* BOSS to be used as the management system for the apps/repos - needs some work still to get stabilised and ready for use
-
* OCS interface defined
+
* OCS interface defined - done
* End-user clients are there in gitorious under the name garage-client
* End-user clients are there in gitorious under the name garage-client
-
* Work on OCS server interface commencing in week 48
+
* Work on OCS server interface commencing in week 48 - still ongoing
 +
 
 +
[http://www.qaiku.com/channels/show/MeeGork/ The stream where the developers have documented progress] and
 +
[http://www.qaiku.com/channels/show/MeeGork/view/d2703a0e135711e0a24633013e50078e078e/ latest comment in the Qaiku workstream by Ferenc]
=== Current tasks that need to be taken ===
=== Current tasks that need to be taken ===
Line 15: Line 23:
=== Requirements ===
=== Requirements ===
-
=== Current status  ===
 
-
 
-
OBS up and running.
 
-
Authentication and authorization is an issue.
 
-
 
-
Web end needs work (short on people to do it)
 
-
 
-
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]
 
=== Scope of this work ===
=== Scope of this work ===
Line 38: Line 38:
[[File:Community_apps_infra.jpg‎]]
[[File:Community_apps_infra.jpg‎]]
-
* Web front end for developers to upload their applications to
+
* 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.
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
* Build server (OBS server), needed for building the applications
* Repository server, for storing the applications and catering them to the end users
* Repository server, for storing the applications and catering them to the end users
-
* The logic for running the build and repository servers
+
* 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
* End user clients, for the end users of MeeGo devices to get the applications with
-
* A web front end to the repository, so that the application lists can also be browsed on the net
+
* A web front end to the repository called 'Apps', so that the application lists can also be browsed on the net
-
* Automated quality assurance
+
* Automated and manual quality assurance
 +
 
 +
[http://static.qaiku.com/d30/350/f4f/d30350f4fef911dfb46fb5ad123b10f010f0.png?t=1291393478 Mock-up of Apps page] running in a test environment.
==== The social side ====
==== The social side ====
Line 52: Line 54:
* The way to manage how applications flow to the final repository from the initial build repository - not everything goes to end users directly
* 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?
* Managing the users - is it completely free for all anonymous users or is there some form of user management in place?
-
 
-
===  How to start ===
 
-
 
-
Things to do first in parallel:
 
-
* Get hardware
 
-
* Build the clients
 
-
* Practice setting up an OBS instance
 
-
* Agree on the web interface for the client
 
-
* Work out the QA rules
 
-
* Work out the security aspects
 
-
 
-
Things that need the hardware
 
-
* Setting up the real OBS instance
 
-
* Setting up the repository
 
-
* Setting up the management interfaces
 
=== People ===
=== People ===
Line 80: Line 67:
* Tero (tekojo) - co-ordination
* Tero (tekojo) - co-ordination
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI
* Jeremiah Foster - observer of the process, considering both client implementation and / or OBS instances with repos for GENIVI
 +
* Henri (bergie) - OCS, web interface
-
=== Servers for the system ===
+
===Links===
 +
* Discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]
 +
* Community Applications repository sprint in November 2010: [http://lists.meego.com/pipermail/meego-community/2010-November/002526.html]
-
Some servers have been ordered, and one of those can be used to get this work going.
+
=== Old log  ===
-
Additional hardware is being bought now, so that we have a sensible level of hardware to go on.
+
-
ETA for the servers is undefined.
+
[http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-02-17.33.log.html Raw meeting log from 2.6.2010]
-
 
+
-
===Links===
+
-
*discussion about above in forum: [http://forum.meego.com/showthread.php?t=135]
+

Latest revision as of 19:07, 2 June 2011

IMPORTANT - this page to be updated or merged with or as a subpage under MeeGo Apps - please move or delete the content and redirect the page.

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

Contents

Current status

As of mid January

  • Apps to come online for testing at apps-beta January/February
  • 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 - needs some work still to get stabilised and ready for use
  • OCS interface defined - done
  • End-user clients are there in gitorious under the name garage-client
  • Work on OCS server interface commencing in week 48 - still ongoing

The stream where the developers have documented progress and latest comment in the Qaiku workstream by Ferenc

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

Community apps infra.jpg

  • 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

Retrieved from "http://wiki.meego.com/Community_Application_Support"
Personal tools