Skip to Content.
Sympa Menu

chtechcomm - Re: [Chtechcomm] Tomorrow night - CH Tech Committee Meeting

chtechcomm AT lists.ibiblio.org

Subject: Chapel Hill Technology Advisory Committee

List archive

Chronological Thread  
  • From: chtechboard AT willraymond.org
  • To: "Chapel Hill Technology Advisory Committee" <chtechcomm AT lists.ibiblio.org>
  • Cc: "Chapel Hill Technology Advisory Committee" <chtechcomm AT lists.ibiblio.org>
  • Subject: Re: [Chtechcomm] Tomorrow night - CH Tech Committee Meeting
  • Date: Mon, 17 Apr 2006 20:08:48 -0700 (PDT)

Thanks Aris,

Excellent points. I hope you can make it to the next couple
meetings.

Will

> Hi folks,
>
> I won't be able to make it tomorrow evening, best of luck to everyone.
> If I were to make suggestions on how a new committe might improve, I'd
> suggest:
>
> - Limit the size to 7 or 8, or increase the frequency of meetings (having
> a roomful of 12+ ppl for 90 minutes a month always seemed like too large a
> group)
> - Set clear goals for the group (it seemed like a large part of the tech.
> meetings were spent trying to read the tea leaves of the town council)
> - Set some process of regular accountability for recommendations (ie, of
> last year's suggestions how much progress has been made). I feel that an
> informal report card would lend a sense of consistency to the tech
> committee, put some pressure on the Town Coucil to implement initiatives,
> and enable some continuity/history to new technology committee members.
> - Allow the public a forum to suggest tech issues this new committe might
> consider.
> - Enable the ability to solicit expertise from the community w/o requiring
> fulltime membership
>
> Take care!
>
> Aris
>
>
>
> -----Original Message-----
> From: chtechcomm-bounces AT lists.ibiblio.org on behalf of Ralph Beisner
> Sent: Mon 4/17/2006 3:49 PM
> To: 'Chapel Hill Technology Advisory Committee'
> Subject: Re: [Chtechcomm] Tomorrow night - CH Tech Committee Meeting
>
> We can decide at our meeting tomorrow whether there is any reason to
> continue beyond tomorrow.
>
> -----Original Message-----
> From: chtechcomm-bounces AT lists.ibiblio.org
> [mailto:chtechcomm-bounces AT lists.ibiblio.org] On Behalf Of Evelyn Daniel
> Sent: Monday, April 17, 2006 2:28 PM
> To: Chapel Hill Technology Advisory Committee
> Subject: Re: [Chtechcomm] Tomorrow night - CH Tech Committee Meeting
>
> Hey, Ralph,
>
> Well, maybe it won't be our final meeting. Will thinks we meet through
> June. It was a bit unclear. The notion from the Council seemed to just
> dismiss us - period, but maybe the intent was to let us finish out the
> term.
>
> Evelyn
>
> --On Monday, April 17, 2006 1:33 PM -0400 Ralph Beisner
> <rbeisner AT nc.rr.com> wrote:
>
>> Evelyn,
>>
>> As you are the senior member of our group I think it would be
>> appropriate
>> for you to act as our convener of what I think should be our last
>> meeting.
>> No reason to drag it out.
>>
>> Ralph
>>
>> -----Original Message-----
>> From: chtechcomm-bounces AT lists.ibiblio.org
>> [mailto:chtechcomm-bounces AT lists.ibiblio.org] On Behalf Of Evelyn Daniel
>> Sent: Monday, April 17, 2006 12:32 PM
>> To: Chapel Hill Technology Advisory Committee
>> Subject: Re: [Chtechcomm] Tomorrow night - CH Tech Committee Meeting
>>
>> Dear Martha and Ralph and all,
>>
>> I agree that it would be good to hae a final wrap-up "hail and farewell"
>> meeting. Perhaps it would be good practice to see if we can agree on
>> some useful comments in a final memo.
>>
>> I think we would do well to have a convener and having suggested it, I'm
>> willing to volunteer, although I would strongly prefer that someone like
>> Steve might act in this capacity.
>>
>> What say the rest of you?
>>
>> This is nice -- like old times, communicating by email. The loss of our
>> ability to communicate in this way was in large part the cause of a lot
>> of our troubles.
>>
>> Evelyn
>>
>>
>>
>> --On Monday, April 17, 2006 11:19 AM -0400 Ralph Beisner
>> <rbeisner AT nc.rr.com> wrote:
>>
>>> I think we should have a final meeting tomorrow to find a way to wrap
>>> up
>>> things nice and neat. Perhaps we can agree on the pertinent comments
>>> of
>>> a joint memo suggesting what the Town Council should consider going
>>> forward.
>>>
>>> Bob, perhaps you could make the arrangements for the meeting by
>>> reserving
>>> a room and letting us know that we are on the room schedule.
>>>
>>> Ralph
>>>
>>> -----Original Message-----
>>> From: chtechcomm-bounces AT lists.ibiblio.org
>>> [mailto:chtechcomm-bounces AT lists.ibiblio.org] On Behalf Of Martha
>>> Hoylman
>>> Sent: Monday, April 17, 2006 10:50 AM
>>> To: Chapel Hill Technology Advisory Committee
>>> Subject: [Chtechcomm] Tomorrow night - CH Tech Committee Meeting
>>>
>>>
>>>
>>> Is there a meeting tomorrow night since we've been disbanded?
>>>
>>>
>>>
>>> Martha
>>>
>>>
>>>
>>> Martha A. Hoylman
>>>
>>> Business Analyst/ Project Manager
>>>
>>> Information Technologies
>>>
>>> Orange County Government
>>>
>>> mhoylman AT co.orange.nc.us
>>>
>>> (919) 245-2287 (office)
>>>
>>> (919) 949-3958 (cell)
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Chtechcomm mailing list
>>> Chtechcomm AT lists.ibiblio.org
>>> http://lists.ibiblio.org/mailman/listinfo/chtechcomm
>>
>>
>>
>>
>>
>> _______________________________________________
>> Chtechcomm mailing list
>> Chtechcomm AT lists.ibiblio.org
>> http://lists.ibiblio.org/mailman/listinfo/chtechcomm
>>
>> _______________________________________________
>> Chtechcomm mailing list
>> Chtechcomm AT lists.ibiblio.org
>> http://lists.ibiblio.org/mailman/listinfo/chtechcomm
>
>
>
>
>
> _______________________________________________
> Chtechcomm mailing list
> Chtechcomm AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/chtechcomm
>
> _______________________________________________
> Chtechcomm mailing list
> Chtechcomm AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/chtechcomm
>
> _______________________________________________
> Chtechcomm mailing list
> Chtechcomm AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/chtechcomm
>






Archive powered by MHonArc 2.6.24.

Top of Page