**>From: J�rgen Thomsen <[EMAIL PROTECTED]> **>To: devel <[email protected]> **>Subject: Re: Kannel is suffering **>Date: Tue, 15 Feb 2005 23:48:11 +0100 **>In-Reply-To: <[EMAIL PROTECTED]>
[ ... lines deleted ... ] **>Exactly. **>One place to start could be better documentation of the program. **>It appears to me, that documentation of the code mainly exists in the minds of the core **>developers (a very dangerous place to store documentation), and in the C source. **>This makes it difficult for others to contribute to the architecture of the project. **>If more documentation was made, especially on the parts involved in achieving the **>ultimate goal, then a broader discussion could be had than just between a few people. **>This would both spur new ideas and more people to implement the ideas. So, when can you start helping with the documentation? I was planning to start this effort after the other 2 Kannel projects I'm working on right now. I am planning to add comments to gwlib source code. Perhaps you might like to document the bearerbox, smsbox, wapbox, or some of the smsc interface code? And, there are efforts from others that are planning to add more documentation on the architecture of Kannel. But, even without complete documentation, you can still look through the code and read the devel mailing list and get a feel for the methodology and SOP of contributing to Kannel. The last time I had a face to face conversation with one of the "core" developers (Lars) was back in 2000. Yet, I feel I understand the goals and issues relating to Kannel. Contributing to the development of Kannel is great. It should not just include R&D into code but also the philosophy of the project. Learn from the the mistakes of the 14th century missionaries. They went out to contribute to the advancement of native people. But, ultimately they destroyed the civilizaton of their "saved" people because they didn't invest the time to understand their culture. See ya... d.c.
