On Thu, 29 Aug 2002 [EMAIL PROTECTED] wrote:
> Date: Thu, 29 Aug 2002 11:25:01 -0400
> From: [EMAIL PROTECTED]
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: [Proposal] Thread Topic Identification (was [BS] Are we
> getti ngo ff the topic)
>
>
> I would agree with putting the tags on. I don't think there needs to be
> an official list of tags, just having them there will be easy enough.
>
I will put them on the description of the STRUTS-USER mailing list, but
only as a recommended convention -- not as a requirement.
Personally, I leave my mail reader in sort-by-thread mode with a different
folder per subscribed list -- and the first menu option I learned was the
"mark thread as read" command ... it works wonders.
> Hopefully, if everyone starts doing it, new people would notice that
> every time there is a question of something about tiles (for example) it
> seems to always start with [tiles]...
>
People do learn by watching -- but I'm going to absolutely *stomp* on
anybody who yells at newbies for not following the convention.
> -1 for new list
I'm already maxed on the number of lists that *I* am willing to subscribe
to ...
Craig
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: ekbush [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 29, 2002 10:35 AM
> To: struts-user
> Subject: Re: [Proposal] Thread Topic Identification (was [BS] Are we
> getti ngo ff the topic)
>
>
> Are filters really _that_ hard to set up? ... I've got probably 30 of
> them going to sift and sort my mail -- continually having to edit them
> as projects evolve (ie there is tomcat5 stuff floating around now, and I
>
> had to edit my tc-dev filter).
>
> I don't see it as much of a problem -- and most (reasonable) clients can
>
> be configured to actually just delete messages off the server if they
> meet certain criteria, so there's not even any need to download them.
>
> +1 for tags
> -1 for a seperate list
> +1 for more fridays in the week :-P
>
> I think the tags would really help us all "zone-in" on what is most
> important to us. As such, I think it would be helpful to everyone -
> devs *and* users. Think of this example (I'm going to pick on Cedric,
> because he comes to mind):
>
> Cedric downloads his mail - there are about 150 struts-user mailings,
> but he's really busy and really just cares to see the ones for tiles
> right now.
>
> without tags:
> Cedric probably has to read all the subjects, and he might still miss
> something that speaks of a tiles issue but doesn't mention it in the
> topic.
>
> with tags:
> Cedric knows immediately which threads need his expert assistance, and
> can even filter them to a (sub-)folder for easy-access. Yes, when he
> has time he can go through the others too (if he wants), but right now
> he's quite busy (probably is but I'm speaking hypothetically, of course)
>
> so he can just "cut to the chase" and take care of those people most in
> need of his help.
>
> ... but I'm sure you all have your own view on why it would be a
> good/bad thing.
>
> Regards,
>
> Eddie
>
> Cliff Rowley wrote:
>
> >True, I hadn't though of that.
> >
> >On Thu, 2002-08-29 at 15:10, Kidd, Polly wrote:
> >
> >>bound to be... if someone isn't sure which category their problem
> falls
> >>into, they will probably mail to both...
> >>
> >>-----Original Message-----
> >>From: Cliff Rowley [mailto:[EMAIL PROTECTED]]
> >>
> >>I guess the question is, filter one list or two. Is the volume of two
> >>separate lists going to be more than the same information in one list?
> >>
> >>On Thu, 2002-08-29 at 15:04, Tim T. Young wrote:
> >>
> >>>My fear with another list is that good information will be available
> in
> >>>both, and I will have to process 300+ emails a day (2 lists x 150 a
> list).
> >>>
> >>>Tim
> >>>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
