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 ===
-
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:
-
layers that build on it. The inter-relationships, examples for processes and
+
** The context of the current middle ware discussed.
-
events etc (dbus, dsme etc)
+
** What's beneath it (another layer, the bare metal?), What's on top of it?
-
* Breakdown to subsystems: Have a section per each one, links to
+
** Nature of inter-relationships: How does it communicate with other components if at all? How does it communicate with hardware?
-
read about the architecture, libs it uses, important bugs for triage
+
 
-
and fix, where offline development discussions happen, low hanging fruits
+
* Breakdown to subsystems:
-
for people wanting to become platform hackers.
+
** Each component have a section with links or content to:
-
* Background for the UI parts and follow the same breakdown as for (2) ??
+
*** Read about the architecture.
-
* Each component resulting in a binary should have a links to the proper documentation for it.
+
*** Libraries and binaries it uses,
 +
*** Current important bugs for triage and fixing, tagged with difficulty level.
 +
*** Find out where offline development discussions happen.
 +
*** Learn about low hanging fruits; not just bug fixing and feature implementation!
 +
* Background for the UI parts and perhaps follow the same breakdown as for (2) ??
 +
* Each component resulting in a binary should have links to the proper documentation for it, or a mention where docs are in the RPM packages itself.

Revision as of 11:42, 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

  • Background of the user-space and middle ware stack:
    • The context of the current middle ware discussed.
    • What's beneath it (another layer, the bare metal?), What's on top of it?
    • Nature of inter-relationships: How does it communicate with other components if at all? How does it communicate with hardware?
  • Breakdown to subsystems:
    • Each component have a section with links or content to:
      • Read about the architecture.
      • Libraries and binaries it uses,
      • Current important bugs for triage and fixing, tagged with difficulty level.
      • Find out where offline development discussions happen.
      • Learn about low hanging fruits; not just bug fixing and feature implementation!
  • Background for the UI parts and perhaps follow the same breakdown as for (2) ??
  • Each component resulting in a binary should have links to the proper documentation for it, or a mention where docs are in the RPM packages itself.
Retrieved from "http://wiki.meego.com/User:Stskeeps/MeeGo_Hacker_Guide"
Personal tools