On Wed, Oct 15, 2008 at 9:11 AM, Greg Troxel <[EMAIL PROTECTED]> wrote:
> So I think the top-level question is whether CGRAN is for code that > isn't assigned. I think that's the only thing that makes sense; people > with assignments can more or less work directly in the gnuradio.org > repository. Maybe there are some overlapping issues here. Suppose, for example, I have some code that's more Cognitive-Radio-related than Software-Defined-Radio, really. It uses Orange < http://www.ailab.si/orange>, which is GPL but not assigned to FSF. At least for now it can't go into the GNU Radio tree. Probably it never will. It's also true that this (my) code is experimental and provisional. It's nothing more than a steppingstone. (The obvious place to put it would be a developer branch, but that's part of the tree.) Perhaps I doubt whether, in its current form, it *should* go into the tree. But that's no reason not to make it visible and easily accessible, if only as a scaffolding for later code destined for the tree. There is also some quantity of code which is useful and usable right now, but which doesn't currently fit well with the unified installation procedure for the GR tree. I'm thinking here primarily of Linux audio subsystem code that uses scons. It seems obvious there has to be a place for GNU Radio code that's GPL but will not be assigned to FSF, with certainty. I believe there should also be a place for code whose status is *uncertain* -- in short, a place with minimal obstacles to publishing early and often. Frank -- I have taken the stand that nobody can be always wrong, but it does seem to me that I have approximated so highly that I am nothing short of a negative genius. -- Charles Fort
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
