“Code-parrots” is totally being added to my lexicon going forward lol
73, N2ADV > On Aug 27, 2020, at 11:36 AM, Fons Adriaensen <f...@linuxaudio.org> wrote: > > On Thu, Aug 27, 2020 at 12:01:53PM +0100, Bill Somerville wrote: > >> you are ignoring those that would take the unfinished work in progress, >> despite protocols not being finalized, and copy the code parrot fashion into >> their so-called derivative products, which they then release as "complete" >> before the original authors have even made a public release. All this >> despite being politely asked not to do just that until the protocols are >> fixed. > > That is indeed a problem with most open source software, it has hit me > as well as developer of audio-related applications. > > But IIRC the OP asked for a description of the protocols, i.e. a design > document, not for ready-to-use code. Surely such documentation does exist, > and I doubt very much it would help the code-parrots who probably don't > even understand the basics. > > Ciao, > > -- > FA > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
