| |
ZL3AI > APRDIG 20.12.03 09:25l 242 Lines 10145 Bytes #999 (0) @ WW
BID : 2520-ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 17, 1/4
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<ON0AR<ZL2BAU<ZL2BAU<ZL3VML
Sent: 031220/0705Z @:ZL3VML.#80.NZL.OC #:14975 [Chch-NZ] FBB7.00i $:2520-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Wednesday, December 17, 2003.
1. Re: Open source licensing
2. Re: Open source licensing
3. Re: Open source licensing
4. Re: Holiday Traveling = 144.39 CTCSS 100
5. Re: TNC-X is Now Shipping
6. Re: Holiday Traveling = 144.39 CTCSS 100
7. Re: Open source licensing
8. Re: Open source licensing
9. Re: Power Poles Double Duty
10. Re: Holiday Traveling = 144.39 CTCSS 100
11. Weather warning
12. Re: Weather warning
13. Re: Weather warning
14. Re: Weather warning
15. Re: Weather warning
16. Re: Weather warning
17. RE: Weather warning
18. Re: Holiday Traveling = 144.39 CTCSS 100
19. FS: Kenwood TH-D7A(G) w/ accessories
20. Re: FS: Kenwood TH-D7A(G) w/ accessories
21. Help: KPC3+ Schematic or PTT transistor #
22. Re: Holiday Traveling = 144.39 CTCSS 100
23. Re: Holiday Traveling = 144.39 CTCSS 100
24. Re: Help: KPC3+ Schematic or PTT transistor #
25. Re: Help: KPC3+ Schematic or PTT transistor #
26. Re: Help: KPC3+ Schematic or PTT transistor #
----------------------------------------------------------------------
Subject: Re: Open source licensing
From: "Byon Garrabrant" <byon@byon.com>
Date: Tue, 16 Dec 2003 23:19:54 -0800
X-Message-Number: 1
On 15 Dec 2003 at 22:28, John Hansen wrote:
>To me this is an incredibly interesting and worthwhile discussion. I
>know
>it is a bit off topic for an APRS group, but I'm hoping Stan will let
>it go a bit.
I agree. I'm just now catching up with the discussion.
For me, the goal of TinyTrak was to make a inexpensive APRS tracker
that anyone could build for themselves. I did not, however, want to
see others selling the chips or kits with the firmware I created. I
released the HEX (but not the source) so anyone could build it
entirely on their own. I included in tinytrak.zip the following:
-------------------------------------------------------------------
This software is available only for non-commercial amateur radio
or educational applications. ALL other uses are prohibited.
This software may not be distributed by anyone other than the
author. Contact the author for information on commercial licenses.
(c)Copyright 1999-2001, Byon Garrabrant, N6BG. All rights reserved.
-------------------------------------------------------------------
I also included right next to the download button on the web site:
-------------------------------------------------------------------
Please do not distribute TinyTrak software, firmware, or
documentation without written permission from the author.
-------------------------------------------------------------------
I don't know which license this is similar to, but it seems to me to
be pretty strict. IOW: If you want it, take it. but if you want
others to have it, have them come to get it from me.
For the most part, it was honored. I've been VERY impressed with the
integrity of the ham community as a whole. But there were people who
made and sold TinyTrak kits without permission. And I realized, with
frustration, that there was not much I could, or was financially
willing to, do about it.
So, my solution was to not release the firmware for TinyTrakII and
TinyTrak3. It no longer allowed people to build entirely on their
own, but for less than $20, and a stocked parts bin, home brewers
still could play. Plus, the original TinyTrak .HEX is still
available. I still include the plead:
-------------------------------------------------------------------
Please do not distribute TinyTrak, TinyTrakII, or TinyTrak3 software,
firmware, or documentation without written permission from the
author.
-------------------------------------------------------------------
While no doubt there are still people out distributing TinyTrak3
chips, I would suspect there are less than those who did for
TinyTrak, and it is definitely now more difficult to do.
My lesson was that a license may not be sufficient to prevent others
from using you work commercially.
Byon
PS: I would love a legal talk at a future DCC!
----------------------------------------------------------------------
Subject: Re: Open source licensing
From: Adi Linden <adil@adis.on.ca>
Date: Wed, 17 Dec 2003 01:22:24 -0600 (Central Standard Time)
X-Message-Number: 2
I would love to see more open source projects hardware and software
projects that are relevant to amateur radio. I can tell you that the few
things I am working away on are open source. The question of whether BSD
or GPL is really a matter of how many strings are attached.
Amateur Radio is a hobby for me. None of the projects I have going are
intended to make me rich or even recover the work I put in. They're for
pure personal enjoyment. Seeing others make use of and appreciate the work
(once there's something worth sharing or publishing) is my reward.
I have a big complaint, though. I have seen very few complete amateur
radio related projects that are true open source.
I have an IRLP node which I'd love to make some changes to. Unfortunately
IRLP is not open source, neither software nor hardware. Sure, I could
reverse engineer, but then I am faced with a dilemma. I cannot share my
work with anyone without offending the original author who didn't make
IRLP open source for whatever reason.
I'd love to work with and contribute some ideas to an APRS tracker
project. Last year I was unable to find anything open source that was
already basically functional. I didn't want to start a project from
scratch, reinvent the wheel so to speak.
I've looked at a repeater controller recently that promised to be open
source. Unfortunately the product is now closed source. Hopes of working
with the existing code base and contributing to the effort have been
crushed. In this case I am proceeding to reinvent the wheel and roll my
own open source controller project.
While I personally don't like the non-commercial clause, it is certainly
much better than having the project closed source. I can see how the
non-commercial issue could hinder contributions to the project. How will
non-commercial impact distribution of the code? What does it mean to
derivative works?
Adi
--
Adi Linden | va3adi | va3adi@adis.ca | http://adis.ca
+-----------------------------------------------------------------+
IRLP Node 2590 in Sioux Lookout, Ontario
----------------------------------------------------------------------
Subject: Re: Open source licensing
From: Jeff King <jeff@aerodata.net>
Date: Wed, 17 Dec 2003 02:43:26 -0500
X-Message-Number: 3
If this is what you put on your software, it is good enough to shut down the
copy-caters on Ebay and even on their U.S. websites via DMCA .
Read up on it, you don't need a lawyer, and if the offender is stupid, they
won't know how to properly respond, and you'll prevail without any court
action what-so-ever. Most people don't know the DMCA, and it gives you as the
copyright holder first bite of the apple. It will work in 99% of the cases
without going to court and it is free.
--
Jeff King, jeff@aerodata.net on 12/17/2003
----------------------------------------------------------------------
Subject: Re: Holiday Traveling = 144.39 CTCSS 100
From: WA8LMF2@aol.com
Date: Wed, 17 Dec 2003 03:06:16 EST
X-Message-Number: 4
In a message dated 12/16/2003 7:53:33 AM Pacific Standard Time,
kallen2@bellsouth.net writes:
>Can I presume that when the ctcss 100 is engaged
>on both sides (xmit and rx), that the only APRS traffic that will make
>it into my radio (TMD-700) are the ones from stations also using the 100
>ctcss tone?
No. The TNC takes it's RX audio from a point in the radio BEFORE the
CTCSS-controlled audio stage. All not having a PL tone on the incoming
signal will do is prevent it from being heard in the speaker. The TNC
will decode it just fine.
This is the whole point of Bob's voice alert function -- normal packet
operation proceeds silently but any nearby PL'd mobile (voice or data) on
the freq WILL be heard.
Stephen H. Smith wa8lmf (at) aol.com
Home Page: http://wa8lmf.com
Ham Radio/Mobile SSTV page: http://members.aol.com/wa8lmf/ham
APRS Stuff
http://members.aol.com/wa8lmf/aprs
----------------------------------------------------------------------
Subject: Re: TNC-X is Now Shipping
From: WA8LMF2@aol.com
Date: Wed, 17 Dec 2003 03:28:36 EST
X-Message-Number: 5
In a message dated 12/14/2003 6:57:06 PM Pacific Standard Time,
hansen@fredonia.edu writes:
>Full information, including photos, the schematic, manual
>and a DCC paper describing the unit can be found at http://www.tnc-x.com .
Well, the information doesn't seen very full (at least yet!)...
Specifically:
1) What voltage does this device run from and how much current?
2) What range of incoming/outgoing audio levels does it need/produce?
3) What range of baud rates does the serial port I/O support?
For APRN applications (APRS + SSTV together) I'm thinking of stuffing it
inside an EPIA-board-based low-power mini-PC with the TNC RX audio line
connected across the back of the soundcard LINE-input jack so that RX audio
from the radio will be automatically be applied simultaneously to the
soundcard (for an SSTV app) and to the TNC (for APRS via UI-View).
BTW, I have successfully run the APRN application using mmSSTV (sound card
SSTV app), UI-View with Precision Mapping 6.0 map database and a KPC3
(going into the serial port) and KB2SCS's APRN app -- all under Win98SE on
a 200MHz Dell 3000 laptop with 128MB RAM and a 100Mbit PCMCIA Ethernet
card.
The target EPIA machine would be a 533MHz Celeron equivalent with built-in
sound and Ethernet.
Stephen H. Smith wa8lmf (at) aol.com
Home Page: http://wa8lmf.com
Ham Radio/Mobile SSTV page: http://members.aol.com/wa8lmf/ham
APRS Stuff
http://members.aol.com/wa8lmf/aprs
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
