[USPS-Webmasters] Check out http://www.usps.org/national/itcom/shared/pol...
Harriman Jett
LNSPS@carolina.rr.com
Wed, 30 Mar 2005 18:53:36 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_003F_01C53559.C75F4C00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Agreed, outdated comments such as inferring that past events will occur =
in the future is confusing and unacceptable. Likewise with outdated =
decal dates, etc.
The LNSPS (Lake Norman, NC) keeps a full year's calendar (plus some =
events for the following year) on its website, complete with links for =
further description of selected events. We find this very helpful for =
reference and to display our activities throughout the year. Anyone =
oriented to current time would readily ascertain that the event is =
"past", "current" or "future". Since I manage several websites, in =
addition to work, teaching and enjoying boating, I try for efficiency. =
Why place unnecessary burden upon volunteers to do meaningless work =
(such as changing fonts on a weekly basis)?
I feel strongly that the phrase, "If past dates are listed on websites =
they should be identified as past events, such as by change in font =
style or color or within a shaded background such as in a calendar =
format." be eliminated or at least re-worded.
Harriman
______________________
Harriman H. Jett, AP
LNSPS@carolina.rr.com
www.usps.org/lc/lakenorman
----- Original Message -----=20
From: Bill Ray=20
To: BSURuss@aol.com ; WMMILLER@aol.com ; usps-webmasters@usps.org=20
Sent: Wednesday, March 30, 2005 2:53 PM
Subject: RE: [USPS-Webmasters] Check out =
http://www.usps.org/national/itcom/shared/pol...
It seems to me that the site should be kept up to date, but that it =
should be the webmaster's prerogative to include historical and future =
information as they see fit so long as the intent is clear. =20
=20
Saying prominently "Our next public boating class is January 2005" =
would be unacceptable now. However listing that a class happened 1/2005 =
should be perfectly reasonable, say in an archive of past Newsletters or =
calendars, or having a photo from last fall's class. We keep several =
issues of the Newsletter on-line and have photos from past events, a =
history page that goes back to the Squadron's founding, and our calendar =
looks ahead to 2006.
=20
The choice of how to show it is 'past' is a matter of style for the =
webmaster to decide including simple context such as a page labeled Jan =
2005 Newsletter. Seems to me the criteria should be that the =
communication should be 'current' as fits its purpose.
=20
Bill Ray
Seattle
=20
-------------------------------------------------------------------------=
-----
From: BSURuss@aol.com [mailto:BSURuss@aol.com]=20
Sent: Wednesday, March 30, 2005 11:09 AM
To: WMMILLER@aol.com; usps-webmasters@usps.org
Subject: Re: [USPS-Webmasters] Check out =
http://www.usps.org/national/itcom/shared/pol...
=20
In a message dated 3/30/2005 12:58:45 A.M. US Eastern Standard Time, =
WMMILLER@aol.com writes:
Click here: =
http://www.usps.org/national/itcom/shared/policy/weballdoc.doc=20
=20
Here is your first opportunity to review the revised rules for all =
websites in USPS. Note we are stressing the subtitles section of the =
rules as well as having the information on the website up to date. =
These rules will form the basis of this years webawards program. There =
will be specific rules posted, hopefully by the end of April.
=20
Bill Miller
Website Coordinator
Bill,
=20
Regarding the updated rule.....
=20
1) Web site must be kept up to date - required=20
Any web site, which contains meeting, activities and/or pubic boating =
course information that is 90 days or more out of date, may be removed =
from linking to the national site. It is extremely important to keep =
websites up to date. Any website found not current in their schedule =
dates for events and educational programs will not be considered in any =
awards evaluations. Note there is no grace period for the awards =
program. If past dates are listed on websites they should be identified =
as past events, such as by change in font style or color or within a =
shaded background such as in a calendar format. Items that are date =
referenced, such as the VSC Decal should show the present years version.
=20
Our squadron elects to post our entire annual watch year =
meeting/social calendar at the beginning of the year so members can plan =
ahead. I generally highlight the next one or two upcoming events so =
members can easily spot where they are on our calendar. I keep all of =
the past events listed on our calendar for several reasons. The most =
important reason that we show all events - past and upcoming - is to =
provide prospective members with a clear, complete picture of our annual =
programming - which we feel is quite good. Our squadron is active, and =
we want prospective members to easily see that. Aside from making sense =
for that reason alone, in my opinion this should be a squadron decision =
- not a USPS decision. Also, in my humble opinion, I'm guessing that =
when I list past dates on our web calendar ... our members are sharp =
enough to understand that those dates have already occurred without me =
needing to explain how that works or identifying them as such. =20
=20
In short, I'm all for keeping current, and I believe a requirement for =
USPS websites to keep updated on upcoming events makes sense. However, =
I frankly feel that the decision to show past events is the local =
squadron's call - not that of USPS and certainly not left up to the =
variable interpretation of the individual reviewers. Anytime USPS =
unlinks a local squadron's website, USPS is shooting itself in the foot =
by reducing promotional reach created by our website network. This is =
important given our membership trend. I realize that we don't need to =
expose prospective members to 'lousy' outdated local websites as a =
matter of image. However, rather than threaten to unlink websites for =
being out of date, I can't help but believe that there would be some way =
to work with these sites to help them improve on this criterion (rather =
than simply pulling the plug). This would help both the local websites =
and USPS rather than coming across as punitive. =20
=20
I realize that I'm raising a trivial issue. However, the reviewer in =
the most recent evaluation apparently took exception to our practice =
vis-a-vis ratings even though our website was meticulously up to date on =
upcoming meetings, social events, and classes. Out of curiosity I =
compared our site's rating on this criterion to other sites that were =
grossly outdated on upcoming schedules and curiously found no consistent =
difference in ratings. I'm attributing that to an inter-rater =
reliability issue. However, that could be improved by tightening up the =
wording of the criteria as in this case. I'm wondering when our =
evaluations are conducted next fall if I need to somehow point out to =
the reviewer that summer events have already passed in order to earn =
points on this scoring criterion. Just a suggestion.
=20
Russ Wahlers
Hoosier Power Squadron - Indianapolis
------=_NextPart_000_003F_01C53559.C75F4C00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1491" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>
<![endif]-->
<STYLE>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US id=3Drole_body bottomMargin=3D7 vLink=3Dblue =
link=3Dblue=20
bgColor=3D#ffffff leftMargin=3D7 topMargin=3D7 rightMargin=3D7>
<DIV><FONT face=3DArial size=3D2>Agreed, outdated comments such as=20
inferring that past events will occur in the future is =
confusing and=20
unacceptable. Likewise with outdated decal dates, etc.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The LNSPS (Lake Norman, NC) keeps a =
full year's=20
calendar (plus some events for the following year) on its =
website, complete with links for further description of selected =
events. We=20
find this very helpful for reference and to display our activities =
throughout=20
the year. Anyone oriented to current time would readily=20
ascertain that the event is "past", "current" or "future". Since I =
manage=20
several websites, in addition to work, teaching and enjoying =
boating, I try=20
for efficiency. Why place unnecessary burden upon volunteers to do =
meaningless=20
work (such as changing fonts on a weekly basis)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I feel strongly that the phrase, <FONT =
size=3D3><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial">"If past dates are listed on =
websites=20
they should be identified as past events, such as by change in font =
style or=20
color or within a shaded background such as in a calendar format."<FONT=20
color=3D#000000 size=3D2> be eliminated or at least=20
re-worded.</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#000000 size=3D2><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: =
Arial"></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#000000 size=3D2><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial"><FONT=20
color=3D#000000>Harriman</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#000000 size=3D2><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial"><FONT=20
color=3D#000000>______________________<BR>Harriman H. Jett, =
AP</FONT><BR><A=20
href=3D"mailto:LNSPS@carolina.rr.com">LNSPS@carolina.rr.com</A><BR><A=20
href=3D"http://www.usps.org/lc/lakenorman">www.usps.org/lc/lakenorman</A>=
<BR></DIV></SPAN></FONT></FONT>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dbray@apian.com href=3D"mailto:bray@apian.com">Bill Ray</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3DBSURuss@aol.com=20
href=3D"mailto:BSURuss@aol.com">BSURuss@aol.com</A> ; <A =
title=3DWMMILLER@aol.com=20
href=3D"mailto:WMMILLER@aol.com">WMMILLER@aol.com</A> ; <A=20
title=3Dusps-webmasters@usps.org=20
href=3D"mailto:usps-webmasters@usps.org">usps-webmasters@usps.org</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, March 30, 2005 =
2:53=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [USPS-Webmasters] =
Check out=20
<A=20
=
href=3D"http://www.usps.org/national/itcom/shared/pol">http://www.usps.or=
g/national/itcom/shared/pol</A>...</DIV>
<DIV><BR></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">It seems to =
me that=20
the site should be kept up to date, but that it should be the =
webmaster=92s=20
prerogative to include historical and future information as they see =
fit so=20
long as the intent is clear. <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Saying =
prominently=20
=93Our next public boating class is January 2005=94 would be =
unacceptable=20
now. However listing that a class happened 1/2005 should be =
perfectly=20
reasonable, say in an archive of past Newsletters or calendars, or =
having a=20
photo from last fall=92s class. We keep several issues of the =
Newsletter=20
on-line and have photos from past events, a history page that goes =
back to the=20
Squadron=92s founding, and our calendar looks ahead to=20
2006.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The choice =
of how to=20
show it is =91past=92 is a matter of style for the webmaster to decide =
including=20
simple context such as a page labeled Jan 2005 Newsletter. Seems =
to me=20
the criteria should be that the communication should be =91current=92 =
as fits its=20
purpose.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><st1:PersonName w:st=3D"on"><FONT face=3DArial =
color=3Dnavy=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Bill=20
Ray</SPAN></FONT></st1:PersonName><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><st1:City w:st=3D"on"><st1:place =
w:st=3D"on"><FONT face=3DArial=20
color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Seattle</SPAN></FONT></st1:place></st1:City><FONT=20
face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
BSURuss@aol.com [mailto:BSURuss@aol.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, March 30, 2005 =
11:09=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
WMMILLER@aol.com;=20
usps-webmasters@usps.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [USPS-Webmasters] =
Check out=20
=
http://www.usps.org/national/itcom/shared/pol...</SPAN></FONT><o:p></o:p>=
</P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">In a =
message dated=20
3/30/2005 12:58:45 A.M. US Eastern Standard Time, WMMILLER@aol.com=20
writes:<o:p></o:p></SPAN></FONT></P></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; MARGIN-TOP: 5pt; PADDING-LEFT: 4pt; MARGIN-BOTTOM: 5pt; =
PADDING-BOTTOM: 0in; MARGIN-LEFT: 3.75pt; BORDER-LEFT: blue 1.5pt solid; =
PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"><A=20
=
title=3Dhttp://www.usps.org/national/itcom/shared/policy/weballdoc.doc=20
=
href=3D"http://www.usps.org/national/itcom/shared/policy/weballdoc.doc">C=
lick=20
here: =
http://www.usps.org/national/itcom/shared/policy/weballdoc.doc</A>=20
<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Here is =
your first=20
opportunity to review the revised rules for all websites in =
USPS. Note=20
we are stressing the subtitles section of the rules as well as =
having the=20
information on the website up to date. These rules will form =
the basis=20
of this years webawards program. There will be specific rules =
posted,=20
hopefully by the end of April.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Bill=20
Miller<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Website=20
Coordinator<o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Bill,<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Regarding =
the=20
updated rule.....<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.25in; TEXT-INDENT: =
-0.25in"><FONT=20
face=3DArial color=3Dblack size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Arial">1)</SPAN></FONT><FONT=20
color=3Dblack size=3D1><SPAN=20
style=3D"FONT-SIZE: 7pt; COLOR: =
black"> =20
</SPAN></FONT><B><FONT face=3DArial color=3Dblack><SPAN=20
style=3D"FONT-WEIGHT: bold; COLOR: black; FONT-FAMILY: Arial">Web site =
must be=20
kept up to date</SPAN></FONT></B><FONT face=3DArial =
color=3Dblack><SPAN=20
style=3D"COLOR: black; FONT-FAMILY: Arial"> - <EM><I><FONT =
face=3DArial><SPAN=20
style=3D"FONT-FAMILY: Arial">required</SPAN></FONT></I></EM>=20
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblack=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Arial">Any web=20
site, which contains meeting, activities and/or pubic boating course=20
information that is 90 days or more out of date, may be removed from =
linking=20
to the national site. It is extremely important to keep websites up to =
date. Any website found not current in their schedule dates for =
events=20
and educational programs will not be considered in any awards=20
evaluations. Note there is no grace period for the awards =
program. =20
</SPAN></FONT><FONT face=3DArial color=3Dred><SPAN=20
style=3D"COLOR: red; FONT-FAMILY: Arial">If past dates are listed on =
websites=20
they should be identified as past events, such as by change in font =
style or=20
color or within a shaded background such as in a calendar=20
format.</SPAN></FONT><FONT face=3DArial color=3Dblack><SPAN=20
style=3D"COLOR: black; FONT-FAMILY: Arial"> Items that are date=20
referenced, such as the VSC Decal should show the present years=20
version.</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
color=3Dblack size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: =
black"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblack=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Arial">Our=20
squadron elects to post our entire annual watch year =
meeting/social=20
calendar at the beginning of the year so members can plan ahead. =
I=20
generally highlight the next one or two upcoming events so members can =
easily=20
spot where they are on our calendar. I keep all of the past =
events=20
listed on our calendar for several reasons. The most =
important=20
reason that we show all events - past and upcoming - is to provide =
prospective=20
members with a clear, complete picture of our annual programming =
- which=20
we feel is quite good. Our squadron is active, and we want =
prospective=20
members to easily see that. Aside from making sense for that =
reason=20
alone, in my opinion this should be a squadron decision - not a USPS=20
decision. Also, in my humble opinion, I'm guessing that when I =
list past=20
dates on our web calendar ... our members are sharp enough to =
understand that=20
those dates have already occurred without me needing to explain =
how that=20
works or identifying them as such. </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
color=3Dblack size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: =
black"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblack=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Arial">In=20
short, I'm all for keeping current, and I believe a requirement for =
USPS=20
websites to keep updated on upcoming events makes sense. =
However, I=20
frankly feel that the decision to show past events is the local =
squadron's=20
call - not that of USPS and certainly not left up to the variable=20
interpretation of the individual reviewers. Anytime USPS unlinks =
a local=20
squadron's website, USPS is shooting itself in the foot by reducing=20
promotional reach created by our website network. This is =
important=20
given our membership trend. I realize that we don't need to =
expose=20
prospective members to 'lousy' outdated local websites as a =
matter=20
of image. However, rather than threaten to unlink websites for =
being out=20
of date, I can't help but believe that there would be some way to work =
with=20
these sites to help them improve on this criterion (rather than simply =
pulling=20
the plug). This would help both the local websites and USPS =
rather than=20
coming across as punitive. </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
style=3D"COLOR: black"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
color=3Dblack size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: =
black"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblack=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Arial">I=20
realize that I'm raising a trivial issue. However, the reviewer =
in the=20
most recent evaluation apparently took exception to our practice =
vis-a-vis=20
ratings even though our website was meticulously up to date on =
upcoming=20
meetings, social events, and classes. Out of curiosity I =
compared our=20
site's rating on this criterion to other sites that were grossly =
outdated on=20
upcoming schedules and curiously found no consistent difference =
in=20
ratings. I'm attributing that to an inter-rater reliability =
issue. =20
However, that could be improved by tightening up the wording of the =
criteria=20
as in this case. I'm wondering when our evaluations are =
conducted next=20
fall if I need to somehow point out to the reviewer that summer events =
have=20
already passed in order to earn points on this scoring =
criterion. Just a=20
suggestion.</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Times =
New Roman"=20
color=3Dblack size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: =
black"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblack=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Arial">Russ=20
Wahlers</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3DArial =
color=3Dblack=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: =
Arial">Hoosier=20
Power Squadron - <st1:City w:st=3D"on"><st1:place=20
w:st=3D"on">Indianapolis</st1:place></st1:City></SPAN></FONT><FONT=20
color=3Dblack><SPAN=20
style=3D"COLOR: =
black"><o:p></o:p></SPAN></FONT></P></DIV></DIV></BLOCKQUOTE></BODY></HTM=
L>
------=_NextPart_000_003F_01C53559.C75F4C00--