I'd like to write a little bit on some of the topics.

*Q&A* *
*
As a beginner developer, I'd like to know the place where answers to all my "stupid" questions are answered. In one place. E.g.:

- How to commit to git tree? - What's the best way to submit a patch? When I asked this question on this list, I got several different answers - post to mailing list, add new bug and post a patch, do both, commit to git tree. Of course some of responders wrote that previous responders are wrong and it should be done in other way and they do it so... and so on. - How to download and compile the source without mixing it with "normal" Gimp installation?
- Who is planning Gimp's development? - How do I know what should be done in Gimp? - What are planned deadlines for next edititons of Gimp? Are there any? - an many many many other.

I think that for a start a Wiki with Q&A edited by everyone could be a good solution. If it gets too complicated, it can be split in sections, pages, categories and so on.

*Scripts*

I think that a good idea is also to include in such Wiki scripts for automated downloading sources and dependencies, updating git tree etc. Maybe not one official script, but several alternatives - each of you writing about his own script says that it does something different than others'. I imagine that such a page with scripts could look similar to a Wiki page with scripts to compile your own PHP source on Dreamhost: http://wiki.dreamhost.com/Installing_PHP5. There is one "Main PHP 5 install script "
- just for a newbie, but also several alternative scripts.

*IDE* *
*
Beginner developers that aren't independent and need some support from more experienced developers probably aren't at all used to working on an open source projects, reading through thousands of lines of new code, hundreds of files and directories. Therefore all their experience is working on some projects in Eclipse or other IDEs. I'm one a such person :) And although I tried to use kate, gedit and vim to edit code, it would be much easier for me to setup and use an Eclipse project. If some of you use IDEs, couldn't you just write on the Wiki how to setup a project in a few easy steps? Some of you will write about Eclipse, some about Qt Creator, maybe NetBeans and other.

*
*
*Tutor / supervisor* (an experienced developer)

It's a good idea to choose one or two developers responsible for the whole "Newbie Developers Boot Camp". Of course the work on Q&A, submitting scripts, guides for IDEs and maybe some other tips should be done by many developers, but someone should supervise it and make sure that these guides are really helpful for people.

From time to time I can see emails "Hey, I'd like to help you, but don't

know where to start". Some people will get this knowledge on their own (or will try to get it from IRC channels), but some won't and aren't brave enough to spam all developers on a Gimp list with his/her newbie questions.

Łukasz Czerwiński

2011/1/28 Alexia Death

2011/1/28 Łukasz Czerwiński :

I'd like to write a little bit on some of the topics. Q&A
I think that for a start a Wiki with Q&A edited by everyone could be a

good

solution. If it gets too complicated, it can be split in sections, pages, categories and so on.

Such a wiki has been started. Its hosted by me at http://gimp-wiki.who.ee and has been devised as unformal developer space. What it lacks is contributors. Joining easy. A request to me with desired wiki name and email and that's it. If you want to maintain the developer FAQ, please step up.

Oh, that's great that something already exists :)

Some time ago I've posted a list of "silly questions" that maybe raised by newbie developers. Why not place it there as a FAQ?

IDE
The wiki pointed out above already contains a howto for netbeans. Netbeans is the only ide Ive gotten to actually code-complete for me and allows me to navigate project in the manner I like. And before netbeans Ive used pretty much anything:P

Maybe Eclipse then? Anyone uses Eclipse to develop GIMP?

From time to time I can see emails "Hey, I'd like to help you, but don't know where to start". Some people will get this knowledge on their own

(or

will try to get it from IRC channels), but some won't and aren't brave enough to spam all developers on a Gimp list with his/her newbie

questions.
People who do this "Hi, im bored, give me something to hack" usually lack the commitment it takes to get into a large code base like GIMP. People who stick around and evolve into developers come to us with an issue or a plan. something they want to fix. And then they read the code and slowly get good enough. Thats the only way I know, that works. Have an idea what you want to change and then do it by asking questions. We like sensible questions. In fact, not asking questions is IMHO a good reason to flunk a student at GSoC mid-term :P If you want answers, join IRC. And stay connected long enough to answer. the last guy who did that(IRC name Acumen) had so bad connection that in the 10 minutes it took for me to see the question his link had already dropped and I had nobody to answer.

Well, I don't agree. There are (many!) people that don't know how developing an open-source program looks like and what can work on at start. So they just ask for some guidance. Maybe there should be a section on Wiki "How to become a developer?" or "Your first steps" or similar. And there: an information about IRC channel, this mailing list, how bug tracking works and that one can find some easy bugs and try to patch them.

Łukasz Czerwiński