Meego Wiki
Views

Web infrastructure/Meego.com

From MeeGo wiki
< Web infrastructure(Difference between revisions)
Jump to: navigation, search
(Process)
(Information Architecture)
 
(15 intermediate revisions not shown)
Line 4: Line 4:
== Team ==
== Team ==
-
 
-
''ToDo: go through the main section and find out who are the factual maintainers. Then ask them whether they should be considered final maintainers or not. Rationale: many pages were created in the scope of the MeeGo launch and perhaps the people that created them are not the ones meant to own them regularly.''
 
* Webmaster: [http://meego.com/users/mshaver Mike Shaver]
* Webmaster: [http://meego.com/users/mshaver Mike Shaver]
* Content coordination: [http://meego.com/users/qgil Quim Gil]
* Content coordination: [http://meego.com/users/qgil Quim Gil]
 +
* Technical writing support: [http://meego.com/users/noel Noel Arnold]
* Content owners:
* Content owners:
** Homepage: [http://meego.com/users/qgil Quim Gil]
** Homepage: [http://meego.com/users/qgil Quim Gil]
-
** Downloads: '''FIXME'''
+
** Downloads: [http://meego.com/users/mshaver Mike Shaver]
-
** Developers: '''FIXME'''
+
** [[ApplicationDeveloperSiteDescription|Developers]]: [http://meego.com/users/macron Ronan Mac Laverty] [http://meego.com/users/bspencer Bob Spencer]
-
** Projects: '''FIXME'''
+
** Projects: [http://meego.com/users/mshaver Mike Shaver] Working on new proposal.
-
** "Garage": '''FIXME'''
+
** "Garage": [http://meego.com/users/bspencer Bob Spencer]
-
** Community: '''FIXME'''
+
** Community: [http://meego.com/users/dawnfoster Dawn Foster]
 +
*** Forum: [http://meego.com/users/reggie Reggie Suplido]
** About: '''FIXME'''
** About: '''FIXME'''
-
** [http://meego.com/devices/netbook Netbook]: '''FIXME'''
+
** [http://meego.com/devices/netbook Netbook]: Netbook Working Group
-
** [http://meego.com/devices/handheld Handsets]: '''FIXME'''
+
** [http://meego.com/devices/handheld Handsets]: Handset Working Group
-
** [http://meego.com/devices/in-vehicle IVI]: '''FIXME'''
+
** [http://meego.com/devices/in-vehicle IVI]: IVI Working Group
-
** [http://meego.com/devices/connected-tv Connected TV]: '''FIXME'''
+
** [http://meego.com/devices/connected-tv Connected TV]: Connected TV Working Group
-
** [http://meego.com/devices/media-phone Media Phone]: '''FIXME'''
+
** [http://meego.com/devices/media-phone Media Phone]: Media Phone Working Group
== Process ==
== Process ==
Line 27: Line 27:
* Develop working architecture diagram (ie, site map) to better handle growth in a consistent and user focused way.
* 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.
* 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.
* 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.
Line 32: Line 33:
* Volunteers can help improving certain area at any time. Use the Community Matters forum or contact the related maintainer in order to get involved.
* 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.
* 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 ==
== Tasks ==
Line 41: Line 52:
== Bugs ==
== Bugs ==
-
Bugs about meego.com content or functionality must be filed at http://bugs.meego.com/enter_bug.cgi?product=meego.com
+
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)

Latest revision as of 23:22, 10 December 2010

PROPOSAL - 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.

Contents

Team

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 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

MeeGo Site Maps OmniGraffle file

Tasks

We are using the main 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 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 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 --Texrat 04:47, 2 September 2010 (UTC)
Personal tools