| Line 1: | Line 1: | ||
== Current Status == | == Current Status == | ||
| - | === FW | + | === FW 37 === |
| - | The | + | The Drupal implementation work has started and a pilot site with some functionality is expected this week. The initial reference guide for the MeeGo API has been produced, mapping the MeeGo architectural services to lower-level APIs, to make the MeeGo API a conceptual whole. This needs theme-ing to match the rest of the site, this work has started, and is ongoing. |
== Old statuses == | == Old statuses == | ||
| + | |||
| + | === FW 35 === | ||
| + | |||
| + | The wireframe design for the developer.meego.com site have been approved by the Maemo UI Lead. There was one comment: the 3rd level landing pages might be too heavy for continuous maintenance. The response to this comment is to use the pilot test site for checking the level of drupal experience required to edit content. | ||
=== FW27 === | === FW27 === | ||
Contents |
The Drupal implementation work has started and a pilot site with some functionality is expected this week. The initial reference guide for the MeeGo API has been produced, mapping the MeeGo architectural services to lower-level APIs, to make the MeeGo API a conceptual whole. This needs theme-ing to match the rest of the site, this work has started, and is ongoing.
The wireframe design for the developer.meego.com site have been approved by the Maemo UI Lead. There was one comment: the 3rd level landing pages might be too heavy for continuous maintenance. The response to this comment is to use the pilot test site for checking the level of drupal experience required to edit content.
There is a draft information architecture available for review and feedback here, this has been bounced around between Nokia and the maintainers of the www.meego.com site. There will be wireframe designs for the top level of the hierarchy available for review soon (scheduled for FW28, but it's the holiday season).
One outcome of the discussion is that this site will lose its marketing focus and become more like other development sites, such as developer.android.com, so there will be less emphasis on attracting new developers.
We have a partner for the development of the developer.meego.com site, ActiveArk. In addition to ActiveArk, there is another company involved, Datafisher, that specialized in online pedagogical design. Both companies have a strong Drupal background, and during the selection process, both companies had clear ideas on how to differentiate from other developer sites.
So far this week we have had some meeting about the way of working (basecamp has been chosen as a project management tool), and are putting together the project team.
The current status is that Nokia has contacted several design agencies who are capable of creating web site design with additional material. The initial offers have been received, and Nokia is now choosing which subcontractor to use for this work.
The key criteria for choosing the subcontractor:
The deadline for the decision on the subcontractor will be FW22-23.