Getting involved

The Maemo community is an active one, and there are lots of areas to get involved and help out. This is an overview of a few of those areas and how to get involved. As you will get more involved, you will see your karma level rise, and your name will climb the Maemo community karma list.

Contents

[edit] maemo.org

There are many ways to get involved with maemo.org and its development.

[edit] maemo.org content

Once you create a Maemo profile you will be able to add comments to your favourite products and rate them, you will be able to favourite or bury blog posts and maemo.org news items, and you will be able to edit pages in the wiki. There is a dedicated page with tips on writing maemo.org content, including how to get access to various resources.

[edit] Bugzilla

Bugzilla is maemo.org's bug tracker. The Bugsquad is the place to go to get involved there. They're always looking for people to help out triaging incoming bugs, and keeping tabs on existing ones.

[edit] Brainstorm

Brainstorm is where proposals for enhancements, new features, new applications etc can be put to the community for discussion. All community members can post their ideas here, and developers are encouraged to look for ones they could help out with. For more information on the Brainstorm process see Brainstorm Intro.

[edit] Wiki

The wiki is always in need of more help and the Wiki gardeners is an excellent place to start if you're looking for areas to help out. If you're not looking for too much structure, you'll likely find small typos and grammatical errors to fix while browsing around. New articles are always highly appreciated!

[edit] API documentation

Most of Maemo's API documentation is available in source format along with the source code. Most of the source code for Maemo-specific components is available via Gitorious.

For example, the libhildondesktop API documentation is generated using gtk-doc from comments in the source code, which is available via Gitorious.

To get a copy of the source code, clone the Gitorious module, and make changes to the relevant comments in the source code - for example, the symbol hd-home-plugin-item-heartbeat-signal-add is documented (at the time of writing) between line 564 and line 585 in the file hd-home-plugin-item.c.

To propose a change to API documentation, submit your proposed change as a patch (in the diff -u format) to a relevant bug in Bugzilla, and if your change is accepted, it will be applied.

Other modules use Doxygen to document APIs rather than gtk-doc - aside from the tool and the mark-up used in the documentation, the rest of the process remains the same.

[edit] Forums

talk.maemo.org, as well as the maemo.org users forum is a great place to get help and hang out with fellow Maemo users. German-language readers may want to read maemousers.de.

Retrieved from "http://bugs.maemo.org/Getting_involved"