[FRC] FYI... Florida Repeater Council Information

MICHAEL WELLS wells8868 at bellsouth.net
Mon Oct 3 18:56:56 EDT 2016


?????????????????????????

      From: Steve Zingman <szingman at msgstor.com>
 To: frc-info at lists.keekles.org 
 Sent: Monday, October 3, 2016 1:26 PM
 Subject: Re: [FRC] FYI... Florida Repeater Council Information
   
How are they not allowing all to communicate?

73, Steve N4IRS

On 10/3/2016 1:25 PM, mccrpt at tampabay.rr.com wrote:
> I agree with Mickey, doing the work of the FRC requires commitment.  It
> aint an easy job.  I for one would not want to see an inexperienced Ham
> deciding coordination, someone who has not been involved with it for a
> while.  Each repeater owner has their own needs and the FRC work has to
> do much more than assign pairs.
>
>
> Just like this discussion and whoever started it, they are not allowing
> all to communicate.  Do we want this in FRC???
>
>
> 73, ron, n9ee/r a know code Extra
>
> Ron Wright, N9EE/R
> BSEE
> Micro Computer Concepts
> 352-683-4476
> mccrpt at tampabay.rr.com
>
>
> ------------------------------------------------------------------------
> *From:* FRC-Info <frc-info-bounces at lists.keekles.org> on behalf of
> Mickey Baker <n4mb at arrl.net>
> *Sent:* Monday, October 3, 2016 11:35 AM
> *To:* Florida Repeater Council Discussion
> *Subject:* Re: [FRC] FYI... Florida Repeater Council Information
>
> A couple of words of advice from an experienced IT engineer - who has
> had an IT management position in Florida in the public sector as well as
> worked at DoD:
> 1. Anyone who doesn't want unpredictable emails on their corporate or
> government email server shouldn't subscribe to open lists. Get a free
> email account, like this one from Google and point all the groups to
> that email.
> 2. Anyone hoping that what they write in an email could remain private
> should learn to use email encryption. I won't go into details, but...
> 3. Anyone sending a plain language email should anticipate that email
> being read by anyone anywhere.
>
> That said, I've found the entire FRC to be a slow moving, difficult to
> deal with organization with antique web sites. Some of the directors are
> a bit gruff and condescending, but I find that a common trait among long
> term hams, particular trying to relate to the current crop of no-code
> licensees. I include myself, as I quickly lose patience with folks who
> don't know the basic things covered in the license material.
>
> I submitted a coordination request the day I got a message in May that
> the W4AB 2m repeater coordination had expired - May 7, 2016. It was
> approved over this weekend - almost 5 months to approve a registration
> for a repeater that has been in operation on that frequency at that site
> for 28 years.
>
> W4AB is currently not in the directory they publish, but now that the
> "official" ARRL repeater directory is now RFinder, I can (and do) deal
> directly with them for directory issues.
>
> My local director (Mark) has been very responsive, but he doesn't have
> direct access to add to or edit the database!
>
> It is my understanding that coordinations are handled by Dana and he's
> the only one with database access. Something might be going on in his
> personal life that causes this delay, but it is the duty of people with
> responsibility to engage with others to ensure succession of the
> organization and the mission. This appears to be the point of failure in
> many organizations but is key to the survival of that organization.
>
> All that said, here's the problem - if everyone on the board resigns or
> gets otherwise terminated, someone needs to have the time, talent and
> inclination to immediately recover data from wherever it is and create a
> new database and start up a complete new system, while doing all the
> things the current FRC are doing now... this will require cooperation
> with the current directors, particularly Dana.
>
> Are we all ready for that?
>
> If so, let's go get this handed over. Exactly where and when is the
> meeting next weekend?
>
> Mickey N4MB
>
>
> Mickey Baker, N4MB
> Fort Lauderdale, FL
> /“Tell me, and I will listen. Show me, and I will understand. Involve
> me, and I will learn.” /Teton Lakota, American Indian Saying.
>
> On Mon, Oct 3, 2016 at 10:03 AM, Dave Messinger H. <dmessing at pbcgov.org
> <mailto:dmessing at pbcgov.org>> wrote:
>
>    Gentlemen (and Ladies, if any) ,____
>
>    I don’t know where you got this e-mail from. I truly doubt you got
>    it legitimatelyfrom the FRC. ____
>
>    __ __
>
>    Regardless, ____
>
>    I have not asked to be included in this group or any discussions, ____
>
>    You are e-mailing my work/Government e-mail account (so everything
>    is open the Florida Sunshine Law),____
>
>    And finally, I have never had any troubles with the Florida Repeater
>    Council. They have always acted quickly and fairly with any
>    questions or registration I have had.____
>
>    __ __
>
>    Mr. Fields,____
>
>    I would ask that, in the future, you consider your actions a bit
>    more before blindly e-mailing a large group of people with your
>    grievances. ____
>
>    __ __
>
>    -----=====-----=====-----____
>
>    *Dave H. Messinger____*
>
>    *Communications Specialist____*
>
>    *Palm Beach County Network Support Services____*
>
>    *FCC Licenses: N4QPM, WQCA678____*
>
>    cid:image002.png at 01CAB493.44E57100____
>
>    __ __
>
>    /Please Note:  Due to Florida’s very broad records laws, most
>    written communications to or from County employees regarding County
>    business are public records, available to the public and media upon
>    request.  Therefore, this written e-mail communication, including
>    your e-mail address, may be subject to public disclosure.____/
>
>    __ __
>
>    ---____
>
>    __ __
>
>    *From:*FRC-Info [mailto:frc-info-bounces at lists.keekles.org
>    <mailto:frc-info-bounces at lists.keekles.org>] *On Behalf Of
>    *kg4ugk at kg4ugk.com <mailto:kg4ugk at kg4ugk.com>
>    *Sent:* Monday, October 03, 2016 8:26 AM
>    *To:* Florida Repeater Council Discussion
>    <frc-info at lists.keekles.org <mailto:frc-info at lists.keekles.org>>
>    *Subject:* Re: [FRC] Florida Repeater Council Information____
>
>    __ __
>
>    Back in 2002, Dana was extremely helpful in getting my coordination
>    completed.____
>
>      ____
>
>    Bryan, question. Why would you need a listing of unused pairs? It
>    seems counter productive to starting a new repeater, as well as
>    trying to find existing ones.____
>
>      ____
>
>    In my understanding and past experience, you request temporary
>    coordination and based on your location and desired output power,
>    they then assign you a frequency pair that won't interfere with
>    existing repeaters in the output powers RF range. They then give you
>    time to setup and test before providing full coordination.____
>
>      ____
>
>    Launching a repeater on an unused frequency pair, would potentially
>    cause interference to those setting one up in the future, and would
>    possibly result in a cease and deceit letter from the FCC when
>    someone else receives coordination for that pair.____
>
>      ____
>
>    Best regards,____
>
>    Shawn Campbell____
>
>    KG4UGK____
>
>      ____
>
>    -----Original Message-----
>    From: vern at highwayusa.com <mailto:vern at highwayusa.com>
>    Sent: Monday, October 3, 2016 6:58am
>    To: "Florida Repeater Council Discussion"
>    <frc-info at lists.keekles.org <mailto:frc-info at lists.keekles.org>>
>    Subject: Re: [FRC] Florida Repeater Council Information____
>
>
>    I must say that I have tried several times to contact the
>    council to see if I could fire my repeater back up on my
>    old pair, and have heard nothing. I thought they were
>    defunct until I saw this email come through.
>
>    Vern
>    KI4ONW
>
>    >
>    > P.S. Please feel free to discuss this on list. If you
>    >wish to not be a part of this discussion you can remove
>    >yourself using the link at the bottom. I'm happy to
>    >oblige your wishes via direct email as well if you have
>    >any questions.
>    >
>    >
>    >
>    > _______________________________________________
>    >FRC-Info mailing list
>    > <mailto:FRC-Info at lists.keekles.org <mailto:FRC-Info at lists.keekles.org>>
>    >FRC-Info at lists.keekles.org <mailto:FRC-Info at lists.keekles.org>
>    > <http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info
>    <http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info>>
>    >http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info
>    <http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info>
>    >
>
>    _______________________________________________
>    FRC-Info mailing list
>    FRC-Info at lists.keekles.org <mailto:FRC-Info at lists.keekles.org>
>    http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info
>    <http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info>____
>
>
>    ------------------------------------------------------------------------
>
>    Under Florida law, e-mail addresses are public records. If you do
>    not want your e-mail address released in response to a public
>    records request, do not send electronic mail to this entity.
>    Instead, contact this office by phone or in writing.
>
>    _______________________________________________
>    FRC-Info mailing list
>    FRC-Info at lists.keekles.org <mailto:FRC-Info at lists.keekles.org>
>    http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info
>    <http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info>
>
>
>
>
> _______________________________________________
> FRC-Info mailing list
> FRC-Info at lists.keekles.org
> http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info
>

-- 
"Just say no to world domination"
_______________________________________________
FRC-Info mailing list
FRC-Info at lists.keekles.org
http://lists.keekles.org/cgi-bin/mailman/listinfo/frc-info


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/frc-info/attachments/20161003/c7b40930/attachment-0001.html>


More information about the FRC-Info mailing list