[Adium-devl] Suggestions to help people get comfortable with the Adium code

[Chris Stewart]

As I've been struggling these past few weeks/months I've kept tabs on a few
items I think would be helpful for new developers of Adium.

1. A visual diagram of how Adium is structured.  I think it would be helpful
to visually see the different components that make up Adium.  For each
component, you could list where in the code the developer can find the
relevant source.

2. A visual representation of how Adium actually works.  I think any sort of
visual on how the notification piece to Adium works would be helpful for
people to understand how Adium actually works.

3. If it exists, a list of the people that maintain or are generally
involved with the different components of Adium.  So if someone starts
working on a specific section they'll know who to contact about design and
potential issues that may arise.

4. It would help to be able to easily find this information from the Trac (
http://trac.adiumx.com/) page on the bottom right side of the page.  Or,
possibly, to make that bottom right side of the page the focus on the page
itself instead of the search.

During this time I've also found a bunch of things that have helped me get
aquainted to the project.

1. The development mailing list!  I couldn't get anything done without
access to this list.  I learn a ton from watching the communication go back
and forth.

2. The IRC channel.  While I'm not a constant visitor, I have used it for
quick questions and it has proven very useful.

3. The development team has been very helpful and interested in getting me
started to contribute.  That goes along ways. :)

Anyway, I hope some of these are seen as useful to others.

-- 
Chris Stewart
compiledmonkey at gmail.com
http://www.compiledmonkey.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20061207/926fb363/attachment-0001.html>