Meego Wiki
Views

User:Stskeeps/MeeGo Hacker Guide

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Theory: Stuff which will make life easier, engage, and profit properly understood)
(→Theory: Stuff which will make life easier, engage, and profit properly understood)
Line 23: Line 23:
=== Theory: Stuff which will make life easier, engage, and profit properly understood ===
=== Theory: Stuff which will make life easier, engage, and profit properly understood ===
-
A suggested content would be:
+
I suggest including the following:
-
** Background of the user-space and middle ware stack used to power
+
* Background of the user-space and middle ware stack used to power
layers that build on it. The inter-relationships, examples for processes and
layers that build on it. The inter-relationships, examples for processes and
events etc (dbus, dsme etc)
events etc (dbus, dsme etc)
-
** Breakdown to subsystems: Have a section per each one, links to
+
* Breakdown to subsystems: Have a section per each one, links to
read about the architecture, libs it uses, important bugs for triage
read about the architecture, libs it uses, important bugs for triage
and fix, where offline development discussions happen, low hanging fruits
and fix, where offline development discussions happen, low hanging fruits
for people wanting to become platform hackers.
for people wanting to become platform hackers.
-
** Background for the UI parts and follow the same breakdown as for (2) ??
+
* Background for the UI parts and follow the same breakdown as for (2) ??
-
** Each component resulting in a binary should have a links to the proper documentation for it.
+
* Each component resulting in a binary should have a links to the proper documentation for it.

Revision as of 11:35, 26 October 2010

DRAFT

Hands On: Setting up your workshop

You'll need:

  • An OBS account on either build.meego.com or cbuild.meego.com (use your meego.com login) or on your own OBS with MeeGo release(s) imported.
  • These tools installed on your development machine:
    • Spectacle, autospectacle (on gitorious)
    • MIC2
    • osc
    • Standard development tools (git, wget, svn, make, diff, patch, rsync, ssh, dd, gdb)
    • A graphical web browser (Firefox, Chrome, etc..)

You might need:

  • For local OBS builds, something supporting SSSE3 instructions (this applies for ARM builds too)
  • qemu-arm installed, vdso=0

.. tools to grab images/releases? .. zypper instructions .. proxy instructions, NAT wlan


Theory: Stuff which will make life easier, engage, and profit properly understood

I suggest including the following:

  • Background of the user-space and middle ware stack used to power

layers that build on it. The inter-relationships, examples for processes and events etc (dbus, dsme etc)

  • Breakdown to subsystems: Have a section per each one, links to

read about the architecture, libs it uses, important bugs for triage and fix, where offline development discussions happen, low hanging fruits for people wanting to become platform hackers.

  • Background for the UI parts and follow the same breakdown as for (2) ??
  • Each component resulting in a binary should have a links to the proper documentation for it.
Retrieved from "http://wiki.meego.com/User:Stskeeps/MeeGo_Hacker_Guide"
Personal tools