[Bf-committers] Reorganizing the development section - ideas

[Shaul Kedem]

Hi all,
I've been asked by ton to take a look at the development section and
suggest how can some order be put into it.

I have a couple of suggestions, but mainly I would like to hear what
you think about it;

My ideas are:
- Having an overall diagram of the path a new developer should take
when starting to learn blender code. The steps are:
   1. Understand the architecture
   2. Learn one topic from step 5.
   3. Code a small module/fix in the topic
   4. let someone look at that fix (use of patch, discuss in forum,
irc, ml, etc.)
   6. Learn topics; we need to divide this into digestible areas which
are not directly connected, for example: UI, renderer, export, file
handling, sdna (maybe sub divide this..), etc.
   7. Learn the coding conventions
   8. The bug tracker
   9. Open projects list + Ideas floating around
  

In this way the new coder will be able to either start from the top
and go down in the steps, learning from broader view to detailed one,

He/she will be able to go the other way, starting from an interesting
project and learning the appropriate project's code,

Or the coder will be able to view the different areas "from the bird's
eye" and decide what he/she wants to focus in each step,

Any thoughts? concerns? constructive criticism?

Regards,
Shaul