Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <07FD1DA8-B61D-4A75-A192-39DCB5CC5CC3@apache.org>
From: Jan Lehnardt <jan@apache.org>
To: dev@couchdb.apache.org
In-Reply-To: <89EDB98E-AC08-44B3-8756-78E8F737AE0F@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Google Summer of Code
Date: Sat, 21 Mar 2009 13:58:14 +0000
References: <075E0C1F-ED7A-4097-8496-17F41B6A2EEB@apache.org>
 <2246F1C5-4008-4326-ACA3-39EF401A8728@apache.org>
 <89EDB98E-AC08-44B3-8756-78E8F737AE0F@apache.org>


On 21 Mar 2009, at 13:43, Jan Lehnardt wrote:

>
> On 5 Mar 2009, at 13:14, Jan Lehnardt wrote:
>
>> A little update.
>>
>> On 3 Mar 2009, at 13:06, Jan Lehnardt wrote:
>>
>>> last year, we missed the Google Summer of Code* application
>>> deadline by hours (my fault). This year, applications run on
>>> March 9th-13th.
>>
>> The ASF is already taking part and we can submit idea lists for
>> CouchDB under their umbrella.
>>
>> See http://wiki.apache.org/general/SummerOfCode2009 for more
>> information.
>>
>> We should have a list of ideas ready by March 23rd. I'll keep this
>> thread open for another while and then start collecting ideas that
>> we can vote on for Students to apply for.
>
> I added our wiki page to
>
> http://wiki.apache.org/general/SummerOfCode2008#preview

Smart move, I now added our proposals to
http://wiki.apache.org/general/SummerOfCode2009 (correct year)

Cheers
Jan
--


>
> Cheers
> Jan
> --
>
>
>
>>
>> Cheers
>> Jan
>> --
>>
>>
>>
>>> *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)?
>>>
>>> - A single person as an administrative contact. I volunteer for this
>>> position if nobody else is eager to take it.
>>>
>>> - A "list of ideas"** that includes a number of sub-projects that  
>>> students
>>> can apply for when working on CouchDB. This is where you come
>>> in! :) What feature of CouchDB would you like a student to work on
>>> during the summer?
>>>
>>> - A vote on which student-proposals to accept.
>>>
>>> - Once we have one or more students with an idea each, we'll need a
>>> 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 your 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 that 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
>>>
>>
>
>