Bruce I have to say I take offense to a comment like that.
I'm trying to make something that will benefit the whole FreeDV community. Yes I don not work on much open source code for the very reason that you describe. It's usually poorly documented, mish mash of code, written in different styles that is difficult to maintain and even more difficult to manage code integrity. I am far more used to developing code for clients that work to well documented code structures and conform to standards that allow for tractability, interoperability and reliability. The kind of code some one can come in years latter and easily update parts to reflect hardware changes or operational needs. In fact with so many people working on an open source project I would have thought it becomes essential to maintain such documentation, commenting and coding standards are the only way to maintain reliability. As I had not found such documentation and with the code not written to embedded C standards I was simply asking, that some one with extensive experience in this project would perhaps be able to help me and get me started. Certainly there are large sections of the project that are not needed and I see no point in wasting time looking at those. A neat simple project with the required files will make coding and reworking far easier. I am sorry that you feel your experience must be kept secret and that I must go it alone and work it out my self. I was hoping to bring significant benefits to the FreeDV project as I thought I had already proven with the hardware contribution and commitment I have made. My time is limited and I do not need to spend hours or days familiarising my self with sections of code I may never need to change or work on again. I have to thank Glenn and Brady for their constructive information that has helped me out a lot and I hope that they dont mind doing so as their posts are truly informative and helpful and a valuable source of guidance in such a project. Regards Eric On 2016-09-07 07:09, Bruce Perens wrote: > Eric, > > When you work with an Open Source project, you are not expected to need > documentation of the overall structure of the code, or a list of the > essential files, or a timing diagram, or an explanation of the interrupt > priority (we already told you it's a busy loop, which means there is no > interrupt priority). > > You are expected to read the code and figure all of that out for yourself. > The code is actually not all that difficult. > > Think of it as a test. You might not be ready to work on this sort of > project. > > Sorry > > Bruce > > ------------------------------------------------------------------------------ > > _______________________________________________ > Freetel-codec2 mailing list > Freetel-codec2@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 [1] Links: ------ [1] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
------------------------------------------------------------------------------
_______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
