Maemo-Barcelona Long Weekend/Documentation

(Participants)
(Save ToC)
Line 43: Line 43:
== Participants ==
== Participants ==
* [http://maemo.org/profile/view/sebas/ Sebastián Colomar] - Maemo Wiki volunteer
* [http://maemo.org/profile/view/sebas/ Sebastián Colomar] - Maemo Wiki volunteer
 +
 +
== Developer ToC ==
 +
* Setup
 +
** Hardware
 +
*** PC
 +
*** Mac
 +
*** Windows
 +
** SDK
 +
*** Install
 +
*** Code
 +
**** C
 +
**** C++
 +
**** Python
 +
** Getting Src
 +
*** DVCS
 +
** Compile + Build
 +
** Package
 +
** Delivery
 +
*** Extras Repository
 +
*** Ovi
 +
** Test
 +
*** Tools
 +
*** Process
 +
*** QA
 +
** Appendix: Reference Links
 +
Including
 +
*** Detailed Reference Material
 +
*** UI Guidance
 +
*** UX Links
 +
 +
* Lego
 +
*** Software Architecture (top-down approach)
 +
*** Flow Suggestion
 +
Start with 'upstream' and core linux
 +
*** gtk
 +
*** dbus
 +
*** kernel
 +
Move on to Maemo services. Focus on high level APIs first and move on
 +
to deeper ones (reflects order of interaction for dev)
 +
*** location
 +
**** (library / interfaces / api)
 +
**** best practice
 +
**** tutorial / example
 +
*** telephony
 +
*** gpio
 +
*** multimedia framework
 +
*** contacts
 +
* Appendix Machine Architecture
 +
* Integration Tutorial

Revision as of 14:16, 10 December 2009

Contents

Documentation workshop

This wiki page is complemented by this discussion thread

There will be a Documentation workshop in Barcelona, where we will discuss the needs of user and developer documentation during a half day, and have a "docfest" to work on a specific wiki task for another half day.

Just now our minds are being boggled by questions on Maemo documentation. Things like: what kind of info is needed, by what kinds of users, how should it be structured so that everyone finds what they need, what's the easiest way for you to add information, questions, answers, etc? How can we get more and better info onto maemo.org, how can we get beginners up and running in the quickest way possible? What questions are boggling your mind? Where do you look for answers?

And most of all: how should Maemo documentation be produced in the future? How can we ensure that community participation in documentation writing and maintenance continues to be possible?

Join us to brainstorm on this important area!

In addition, we are asking people for short interviews on their exepriences with Maemo documentation throughout the weekend. This involves chocolate!


Schedule

Friday 4th December
Attend UX meets Code sessions, and find out expectations developers have of Maemo developer documentation
Participate in discussions of UX documentation
Saturday 5th December
Morning:
Brainstorming session, around the following core goal - how can we structure Maemo documentation and infrastructure to best facilitate work on Maemo? This question leads to others:
  • What do Maemo developers expect from documentation on maemo.org?
  • What do community documentation contributors expect from infrastructure?
  • What are the various roles of maemo.org and wiki.maemo.org?
  • How can we ensure that the Maemo wiki grows in a healthy way?
  • Should the focus of efforts be on writing new material or on cleaning up existing material?
  • What are the main places where newcomers look for information?
  • Where do more experienced Maemo community members go for information?


Afternoon:
Working session to improve some content in the wiki and on maemo.org.
  • Consolidate and improve FAQs
  • Improve navigation to wiki from maemo.org & within wiki
  • Work on maemo.org/intro as an introduction & filter page for new Maemo visitors
Sunday 6th December
Morning:
Continue workshop from Saturday, or participate in UX meets Code workshop (to be decided)

Participants

Developer ToC

  • Setup
    • Hardware
      • PC
      • Mac
      • Windows
    • SDK
      • Install
      • Code
        • C
        • C++
        • Python
    • Getting Src
      • DVCS
    • Compile + Build
    • Package
    • Delivery
      • Extras Repository
      • Ovi
    • Test
      • Tools
      • Process
      • QA
    • Appendix: Reference Links

Including

      • Detailed Reference Material
      • UI Guidance
      • UX Links
  • Lego
      • Software Architecture (top-down approach)
      • Flow Suggestion

Start with 'upstream' and core linux

      • gtk
      • dbus
      • kernel

Move on to Maemo services. Focus on high level APIs first and move on to deeper ones (reflects order of interaction for dev)

      • location
        • (library / interfaces / api)
        • best practice
        • tutorial / example
      • telephony
      • gpio
      • multimedia framework
      • contacts
  • Appendix Machine Architecture
  • Integration Tutorial