Let's talk about it

This was one of my first questions in the project: How can we talk about stuff? I mean stuff like concepts or code that I don't understand, proposals to change or extend concepts or code, org stuff like where I can upload new specs or patches, and so on.

My first concerns were (and still are), that I could step on someone's nerves when discussing things in public mailing lists or IRC channels. Not everyone is interested in my questions, proposals, or even in the project. After being convinced by my mentors Roger and Nick I decided to give it a try. This is why the developers' mailing list is a little overcrowded by my questions at the moment. Sorry! I promise that this will at least decrease in the future.

Further, one needs to be even more careful what to write to a public mailing list, because it will be archived and read by even more people than the mentors who might pardon a silly question or proposal more easily. However, thinking about how to write a question once more is never a bad thing. And you are faced with the same problem when writing a blog entry, though. :)

A third concern to think about is that everyone can directly participate in your thoughts. Sounds egoistic, but in academia---as I know it---it's always an advantage to be some months earlier than others. Write a paper before someone else does. And papers are money. So, when talking about ideas in public you risk to bite the hand that feeds you. On the other hand I would not like to hide 3 years in my room just to come out with a unique idea. After all that takes too much time. I decided to take the plunge.

My conclusion is that I will try to make this project as open as I can. If someone feels that it's too much of a good thing, tell me. But I think that it's better to move a discussion from public to private rather than start a discussion in private that ought to be public.