[PaQSO] PA QSO Party Software

[Ron Notarius W3WN]

Amen.

And for what it's worth... if KA3JWE no longer wishes to update or support
his excellent program, I would be willing to assume the responsibility.
However, I don't know if he would wish to release his program into someone
else's hands, which is understandable!

73

-----Original Message-----
From: paqso-bounces at mailman.qth.net
[mailto:paqso-bounces at mailman.qth.net]On Behalf Of Goody K3NG
Sent: Wednesday, October 31, 2007 9:42 AM
To: PA QSO Party
Subject: [PaQSO] PA QSO Party Software


While it's often a pain to accommodate Party changes in software, it's a
fact of life in software development.  Anyone who develops software
professionally or on the side knows this.  When you volunteer to develop
software, you sign up for a couple things: annual updates, bug reports,
feature requests, clueless users, people emailing the day of the Party,
etc.  It comes with the territory.  It's not all pain and drudgery
though; the developers must derive some pleasure out of developing
otherwise they wouldn't do it.  Show me a piece of commercial software
that hasn't changed in the past five years and I'll show you a bankrupt
software development company, or a dying industry or a screwed up
government agency using it.

We shouldn't hesitate to make changes based on software issues.  We
should certainly give ample time for developers to make changes (now is
the time to make changes, not September 2008), but the needs of the
Party participants drive the structure of the party, not the software.
This is a QSO Party and not a software party.

Developers, please don't take this post as a dig, but more as a
recognition of the difficulties you go through.  My hat goes off to
those who develop software; we all owe a debt of gratitude to you.

73
Goody
K3NG

--
Blog: http://thek3ngreport.blogspot.com/

_______________________________________________
PaQSO mailing list
PaQSO at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/paqso