Re: [Phpgroupware-developers] Not to be impolite (2 issues, issue #1)...

[Chris Weiss]

I agree it is long, but i've also found that when people setup lists there are
often reasons for the names they choose and most are very unwilling to change
them.

part of the problem here is that the project is called phpgroupware on gnu's
servers so that part of the subject is not negociable.

As for the others, the name has been this way for years and you are the first to
complain.  I have my mail in a failrly small window, under 1024x768, and I don't
think the subject is problematicly long.

You always have the option of using a procmail rule or something and rewritting 
the
suject to your prefs, but then replying will add yet another tag on the subject 
:)

Ron (address@hidden) wrote:
>
>I've mentioned this before only to be shot down... Perhaps if I persist
>I can gain some momentum:
>
>ISSUE #1 (of 2):
>
>The subject line prefix is TOOOOOOO LOOOONNNNNGGG:
>
>I'm on 30+ lists and process hundreds of messages a day, but when I get
>to [Phhpppggrrroouupppwwaarree--ddeevvveeellloopperrrssss] there is NO
>SPACE left on the Subject line!
>
>What about changing to something shorter, like:
>
>    [phpgw-dev] and [phpgw-user]
>
>Failing that... could those in opposition provide a reason to usurp so
>much real estate on the subject line...
>
>(here are a few of my suspects:)
>
>    -> A. Must advertise PHPGROUPWARE-DEVELOPERS, and no place better
>then "to the choir".
>
>    -> B. Users and developers of PhpGroupWare have short memories and
>consistently forget what PhpGw refers to (... that's PhpGroupWare, for
>those that have forgotten) unless it is spelled out each time.
>
>    -> C. The person in charge of the mail list doesn't know/remember
>how to change the subject line prefix.
>
>    -> D. Changing the subject line prefix requires a committee meeting,
>that meeting was convened last year (the last time I posted this
>request) and is currently in session, still deciding on this very issue.
>
>    -> E. The list server for PhpGw (oops... PhpGroupWare) gives
>discounts for Gigabytes served.
>
>    -> F. It has always been "Phpgroupware-developers" and
>"Phpgroupware-users" and we see no need to change just because someone
>is more interested in the Subject line of a message then reading
>over-and-over the name "Phpgroupware-developers" and
>"Phpgroupware-users." If anyone has a problem with that, go out and
>invent your own darn program and name it what ever you wish!
>
>    -> G. It is not the intention of PhpGw (that's PhpGroupWare)
>software to lend itself to addressing the issue it is designed for, but
>rather for drawing attention to itself. If any time / space / memory /
>cpu / subject line is available after that, what the heck... In keeping
>with that philosophy, we attempt to draw as much attention to PhpGw
>(that's PhpGroupWare) as possible on the subject line!
>
>(Two examples on the list I'm looking at as I type where the subject
>prefix is longer then the subject:)
>
>    RE: [Phpgroupware-developers] PDF - support
>    RE: [Phpgroupware-users] Problem with project
>
>    -> H. Because!
>
>If anyone agrees with me on this issue PLEASE ATTACH an "I AGREE" to
>this message or nothing will probably get done (like the last time :-(
>
>********** (NEW ISSUE) ***********
>
>The second _ISSUE_ I have will be posted in a second message with the
>subject line:
>
>      Re: [Phpgroupware-developers] Not to be impolite (2 issues, issue
>#2)...
>
>Rather then the subject line:
>
>      Re: [phpgw-dev] Not to be impolite (2 issues, issue #2)...
>
>That message, btw, will be "threaded" to this one... if anyone is
>interested in the concept of "threaded messages."
>
>Thank you,
>
>-Ron
>
>
>
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>