Re: Request for comments: archive for mailing lists
Re: Request for comments: archive for mailing lists
- Subject: Re: Request for comments: archive for mailing lists
- From: Ondra Cada <email@hidden>
- Date: Mon, 23 Sep 2002 13:15:52 +0200
On Monday, September 23, 2002, at 12:42 , Bertrand Mansion wrote:
If I archive the cocoapro list with the other two lists, its messages will
be considered the same as cocoadev or macosxdev messages. It means that
when
they will be indexed, they won't come out first. Except if I set a meta
tag
that says these messages have a better score factor than the others.
But IMO, they should be considered the same as the others because they
have
the same topic. Don't you think ?
I do.
Well, I can imagine a very sophisticated search system which would allow
the user to set his own preferences for relative weight of different
sources (like, "I want omnidev hits first, cocoapro then, cocoadev last"
or whatever), but I frankly think it would not be worth the effort.
There is another solution, which I will use to archive java-dev,
projectbuilder users and gnustep: to put these lists into specific areas.
Users will be able to search in the area they choose and won't get results
from the other areas. So javadev results won't mix up with projectbuilder
results for example.
Yeah, with java and gnustep it is very sensible; with PB in principle too,
had it not been for the unfortunate fact that many people think that PB
compiles itself and seem not to grasp that it does not -- with the sad
result of plain "compiler" and sometimes even "cocoa" questions and
answers inside the PB list.
Nevertheless, still I think the PB/others ratio is good enough to make it
so (ie. to place PB into a different area).
So, should I make a special area for cocoapro itself or mix it with
cocoadev
and macosxdev ?
In my opinion, you should not -- when searching archives, IMHO cocoapro
should be seen as just part of cocoadev+omnidev.
Also depends on how the area management is made: I regret to say I haven't
ever tried mamasam archives (shame on me ;)), so I don't know. If a user
can make something similar to "bookshelves" of different areas, it would
be probably worth to make a separate area for each list, since then it
would be easy just to place cocoadev, omnidev, and cocoapro to a "cocoa"
bookshelf for the "normal" behaviour, and switch some of them off in
special cases.
Well, seems I've effectively wrote "Each way of doing it has its merits,
choose yourself". Sorry ;)
I am not surprised, you are one of the top contributor to these lists, if
you make a search in cocoa.mamasam.com, you would surely find a lot of
replies come from you. ;-)
Good for my conceit, is it not? ;)))
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.