MeeGo wiki - User contributions [en]

MeeGo Conference Spring 2011/Volunteering

2011-05-04T16:54:00Z

Mshaver:

Your help is needed to make the MeeGo Conference 2011 a success! Please fill in your name for any of the 2 hour needed slots.

We need volunteers in the following roles:

; Conference Setup/Cleanup
: Setting up banners, installing wires, tables, chairs, ensuring that the conference hall is looking great for the early arrivals on Monday morning; and then packing everything up again on Wednesday evening. Lots of hands needed!
; Info Desk
: We need volunteers to take a couple of hours out of their conference to ensure that people know what's going on, give directions to newcomers, help co-ordinate with the conference staff when small issues arise.
; Session Tech Support
: Work with the conference center audio/visual staff, ensure that speakers are wired up with mics, that video is working, that presenters have the technical assistance they need (for example, if they need to play audio).
; Speaker Assistants
: Co-ordinate with speakers, organise a signal to let them know when they are running out of time, introduce them before their presentation, and handle audience questions on their behalf.
; Live Stream IRC Moderators
: Sit on IRC and ensure everything stays clean and on-topic. Be op for an hour! - Contact Stskeeps on IRC (#meego , irc.freenode.net) once signed up. If you have a mobile device with WiFi and a capable IRC client, that's all you need during the shift (and a watchful eye on the IRC channel)
; Hacking Lounge
: We need a volunteer to supervise the hacking lounge schedule outside conference hours, if people want to get together for a hackfest.
; Other
: You'd like to help, but don't want to do any of the tasks above, or can't decide? Add your name here, and we will put you to use somewhere!

X = needs a volunteer

{| class="wikitable" cellpadding="5" cellspacing="0" border="1"
|- style="background:LightGrey"
! Day/Time
! Conference Setup/Cleanup
! Info Desk
! Session Tech Support
! Speaker Assistants Need one per track, except for keynote track
! Live Stream IRC Moderators Needs 1 during live streaming talks
! Hacking Lounge Needs 1 outside conference hours
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday May 21
|-
| May 13, 13:00-15:00
|
|
|
|
|
|
|
|-
| May 21, 15:00-17:00
|
|
|
|
|
|
|
|-
| May 21, 17:00-19:00
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Sunday May 22
|-
| May 22, 9:00-11:00
|
|
|
|
|
|
|
|-
| May 22, 11:00-13:00
|
|
|
|
|
|
|
|-
| May 22, 13:00-15:00
| NONE Needed:
|
|
|
|
|
|-
| May 22, 15:00-17:00
| NONE Needed:
|
|
|
|
|
|-
| May 22, 19:00- 21:00
| Needed: 5
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday May 23
|-
| May 23, 8:00-10:00
|
| Needed: 2 
| X
|
| X
|
|
|-
| May 23, 10:00-12:00
|
|Needed: 2 
| X
|
|
|
|
|-
| May 23, 12:00-14:00
|
| Needed: 2
| X
| Needed: 4 
| X
|
|
|-
| May 23, 14:00-16:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 23, 16:00-18:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|- style="background:LightBlue"
|colspan="9"| Tuesday May 24
|-
| May 24, 8:00-10:00
|
| Needed: 2 
| X
| Needed: 4
| X
|
|
|-
| May 24, 10:00-12:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 24, 12:00-14:00
|
| Needed: 2 
| X
| Needed: 4 
| X
| X
|
|-
| May 24, 14:00-16:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 24, 16:00-18:00
|
| Needed: 2 
| X
| Needed: 4
| X
|
|
|-
| May 24, 18:00-19:00
|
|
|
|
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday May 25
|-
| May 25, 8:00-10:00
|
| Needed: 2
| X
| Needed: 2 
| X
|
|
|-
| May 25, 10:00-12:00
|
| Needed: 2
| X
| Needed: 2 
|
| X
|
|-
| May 25, 12:00-14:00
|
| Needed: 2
| X
| Needed: 2 
|
| X
|
|-
| May 25, 14:00-16:00
| All hands on deck 
| Needed: 2 
| X
| X
|
| X
|
|}

MeeGo Conference Spring 2011/Volunteering

2011-05-04T16:52:57Z

Mshaver:

Your help is needed to make the MeeGo Conference 2011 a success! Please fill in your name for any of the 2 hour needed slots.

We need volunteers in the following roles:

; Conference Setup/Cleanup
: Setting up banners, installing wires, tables, chairs, ensuring that the conference hall is looking great for the early arrivals on Monday morning; and then packing everything up again on Wednesday evening. Lots of hands needed!
; Info Desk
: We need volunteers to take a couple of hours out of their conference to ensure that people know what's going on, give directions to newcomers, help co-ordinate with the conference staff when small issues arise.
; Session Tech Support
: Work with the conference center audio/visual staff, ensure that speakers are wired up with mics, that video is working, that presenters have the technical assistance they need (for example, if they need to play audio).
; Speaker Assistants
: Co-ordinate with speakers, organise a signal to let them know when they are running out of time, introduce them before their presentation, and handle audience questions on their behalf.
; Live Stream IRC Moderators
: Sit on IRC and ensure everything stays clean and on-topic. Be op for an hour! - Contact Stskeeps on IRC (#meego , irc.freenode.net) once signed up. If you have a mobile device with WiFi and a capable IRC client, that's all you need during the shift (and a watchful eye on the IRC channel)
; Hacking Lounge
: We need a volunteer to supervise the hacking lounge schedule outside conference hours, if people want to get together for a hackfest.
; Other
: You'd like to help, but don't want to do any of the tasks above, or can't decide? Add your name here, and we will put you to use somewhere!

X = needs a volunteer

{| class="wikitable" cellpadding="5" cellspacing="0" border="1"
|- style="background:LightGrey"
! Day/Time
! Conference Setup/Cleanup
! Info Desk Needs 2 all the time on 15th & 16th
! Session Tech Support
! Speaker Assistants Need one per track, except for keynote track
! Live Stream IRC Moderators Needs 1 during live streaming talks
! Hacking Lounge Needs 1 outside conference hours
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday May 21
|-
| May 13, 13:00-15:00
|
|
|
|
|
|
|
|-
| May 21, 15:00-17:00
|
|
|
|
|
|
|
|-
| May 21, 17:00-19:00
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Sunday May 22
|-
| May 22, 9:00-11:00
|
|
|
|
|
|
|
|-
| May 22, 11:00-13:00
|
|
|
|
|
|
|
|-
| May 22, 13:00-15:00
| NONE Needed:
|
|
|
|
|
|-
| May 22, 15:00-17:00
| NONE Needed:
|
|
|
|
|
|-
| May 22, 19:00- 21:00
| Needed: 5
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday May 23
|-
| May 23, 8:00-10:00
|
| Needed: 2 
| X
|
| X
|
|
|-
| May 23, 10:00-12:00
|
|Needed: 2 
| X
|
|
|
|
|-
| May 23, 12:00-14:00
|
| Needed: 2
| X
| Needed: 4 
| X
|
|
|-
| May 23, 14:00-16:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 23, 16:00-18:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|- style="background:LightBlue"
|colspan="9"| Tuesday May 24
|-
| May 24, 8:00-10:00
|
| Needed: 2 
| X
| Needed: 4
| X
|
|
|-
| May 24, 10:00-12:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 24, 12:00-14:00
|
| Needed: 2 
| X
| Needed: 4 
| X
| X
|
|-
| May 24, 14:00-16:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 24, 16:00-18:00
|
| Needed: 2 
| X
| Needed: 4
| X
|
|
|-
| May 24, 18:00-19:00
|
|
|
|
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday May 25
|-
| May 25, 8:00-10:00
|
| Needed: 2
| X
| Needed: 2 
| X
|
|
|-
| May 25, 10:00-12:00
|
| Needed: 2
| X
| Needed: 2 
|
| X
|
|-
| May 25, 12:00-14:00
|
| Needed: 2
| X
| Needed: 2 
|
| X
|
|-
| May 25, 14:00-16:00
| All hands on deck 
| Needed: 2 
| X
| X
|
| X
|
|}

MeeGo Conference Spring 2011/Volunteering

2011-05-04T16:37:14Z

Mshaver:

Your help is needed to make the MeeGo Conference 2011 a success! Please fill in your name for any of the 2 hour needed slots.

We need volunteers in the following roles:

; Conference Setup/Cleanup
: Setting up banners, installing wires, tables, chairs, ensuring that the conference hall is looking great for the early arrivals on Monday morning; and then packing everything up again on Wednesday evening. Lots of hands needed!
; Info Desk
: We need volunteers to take a couple of hours out of their conference to ensure that people know what's going on, give directions to newcomers, help co-ordinate with the conference staff when small issues arise.
; Session Tech Support
: Work with the conference center audio/visual staff, ensure that speakers are wired up with mics, that video is working, that presenters have the technical assistance they need (for example, if they need to play audio).
; Speaker Assistants
: Co-ordinate with speakers, organise a signal to let them know when they are running out of time, introduce them before their presentation, and handle audience questions on their behalf.
; Live Stream IRC Moderators
: Sit on IRC and ensure everything stays clean and on-topic. Be op for an hour! - Contact Stskeeps on IRC (#meego , irc.freenode.net) once signed up. If you have a mobile device with WiFi and a capable IRC client, that's all you need during the shift (and a watchful eye on the IRC channel)
; Hacking Lounge
: We need a volunteer to supervise the hacking lounge schedule outside conference hours, if people want to get together for a hackfest. (I don't really understand what is involved here --[[User:Dneary|Dneary]] 09:44, 9 November 2010 (UTC))
; Other
: You'd like to help, but don't want to do any of the tasks above, or can't decide? Add your name here, and we will put you to use somewhere!

X = needs a volunteer

{| class="wikitable" cellpadding="5" cellspacing="0" border="1"
|- style="background:LightGrey"
! Day/Time
! Conference Setup/Cleanup
! Info Desk Needs 2 all the time on 15th & 16th
! Session Tech Support
! Speaker Assistants Need one per track, except for keynote track
! Live Stream IRC Moderators Needs 1 during live streaming talks
! Hacking Lounge Needs 1 outside conference hours
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday May 21
|-
| May 13, 13:00-15:00
|
|
|
|
|
|
|
|-
| May 21, 15:00-17:00
|
|
|
|
|
|
|
|-
| May 21, 17:00-19:00
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Sunday May 22
|-
| May 22, 9:00-11:00
|
|
|
|
|
|
|
|-
| May 22, 11:00-13:00
|
|
|
|
|
|
|
|-
| May 22, 13:00-15:00
| NONE Needed:
|
|
|
|
|
|-
| May 22, 15:00-17:00
| NONE Needed:
|
|
|
|
|
|-
| May 22, 19:00- 21:00
| Needed: 5
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday May 23
|-
| May 23, 8:00-10:00
|
| Needed: 2 
| X
|
| X
|
|
|-
| May 23, 10:00-12:00
|
|Needed: 2 
| X
|
|
|
|
|-
| May 23, 12:00-14:00
|
| Needed: 2
| X
| Needed: 4 
| X
|
|
|-
| May 23, 14:00-16:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 23, 16:00-18:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|- style="background:LightBlue"
|colspan="9"| Tuesday May 24
|-
| May 24, 8:00-10:00
|
| Needed: 2 
| X
| Needed: 4
| X
|
|
|-
| May 24, 10:00-12:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 24, 12:00-14:00
|
| Needed: 2 
| X
| Needed: 4 
| X
| X
|
|-
| May 24, 14:00-16:00
|
| Needed: 2 
| X
| Needed: 4 
| X
|
|
|-
| May 24, 16:00-18:00
|
| Needed: 2 
| X
| Needed: 4
| X
|
|
|-
| May 24, 18:00-19:00
|
|
|
|
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday May 25
|-
| May 25, 8:00-10:00
|
| Needed: 2
| X
| Needed: 2 
| X
|
|
|-
| May 25, 10:00-12:00
|
| Needed: 2
| X
| Needed: 2 
|
| X
|
|-
| May 25, 12:00-14:00
|
| Needed: 2
| X
| Needed: 2 
|
| X
|
|-
| May 25, 14:00-16:00
| All hands on deck 
| Needed: 2 
| X
| X
|
| X
|
|}

MeeGo Conference Spring 2011/Volunteering

2011-05-04T16:29:59Z

Mshaver: Created page with "Your help is needed to make the MeeGo Conference 2011 a success! Please fill in your name for any of the 2 hour needed slots. We need volunteers in the following roles: ; Conf..."

Your help is needed to make the MeeGo Conference 2011 a success! Please fill in your name for any of the 2 hour needed slots.

We need volunteers in the following roles:

; Conference Setup/Cleanup
: Setting up banners, installing wires, tables, chairs, ensuring that the conference hall is looking great for the early arrivals on Monday morning; and then packing everything up again on Wednesday evening. Lots of hands needed!
; Info Desk
: We need volunteers to take a couple of hours out of their conference to ensure that people know what's going on, give directions to newcomers, help co-ordinate with the conference staff when small issues arise.
; Session Tech Support
: Work with the conference center audio/visual staff, ensure that speakers are wired up with mics, that video is working, that presenters have the technical assistance they need (for example, if they need to play audio).
; Speaker Assistants
: Co-ordinate with speakers, organise a signal to let them know when they are running out of time, introduce them before their presentation, and handle audience questions on their behalf.
; Live Stream IRC Moderators
: Sit on IRC and ensure everything stays clean and on-topic. Be op for an hour! - Contact Stskeeps on IRC (#meego , irc.freenode.net) once signed up. If you have a mobile device with WiFi and a capable IRC client, that's all you need during the shift (and a watchful eye on the IRC channel)
; Hacking Lounge
: We need a volunteer to supervise the hacking lounge schedule outside conference hours, if people want to get together for a hackfest. (I don't really understand what is involved here --[[User:Dneary|Dneary]] 09:44, 9 November 2010 (UTC))
; Other
: You'd like to help, but don't want to do any of the tasks above, or can't decide? Add your name here, and we will put you to use somewhere!

X = needs a volunteer

{| class="wikitable" cellpadding="5" cellspacing="0" border="1"
|- style="background:LightGrey"
! Day/Time
! Conference Setup/Cleanup
! Info Desk Needs 2 all the time on 15th & 16th
! Session Tech Support
! Speaker Assistants Need one per track, except for keynote track
! Live Stream IRC Moderators Needs 1 during live streaming talks
! Hacking Lounge Needs 1 outside conference hours
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday Nov 13
|-
| Nov 13, 13:00-15:00
|
| [[User:macron | Ronan Mac Laverty]]
|
|
|
|
|
|-
| Nov 13, 15:00-17:00
|
|
|
|
|
|
|
|-
| Nov 13, 17:00-19:00
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Sunday Nov 14
|-
| Nov 14, 9:00-11:00
|
|
|
|
|
|
|
|-
| Nov 14, 11:00-13:00
|
|
|
|
|
|
|
|-
| Nov 14, 13:00-15:00
| NONE Needed:
|
|
|
|
|
|-
| Nov 14, 15:00-17:00
| NONE Needed:
|
|
|
|
|
|-
| Nov 14, 19:00- 21:00
| Needed: 5
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday Nov 15
|-
| Nov 15, 8:00-10:00
|
| Needed: 2 [[User:Jsmanrique| Manrique López]] Iñigo Gonzalez
| X
| Quim Gil
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 10:00-12:00
|
|Needed: 2 [[User:RevdKathy| Kathy Smith]] [[User:ymb |Mike Bradshaw]] 
| X
| [[User:Msinternet | Martin Saunders]]
| [[User:Netvandal | Michele Tameni]]
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 12:00-14:00
|
| Needed: 2
| X
| Needed: 4 [[User:mdamt | mdamt]] (preferably President then 1872 room) [[User:Chippy |Chippy]] 
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 14:00-16:00
|
| Needed: 2 [[User:frethop| Mike Jipping]]
| X
| Needed: 4 [[User:Vdvsx | Valerio Valerio]] [[User:Chippy |Chippy]]
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 16:00-18:00
|
| Needed: 2 [[User:timsamoff | timsamoff]] [[User:RevdKathy| Kathy Smith]]
| X
| Needed: 4 Daniel Wilms
| X
| [[User:Leinir | Dan Leinir ]]
|
|- style="background:LightBlue"
|colspan="9"| Tuesday Nov 16
|-
| Nov 16, 8:00-10:00
|
| Needed: 2 [[User:Jsmanrique | Manrique Lopez]] Iñigo Gonzalez
| X
| Needed: 4
| X
|
|
|-
| Nov 16, 10:00-12:00
|
| Needed: 2 [[User:ymb |Mike Bradshaw]] [[User:jnwi |Jens Wiik]]
| X
| Needed: 4 [[User:Vdvsx | Valerio Valerio]]
| X
|
|
|-
| Nov 16, 12:00-14:00
|
| Needed: 2 [[User:RevdKathy| Kathy Smith]] [[User:nitingarg | Nitin Garg]]
| X
| Needed: 4 [[User:Chippy |Chippy]]
| X
| X
|
|-
| Nov 16, 14:00-16:00
|
| Needed: 2 [[User:ymb |Mike Bradshaw]] [[User:frethop |Mike Jipping]]
| X
| Needed: 4 [[User:Chippy |Chippy]]
| X
|
|
|-
| Nov 16, 16:00-18:00
|
| Needed: 2 [[User:timsamoff | timsamoff]] [[User:jnwi |Jens Wiik]]
| X
| Needed: 4
| X
|
|
|-
| Nov 16, 18:00-19:00
|
|
|
|
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday Nov 17
|-
| Nov 17, 8:00-10:00
|
| Needed: 2
| X
| Needed: 2 [[User:Dneary | Dave Neary]]
| X
|
|
|-
| Nov 17, 10:00-12:00
|
| Needed: 2
| X [[User:Saviq | Michał Sawicz]]
| Needed: 2 [[User: Chippy | Chippy]]
|
| X
|
|-
| Nov 17, 12:00-14:00
|
| Needed: 2
| X
| Needed: 2 [[User:Chippy |Chippy]]
|
| X
|
|-
| Nov 17, 14:00-16:00
| All hands on deck [[User:Chippy |Chippy]] Quim Gil [[User:macron | Ronan Mac Laverty]] [[User:ymb |Mike Bradshaw]] 
| Needed: 2 
| X
| X
|
| X
|
|}

File:MeeGoIntegrationFlow.JPG

2011-04-15T19:59:29Z

Mshaver: uploaded a new version of "File:MeeGoIntegrationFlow.JPG"

Description of stages between developer and MeeGo Trunk

File:WeeklyReleaseCycle.png

2011-04-15T19:58:48Z

Mshaver: uploaded a new version of "File:WeeklyReleaseCycle.png"

Weekly Cycle

File:Meego-mollom-spam.png

2011-04-08T15:28:01Z

Mshaver:

MeeGo Conference Spring 2011

2011-04-04T18:13:18Z

Mshaver: /* Organizing Committee */

The main Conference site is: [http://sf2011.meego.com/ San Francisco Meego Conference 2011]

== Logistics ==
May 23 - 25: San Francisco Regency Hyatt
* Annual industry event
* Announcements / Information focus
* Broader industry audience
* Call for Proposals and Registration will open early February

== Organizing Committee ==
[[File:Organizing committee.pdf]]

'''Team Lead: Amy Leeland'''

Advisory and Community Interface:
* Dawn Foster - Community Management
* Quim Gil - Marketing Management

Program Committee:
* Lead: Dirk Hohndel
* Carsten Munk
* Thiago Maciera
* Ashley Walker (Speaker Management)

Coordination:
* Lead: Brian Warner Sponsorships
* AJ Reed: Post Event management
* Mike Shaver: Web Management
* Dave Neary: Early Bird Events

== Call for proposals ==

* [http://sf2011.meego.com/program/call-session-proposals CfP]
* [[MeeGo Conference Spring 2011/CfP Drafting|Draft CfP]]

== Hyatt Space details==

Link to conference area map:[http://sanfranciscoregency.hyatt.com/hyatt/images/hotels/sfors/floorplan.pdf]

'''2nd Floor ''Street Level'' entrance'''
*Grand Ballroom A+B+C will be used as our Keynote room with redundant Screens/Sound in Market Street Foyer and Grand Ballroom Foyer (Seats 1300, with 100 standing in lobby spaces and feeds coming out)
Breakouts and room descriptions as follows:
*1 Grand Ballroom A (700 theater)
*2 Grand Ballroom B (200 cab)
*3 Grand Ballroom C (200 cab)
*Tech Showcase will take place in Market Street Foyer and Grand Ballroom Foyer. Not to be just single table tops, requested 3 different orientations to choose from. Tea and Coffee will be available in Tech showcase area
*Registration + Welcome Kit fulfillment: Market Street Foyer and Grand Ballroom Foyer. Kits will be organized based upon gender/size, not name
*Media/Blogger Room: Regency A
*Keynote Prep Room: Regency B
*Event Office: Plaza Room

'''3rd floor ''Bay Level'''''
*4 Seacliff A-B (110 cab)
*5 Seacliff C-D (110 cab)
*6 Bayview Room A-B (200 cab)
*Platinum Meeting Rooms: Marina Room and Golden Gate room on Bay Level

'''4th floor ''Atrium Lobby Level'''''
*All Catering Breakfast, Lunch, breaks and receptions will be held in Atrium of Hotel
This includes Garden Room A+B, 13 Views Lounge, and Hospitality Room can seat up to 1400 in this area.
*Nokia Boardroom: Boardroom A [atrium]
*Intel Boardroom: Boardroom B [atrium]

'''1st Floor ''Pacific Concourse Level'''''
*This will all be used as Early Bird space partitioned rooms A-O (17,000 sq ft all partitionable) Saturday until Sunday evening then it will be………
*Hacker Lounge: Pacific Concourse K—O
*Meeting rooms partitioned in Pacific Concourse: A, B, C, D, E
*Gold sponsors get A and B
*Spaces F and G will be used as a meeting room bookable space

== MeeGo Conference Warm-Up ==

The MeeGo Conference Warm-Up will include workshops catering to MeeGo application developers, and tutorials to help people get started developing for the platform. We also plan to have some fun extra-curricular activities involving building things. The warm-up sessions will be held at the Hyatt in San Francisco (the conference hotel/ conference facility).

We will have two tutorial sessions, and an application development workshop, running in parallel. Among the topics we are planning to have hands-on tutorials for are:

* Using OBS
* MeeGo developer tools
* Qt, QML and QtQuick development
* Developing, testing and deploying MeeGo software with the MeeGo SDK

Because of space and equipment constraints, attendance for some of the workshops will be limited. As we get more information, we will keep you posted.

We also plan to have application developer workshops on:

* Designing a better user experience
* Building software with Community OBS, and community application distribution

And we plan a fun Maker's Contest where contestants will have to use raw materials including balsa wood, paper clips, string, paper and glue to build a machine capable of launching a projectile (Trebuchet, slingshot, catapult, whatever) over a distance of ~10m. The results will be judged with a live-action Angry Birds contest.

We are still working on the contents of these sessions and who will be leading them. As we get more information, we will pass it on.

== Hacker Lounge ==
Was a very popular activity for community members. Having it stocked with beer and snacks was perfect, and we'd love to do something similar for spring.

== Ideas for fun activities ==
* The [[MeeGo_Conference_2010/Werewolf]] was popular, and we're scheming on some additional [[MeeGo_Conference_Spring_2011/Werewolf]] MeeGo Werewolf variations for 2010.
* During the fun activities of #MeeGoConf 2010, we spoke about the idea of having a full scale game during the conference. The game would involve as many participants as possible and be played from opening to closing of the conference. Based on the "Killer" game, we'll discuss the details on the [[MeeGo_Conference_Spring_2011/Killer]] page.
* Some ideas for the Maker's Contest are a parachute launcher (need to balance heaviness for the way up & lightness for the way down); building a catapult or trebuchet to throw some predefined object, building some kind of Rube Goldberg machine to accomplish an agreed task.
[[File:Example.jpg]]

MeeGo Conference Spring 2011/CfP Drafting

2011-03-22T19:11:38Z

Mshaver:

DRAFT. If you're not a program committee member your changes will be reverted

<pre>
Following up on the success of the Dublin conference, the global developer
community around MeeGo is set to reunite in San Francisco for the MeeGo
Conference Spring 2011.

From application developers to platform designers, hardware vendors
to open source enthusiasts, anyone engaged in MeeGo is invited to
contribute and participate at the San Francisco Regency Hyatt, California, USA, from
May 23rd-25th, 2011.

Much of this event will be the same as in Dublin. There will be MeeGo Warm-Up events on
site the weekend before the conference and there will be lots of time to network and talk
(the ever important "hall-way track"). But there are also a few changes.

The San Francisco conference will be somewhat more focused on the industry and not
just on the developers. And instead of an un-conference day, we will have three days of
scheduled sessions, but will keep 15-20% of the slots open until right before the
conference and even during the conference, to allow scheduling of "Late Breaking News"
sessions, impromptu developer meetings, etc.

We are inviting proposals for presentations in a wide variety of areas:

Device/Product development
- New devices and product development stories
(experiences, process, challenges, differentiation)
- Improvements and developments in MeeGo hardware adaptation
(performance, power, Linux kernel developments, porting process, etc.)
- Information around supported hardware platforms
(tutorials/introductions, improvements/developments, challenges)

App development
- Upcoming and popular Apps
(development stories, sharing experience, etc.)
- MeeGo API and SDK
(tutorials, news, roadmaps, tips and tricks for making great
applications, development tools and helpers)
- Internationalization and Localization
- Design guidelines and User Experience
(different MeeGo verticals, form factors, crossing the boundaries between them,
differentiation)

Platform development
- Current and possible future components within the MeeGo architecture
(status, overview, and roadmap)
- Platform tools and process
(tutorials/introductions, improvements/developments, tips and tricks, etc.)
- Quality Assurance
(methods, tools, tutorials, experiences)

MeeGo project, process, and progress
- Activity reports and roadmaps from various project areas
- Project challenges and discussions on project and process
- Marketing, outreach; engaging companies, governments, and others
- App stores and monetization strategies
- Community building and fostering
- Documentation, artwork, infrastructure

We also welcome submissions on any other MeeGo related topics. Be
creative, the program committee will look at each and every submission, to
create a vibrant and interesting conference. This includes community and
open source related proposals, as well as commercial or proprietary
developments around MeeGo.

Submissions should include:
- Author(s) (including their work affiliation)
- Short BIO (100-150 words, written in 3rd person)
- Short Abstract (120-150 words, crisply defines the topic)
- Abstract (300-500 words, explains the scope of the presentation)
- Preferred session duration (default is 30 minutes + 10 minutes Q&A, but we'll entertain
other requests where possible)

Please also mention if this will include any form of product
presentation. In general, we are not soliciting sales pitches,
but it is ok for technical presentations to refer to (or announce)
MeeGo related products.

If you will need travel support, note this in your submission, also.

To submit a session proposal, either create a meego.com account or
login with your existing meego.com account at http://sf2011.meego.com/user
and create a proposal at http://sf2011.meego.com/node/add/session.
Registration for the conference can be done now or you can wait
until sessions are accepted to find out if you'll be a presenter.

Submissions will be due by 11:59 PM Pacific Time on March 25, 2011.
Around that time, we'll open a second process for lightning
talk submissions.

We expect to have a large subset of the presentations approved and
scheduled by April 4th and are planning to have the final program
ready before April 15th.

The Program Committee

Dirk Hohndel
Thiago Macieira
Carsten Munk

</pre>

MeeGo Conference Spring 2011/CfP Drafting

2011-03-22T19:10:57Z

Mshaver:

DRAFT. If you're not a program committee member your changes will be reverted

<pre>
Following up on the success of the Dublin conference, the global developer
community around MeeGo is set to reunite in San Francisco for the MeeGo
Conference Spring 2011.

From application developers to platform designers, hardware vendors
to open source enthusiasts, anyone engaged in MeeGo is invited to
contribute and participate at the San Francisco Regency Hyatt, California, USA, from
May 23rd-25th, 2011.

Much of this event will be the same as in Dublin. There will be MeeGo Warm-Up events on
site the weekend before the conference and there will be lots of time to network and talk
(the ever important "hall-way track"). But there are also a few changes.

The San Francisco conference will be somewhat more focused on the industry and not
just on the developers. And instead of an un-conference day, we will have three days of
scheduled sessions, but will keep 15-20% of the slots open until right before the
conference and even during the conference, to allow scheduling of "Late Breaking News"
sessions, impromptu developer meetings, etc.

We are inviting proposals for presentations in a wide variety of areas:

Device/Product development
- New devices and product development stories
(experiences, process, challenges, differentiation)
- Improvements and developments in MeeGo hardware adaptation
(performance, power, Linux kernel developments, porting process, etc.)
- Information around supported hardware platforms
(tutorials/introductions, improvements/developments, challenges)

App development
- Upcoming and popular Apps
(development stories, sharing experience, etc.)
- MeeGo API and SDK
(tutorials, news, roadmaps, tips and tricks for making great
applications, development tools and helpers)
- Internationalization and Localization
- Design guidelines and User Experience
(different MeeGo verticals, form factors, crossing the boundaries between them,
differentiation)

Platform development
- Current and possible future components within the MeeGo architecture
(status, overview, and roadmap)
- Platform tools and process
(tutorials/introductions, improvements/developments, tips and tricks, etc.)
- Quality Assurance
(methods, tools, tutorials, experiences)

MeeGo project, process, and progress
- Activity reports and roadmaps from various project areas
- Project challenges and discussions on project and process
- Marketing, outreach; engaging companies, governments, and others
- App stores and monetization strategies
- Community building and fostering
- Documentation, artwork, infrastructure

We also welcome submissions on any other MeeGo related topics. Be
creative, the program committee will look at each and every submission, to
create a vibrant and interesting conference. This includes community and
open source related proposals, as well as commercial or proprietary
developments around MeeGo.

Submissions should include:
- Author(s) (including their work affiliation)
- Short BIO (100-150 words, written in 3rd person)
- Short Abstract (120-150 words, crisply defines the topic)
- Abstract (300-500 words, explains the scope of the presentation)
- Preferred session duration (default is 30 minutes + 10 minutes Q&A, but we'll entertain
other requests where possible)

Please also mention if this will include any form of product
presentation. In general, we are not soliciting sales pitches,
but it is ok for technical presentations to refer to (or announce)
MeeGo related products.

If you will need travel support, note this in your submission, also.

To submit a session proposal, either create a meego.com account or login with your existing meego.com account at http://sf2011.meego.com/user and create a proposal at http://sf2011.meego.com/node/add/session. Registration for the conference can be done now or you can wait until sessions are accepted to find out if you'll be a presenter.

Submissions will be due by 11:59 PM Pacific Time on March 25, 2011. Around that time, we'll open a second process for lightning talk submissions.

We expect to have a large subset of the presentations approved and
scheduled by April 4th and are planning to have the final program
ready before April 15th.

The Program Committee

Dirk Hohndel
Thiago Macieira
Carsten Munk

</pre>

Community Application Support/Design Apps aka Downloads

2011-02-10T18:50:06Z

Mshaver: /* Front page */

This page is intended to be a starting point of the design for the end-user downloads Apps website. In maemo.org there is [http://maemo.org/downloads/ maemo.org Downloads], which is a good example of what can be expected.

I'll give a list of available data and suggestions of what we can add. Let's try to find out what a MeeGo Apps website should show.

After we have created a clear list of requirements, we can ask the community for a design or design suggestions. The work ongoing at apps-beta is currently concentrating on getting the correct data from the community OBS and making sure everything is in place for community QA. The Apps website itself will be running on top of this data, but with a clear end-user oriented view on top of this.

The Apps website will also have an [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS api] interface, so App installer/clients can use the same data as the Apps website.

''Feel free to add points. Make sure you end the line with '''<nowiki>--~~~~</nowiki>''', so it is clear who posted what.''

== Data available ==
=== Application info ===
* title
* short description
* long description
* version
* icon
* category
* screenshot(s)
* rating
* comments
* download link
* timestamp of publishing
* maintainer/company
* homepage
* code development (github, gitorious, etc)
* license

=== Statistics ===
* rating
* comments
* downloads (TODO, data not available yet)

== Design ==
We should probably come up with wireframe designs, based on the discussion.
=== Front page ===
==== Target selection ====
The Apps front page will most likely be visited from either a MeeGo or a non-MeeGo device. When browsing to the site from a MeeGo device, we can probably detect what version of MeeGo and architecture it is running by looking at the browser string. If this is not possible, we should present a screen where one can select the target UX, architecture and version.

After this selection has been made, it will be stored in the current session so that the interface will only show the correct target.
==== Target front page ====
The actual front page for the selected target should show a top list of featured, new, updated, most downloaded.

Should it can also give a list of available categories? --[[User:Xfade|Xfade]] 11:29, 9 February 2011 (UTC)

==== Sample Wireframe ====
This is just a sample of a listing of apps. It doesn't take into account target or a few other app details, but might be helpful to kickstart the discussion.

[[File:Meego-apps-list.png|200px|thumb|none|Apps List]]

=== App details page ===
This should show detailed info about the application including screenshots.

Sample wireframe. This is a bit old but can start the conversation.

[[File:Meego-apps-page.png|200px|thumb|none|App Page]]

=== App categories ===

This should show a list of available categories.

=== Comments and rating ===

Comment blocks should be designed to fit in the style of the website and show the appropriate info.

Community Application Support/Design Apps aka Downloads

2011-02-10T18:48:09Z

Mshaver: /* App details page */

This page is intended to be a starting point of the design for the end-user downloads Apps website. In maemo.org there is [http://maemo.org/downloads/ maemo.org Downloads], which is a good example of what can be expected.

I'll give a list of available data and suggestions of what we can add. Let's try to find out what a MeeGo Apps website should show.

After we have created a clear list of requirements, we can ask the community for a design or design suggestions. The work ongoing at apps-beta is currently concentrating on getting the correct data from the community OBS and making sure everything is in place for community QA. The Apps website itself will be running on top of this data, but with a clear end-user oriented view on top of this.

The Apps website will also have an [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS api] interface, so App installer/clients can use the same data as the Apps website.

''Feel free to add points. Make sure you end the line with '''<nowiki>--~~~~</nowiki>''', so it is clear who posted what.''

== Data available ==
=== Application info ===
* title
* short description
* long description
* version
* icon
* category
* screenshot(s)
* rating
* comments
* download link
* timestamp of publishing
* maintainer/company
* homepage
* code development (github, gitorious, etc)
* license

=== Statistics ===
* rating
* comments
* downloads (TODO, data not available yet)

== Design ==
We should probably come up with wireframe designs, based on the discussion.
=== Front page ===
==== Target selection ====
The Apps front page will most likely be visited from either a MeeGo or a non-MeeGo device. When browsing to the site from a MeeGo device, we can probably detect what version of MeeGo and architecture it is running by looking at the browser string. If this is not possible, we should present a screen where one can select the target UX, architecture and version.

After this selection has been made, it will be stored in the current session so that the interface will only show the correct target.
==== Target front page ====
The actual front page for the selected target should show a top list of featured, new, updated, most downloaded.

Should it can also give a list of available categories? --[[User:Xfade|Xfade]] 11:29, 9 February 2011 (UTC)

=== App details page ===
This should show detailed info about the application including screenshots.

Sample wireframe. This is a bit old but can start the conversation.

[[File:Meego-apps-page.png|200px|thumb|none|App Page]]

=== App categories ===

This should show a list of available categories.

=== Comments and rating ===

Comment blocks should be designed to fit in the style of the website and show the appropriate info.

Community Application Support/Design Apps aka Downloads

2011-02-10T18:47:11Z

Mshaver: /* App details page */

This page is intended to be a starting point of the design for the end-user downloads Apps website. In maemo.org there is [http://maemo.org/downloads/ maemo.org Downloads], which is a good example of what can be expected.

I'll give a list of available data and suggestions of what we can add. Let's try to find out what a MeeGo Apps website should show.

After we have created a clear list of requirements, we can ask the community for a design or design suggestions. The work ongoing at apps-beta is currently concentrating on getting the correct data from the community OBS and making sure everything is in place for community QA. The Apps website itself will be running on top of this data, but with a clear end-user oriented view on top of this.

The Apps website will also have an [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS api] interface, so App installer/clients can use the same data as the Apps website.

''Feel free to add points. Make sure you end the line with '''<nowiki>--~~~~</nowiki>''', so it is clear who posted what.''

== Data available ==
=== Application info ===
* title
* short description
* long description
* version
* icon
* category
* screenshot(s)
* rating
* comments
* download link
* timestamp of publishing
* maintainer/company
* homepage
* code development (github, gitorious, etc)
* license

=== Statistics ===
* rating
* comments
* downloads (TODO, data not available yet)

== Design ==
We should probably come up with wireframe designs, based on the discussion.
=== Front page ===
==== Target selection ====
The Apps front page will most likely be visited from either a MeeGo or a non-MeeGo device. When browsing to the site from a MeeGo device, we can probably detect what version of MeeGo and architecture it is running by looking at the browser string. If this is not possible, we should present a screen where one can select the target UX, architecture and version.

After this selection has been made, it will be stored in the current session so that the interface will only show the correct target.
==== Target front page ====
The actual front page for the selected target should show a top list of featured, new, updated, most downloaded.

Should it can also give a list of available categories? --[[User:Xfade|Xfade]] 11:29, 9 February 2011 (UTC)

=== App details page ===
This should show detailed info about the application including screenshots.

Sample wireframe. This is a bit old but can start the conversation.

[[File:Meego-apps-page.png|200px|thumb|App Page]]

=== App categories ===

This should show a list of available categories.

=== Comments and rating ===

Comment blocks should be designed to fit in the style of the website and show the appropriate info.

Community Application Support/Design Apps aka Downloads

2011-02-10T18:46:37Z

Mshaver: /* App details page */

This page is intended to be a starting point of the design for the end-user downloads Apps website. In maemo.org there is [http://maemo.org/downloads/ maemo.org Downloads], which is a good example of what can be expected.

I'll give a list of available data and suggestions of what we can add. Let's try to find out what a MeeGo Apps website should show.

After we have created a clear list of requirements, we can ask the community for a design or design suggestions. The work ongoing at apps-beta is currently concentrating on getting the correct data from the community OBS and making sure everything is in place for community QA. The Apps website itself will be running on top of this data, but with a clear end-user oriented view on top of this.

The Apps website will also have an [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS api] interface, so App installer/clients can use the same data as the Apps website.

''Feel free to add points. Make sure you end the line with '''<nowiki>--~~~~</nowiki>''', so it is clear who posted what.''

== Data available ==
=== Application info ===
* title
* short description
* long description
* version
* icon
* category
* screenshot(s)
* rating
* comments
* download link
* timestamp of publishing
* maintainer/company
* homepage
* code development (github, gitorious, etc)
* license

=== Statistics ===
* rating
* comments
* downloads (TODO, data not available yet)

== Design ==
We should probably come up with wireframe designs, based on the discussion.
=== Front page ===
==== Target selection ====
The Apps front page will most likely be visited from either a MeeGo or a non-MeeGo device. When browsing to the site from a MeeGo device, we can probably detect what version of MeeGo and architecture it is running by looking at the browser string. If this is not possible, we should present a screen where one can select the target UX, architecture and version.

After this selection has been made, it will be stored in the current session so that the interface will only show the correct target.
==== Target front page ====
The actual front page for the selected target should show a top list of featured, new, updated, most downloaded.

Should it can also give a list of available categories? --[[User:Xfade|Xfade]] 11:29, 9 February 2011 (UTC)

=== App details page ===
This should show detailed info about the application including screenshots.

Sample wireframe. This is a bit old but can start the conversation.

[[File:Meego-apps-page.png|200px|thumb|left|App Page]]

=== App categories ===

This should show a list of available categories.

=== Comments and rating ===

Comment blocks should be designed to fit in the style of the website and show the appropriate info.

File:Meego-apps-page.png

2011-02-10T18:44:25Z

Mshaver: Sample of apps page.

Sample of apps page.

File:Meego-apps-list.png

2011-02-10T18:44:01Z

Mshaver: Sample of apps list.

Sample of apps list.

Community Application Support/Design Apps aka Downloads

2011-02-10T18:35:27Z

Mshaver: /* Application info */

This page is intended to be a starting point of the design for the end-user downloads Apps website. In maemo.org there is [http://maemo.org/downloads/ maemo.org Downloads], which is a good example of what can be expected.

I'll give a list of available data and suggestions of what we can add. Let's try to find out what a MeeGo Apps website should show.

After we have created a clear list of requirements, we can ask the community for a design or design suggestions. The work ongoing at apps-beta is currently concentrating on getting the correct data from the community OBS and making sure everything is in place for community QA. The Apps website itself will be running on top of this data, but with a clear end-user oriented view on top of this.

The Apps website will also have an [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS api] interface, so App installer/clients can use the same data as the Apps website.

''Feel free to add points. Make sure you end the line with '''<nowiki>--~~~~</nowiki>''', so it is clear who posted what.''

== Data available ==
=== Application info ===
* title
* short description
* long description
* version
* icon
* category
* screenshot(s)
* rating
* comments
* download link
* timestamp of publishing
* maintainer/company
* homepage
* code development (github, gitorious, etc)
* license

=== Statistics ===
* rating
* comments
* downloads (TODO, data not available yet)

== Design ==
We should probably come up with wireframe designs, based on the discussion.
=== Front page ===
==== Target selection ====
The Apps front page will most likely be visited from either a MeeGo or a non-MeeGo device. When browsing to the site from a MeeGo device, we can probably detect what version of MeeGo and architecture it is running by looking at the browser string. If this is not possible, we should present a screen where one can select the target UX, architecture and version.

After this selection has been made, it will be stored in the current session so that the interface will only show the correct target.
==== Target front page ====
The actual front page for the selected target should show a top list of featured, new, updated, most downloaded.

Should it can also give a list of available categories? --[[User:Xfade|Xfade]] 11:29, 9 February 2011 (UTC)

=== App details page ===
This should show detailed info about the application including screenshots.

=== App categories ===

This should show a list of available categories.

=== Comments and rating ===

Comment blocks should be designed to fit in the style of the website and show the appropriate info.

MeeGo Software Updates

2011-01-05T05:38:24Z

Mshaver:

== Software Updates ==
MeeGo releases periodic software updates for each of the various releases to fix bugs and patch security issues. Release notes for all updates are posted on meego.com at: http://meego.com/downloads/releases/updates

The following documentation details how to update your system with the latest update. Please review the known issues section of the release notes before starting the update process.

== Automatic Updates ==

The first time you run the update, you will most likely get one package manager update that is required before we can send you the rest of the updates. Don't worry, more updates will follow.

The Update System will often run through more than one wave of updates. This is normal. We often need to do updates in stages to resolve update dependencies. Continue to let it run through the updates.

You should receive notifications that you have an 'Important update available'.
* Click Install updates when you see this notification.
* After it refreshes the software list, Click 'Install Updates'.
* You may receive the "Additional confirmation required' dialog box if this is the first time you are running an update. If so, click 'Continue' (if your netbook display resolution obscures the text on these buttons, the "Continue" button is on the RIGHT).
* You should receive a confirmation that all updates have installed successfully. Click 'OK'. Note: This box will disappear after a couple of minutes even if you do not click 'OK'. This is normal.

[http://help.meego.com/netbook/settings/installing-updating-and-removing-software/update-system-software More help using the GUI update system] can be found in our online user help documentation.

== Manually Check for Updates ==

If you don't want to wait for a notification, you can also manually check for updates.

* Navigate in the user interface to Applications -> System Tools -> Update System.
* Follow the instructions above in the 'Automatic Updates' section.

Note: If you have already installed your updates or there, you should get a dialog telling you that all software is up to date.

More help [http://help.meego.com/netbook/settings/installing-updating-and-removing-software/update-system-software using the GUI update system] can be found in our online user help documentation.

== Known Issues ==

=== Can't See the Continue Button on First Update ===

We are working to fix this [http://bugs.meego.com/show_bug.cgi?id=2856 bug].

If your netbook display resolution obscures the text on the continue or cancel buttons, but you can see the top of the buttons, the "Continue" button is on the RIGHT and can be clicked to continue.

If you can't see the buttons at all, here is the workaround to do a manual command line update:
* Open a terminal window (Applications -> System Tools -> Terminal)
* Change to the super user using the 'su' command.
* You will need to do a refresh to download the updates by typing:

zypper refresh

* Install the updates

zypper patch

Note: You may see several warnings. Do not be alarmed - the update should continue past the warnings. Again, keep in mind that this is a one-time step and future updates will be easier to complete using the GUI update tool.

=== Broadcom Wireless Drivers ===

Those of you who have installed Broadcom Wireless Drivers from Slaine.org may find they no longer work after the update so will need to rebuild them by opening a terminal and running
rpmbuild --rebuild --target=i586 wl-kmod-5.60.48.36-1.moblin.src.rpm

After rebuilding you may need to reinstall the package.
sudo rpm --replacepkgs -i wl-kmod-5.60.48.36-1.meego.i586.rpm

After rebuilding, you should have working wifi. More [http://slaine.org/_slaine/Meego_1.0_Wifi.html details about the Broadcom drivers can be found at Slaine.org], and more details about this update issue can be found in [http://forum.meego.com/showthread.php?t=662&page=1 this forum post].

===Failed to Complete Request Error===

If after pressing "Apply" in the updates window, you get a "failed to complete a request" error, you can use zypper to manually complete the updates.

At a terminal window type:
su
zypper refresh
zypper patch

Talk:MeeGo 1.0 Netbook Updates

2011-01-05T05:33:05Z

Mshaver: moved Talk:MeeGo 1.0 Netbook Updates to Talk:MeeGo Software Updates

#REDIRECT [[Talk:MeeGo Software Updates]]

Talk:MeeGo Software Updates

2011-01-05T05:33:05Z

Mshaver: moved Talk:MeeGo 1.0 Netbook Updates to Talk:MeeGo Software Updates

The following taken from the Manual Update section:

*******************

If you can't see the buttons at all, here is the workaround to do a manual command line update:

* Open a terminal window (Applications -> System Tools -> Terminal)
* Change to the super user using the 'su' command.
* After adding your repos, you will need to do a refresh by typing:

zypper refresh

* Install the updates

zypper patch

******************

I have a question regarding the above "After adding your repos..."

How does one add repos?

-----

Sorry about that. I had additional instructions about adding repos when we doing some testing a while back (adding test repos). You should already have all of the repos you need for these updates. I'll fix the doc -- [[User:Dawnfoster|Dawnfoster]] 22:14, 2 August 2010 (UTC)

MeeGo 1.0 Netbook Updates

2011-01-05T05:33:04Z

Mshaver: moved MeeGo 1.0 Netbook Updates to MeeGo Software Updates

#REDIRECT [[MeeGo Software Updates]]

MeeGo Software Updates

2011-01-05T05:33:04Z

Mshaver: moved MeeGo 1.0 Netbook Updates to MeeGo Software Updates

Please review the known issues section before starting the update process.

== Automatic Updates ==

The first time you run the update, you will most likely get one package manager update that is required before we can send you the rest of the updates. Don't worry, more updates will follow.

The Update System will often run through more than one wave of updates. This is normal. We often need to do updates in stages to resolve update dependencies. Continue to let it run through the updates.

You should receive notifications that you have an 'Important update available'.
* Click Install updates when you see this notification.
* After it refreshes the software list, Click 'Install Updates'.
* You may receive the "Additional confirmation required' dialog box if this is the first time you are running an update. If so, click 'Continue' (if your netbook display resolution obscures the text on these buttons, the "Continue" button is on the RIGHT).
* You should receive a confirmation that all updates have installed successfully. Click 'OK'. Note: This box will disappear after a couple of minutes even if you do not click 'OK'. This is normal.

[http://help.meego.com/netbook/settings/installing-updating-and-removing-software/update-system-software More help using the GUI update system] can be found in our online user help documentation.

== Manually Check for Updates ==

If you don't want to wait for a notification, you can also manually check for updates.

* Navigate in the user interface to Applications -> System Tools -> Update System.
* Follow the instructions above in the 'Automatic Updates' section.

Note: If you have already installed your updates or there, you should get a dialog telling you that all software is up to date.

More help [http://help.meego.com/netbook/settings/installing-updating-and-removing-software/update-system-software using the GUI update system] can be found in our online user help documentation.

== Known Issues ==

=== Can't See the Continue Button on First Update ===

We are working to fix this [http://bugs.meego.com/show_bug.cgi?id=2856 bug].

If your netbook display resolution obscures the text on the continue or cancel buttons, but you can see the top of the buttons, the "Continue" button is on the RIGHT and can be clicked to continue.

If you can't see the buttons at all, here is the workaround to do a manual command line update:
* Open a terminal window (Applications -> System Tools -> Terminal)
* Change to the super user using the 'su' command.
* You will need to do a refresh to download the updates by typing:

zypper refresh

* Install the updates

zypper patch

Note: You may see several warnings. Do not be alarmed - the update should continue past the warnings. Again, keep in mind that this is a one-time step and future updates will be easier to complete using the GUI update tool.

=== Broadcom Wireless Drivers ===

Those of you who have installed Broadcom Wireless Drivers from Slaine.org may find they no longer work after the update so will need to rebuild them by opening a terminal and running
rpmbuild --rebuild --target=i586 wl-kmod-5.60.48.36-1.moblin.src.rpm

After rebuilding you may need to reinstall the package.
sudo rpm --replacepkgs -i wl-kmod-5.60.48.36-1.meego.i586.rpm

After rebuilding, you should have working wifi. More [http://slaine.org/_slaine/Meego_1.0_Wifi.html details about the Broadcom drivers can be found at Slaine.org], and more details about this update issue can be found in [http://forum.meego.com/showthread.php?t=662&page=1 this forum post].

===Failed to Complete Request Error===

If after pressing "Apply" in the updates window, you get a "failed to complete a request" error, you can use zypper to manually complete the updates.

At a terminal window type:
su
zypper refresh
zypper patch

Web infrastructure

2010-12-22T00:25:06Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/qgil Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|[http://meego.com/users/bspencer Bob Spencer]
|[[SDK|details]]
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|[http://meego.com/users/agretzinger Adam Gretzinger]
|[[Mailing list guidelines|details]]
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|[http://meego.com/users/reggie Reggie Suplido]
|[[Web_infrastructure/Forum|details]]
|-
|http://planet.meego.com
|Midgard
|OSU
|active
|[http://meego.com/users/bergie Henri Bergius]
|[[Web_infrastructure/Planet.meego.com|details]]
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|-
|ots.meego.com
|http://gitorious.org/qa-tools/ots
|OSU
|active
| [http://meego.com/users/vilvo Ville Ilvonen]
|[http://wiki.meego.com/Quality/QA-tools/OTS details]
|}

News and Planet

2010-12-21T21:37:39Z

Mshaver: Redirected page to Web infrastructure/Planet.meego.com

#REDIRECT [[Web infrastructure/Planet.meego.com]]

News.meego.com

2010-12-21T21:36:32Z

Mshaver: Redirected page to Web infrastructure/Planet.meego.com

#REDIRECT [[Web infrastructure/Planet.meego.com]]

Talk:Planet.meego.com

2010-12-21T21:29:42Z

Mshaver: moved Talk:Planet.meego.com to Talk:Web infrastructure/Planet.meego.com: organizing web infrastructure under one heading

#REDIRECT [[Talk:Web infrastructure/Planet.meego.com]]

Talk:Web infrastructure/Planet.meego.com

2010-12-21T21:29:42Z

Mshaver: moved Talk:Planet.meego.com to Talk:Web infrastructure/Planet.meego.com: organizing web infrastructure under one heading

We should probably move the media team proposal & info about the @meegocom Twitter account to a separate page, since neither of them are directly related to the planet. --[[User:Dawnfoster|Dawnfoster]] 22:50, 14 December 2010 (UTC)
:[[Marketing/Media Team|Media Team]] moved to own page. Good point. Let's kleep still the Twitter account there since it's main window within meego.com will be at planet.meego.com (once the block is implemented).--[[User:Qgil|Qgil]] 18:44, 15 December 2010 (UTC)

Planet.meego.com

2010-12-21T21:29:42Z

Mshaver: moved Planet.meego.com to Web infrastructure/Planet.meego.com: organizing web infrastructure under one heading

#REDIRECT [[Web infrastructure/Planet.meego.com]]

Web infrastructure/Planet.meego.com

2010-12-21T21:29:42Z

Mshaver: moved Planet.meego.com to Web infrastructure/Planet.meego.com: organizing web infrastructure under one heading

http://planet.meego.com aims to aggregate all the relevant MeeGo news sources and extract the best of it through community promotion and editorial work. It is maintained by the [[Marketing/Media Team|Media team]].

We are not quite there yet, but we want to have everything ready before the MeeGo 1.2 release.

== planet.meego.com structure ==
The News section is reachable from several meego.com homepage blocks and the "News" item in the top navigation bar. It is made of different types of content. http://news.meego.com needs to combine them all in an efficient and nice looking way.

* Sticky news item (e.g. TSG blog post) and a link to the previous stickies archived.
** Should we use a tag for this? --[[User:Qgil|Qgil]] 23:21, 23 November 2010 (UTC)
* Top ranked blog posts from http://news.meego.com/blogs/ and a link to [http://news.meego.com/blogs/ Most recent].
* Last [http://twitter.com/meegocom @meegocom] tweets
** Plus most popular [http://twitter.com/#search?q=meego #meego] tweet? Is there an API for this?--[[User:Qgil|Qgil]] 23:21, 23 November 2010 (UTC)
* Next events and link to [http://meego.com/community/events Calendar]
* Static link to "Media Center", "Aggregate your blog" and "How this works".

''To be defined'':
* Should we have a static space featuring a top video (feeding from YouTube/Vimeo/Blip...) and a top image (Flickr, Picasa...)?--[[User:Qgil|Qgil]] 23:21, 23 November 2010 (UTC)

== Status ==
{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=planet.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== @meegocom at Twitter ==

http://twitter.com/meegocom aims to be a channel forwarding the most relevant activity happening inside and around the MeeGo project.

PURPOSE
* Retweet the most interesting statuses related to MeeGo
* Reply interesting questions or comments addressed to @meegocom

PROCESS
* Anybody can "forward" news by including "#meegocom" in the status.
* Extended Media Team aims to cover all the community channels
* Media Team members have all access to @meegocom
* In most cases meegocom will simply RT what goes through the filter
* Objective replies only (e.g. links to sources), neutral voice
* Twitter best practice is to use shortened links - @meegocom will shorten the link if not already shortened.

FOLLOWING
* Only official users followed e.g. @MeeGoConf
* Specific lists created to point interesting users e.g. @meegocom/sdk

PS: vaguely inspired by the light process behind MWKN
http://wiki.maemo.org/Maemo_Weekly_News

== Social News ==

Everybody likes the principle of news written by the community. It seems that everybody actually likes the http://maemo.org/news system, combining over hundred sources that get promoted or demoted based on user input (thumbs up & down) and karma from several sources e.g. del.icio.us, technorati... [http://bergie.iki.fi/blog/maemo_social_news_launched/ read more]

But it will take us a while to implement [http://trac.midgard-project.org/browser/branches/ragnaroek/midcom/org.maemo.socialnews something like that] in meego.com. In the meantime we can start aggregating blogs and other MeeGo specific news sources.

Drupal includes an Aggregation module out of the box: http://drupal.org/handbook/modules/aggregator
There is an official module that resembles a PlanetPlanet, but do we really need the extra maintenance for that? http://drupal.org/project/udplanet

The maemo.org Midgard team has prepared a deployment of using Maemo's Midgard-based Social News system for MeeGo News. The system uses the regular meego.com accounts (though not yet sessions pending for [[Single sign-on]] deployment) via LDAP.

The deployment consists of:

* Midgard LTS installation with a MeeGo theme and LDAP auth
* Social News and Planet setup where users can vote incoming posts in http://news.meego.com/
* RSS feed of top ranked (most relevant) posts in http://news.meego.com/items.xml
* RSS feed of all incoming posts in http://news.meego.com/blogs/rss.xml

This system still waits for integration with the main meego.com homepage.

== Blog aggregation checklist ==

Anybody can request the aggregation of their blog at meego.com under the following conditions:

# You are contributing to MeeGo in a direct way: software & community contributors, partners, manufacturers, specialized media...
# You have a public profile created at meego.com specifying your link with the MeeGo project.
# You have a blog somewhere with a MeeGo specific feed (your posts about lolcats won't show up @ Planet MeeGo).
# Your posts in that MeeGo feed are in English.
# You have been blogging about MeeGo for a while already. Exception: you have an official role in the project and you are starting to blog about your work at MeeGo.
# Your feed must be valid and must contain at least one MeeGo post (more preferred).

=== Request the aggregation of your blog ===

If you fulfill your requirements above you can request the aggregation of your blog by adding it to the candidates list below:
* URL of your meego.com profile.
* URL of your MeeGo specific feed.
* Also [http://news.meego.com/midcom-login- log in] to MeeGo News with your meego.com account.

Note: If it hasn't been added within 2-3 days, please send a message to [http://meego.com/users/dawnfoster Dawn Foster] or [http://meego.com/users/qgil Quim Gil]. Please remember that it will only be added if it meets the criteria.

=== Candidates ===
Or you can start adding yourself to the list of candidates (please do not add other people's blogs to this list):
* [http://www.maemopeople.org/index.php/jaffa?tempskin=_rss2&cat=94 Andrew Flegg] - http://www.maemopeople.org/index.php/jaffa?tempskin=_rss2&cat=94
* [http://meego.com/users/kate Kate Alhola] http://blogs.forum.nokia.com/rss.php?blogId=300003&profile=rss20
* [http://meego.com/users/kgronholm Kaj Grönholm] - http://kgronholm.blogspot.com/feeds/posts/default/-/MeeGo
* [http://meego.com/users/vaibhavsharma Vaibhav Sharma] http://thehandheldblog.com/category/meego/feed/
* [http://meego.com/users/arfoll Brendan Le Foll] - http://www.madeo.co.uk/?tag=meego&feed=rss2
* [http://meego.com/users/agrin Alejandro Grin] - http://meego.com.ar/feed/
* [http://meego.com/users/jfourgeaud Julien Fourgeaud] - http://www.fourgeaud.com/category/meego/feed/
* [http://wiki.meego.com/Quality/QA-tools MeeGo QA-tools] - http://meegoqatools.wordpress.com/feed/
(Add after first post to validate feed)
* [http://meego.com/users/timoph Timo Härkönen] - http://timoph.wordpress.com/category/meego/feed/ (moved the blog from timoph.blogspot.com to wordpress because of the issues with blogspot feeds. The old blog can be removed from the feeds since I'm not going to continue posting to it)
* [http://meego.com/users/andre Andre Klapper] http://blogs.gnome.org/aklapper/category/computer/meego/feed/

See also:
Note: I believe that these 2 blogs listed below were submitted by someone other than the blog author, so they can't be syndicated until the author confirms that they would like to have their content republished as part of the MeeGo planet.
* Emmanuele Bassi's [http://blogs.gnome.org/ebassi blog]

'''Added'''

See canonical list in [http://news.meego.com/blogs/feeds/list/ MeeGo blogs aggregator] or in [http://news.meego.com/blogs/feeds.opml OPML format].

* [http://meego.com/users/qgil Quim Gil] - http://flors.wordpress.com/tag/meego/feed/
* [http://meego.com/users/w00t Robin Burchell] - http://blog.rburchell.com/feeds/posts/default/-/meego?alt=rss
* [http://meego.com/users/macron Ronan Mac Laverty] - http://maclaver.wordpress.com/tag/meego/feed/
* [http://meego.com/users/zaheerm Zaheer Abbas Merali] - http://zaheer.merali.org/articles/category/meego/feed
* [http://meego.com/users/dawnfoster Dawn Foster] - http://fastwonderblog.com/tag/meego/feed
* [http://meego.com/users/mattaustin Matt Austin] - http://meegoreview.com/feed/
* [http://meego.com/users/achipa Attila Csipa] - http://achipa.blogspot.com/feeds/posts/default/-/meego
* [http://meego.com/users/abock Aaron Bockover] - http://abock.org/tag/meego/feed
* [http://meego.com/users/lbt David Greaves] - http://mer-l-in.blogspot.com/feeds/posts/default/-/MeeGo (having some issues with this feed)
* [http://www.hohndel.org/communitymatters/category/meego/feed/ Dirk Hohndel, Community Matters] - this is a MeeGo feed; and yes, my blog has been named Community Matters for many years - long before this term was used here in MeeGo
* [http://marcin.soltysiak.com/feeds/category/MeeGo/ Marcin Soltysiak]
* [http://labs.qt.nokia.com/blogs/category/meego/feed/ Qt blog] - http://labs.qt.nokia.com/blogs/category/meego/feed/
* [http://meego.com/users/thenokiablog Mark Guim] - http://thenokiablog.com/tag/meego/feed/
* [http://meego.com/users/texrat Randall Arnold] - http://tabulacrypticum.wordpress.com/category/the-process-and-product-frontier/mentioning-meego/feed/ (feed updated)
* [http://meego.com/users/jaffa Andrew Flegg] - http://www.mwkn.net/issues.rss
* [http://meego.com/users/zimmerle Felipe Zimmerle] - http://www.zimmerle.org/?cat=17&feed=rss2
* [http://meego.com/users/bergie Henri Bergius] - http://bergie.iki.fi/blog/feeds/category/meego/
* [http://meego.com/users/rafe Rafe Blandford] - http://rss.allaboutmeego.com/aam-feed-full-cat-meego.xml
* [http://meego.com/users/thos Thomas Wood] - http://blogs.gnome.org/thos/category/intel/meego/feed/
* [http://meego.com/users/eipi Sanjeev Visvanatha (EIPI)] - http://mobiletablets.blogspot.com/feeds/posts/default/-/Meego (having some issues with this feed & other blogspot feeds)
* [http://meego.com/users/parancibia Paulo Arancibia] - http://realnorth.net/blog/tag/meego/
* [http://meego.com/users/timoph Timo Härkönen] - http://timoph.blogspot.com/feeds/posts/default/-/MeeGo (having some issues with this feed & other blogspot feeds)
* [http://meego.com/users/sivan Sivan Greenberg] - http://blogs.forum.nokia.com/blog/sivan-greenbergs-forum-nokia-blog/
* [http://meego.com/users/yerga Daniel Martin Yerga] - http://yerga.wordpress.com/category/meego/feed/
* [http://meego.com/users/felipec Felipe Contreras] - http://felipec.wordpress.com/category/meego/feed/
* [http://pvanhoof.be/blog/index.php/category/meego/feed Philip Van Hoof] - http://pvanhoof.be/blog/index.php/category/meego - Software developer for Tracker (metadata / SPARQL service on MeeGo) - http://meego.com/user/11360 - (having some issues with this feed)
* [http://dz015.wordpress.com/category/software/maemo/ Ivan Frade] - http://dz015.wordpress.com/category/software/maemo/ - Tracker maintainer in Meego - http://meego.com/users/ifrade - (having some issues with this feed)
* [http://mbatle.wordpress.com/category/meego/feed/rss/ Mateu Batle] - http://mbatle.wordpress.com/category/meego/feed/rss/
* [http://meego.com/users/piacentini Mauricio Piacentini] - http://piacentini.blog.br/category/meego/feed/
* Travis Reitter - http://treitter.livejournal.com/data/rss?tag=meego
* [http://meego.com/users/przybils Michael Przybilski] - https://www.nixuopen.org/blog/

Web infrastructure

2010-12-21T21:27:30Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/qgil Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|[http://meego.com/users/bspencer Bob Spencer]
|[[SDK|details]]
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|[http://meego.com/users/agretzinger Adam Gretzinger]
|[[Mailing list guidelines|details]]
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|[http://meego.com/users/reggie Reggie Suplido]
|[[Web_infrastructure/Forum|details]]
|-
|http://planet.meego.com
|Midgard
|OSU
|active
|[http://meego.com/users/bergie Henri Bergius]
|[[News.meego.com|details]]
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|-
|ots.meego.com
|http://gitorious.org/qa-tools/ots
|OSU
|active
| [http://meego.com/users/vilvo Ville Ilvonen]
|[http://wiki.meego.com/Quality/QA-tools/OTS details]
|}

Web infrastructure/Meego.com

2010-12-10T23:22:33Z

Mshaver: /* Information Architecture */

'''PROPOSAL''' - [http://forum.meego.com/showthread.php?t=113 discussion]

The team in charge of the maintenance, update and expansion of meego.com. Any significant change in the website content or structure is coordinated here.

== Team ==

* Webmaster: [http://meego.com/users/mshaver Mike Shaver]
* Content coordination: [http://meego.com/users/qgil Quim Gil]
* Technical writing support: [http://meego.com/users/noel Noel Arnold]
* Content owners:
** Homepage: [http://meego.com/users/qgil Quim Gil]
** Downloads: [http://meego.com/users/mshaver Mike Shaver]
** [[ApplicationDeveloperSiteDescription|Developers]]: [http://meego.com/users/macron Ronan Mac Laverty] [http://meego.com/users/bspencer Bob Spencer]
** Projects: [http://meego.com/users/mshaver Mike Shaver] Working on new proposal.
** "Garage": [http://meego.com/users/bspencer Bob Spencer]
** Community: [http://meego.com/users/dawnfoster Dawn Foster]
*** Forum: [http://meego.com/users/reggie Reggie Suplido]
** About: '''FIXME'''
** [http://meego.com/devices/netbook Netbook]: Netbook Working Group
** [http://meego.com/devices/handheld Handsets]: Handset Working Group
** [http://meego.com/devices/in-vehicle IVI]: IVI Working Group
** [http://meego.com/devices/connected-tv Connected TV]: Connected TV Working Group
** [http://meego.com/devices/media-phone Media Phone]: Media Phone Working Group

== Process ==
'''PROPOSAL'''

* Develop working architecture diagram (ie, site map) to better handle growth in a consistent and user focused way.
* Documentation/tutorials for creating and editing content, see [[Community working group#Tasks|Community WG list of tasks]].
* Use the wiki for rapid growth. Then the consolidated pages can be agreed to move to the main site.
* Significant changes in the homepage and the main pages of each section need to be agreed first. Use the wiki to document major changes and the Community Matters forum to discuss the proposals. Bugzilla should be used to track the tasks.
* Following the point above, content owners have flexibility to improve and expand their own areas.
* Volunteers can help improving certain area at any time. Use the Community Matters forum or contact the related maintainer in order to get involved.
* Regular contributors in a specific area can request editing permissions and content ownership. Make sure the maintainers of a specific area agree with your candidacy before requesting it to the meego.com team coordinators.

== Information Architecture ==
<gallery>
File:Web_Infrastructure_Site_Map_v01.png|Web Infrastructure Overview Diagram
File:Meego.com_Site_Map_v1.1.png|Existing site map for meego.com
File:Meego.com_Home_Page_v1.0.png|meego.com home page overview
File:Meego.com_developers_section_v1.0.png|meego.com/developers sample page
</gallery>

[[media:Meego_sitemaps_v01.1.graffle|MeeGo Site Maps OmniGraffle file]]

== Tasks ==
We are using the main [[Community working group#Tasks|Community WG list of tasks]] to organize the meego.com specific work.

meego.com tasks are assigned and prioritized at the [[Community Working Group Meeting]].

If you want to suggest a new task or get a task assigned to you just follow the usual [[Community working group#Process|Community WG process]].

== Bugs ==
Bugs and enhancement requests about meego.com content or functionality must be filed at http://bugs.meego.com/enter_bug.cgi?product=meego.com

== Get involved ==
We welcome volunteers testing the site and providing feedback. Get started proposing specific improvements at [http://bugs.meego.com/enter_bug.cgi?product=meego.com bugs.meego.com], propose new content (text, graphics) and get involved in regular tasks.

* I can do some technical writing and graphics work as well --[[User:Texrat|Texrat]] 04:47, 2 September 2010 (UTC)

File:Meego sitemaps v01.1.graffle

2010-12-10T23:20:41Z

Mshaver: meego.com site maps OmniGraffle file.

meego.com site maps OmniGraffle file.

Web infrastructure/Meego.com

2010-12-10T23:14:34Z

Mshaver: /* Information Architecture */

'''PROPOSAL''' - [http://forum.meego.com/showthread.php?t=113 discussion]

The team in charge of the maintenance, update and expansion of meego.com. Any significant change in the website content or structure is coordinated here.

== Team ==

* Webmaster: [http://meego.com/users/mshaver Mike Shaver]
* Content coordination: [http://meego.com/users/qgil Quim Gil]
* Technical writing support: [http://meego.com/users/noel Noel Arnold]
* Content owners:
** Homepage: [http://meego.com/users/qgil Quim Gil]
** Downloads: [http://meego.com/users/mshaver Mike Shaver]
** [[ApplicationDeveloperSiteDescription|Developers]]: [http://meego.com/users/macron Ronan Mac Laverty] [http://meego.com/users/bspencer Bob Spencer]
** Projects: [http://meego.com/users/mshaver Mike Shaver] Working on new proposal.
** "Garage": [http://meego.com/users/bspencer Bob Spencer]
** Community: [http://meego.com/users/dawnfoster Dawn Foster]
*** Forum: [http://meego.com/users/reggie Reggie Suplido]
** About: '''FIXME'''
** [http://meego.com/devices/netbook Netbook]: Netbook Working Group
** [http://meego.com/devices/handheld Handsets]: Handset Working Group
** [http://meego.com/devices/in-vehicle IVI]: IVI Working Group
** [http://meego.com/devices/connected-tv Connected TV]: Connected TV Working Group
** [http://meego.com/devices/media-phone Media Phone]: Media Phone Working Group

== Process ==
'''PROPOSAL'''

* Develop working architecture diagram (ie, site map) to better handle growth in a consistent and user focused way.
* Documentation/tutorials for creating and editing content, see [[Community working group#Tasks|Community WG list of tasks]].
* Use the wiki for rapid growth. Then the consolidated pages can be agreed to move to the main site.
* Significant changes in the homepage and the main pages of each section need to be agreed first. Use the wiki to document major changes and the Community Matters forum to discuss the proposals. Bugzilla should be used to track the tasks.
* Following the point above, content owners have flexibility to improve and expand their own areas.
* Volunteers can help improving certain area at any time. Use the Community Matters forum or contact the related maintainer in order to get involved.
* Regular contributors in a specific area can request editing permissions and content ownership. Make sure the maintainers of a specific area agree with your candidacy before requesting it to the meego.com team coordinators.

== Information Architecture ==
<gallery>
File:Web_Infrastructure_Site_Map_v01.png|Web Infrastructure Overview Diagram
File:Meego.com_Site_Map_v1.1.png|Existing site map for meego.com
File:Meego.com_Home_Page_v1.0.png|meego.com home page overview
File:Meego.com_developers_section_v1.0.png|meego.com/developers sample page
</gallery>

== Tasks ==
We are using the main [[Community working group#Tasks|Community WG list of tasks]] to organize the meego.com specific work.

meego.com tasks are assigned and prioritized at the [[Community Working Group Meeting]].

If you want to suggest a new task or get a task assigned to you just follow the usual [[Community working group#Process|Community WG process]].

== Bugs ==
Bugs and enhancement requests about meego.com content or functionality must be filed at http://bugs.meego.com/enter_bug.cgi?product=meego.com

== Get involved ==
We welcome volunteers testing the site and providing feedback. Get started proposing specific improvements at [http://bugs.meego.com/enter_bug.cgi?product=meego.com bugs.meego.com], propose new content (text, graphics) and get involved in regular tasks.

* I can do some technical writing and graphics work as well --[[User:Texrat|Texrat]] 04:47, 2 September 2010 (UTC)

Web infrastructure/Meego.com

2010-12-10T23:12:50Z

Mshaver:

'''PROPOSAL''' - [http://forum.meego.com/showthread.php?t=113 discussion]

The team in charge of the maintenance, update and expansion of meego.com. Any significant change in the website content or structure is coordinated here.

== Team ==

* Webmaster: [http://meego.com/users/mshaver Mike Shaver]
* Content coordination: [http://meego.com/users/qgil Quim Gil]
* Technical writing support: [http://meego.com/users/noel Noel Arnold]
* Content owners:
** Homepage: [http://meego.com/users/qgil Quim Gil]
** Downloads: [http://meego.com/users/mshaver Mike Shaver]
** [[ApplicationDeveloperSiteDescription|Developers]]: [http://meego.com/users/macron Ronan Mac Laverty] [http://meego.com/users/bspencer Bob Spencer]
** Projects: [http://meego.com/users/mshaver Mike Shaver] Working on new proposal.
** "Garage": [http://meego.com/users/bspencer Bob Spencer]
** Community: [http://meego.com/users/dawnfoster Dawn Foster]
*** Forum: [http://meego.com/users/reggie Reggie Suplido]
** About: '''FIXME'''
** [http://meego.com/devices/netbook Netbook]: Netbook Working Group
** [http://meego.com/devices/handheld Handsets]: Handset Working Group
** [http://meego.com/devices/in-vehicle IVI]: IVI Working Group
** [http://meego.com/devices/connected-tv Connected TV]: Connected TV Working Group
** [http://meego.com/devices/media-phone Media Phone]: Media Phone Working Group

== Process ==
'''PROPOSAL'''

* Develop working architecture diagram (ie, site map) to better handle growth in a consistent and user focused way.
* Documentation/tutorials for creating and editing content, see [[Community working group#Tasks|Community WG list of tasks]].
* Use the wiki for rapid growth. Then the consolidated pages can be agreed to move to the main site.
* Significant changes in the homepage and the main pages of each section need to be agreed first. Use the wiki to document major changes and the Community Matters forum to discuss the proposals. Bugzilla should be used to track the tasks.
* Following the point above, content owners have flexibility to improve and expand their own areas.
* Volunteers can help improving certain area at any time. Use the Community Matters forum or contact the related maintainer in order to get involved.
* Regular contributors in a specific area can request editing permissions and content ownership. Make sure the maintainers of a specific area agree with your candidacy before requesting it to the meego.com team coordinators.

== Information Architecture ==
<gallery>
File:Meego.com_Site_Map_v1.1.png|Existing site map for meego.com
File:Web_Infrastructure_Site_Map_v01.png|Web Infrastructure Overview Diagram
</gallery>

== Tasks ==
We are using the main [[Community working group#Tasks|Community WG list of tasks]] to organize the meego.com specific work.

meego.com tasks are assigned and prioritized at the [[Community Working Group Meeting]].

If you want to suggest a new task or get a task assigned to you just follow the usual [[Community working group#Process|Community WG process]].

== Bugs ==
Bugs and enhancement requests about meego.com content or functionality must be filed at http://bugs.meego.com/enter_bug.cgi?product=meego.com

== Get involved ==
We welcome volunteers testing the site and providing feedback. Get started proposing specific improvements at [http://bugs.meego.com/enter_bug.cgi?product=meego.com bugs.meego.com], propose new content (text, graphics) and get involved in regular tasks.

* I can do some technical writing and graphics work as well --[[User:Texrat|Texrat]] 04:47, 2 September 2010 (UTC)

File:Meego.com developers section v1.0.png

2010-12-10T23:00:21Z

Mshaver: Sample of the potential developers section of meego.com. Most content will now live on developer.meego.com.

Sample of the potential developers section of meego.com. Most content will now live on developer.meego.com.

File:Meego.com Home Page v1.0.png

2010-12-10T22:58:46Z

Mshaver: Summary of the content areas on the meego.com home page.

Summary of the content areas on the meego.com home page.

File:Meego.com Site Map v1.1.png

2010-12-10T22:57:58Z

Mshaver: Site map of the existing meego.com structure.

Site map of the existing meego.com structure.

File:Web Infrastructure Site Map v01.png

2010-12-10T22:56:59Z

Mshaver: This diagram attempts to describe the various MeeGo services in categories of action.

This diagram attempts to describe the various MeeGo services in categories of action.

Web infrastructure

2010-11-14T15:06:53Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/qgil Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|[http://meego.com/users/bspencer Bob Spencer]
|[[SDK|details]]
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|[http://meego.com/users/agretzinger Adam Gretzinger]
|[[Mailing list guidelines|details]]
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|[http://meego.com/users/reggie Reggie Suplido]
|[[Web_infrastructure/Forum|details]]
|-
|planet.meego.com
|Midgard
|External community hosted
|ready for deployment
|
|details
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|}

Web infrastructure

2010-11-14T14:58:41Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/qgil Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|[http://meego.com/users/ericlr Eric Le Roux] [http://meego.com/users/may May Xie]
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|
|details
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|
|details
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|
|[[Web_infrastructure/Forum|details]]
|-
|planet.meego.com
|Midgard
|External community hosted
|ready for deployment
|
|details
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|}

Web infrastructure

2010-11-14T14:53:21Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/qgil Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver Mike Shaver] [http://meego.com/users/noel Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|
|details
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|
|details
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|
|[[Web_infrastructure/Forum|details]]
|-
|planet.meego.com
|Midgard
|External community hosted
|ready for deployment
|
|details
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|}

Web infrastructure

2010-11-14T14:52:28Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver|Mike Shaver] [http://meego.com/users/qgil|Quim Gil]
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|[http://meego.com/users/mshaver|Mike Shaver] [http://meego.com/users/noel|Noel Arnold]
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|??
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|
|details
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|
|details
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|
|[[Web_infrastructure/Forum|details]]
|-
|planet.meego.com
|Midgard
|External community hosted
|ready for deployment
|
|details
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.pub.meego.com api.pub.meego.com
|Community OBS
|OSU servers
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|}

Web infrastructure

2010-11-14T14:41:59Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|
|details
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|
|details
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|
|[[Web_infrastructure/Forum|details]]
|-
|planet.meego.com
|Midgard
|External community hosted
|ready for deployment
|
|details
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|Drupal 6.x
|Offsite/moving to OSU or Softlayer
|In Review
|[http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)]
|[[Application developer site|details]]
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.community.meego.com api.community.meego.com
|Community OBS
|maemo.org spare hardware.
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|}

Web infrastructure

2010-11-14T14:34:13Z

Mshaver: /* MeeGo Services */

== OSUOSL Migration ==
A plan is being drawn up for the move of all MeeGo services to OSUOSL for hosting. Look for details of the plan: [[Web_infrastructure/Planning_Security_Review|Planning and Security Review]]

== Request new services ==
[[Web_infrastructure/Processes|Here]] you can find a description about how to request new services or change requests to existing services.

== MeeGo Services ==
Like most open source projects, MeeGo has a vast number of services that keep the community functioning on a day to day basis. As the number of services grows and the number of people involved in administering these services grows, it's important to closely track. Below is a list of the various services with links to details about these services.

{| border="1" cellpadding="5"
!Service
!Platform
!Current Host
!Status
!Owners
!Details
|-
|http://meego.com
|Drupal 6.x
|Softlayer
|active
|
|[[Web_infrastructure/Meego.com|details]]
|-
|http://help.meego.com
|Drupal 6.x
|Softlayer
|active
|
|details
|-
|http://wiki.meego.com
|MediaWiki 1.15.1
|Softlayer
|active
|
|[[Web_infrastructure/Help.meego.com|details]]
|-
|http://bugs.meego.com
|Bugzilla 3.6x
|Softlayer
|active
|
|details
|-
|http://apidocs.meego.com
|Static HTML/files
|Softlayer
|active
|
|details
|-
|http://lists.meego.com
|Mailman
|Softlayer
|active
|
|details
|-
|http://forum.meego.com
|vBulletin
|external community hosted
|active
|
|[[Web_infrastructure/Forum|details]]
|-
|planet.meego.com
|Midgard
|External community hosted
|ready for deployment
|
|details
|-
|http://crashdb.meego.com
|Custom PHP
|??
|active
|
|details
|-
|developer.meego.com
|??
|none
|proposed
|
|details
|-
|http://downloads.meego.com
|??
|??
|active
|
|details
|-
|Metrics Website
|??
|??
|proposed
|
|details
|-
|Conference Website http://conference2010.meego.com/
|Drupal 6.x
|none
|active/in process
|
|details
|-
|Meeting IRC Bot
|[http://wiki.debian.org/MeetBot MeetBot]
|Stskeeps' shell in DK
|active/should migrate to central location
|
|details
|-
|povbot IRC bot (#meego) + web logs
|Supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
|mgedmin
|active/should migrate to central location
|
|details
|-
|merbot IRC bot (#meego-arm etc) + web logs
|irssi
|Stskeeps' shell in DK
|active/should migrate to central location/merge with meetbot
|
|details
|-
| MeeBot IRC bot
| supybot + [http://mg.pov.lt/irclog2html/ irclog2html]
| OSUOSL
| proposed, centralisation of meeting bot and logging
|
| [[Web_infrastructure/IRC|details]]
|-
|build.community.meego.com api.community.meego.com
|Community OBS
|maemo.org spare hardware.
|beta setup on spare hardware, currently setting up servers at OSU.
|
|details
|-
|Community Apps Website
|??
|??
|proposed
|
|details
|-
|http://meego.gitorious.org
|Gitorious
|http://meego.gitorious.org
|active
|
|[[Web_infrastructure/Meego.gitorious.org|details]]
|-
|http://transifex.moblin.org
|Transifex
|Softlayer
|active/in process of being migrated to below
|
|details
|-
|http://meego.transifex.org
|Transifex
|http://meego.transifex.org
|active/in process
|
|details
|-
|http://mxr.meego.com
|??
|http://mxr.moego.org
|active/in process
|
|details
|-
|http://tl.meego.com
|http://www.teamst.org/
|none
|active/in process
|
|details
|-
|http://hg.meego.com
|http://mercurial.selenic.com/
|Bitbucket
|none
|
|details
|-
|Patchwork
|http://ozlabs.org/~jk/projects/patchwork/
|none
|proposed
|
|[http://lists.meego.com/pipermail/meego-dev/2010-August/005169.html details]
|}

Web infrastructure/Processes

2010-11-14T11:34:42Z

Mshaver: /* Request Workflow */

== Services Definition ==
A service for MeeGo is defined as a specific project that provides some type of useful function within the community. Not all services will be user facing or be accessible by all meego.com users, but the project should be valuable to the entire MeeGo project.

It's important to review the existing services list on [[Web infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged.

== Requesting a NEW service ==
* Review [[Web infrastructure]] list
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests)

=== Request Template ===
# What service (link to tarball, package, webpage or so)
# Service description
# Purpose of service
# Estimate of 6 month user base
# Possible interdependencies between services
# Urgency
# Service owner
# Service admin(s)

=== Request Workflow ===
* Once the bug goes to assigned state this
** gets discussed at a technical level in MeegoIT team
*** Implementation effort
*** Maintenance effort
** gets sent to Community office for discussion and approval
** gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase:

* Create a component in bugzilla
** define default CC
** define QA
* Add service to list on [[Web infrastructure]]
* Creation of beta site
** testing
* Go live

== Process for a Change Request ==
* Open a bug in the service component in bugs.meego.com
* Template:
** What change
*** possible interdependencies between services
*** urgency
* gets discussed at a technical level in MeegoIT team
** Implementation effort
* gets sent to Community office for discussion and approval
* gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase.

Web infrastructure/Processes

2010-11-14T11:24:52Z

Mshaver: /* Workflow */

== Services Definition ==
A service for MeeGo is defined as a specific project that provides some type of useful function within the community. Not all services will be user facing or be accessible by all meego.com users, but the project should be valuable to the entire MeeGo project.

It's important to review the existing services list on [[Web infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged.

== Requesting a NEW service ==
* Review [[Web infrastructure]] list
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests)

=== Request Template ===
# What service (link to tarball, package, webpage or so)
# Service description
# Purpose of service
# Estimate of 6 month user base
# Possible interdependencies between services
# Urgency
# Service owner
# Service admin(s)

=== Request Workflow ===
* Once the bug goes to assigned state this
** gets discussed at a technical level in MeegoIT team
*** Implementation effort
*** Maintenance effort
** gets sent to Community office for discussion and approval
** gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase:

* Create a component in bugzilla
** define default CC
** define QA
* Creation of beta site
** testing
* Go live

== Process for a Change Request ==
* Open a bug in the service component in bugs.meego.com
* Template:
** What change
*** possible interdependencies between services
*** urgency
* gets discussed at a technical level in MeegoIT team
** Implementation effort
* gets sent to Community office for discussion and approval
* gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase.

Web infrastructure/Processes

2010-11-14T11:24:36Z

Mshaver: /* Template */

== Services Definition ==
A service for MeeGo is defined as a specific project that provides some type of useful function within the community. Not all services will be user facing or be accessible by all meego.com users, but the project should be valuable to the entire MeeGo project.

It's important to review the existing services list on [[Web infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged.

== Requesting a NEW service ==
* Review [[Web infrastructure]] list
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests)

=== Request Template ===
# What service (link to tarball, package, webpage or so)
# Service description
# Purpose of service
# Estimate of 6 month user base
# Possible interdependencies between services
# Urgency
# Service owner
# Service admin(s)

=== Workflow ===
* Once the bug goes to assigned state this
** gets discussed at a technical level in MeegoIT team
*** Implementation effort
*** Maintenance effort
** gets sent to Community office for discussion and approval
** gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase:

* Create a component in bugzilla
** define default CC
** define QA
* Creation of beta site
** testing
* Go live

== Process for a Change Request ==
* Open a bug in the service component in bugs.meego.com
* Template:
** What change
*** possible interdependencies between services
*** urgency
* gets discussed at a technical level in MeegoIT team
** Implementation effort
* gets sent to Community office for discussion and approval
* gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase.

Web infrastructure/Processes

2010-11-14T11:14:32Z

Mshaver: /* Process for requesting a NEW service */

== Services Definition ==
A service for MeeGo is defined as a specific project that provides some type of useful function within the community. Not all services will be user facing or be accessible by all meego.com users, but the project should be valuable to the entire MeeGo project.

It's important to review the existing services list on [[Web infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged.

== Requesting a NEW service ==
* Review [[Web infrastructure]] list
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests)

=== Template ===
# What service (link to tarball, package, webpage or so)
# Service description
# Purpose of service
# Estimate of 6 month user base
# Possible interdependencies between services
# Urgency
# Service owner
# Service admin(s)

=== Workflow ===
* Once the bug goes to assigned state this
** gets discussed at a technical level in MeegoIT team
*** Implementation effort
*** Maintenance effort
** gets sent to Community office for discussion and approval
** gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase:

* Create a component in bugzilla
** define default CC
** define QA
* Creation of beta site
** testing
* Go live

== Process for a Change Request ==
* Open a bug in the service component in bugs.meego.com
* Template:
** What change
*** possible interdependencies between services
*** urgency
* gets discussed at a technical level in MeegoIT team
** Implementation effort
* gets sent to Community office for discussion and approval
* gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase.

Web infrastructure/Processes

2010-11-14T11:08:58Z

Mshaver: /* Services Definition */

== Services Definition ==
A service for MeeGo is defined as a specific project that provides some type of useful function within the community. Not all services will be user facing or be accessible by all meego.com users, but the project should be valuable to the entire MeeGo project.

It's important to review the existing services list on [[Web infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged.

== Process for requesting a NEW service ==
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests)
* Template:
** What service (link to tarball, package, webpage or so)
** Service description
*** purpose
*** estimate of 6 months userbase
*** possible interdependencies between services
*** urgency
*** who needs admin access to the service
* Once the bug goes to assigned state this
** gets discussed at a technical level in MeegoIT team
*** Implementation effort
*** Maintenance effort
** gets sent to Community office for discussion and approval
** gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase:

* Create a component in bugzilla
** define default CC
** define QA
* Creation of beta site
** testing
* Go live

== Process for a Change Request ==
* Open a bug in the service component in bugs.meego.com
* Template:
** What change
*** possible interdependencies between services
*** urgency
* gets discussed at a technical level in MeegoIT team
** Implementation effort
* gets sent to Community office for discussion and approval
* gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase.

Web infrastructure/Processes

2010-11-14T11:08:26Z

Mshaver: /* Services Definition */

== Services Definition ==
A service for MeeGo is defined as a specific project that provides some type of useful function within the community. Not all services will be user facing or be accessible by all meego.com users, but the project should be valuable to the entire MeeGo project.

It's important to review the existing services list on [[Web_Infrastructure]] before submitting a NEW request. Duplication of services will be highly discouraged.

== Process for requesting a NEW service ==
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests)
* Template:
** What service (link to tarball, package, webpage or so)
** Service description
*** purpose
*** estimate of 6 months userbase
*** possible interdependencies between services
*** urgency
*** who needs admin access to the service
* Once the bug goes to assigned state this
** gets discussed at a technical level in MeegoIT team
*** Implementation effort
*** Maintenance effort
** gets sent to Community office for discussion and approval
** gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase:

* Create a component in bugzilla
** define default CC
** define QA
* Creation of beta site
** testing
* Go live

== Process for a Change Request ==
* Open a bug in the service component in bugs.meego.com
* Template:
** What change
*** possible interdependencies between services
*** urgency
* gets discussed at a technical level in MeegoIT team
** Implementation effort
* gets sent to Community office for discussion and approval
* gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase.

Web infrastructure/Processes

2010-11-14T10:56:11Z

Mshaver:

== Services Definition ==

== Process for requesting a NEW service ==
* Open a bug in 'General Requests' in bugs.meego.com (http://bugs.meego.com/enter_bug.cgi?product=General%20Requests)
* Template:
** What service (link to tarball, package, webpage or so)
** Service description
*** purpose
*** estimate of 6 months userbase
*** possible interdependencies between services
*** urgency
*** who needs admin access to the service
* Once the bug goes to assigned state this
** gets discussed at a technical level in MeegoIT team
*** Implementation effort
*** Maintenance effort
** gets sent to Community office for discussion and approval
** gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase:

* Create a component in bugzilla
** define default CC
** define QA
* Creation of beta site
** testing
* Go live

== Process for a Change Request ==
* Open a bug in the service component in bugs.meego.com
* Template:
** What change
*** possible interdependencies between services
*** urgency
* gets discussed at a technical level in MeegoIT team
** Implementation effort
* gets sent to Community office for discussion and approval
* gets sent to TSG for budget approval if needed

If all of this pass we go to the implementation phase.