Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of barrywark@gmail.com designates
 74.125.44.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=SciioZ6meZ1GvJWcbn268rWxS+ObnQ29A5PEToXpkvi1g6mLXjYN+o42ohmC1QTGpf
         tFU7kmMGaI6p03mIGNovfF4zWDllBP3mPJmM+chcY8/BGKIjPAL+ssHaN6IPNbt1KdLq
         95IvToTEyUQ7A+nKSsVX5lFILnwadok5RE33I=
MIME-Version: 1.0
In-Reply-To: <075E0C1F-ED7A-4097-8496-17F41B6A2EEB@apache.org>
References: <075E0C1F-ED7A-4097-8496-17F41B6A2EEB@apache.org>
Date: Tue, 3 Mar 2009 14:17:45 -0800
Message-ID: <cd7634ce0903031417o2b5f25dcib13fcbf2019c4349@mail.gmail.com>
Subject: Re: Google Summer of Code
From: Barry Wark <barrywark@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I don't claim to have groked CouchDB enough to know what the
priorities for GSoC projects should be, but the missing feature that
is preventing my organization from using CouchDB is the ability to
combine view results using boolean combinations (e.g. I want all the
doc ids of documents in view1 AND in view2 or all the doc ids of
documents in view1 OR view2 etc.), including temporary views.

I suspect this would be best implemented in Erlang, though perhaps the
proposal for enhancing the external view servers or better Lucene
integration is the better approach.

Barry

On Tue, Mar 3, 2009 at 4:06 AM, Jan Lehnardt <jan@apache.org> wrote:
> Hi dev@,
>
> last year, we missed the Google Summer of Code* application
> deadline by hours (my fault). This year, applications run on
> March 9th-13th.
>
> *http://code.google.com/soc/
>
> GSoC provides an excellent opportunity for open source projects
> to get students involved with the project and have larger areas of
> functionality covered.
>
> What is needed from our end (roughly, see the rest of the GSoC
> FaQ*** for more info)?
>
> =A0- A single person as an administrative contact. I volunteer for this
> =A0 position if nobody else is eager to take it.
>
> =A0- A "list of ideas"** that includes a number of sub-projects that stud=
ents
> =A0 can apply for when working on CouchDB. This is where you come
> =A0 in! :) What feature of CouchDB would you like a student to work on
> =A0 during the summer?
>
> =A0- A vote on which student-proposals to accept.
>
> =A0- Once we have one or more students with an idea each, we'll need a
> =A0 mentor for each sub-project.
>
>
> ** From the GSoC FaQ***:
>
> An "Ideas" list should be a list of suggested student projects. This list=
 is
> meant to introduce contributors to your project's needs and to provide
> inspiration to would-be student applicants. It is useful to classify each
> idea as specifically as possible, e.g. "must know Python" or "easier
> project; good for a student with more limited experience with C++." If yo=
ur
> organization plans to provide an application template, you should include=
 it
> on your Ideas list.
> Keep in mind that your Ideas list should be a starting point for student
> applications; we've heard from past mentoring organization participants t=
hat
> some of their best student projects are those that greatly expanded on a
> proposed idea or were blue-sky proposals not mentioned on the Ideas list =
at
> all.
>
> *** http://code.google.com/opensource/gsoc/2009/faqs.html
>