[RVRC] FW: RVRC Meetings.

[John T McAuley]

Good discussion so far. IMHO, we should have a business meeting every other
month and a technical/what's new meeting between business meetings. I
believe that the technical committee does an outstanding job of keeping out
site up and running and completing the "shed" project. It's too much to ask
them to condense their work and open issues into a nice tidy report prior to
the meeting and send it out. Some technical/implementation issues require
and deserve open discussion with the membership.
Hope you find my thoughts constructive
73,
John
AB2XH

John T McAuley
-----Original Message-----
From: rvrc-bounces at mailman.qth.net [mailto:rvrc-bounces at mailman.qth.net] On
Behalf Of Marvin Bronstein
Sent: Friday, January 10, 2014 8:21 PM
To: drew Moore; RVRC
Subject: Re: [RVRC] FW: RVRC Meetings.


Members,
It would certainly be a benefit for all the members to have a technical
committee report in advance of the monthly meeting .  There has been a great
deal of tech. comm. work that the majority of members do not know has been
done until meeting night. But this would most likely not shorten the meeting
as it would more likely bring more questions to the chairman at those
meetings.

As I have, at least once, brought up at a meeting that it would be more
useful to have a separate technical session/meeting that would bring members
up to date on tech. issues.  Because some technical matters may be
time-consuming to present at business meetings, it holds the meeting very
late and may be a cause for low member attendance!  Perhaps every-other
meeting can be totally devoted to technical matters and training on the use
of our systems; having the reports in advance of business meetings could
satisfy the requirement of having given the report at each business meeting
while details of technical nature are presented at alternate meetings for
discussion.
Of course, when votes need to be taken for expenditures, these matters would
be taken-up at any regular meeting.

Most of our required ''business'' matters should be completed in about one
hour but long discussions over technical items drag the meetings on a bit
too late.

Marv, K2VHW

.........................................................


Sent: Friday, January 10, 2014 6:35 PM
Subject: [RVRC] FW: RVRC Meetings.


> Members,
>
>
>
> Comments welcomed. Perhaps the technical committee report could be 
> sent out prior to the meeting. Anyone thinking out of the box?
>
>
>
> 73,
>
> Drew
>
>
>
> From: asajm at optimum.net [mailto:asajm at optimum.net]
> Sent: Friday, January 10, 2014 6:30 PM
> To: Moore, Drew
> Subject: RVRC Meetings.
>
>
>
> The RVRC meetings are usually too long. I would think that the technical
> report
>
> could be a shorter report. Seems like the tech report takes up half of the
> meeting.
>
> Other members mentioned the same complaint and that it is discouraging at
> times.
>
> Perhaps this ought to be sent out to members and ask them for comments.
>
>


----------------------------------------------------------------------------
----


> ______________________________________________________________
> RVRC mailing list
> Home: http://mailman.qth.net/mailman/listinfo/rvrc
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:RVRC at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> 


______________________________________________________________
RVRC mailing list
Home: http://mailman.qth.net/mailman/listinfo/rvrc
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:RVRC at mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html