Return-Path: Message-Id: <77B155F2-6129-4953-932A-E3B62C7AA17B@holtmann.org> From: Marcel Holtmann To: BlueZ users In-Reply-To: Mime-Version: 1.0 (Apple Message framework v915) Date: Tue, 19 Feb 2008 21:43:58 +0100 References: <47B5B3FA.1050107@wurmsdobler.org> <1203101519.7664.552.camel@violet> Subject: Re: [Bluez-users] Missing: big picture Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net Hi Brian, >>> I recognise that all the developers do a great job implementing >>> features >>> and advancing fast. They do a great job, but are far too deep in the >>> matter in order to understand the comprehension difficulties of a >>> newcomer. Certainly all reasons why there is no "big picture". The >>> sparse collection of Wikis does not help either. Of course, look >>> at the >>> code is always an option, but it is time consuming. >> >> and that is the point why developers should never write >> documentation, >> because they always have a total different view point. I would >> prefer to >> have some newbie starting some documentation and let the developers >> assist him on question. People with no knowledge do the best manuals, > > The problem with this system is that you need someone to answer > users questions. > The developers don't seem to be doing that consistently on this > list. I've asked a few questions here in the past, in an attempt to > get a conceptual overview of how things work, and they were either > ignored, or I got an answer from another user, usually along the > lines of "Try this, it worked for me", an answer that sometimes > worked, but was not helpful in getting understanding. > > Please, encourage the developers to read and respond to this list-- > or should the users be posting these kinds of questions on bluez- > devel? this works very well and a lot of people spent a lot of time to answer questions on the mailing list and track down problems. However you should read this first: http://www.catb.org/~esr/faqs/smart-questions.html It is important to understand what you can expect and what not. Also you go to #bluez on freenode.net and ask questions. My advise would be to start some documentation inside the wiki and then ask questions. Asking them up-front without showing that you will contribute to the project doesn't go good with any developers of any open source project. The secret is to give something back and you would be surprised how much help you can get quite quickly. Regards Marcel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users