Announcing GNU Radio Release 3.0 RC 1

All,

We’ve created release candidate 3.0rc1 for testing:

http://gnuradio.org/releases/gnuradio/gnuradio-3.0rc1.tar.gz

The tarball contains most of the components that exist on the trunk;
however several have been held back because they are either experimental
in nature or will likely be moved to a ‘contrib’ type distribution in
the future.

Contained in release 3.0rc1 are:

gnuradio-core
gnuradio-examples
gr-audio-alsa
gr-audio-jack
gr-audio-oss
gr-audio-osx
gr-audio-portaudio
gr-audio-windows
gr-gsm-fr-vocoder
gr-how-to-write-a-block
gr-radio-astronomy
gr-trellis
gr-usrp
gr-video-sdl
gr-wxgui
usrp

Not contained in the release but still available via svn on the trunk:

ezdop
gr-atsc
gr-comedi
gr-error-correcting-codes
gr-ezdop
gr-pager
gr-radar
gr-rdf
mblock
pmt

Building GNU Radio using the release tarball is only slightly different
from building from the SVN repository. You do not need to have automake
or autoconf installed, and you do not run the first ‘bootstrap’ command.
Other than that, everything else is the same, including the the build
dependencies that must be satisfied.

Release 3.0 will contain only incremental functionality over release
2.8; however, this represents the first release using the integrated
build system and combined distribution.

Please download the release candidate tarball and give it a whirl. You
can report problems via the Trac system at:

http://gnuradio.org/trac

To create a ticket, you must log in as ‘guest’ with password ‘gnuradio’.
Please make sure you indicate 3.0rc1 as the software version; the SVN
trunk has now been revved to 3.0svn.

I will be putting up a Wiki page for the release “soon”.

Johnathan C., AE6HO
[email protected]

Johnathan C. wrote:

Release 3.0 will contain only incremental functionality over release
2.8; however, this represents the first release using the integrated
build system and combined distribution.

Would it be possible to compile something like a NEWS file with all new
features, enhancements and fixes from the last version (2.8)? This could
be done via the list.

I think this would be a great thing for showing regular readers and
bystoppers what’s going on in the project. Of course people reading the
list are up to date, but it’s not easy to see what was achieved in the
say last year or half year. With a listing of achievements people can
better realize what a fine thing GNURadio is and how fast it is moving
forward.

Morover there are a couple of tutorials out there that would be fine to
be compiled in a list in the Wiki (that could be linked to from the
release docs). I suggest people just throw in their links on the list.

Are there any licence issues if we want to copy the tutorial’s contents?
I guess authors mast give their OK, but what else? Licence?

Patrick

Engineers motto: cheap, good, fast: choose any two
Patrick S.
Student of Telematik, Techn. University Graz, Austria

Patrick - The following are my beliefs and understandings on the
“just copy it” tutorial issue; I’m sure the list will correct me
where I’m wrong (;). Sorry if it all sounds absurd; it IS to some
degree, but that’s the way our society has progressed when it comes
to IP and covering one’s bases.

Dawei’s tutorial has recently become available for my group (UND, EE,
JNL) to (re)post and (to the best of my knowledge and understanding)
update; I certainly hope this is the case because, as Eric points
out, the tutorial is far enough out of date that its use is of
marginal value. And, my group, being heavy users of GR, holds
significant value in our works and hence will make all reasonable
efforts to keep the tutorial updated. - MLD

Quick version

I wish it were as simple as “just copy it”, but these days
intellectual property (IP) is a hot item, and these tutorials are
IP. “Just copying” IP w/o the author’s (and possibly others’)
permission could result in lawsuits; folks generally just don’t want
to go there (even if they could afford to). Further, having a
license to -copy- doesn’t always grant a license to -modify-, so even
if someone did copy a tutorial (with or without permission) does not
necessarily mean that that tutorial can be legally updated. There
are a number of complications to the issue, which is why GR
developers sign over © and license rights to the FSF via a physical
(USPS) letter of agreement.

Longer version

Are there any licence issues if we want to copy the tutorial’s
contents?

YES! There are potentially huge issues if those tutorials are just
copied without permission unless they are already under a license
which -explicitly- grants that permission. Even if the license
grants -copying- it might not grant -modifying-.

I guess authors mast give their OK, but what else? Licence?

A written statement from the author(s) is the best way to get
permission - e.g. a digitally signed email would probably suffice for
these install guides (not good enough for general GR code submission
though, understandably); a USPS notarized letter (of appropriate
content) would be even better but I don’t think anybody’s expecting
that level of anality for these tutorials (I might be wrong; folks
really like to cover their bases these days). It’s always good if
the author(s) put the tutorial under an appropriate OSS license (e.g.
Creative Commons or GPL), since those allow for copying so long as
the content (including the license info) isn’t modified beyond (re)
formatting. But, generally, for -modifying- one really wants to gain
the owner’s permission (in some verifiable form, not just a non-
digitally-signed email, which could be easily faked) unless the
license is quite explicit about that aspect of ownership.

You’ll notice that my OSX install guide is linked into the GR Wiki,
but I haven’t copied it there. I’m required by my school (UND) and
my department (EE) and my advisor (JNL) to copyright the document to
them, and / or provide an appropriate license so that they can have
royalty-free access to the document; the license and © are in the
works as we transition from personal WWW pages into sdr.nd.edu .
While certainly I could just “copy it over”, technically I have to
gain permission from UND (UND, EE, JNL) to do so - which from past
experience is somewhat of a PITA (UND). Hence just the link to the
tutorial at this time.

Also, just because I am required to license my works while at UND to
UND, this does not grant UND permission to -modify- those works.
This permission must come from me explicitly, in writing, etc…
Now, of course, I’m not unreasonable about my dealings with UND since
they allow me to get my grad education there … but IP is still IP
and I need to protect mine as much as you should be protecting yours.

Patrick S. wrote:

Would it be possible to compile something like a NEWS file with all new
features, enhancements and fixes from the last version (2.8)? This could
be done via the list.

Eric and I discussed this. You’re right–it’s a very good thing to do,
albeit one of the less glamorous parts of doing software. It would have
been best if we accumulated these things into a NEWS file as they were
done, but we did not. Volunteers welcome :slight_smile:

The intrepid can always read the log history for a particular component
via the Trac interface. That doesn’t help people just “stopping by”, as
you say, but at least it’s there.

Morover there are a couple of tutorials out there that would be fine to
be compiled in a list in the Wiki (that could be linked to from the
release docs). I suggest people just throw in their links on the list.

Or just as easily on a Wiki page. Username ‘guest’, password
‘gnuradio’.

-Johnathan

Eric B. wrote:

There should be a (brief) NEWS file in the tarball. It was in the tree.
Johnathan, if it’s not in the tarball, can you please add it to
EXTRA_DIST.

It’s there.

Johnathan C., AE6HO
[email protected]

On Fri, Sep 29, 2006 at 08:16:01PM -0700, Johnathan C. wrote:

Patrick S. wrote:

Would it be possible to compile something like a NEWS file with all new
features, enhancements and fixes from the last version (2.8)? This could
be done via the list.

Eric and I discussed this. You’re right–it’s a very good thing to do,
albeit one of the less glamorous parts of doing software. It would have
been best if we accumulated these things into a NEWS file as they were
done, but we did not. Volunteers welcome :slight_smile:

There should be a (brief) NEWS file in the tarball. It was in the tree.
Johnathan, if it’s not in the tarball, can you please add it to
EXTRA_DIST.

Eric

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs