Last modified: 2014-11-17 09:21:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T19390, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17390 - Mailing lists need search function readded
Mailing lists need search function readded
Status: NEW
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
unspecified
All All
: Lowest enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://lists.wikimedia.org/pipermail/...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-06 19:24 UTC by MZMcBride
Modified: 2014-11-17 09:21 UTC (History)
14 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2009-02-06 19:24:33 UTC
There used to be a search bar at the top of pages like this: http://lists.wikimedia.org/pipermail/wikitech-l/

It has disappeared sometime in January. Either it should be reimplemented or a prominent link to Gmane or something should be included there. It's nearly impossible to find things without a search feature of some kind.
Comment 1 MZMcBride 2009-03-06 07:30:54 UTC
It should be noted that Gmane will (obviously) only work for public lists.

Lists like checkuser-l and oversight-l are currently entirely un-searchable. Bumping up the severity from enhancement to normal (as though anyone cares about the several level).
Comment 2 Brion Vibber 2009-03-27 22:55:39 UTC
For a while we attempted to use htdig search integration; this sort of worked but:
a) The search quality was not very good
b) The UI was terrible
c) It took so long to reindex that it would no longer complete. :P

Additionally, we block the archives from public search engines via robots.txt to reduce requests for removal of archived posts (since it's a huge pain in the butt to remove a post and regenerate the pipermail archives, and tends to be fragile and break things).

Our public mailing lists are generally also mirrored to gmane and other services and are searchable there, but private lists currently have no search of their archives.
Comment 3 Mike.lifeguard 2009-04-02 17:00:53 UTC
Searching the archives is incredibly important for private lists like checkuser-l. Currently unless one has a copy of the archives it is next to impossible to find what you're looking for. Restoring the search for such lists should be considered reasonably urgent and important. For such private lists, horrid UI isn't really a concern. I suppose low-quality results is a concern, but I never had real difficulties there. WRT reindex time - if this is re-enabled only for selected private lists, would that issue be reduced to an acceptable level?
Comment 4 Fred Vassard 2009-04-02 22:29:58 UTC
There doesn't seem to be many alternative to htdig. 
Did anyone look into Swish-e?
Seems to be the more popular way of incorporating searching.
Let me know, and if there are no objection, I will get it setup-ed.

(somewhat nice guide: http://wpkg.org/Integrating_Mailman_with_a_Swish-e_search_engine)

--Fred.
Comment 5 Brion Vibber 2009-04-07 20:54:03 UTC
The main thing to keep in mind is that this is most needed for private-access mailing lists, in which case we need to ensure that access to the search is restricted to authenticated list members; from skimming the swish-e integration page I'm not clear how secure that is for this case.
Comment 6 Platonides 2009-12-20 22:13:57 UTC
I don't see why it *needs* to be slow to index new posts, with any software.
Reindex just the last month and merge the results from different months when showing to the user.

It would even be acceptable to filter by dates:
Results for your search of Foo from Jan 2009 to June 2009: 5 [link]
Results for your search of Foo on 2008: 1 [link]
No hits found on other dates.
Comment 7 Mike.lifeguard 2009-12-31 05:11:40 UTC
(In reply to comment #4)
> Let me know, and if there are no objection, I will get it setup-ed.

Did you decide that Swish-e wasn't appropriate for use here, or is it simply on the backburner?
Comment 8 Huji 2010-10-26 19:05:28 UTC
For the record, I contacted Barry Warsaw (lead developer of Mailman) about a week ago. According to him, there is no active development of a search feature for Mailman right now (he invited me to help the project as a developer, but I'm afraid I can't develop the extension all by myself).

The implications are:
1) Either, we should us an existing search plugin (but we need to make sure it's secure enough)
2) Or, we can develop our own secure extension (which we can then send to Barry as well, for inclusion in the next version of Mailman as a core feature)
Comment 9 Max Semenik 2010-11-06 07:11:05 UTC
(In reply to comment #8)
> 1) Either, we should us an existing search plugin (but we need to make sure
> it's secure enough)
> 2) Or, we can develop our own secure extension (which we can then send to Barry
> as well, for inclusion in the next version of Mailman as a core feature)

Or ditch Mailman completely, it does not deserve to be a holy cow.
Comment 10 Andre Klapper 2012-11-10 16:41:36 UTC
Enhancement nowadays, preferably to fix in upstream Mailman, however I don't see this happen without volunteers' contributions.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links