| |
|
Meeting This Month
|
|
|
| |
|
|
|
|
| |
|
Feb. 20, 2003 at 7:00 pm |
|
|
| |
|
|
|
|
| |
|
At Seven Oaks Elementary School |
|
|
| |
|
|
|
|
| |
|
6:30 pm set up and get everything ready |
|
|
| |
|
|
|
|
| |
|
7:00 pm meeting |
|
|
| |
|
|
|
|
| |
|
8:00 pm after meeting social and clean up |
|
|
| |
|
|
|
|
| |
|
be gone by 8:30 pm |
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
I'm sorry for the confusion with last months meeting.
We received conflicting information about road conditions. I did not
have a way to contact anyone about the school when it was closed, to confirm
whether it would be open or not. (I have gotten this information now
for future use). Rather than someone getting hurt in the bad weather, I felt it best just to cancel the
meeting. The problems encountered in notifying the community
membership about the cancelled meeting made it clear that we need to improve
our communication system. That brings up
another question. How do we notify everyone about a canceled meeting? Any input in this area
would be very welcome. |
|
|
| |
|
|
|
|
| |
|
One of the areas of communication I would like to see
established is a telephone
tree so we can quickly contact everyone when necessary. To this end, I am
using our new neighborhood directory to break up the
neighborhood streets into segments. If we have enough community
members volunteering to take one segment, they will be small enough so no
one will be over-burdened. Again, any input in this area would be very
welcome. |
|
|
| |
|
|
|
|
| |
|
other agenda items |
|
|
| |
|
|
|
|
| |
|
1. Telephone Tree |
|
|
| |
|
|
|
|
| |
|
2. Communication Plan |
|
|
| |
|
|
|
|
| |
|
3. Neighborhood watch / Crime Watch being set up |
|
|
| |
|
|
|
|
| |
|
4. Ground rules for yard of the month |
|
|
| |
|
|
|
|
| |
|
5. Neighborhood Directory |
|
|
