Return-Path: X-Original-To: apmail-lucene-general-archive@www.apache.org Delivered-To: apmail-lucene-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DAD6D1DA for ; Tue, 11 Dec 2012 13:58:53 +0000 (UTC) Received: (qmail 29043 invoked by uid 500); 11 Dec 2012 13:58:53 -0000 Delivered-To: apmail-lucene-general-archive@lucene.apache.org Received: (qmail 28593 invoked by uid 500); 11 Dec 2012 13:58:48 -0000 Mailing-List: contact general-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@lucene.apache.org Delivered-To: mailing list general@lucene.apache.org Received: (qmail 28568 invoked by uid 99); 11 Dec 2012 13:58:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 13:58:47 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com) (209.85.217.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2012 13:58:39 +0000 Received: by mail-lb0-f176.google.com with SMTP id k6so3263737lbo.35 for ; Tue, 11 Dec 2012 05:58:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=DJ7pIYSVh5RVE9KWZtC8xc9E0f3MHq3/SwnIwBdDtyE=; b=mF0ez99mP5U8hq3esyfYHqZPNvzRFNv8ki3/hxQL/ID7j6l9m4E0Vnf2yNoWKJDwBR I9QIy2zYwR83WyKVLxk9J60OsXrjGGl6ZyT9HqgzTUOIniAR3sblQPuSeNMEeh73v6px yTZ3rlqtduCsqrQBlnEP2hTJcWhOPSKcfL3UIs4kydQVg9vFiKETc6UQeDrannj4PyjY 8QjoodG74h529c/EovUYasJbjaqDHLT1DTkg4V3AdTxOTt7Dclfam+4/8HKpx/Jrdc0y Puixruq0fyjOmraKSxluRhZSG7NiEhTltMsiIYkSXz0N5LH2EV8unpurmHJu1YM1ovdu WSHQ== Received: by 10.112.40.197 with SMTP id z5mr7254549lbk.14.1355234298765; Tue, 11 Dec 2012 05:58:18 -0800 (PST) Received: from [10.99.1.35] (host86-150-222-41.range86-150.btcentralplus.com. [86.150.222.41]) by mx.google.com with ESMTPS id er8sm9341955lbb.9.2012.12.11.05.58.16 (version=SSLv3 cipher=OTHER); Tue, 11 Dec 2012 05:58:17 -0800 (PST) Message-ID: <50C73BED.50406@swiftkey.net> Date: Tue, 11 Dec 2012 13:58:05 +0000 From: Matthew Willson Reply-To: Paul Butcher User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: general@lucene.apache.org CC: Paul Butcher Subject: Advice/consulting from Lucene community on NLP-heavy search applications Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQn5vjaXzwENujNiYotGLV9rQGDOhazn1N8HjtQavngTtu/xSyEUejHQHrRy8lZTP8WWoT9H X-Virus-Checked: Checked by ClamAV on apache.org Hi all At Swiftkey we've developed a lot of expertise in language modelling in the course of developing predictive text entry products. We're now increasingly looking to solve information retrieval problems using related techniques, and have identified Lucene 4 as a potential basis for this work. Ours aren't standard web search applications though. We face some interesting challenges in incorporating NLP techniques into a scalable search architecture, and from our work so far it's clear that a fair amount of custom development will be necessary on top of Lucene. So we're reaching out for advice -- to help us avoid engineering pitfalls, speed up our understanding of relevant Lucene internals and extension points, and to ensure we make the best use of existing work in the Lucene ecosystem. For the right person this is something we're happy to pay for, either as commercial support, a consulting gig or potentially a full-time role out of our London office surrounded by a great engineering team full of NLP experts. We're also keen to give back to the Lucene community and open to discussion around open-sourcing some of the results of our work, potentially sponsoring specific pieces of feature development where we can identify a piece of work which fits into the community roadmap. Do get in touch with paul@swiftkey.net if this sounds interesting to you, or anyone else you know! Cheers, -Matthew