You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Dan Filimon <da...@gmail.com> on 2013/03/26 16:24:34 UTC

GSOC proposals and mentors [was Call to action – Mahout needs your help]

GSOC was mentioned in the other thread a couple of times.
And it turns out the deadline for mentoring organizations is coming up
this Friday _March 29_!

Isabel and Ted say they've had good experiences in the past and
Shannon and I are interested in helping this year.

__Do the rest of you want to do this? If so we need to get everything
ready really soon.__

So, let's get this moving if we want any students this year! Please
reply to this thread and say what you'd like to do for this summer and
what projects would be interesting for students to work on

Here's what we need to do [1] and number 7,
"
What is the URL for your Ideas list? **This is the most important part
of your proposal. Please make sure we can access it and it is complete
when you submit this proposal. “Placeholder” or inaccessible ideas
pages will be grounds for an automatic rejection for participation in
Google Summer of Code2013.**
"
is vital.

Here's [2] a list of requirements that mentors should ideally fulfill.
And here's what an ideas page should look like [3].

For everyone who's been working on this for some time and they have
new project ideas, let's get in touch!

We need to register here [4] by March 29 (Friday). I can take care of
the admin details, but we need the ideas.

[1] http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page#1._How_does_a_mentoring_organization
[2] http://en.flossmanuals.net/GSoCMentoring/what-makes-a-good-mentor/
[3] http://en.flossmanuals.net/GSoCMentoring/making-your-ideas-page/
[4] http://www.google-melange.com/gsoc/homepage/google/gsoc2013

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
More consistency is definitely a good thing and in the direction of what
Gokhan's been talking about in the other thread. :)

Would you kindly open JIRA issues for these proposals and label them
"gsoc2013" and "mentors"?
Thanks!


On Thu, Mar 28, 2013 at 7:32 PM, Andy Twigg <an...@gmail.com> wrote:

> I have two proposals:
> 1) I would be happy to support a similar effort on the classifier API.
> Indeed, I think the two APIs should be roughly the same, at least in
> terms of input/output so that pipelining etc is easier. (cf
> scikit-learn clustering/classifier/regression API)
>
> 2) As discussed before, I would like a cleaner interface for
> input/output and for specifying/inferring the data format. Marty has
> made great progress on ARFF formats for classifiers.
>
>
>
>
> On 28 March 2013 15:58, Dan Filimon <da...@gmail.com> wrote:
> > I made an issue for Ted's first suggestion about reforming the clustering
> > APIs. [1]
> >
> > Ted, could you explain a bit more what you mean by "simplify the
> connection
> > to Lucene for clustering and classification"? It's too vague for an idea
> > proposal.
> >
> > Also, everyone, don't hesitate to post new ideas and volunteer. :)
> > Tomorrow (March 29) is the deadline!
> >
> > [1] https://issues.apache.org/jira/browse/MAHOUT-1177
> >
> > On Wed, Mar 27, 2013 at 5:08 PM, Isabel Drost-Fromm <isabel@apache.org
> >wrote:
> >
> >> On Tuesday, March 26, 2013 07:26:22 PM Dan Filimon wrote:
> >> > Makes a lot of sense. Maybe you can give some advice to this year's
> >> > mentors though?
> >>
> >> Helping out and providing advice is no problem.
> >>
> >> Isabel
> >>
>
>
>
> --
> Dr Andy Twigg
> Junior Research Fellow, St Johns College, Oxford
> Room 351, Department of Computer Science
> http://www.cs.ox.ac.uk/people/andy.twigg/
> andy.twigg@cs.ox.ac.uk | +447799647538
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Andy Twigg <an...@gmail.com>.
I have two proposals:
1) I would be happy to support a similar effort on the classifier API.
Indeed, I think the two APIs should be roughly the same, at least in
terms of input/output so that pipelining etc is easier. (cf
scikit-learn clustering/classifier/regression API)

2) As discussed before, I would like a cleaner interface for
input/output and for specifying/inferring the data format. Marty has
made great progress on ARFF formats for classifiers.




On 28 March 2013 15:58, Dan Filimon <da...@gmail.com> wrote:
> I made an issue for Ted's first suggestion about reforming the clustering
> APIs. [1]
>
> Ted, could you explain a bit more what you mean by "simplify the connection
> to Lucene for clustering and classification"? It's too vague for an idea
> proposal.
>
> Also, everyone, don't hesitate to post new ideas and volunteer. :)
> Tomorrow (March 29) is the deadline!
>
> [1] https://issues.apache.org/jira/browse/MAHOUT-1177
>
> On Wed, Mar 27, 2013 at 5:08 PM, Isabel Drost-Fromm <is...@apache.org>wrote:
>
>> On Tuesday, March 26, 2013 07:26:22 PM Dan Filimon wrote:
>> > Makes a lot of sense. Maybe you can give some advice to this year's
>> > mentors though?
>>
>> Helping out and providing advice is no problem.
>>
>> Isabel
>>



-- 
Dr Andy Twigg
Junior Research Fellow, St Johns College, Oxford
Room 351, Department of Computer Science
http://www.cs.ox.ac.uk/people/andy.twigg/
andy.twigg@cs.ox.ac.uk | +447799647538

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Ted Dunning <te...@gmail.com>.
Fast iterators over different views of an index is definitely good for
recommendation.

An in-memory version is also nice.

A new JIRA for the part that you don't have is probably a good thing.
 Submit the patch you have so that we can make progress.



On Thu, Apr 11, 2013 at 5:20 AM, Gokhan Capan <gk...@gmail.com> wrote:

> Ok,
>
> Honestly I didn't understand the cross-recommendation, and I guess for
> possible persistent Lucene Matrix implementation, the desired feature is a
> fast iterator, which computes next by querying the index. Am I correct?
>
> Should I submit the diff for in memory version to MAHOUT-1178, or create a
> separate issue?
>
>
> On Wed, Apr 10, 2013 at 5:00 PM, Ted Dunning <te...@gmail.com>
> wrote:
>
> > This is awesome.  Not exactly what I asked for, but in some ways better
> > than what I asked for (I love it when that happens).  I think a
> sequential
> > implementation like this is a fine place to start.
> >
> > The array of matrices should work very well for moderate to small cross
> > recommendation.  If we have a sharded index, then we can build an
> > InputFormat on the top of this pretty easily.
> >
> > Can you put up a JIRA and a patch for this?
> >
> >
> > On Tue, Apr 9, 2013 at 10:43 AM, Gokhan Capan <gk...@gmail.com> wrote:
> >
> > > I have an implementation of "casting" a Lucene index to a
> > SparseRowMatrix,
> > > with following properties:
> > >
> > > - Row vectors are named and labeled with unique identifier id
> > > - Column vectors are labeled with terms
> > > - Dimensionality is numDocs * vocabularySize
> > > - It works on StringField, too.
> > > - It has a static creator for multiple fields, returns an array of
> > matrix.
> > > - It doesn't support numerical fields, yet.
> > >
> > > The code is tested, and I use it for instantiating matrices from Lucene
> > > indexes. I can submit a patch if it is desired.
> > >
> > > This is in memory, and loads the entire index to the matrix. Lately
> I've
> > > decided to implement a persistent version of it, which is planned to
> load
> > > from index whenever a get request is made, and writes to actual index
> > with
> > > a set request. And I plan to use the docID field, which was attached as
> > the
> > > row label in previous implementation as the actual row index. Rest will
> > be
> > > the same.
> > >
> > >
> > >
> > >
> > > On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
> > > wrote:
> > >
> > > > It should be possible to view a Lucene index as a matrix.  This would
> > > > require that we standardize on a way to convert documents to rows.
> >  There
> > > > are many choices, the discussion of which should be deferred to the
> > > actual
> > > > work on the project, but there are a few obvious constraints:
> > > >
> > > > a) it should be possible to get the same result as dumping the term
> > > vectors
> > > > for each document each to a line and converting that result using
> > > standard
> > > > Mahout methods.
> > > >
> > > > b) numeric fields ought to work somehow.
> > > >
> > > > c) if there are multiple text fields that ought to work sensibly as
> > well.
> > > >  Two options include dumping multiple matrices or to convert the
> fields
> > > > into a single row of a single matrix.
> > > >
> > > > d) it should be possible to refer back from a row of the matrix to
> find
> > > the
> > > > correct document.  THis might be because we remember the Lucene doc
> > > number
> > > > or because a field is named as holding a unique id.
> > > >
> > > > e) named vectors and matrices should be used if plausible.
> > > >
> > > > On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
> > > dangeorge.filimon@gmail.com
> > > > >wrote:
> > > >
> > > > > ...
> > > > > Ted, could you explain a bit more what you mean by "simplify the
> > > > connection
> > > > > to Lucene for clustering and classification"? It's too vague for an
> > > idea
> > > > > proposal.
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Gokhan
> > >
> >
>
>
>
> --
> Gokhan
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Gokhan Capan <gk...@gmail.com>.
Ok,

Honestly I didn't understand the cross-recommendation, and I guess for
possible persistent Lucene Matrix implementation, the desired feature is a
fast iterator, which computes next by querying the index. Am I correct?

Should I submit the diff for in memory version to MAHOUT-1178, or create a
separate issue?


On Wed, Apr 10, 2013 at 5:00 PM, Ted Dunning <te...@gmail.com> wrote:

> This is awesome.  Not exactly what I asked for, but in some ways better
> than what I asked for (I love it when that happens).  I think a sequential
> implementation like this is a fine place to start.
>
> The array of matrices should work very well for moderate to small cross
> recommendation.  If we have a sharded index, then we can build an
> InputFormat on the top of this pretty easily.
>
> Can you put up a JIRA and a patch for this?
>
>
> On Tue, Apr 9, 2013 at 10:43 AM, Gokhan Capan <gk...@gmail.com> wrote:
>
> > I have an implementation of "casting" a Lucene index to a
> SparseRowMatrix,
> > with following properties:
> >
> > - Row vectors are named and labeled with unique identifier id
> > - Column vectors are labeled with terms
> > - Dimensionality is numDocs * vocabularySize
> > - It works on StringField, too.
> > - It has a static creator for multiple fields, returns an array of
> matrix.
> > - It doesn't support numerical fields, yet.
> >
> > The code is tested, and I use it for instantiating matrices from Lucene
> > indexes. I can submit a patch if it is desired.
> >
> > This is in memory, and loads the entire index to the matrix. Lately I've
> > decided to implement a persistent version of it, which is planned to load
> > from index whenever a get request is made, and writes to actual index
> with
> > a set request. And I plan to use the docID field, which was attached as
> the
> > row label in previous implementation as the actual row index. Rest will
> be
> > the same.
> >
> >
> >
> >
> > On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
> > wrote:
> >
> > > It should be possible to view a Lucene index as a matrix.  This would
> > > require that we standardize on a way to convert documents to rows.
>  There
> > > are many choices, the discussion of which should be deferred to the
> > actual
> > > work on the project, but there are a few obvious constraints:
> > >
> > > a) it should be possible to get the same result as dumping the term
> > vectors
> > > for each document each to a line and converting that result using
> > standard
> > > Mahout methods.
> > >
> > > b) numeric fields ought to work somehow.
> > >
> > > c) if there are multiple text fields that ought to work sensibly as
> well.
> > >  Two options include dumping multiple matrices or to convert the fields
> > > into a single row of a single matrix.
> > >
> > > d) it should be possible to refer back from a row of the matrix to find
> > the
> > > correct document.  THis might be because we remember the Lucene doc
> > number
> > > or because a field is named as holding a unique id.
> > >
> > > e) named vectors and matrices should be used if plausible.
> > >
> > > On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
> > dangeorge.filimon@gmail.com
> > > >wrote:
> > >
> > > > ...
> > > > Ted, could you explain a bit more what you mean by "simplify the
> > > connection
> > > > to Lucene for clustering and classification"? It's too vague for an
> > idea
> > > > proposal.
> > > >
> > >
> >
> >
> >
> > --
> > Gokhan
> >
>



-- 
Gokhan

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Ted Dunning <te...@gmail.com>.
This is awesome.  Not exactly what I asked for, but in some ways better
than what I asked for (I love it when that happens).  I think a sequential
implementation like this is a fine place to start.

The array of matrices should work very well for moderate to small cross
recommendation.  If we have a sharded index, then we can build an
InputFormat on the top of this pretty easily.

Can you put up a JIRA and a patch for this?


On Tue, Apr 9, 2013 at 10:43 AM, Gokhan Capan <gk...@gmail.com> wrote:

> I have an implementation of "casting" a Lucene index to a SparseRowMatrix,
> with following properties:
>
> - Row vectors are named and labeled with unique identifier id
> - Column vectors are labeled with terms
> - Dimensionality is numDocs * vocabularySize
> - It works on StringField, too.
> - It has a static creator for multiple fields, returns an array of matrix.
> - It doesn't support numerical fields, yet.
>
> The code is tested, and I use it for instantiating matrices from Lucene
> indexes. I can submit a patch if it is desired.
>
> This is in memory, and loads the entire index to the matrix. Lately I've
> decided to implement a persistent version of it, which is planned to load
> from index whenever a get request is made, and writes to actual index with
> a set request. And I plan to use the docID field, which was attached as the
> row label in previous implementation as the actual row index. Rest will be
> the same.
>
>
>
>
> On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
> wrote:
>
> > It should be possible to view a Lucene index as a matrix.  This would
> > require that we standardize on a way to convert documents to rows.  There
> > are many choices, the discussion of which should be deferred to the
> actual
> > work on the project, but there are a few obvious constraints:
> >
> > a) it should be possible to get the same result as dumping the term
> vectors
> > for each document each to a line and converting that result using
> standard
> > Mahout methods.
> >
> > b) numeric fields ought to work somehow.
> >
> > c) if there are multiple text fields that ought to work sensibly as well.
> >  Two options include dumping multiple matrices or to convert the fields
> > into a single row of a single matrix.
> >
> > d) it should be possible to refer back from a row of the matrix to find
> the
> > correct document.  THis might be because we remember the Lucene doc
> number
> > or because a field is named as holding a unique id.
> >
> > e) named vectors and matrices should be used if plausible.
> >
> > On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
> dangeorge.filimon@gmail.com
> > >wrote:
> >
> > > ...
> > > Ted, could you explain a bit more what you mean by "simplify the
> > connection
> > > to Lucene for clustering and classification"? It's too vague for an
> idea
> > > proposal.
> > >
> >
>
>
>
> --
> Gokhan
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Gokhan Capan <gk...@gmail.com>.
*- Row vectors are named and labeled with unique identifier field of the
index defined by the client


On Tue, Apr 9, 2013 at 8:43 PM, Gokhan Capan <gk...@gmail.com> wrote:

> I have an implementation of "casting" a Lucene index to a SparseRowMatrix,
> with following properties:
>
> - Row vectors are named and labeled with unique identifier id
> - Column vectors are labeled with terms
> - Dimensionality is numDocs * vocabularySize
> - It works on StringField, too.
> - It has a static creator for multiple fields, returns an array of matrix.
> - It doesn't support numerical fields, yet.
>
> The code is tested, and I use it for instantiating matrices from Lucene
> indexes. I can submit a patch if it is desired.
>
> This is in memory, and loads the entire index to the matrix. Lately I've
> decided to implement a persistent version of it, which is planned to load
> from index whenever a get request is made, and writes to actual index with
> a set request. And I plan to use the docID field, which was attached as the
> row label in previous implementation as the actual row index. Rest will be
> the same.
>
>
>
>
> On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>wrote:
>
>> It should be possible to view a Lucene index as a matrix.  This would
>> require that we standardize on a way to convert documents to rows.  There
>> are many choices, the discussion of which should be deferred to the actual
>> work on the project, but there are a few obvious constraints:
>>
>> a) it should be possible to get the same result as dumping the term
>> vectors
>> for each document each to a line and converting that result using standard
>> Mahout methods.
>>
>> b) numeric fields ought to work somehow.
>>
>> c) if there are multiple text fields that ought to work sensibly as well.
>>  Two options include dumping multiple matrices or to convert the fields
>> into a single row of a single matrix.
>>
>> d) it should be possible to refer back from a row of the matrix to find
>> the
>> correct document.  THis might be because we remember the Lucene doc number
>> or because a field is named as holding a unique id.
>>
>> e) named vectors and matrices should be used if plausible.
>>
>> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <dangeorge.filimon@gmail.com
>> >wrote:
>>
>> > ...
>> > Ted, could you explain a bit more what you mean by "simplify the
>> connection
>> > to Lucene for clustering and classification"? It's too vague for an idea
>> > proposal.
>> >
>>
>
>
>
> --
> Gokhan
>



-- 
Gokhan

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Gokhan Capan <gk...@gmail.com>.
I have an implementation of "casting" a Lucene index to a SparseRowMatrix,
with following properties:

- Row vectors are named and labeled with unique identifier id
- Column vectors are labeled with terms
- Dimensionality is numDocs * vocabularySize
- It works on StringField, too.
- It has a static creator for multiple fields, returns an array of matrix.
- It doesn't support numerical fields, yet.

The code is tested, and I use it for instantiating matrices from Lucene
indexes. I can submit a patch if it is desired.

This is in memory, and loads the entire index to the matrix. Lately I've
decided to implement a persistent version of it, which is planned to load
from index whenever a get request is made, and writes to actual index with
a set request. And I plan to use the docID field, which was attached as the
row label in previous implementation as the actual row index. Rest will be
the same.




On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com> wrote:

> It should be possible to view a Lucene index as a matrix.  This would
> require that we standardize on a way to convert documents to rows.  There
> are many choices, the discussion of which should be deferred to the actual
> work on the project, but there are a few obvious constraints:
>
> a) it should be possible to get the same result as dumping the term vectors
> for each document each to a line and converting that result using standard
> Mahout methods.
>
> b) numeric fields ought to work somehow.
>
> c) if there are multiple text fields that ought to work sensibly as well.
>  Two options include dumping multiple matrices or to convert the fields
> into a single row of a single matrix.
>
> d) it should be possible to refer back from a row of the matrix to find the
> correct document.  THis might be because we remember the Lucene doc number
> or because a field is named as holding a unique id.
>
> e) named vectors and matrices should be used if plausible.
>
> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <dangeorge.filimon@gmail.com
> >wrote:
>
> > ...
> > Ted, could you explain a bit more what you mean by "simplify the
> connection
> > to Lucene for clustering and classification"? It's too vague for an idea
> > proposal.
> >
>



-- 
Gokhan

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
On Tue, Apr 9, 2013 at 5:15 PM, Shannon Quinn <sq...@gatech.edu> wrote:

> I volunteer.


Brave man! Thank you!

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Shannon Quinn <sq...@gatech.edu>.
I volunteer.

On 4/9/13 10:12 AM, Dan Filimon wrote:
> I can confirm Apache got in! :)
> The slot assignment is not yet clear however.
>
> And, because mailing people to death is what I do, volunteers for mentoring?
>
>
> On Thu, Apr 4, 2013 at 9:49 PM, Shannon Quinn <sq...@gatech.edu> wrote:
>
>> According to the GSoC calendar, accepted organizations aren't posted until
>> April 8 (Monday), at which point (assuming Apache is accepted...I can't
>> imagine it wouldn't be) slots will be doled out internally. This will
>> probably take at least a day or two, so probably by middle of next week
>> we'll know how many slots Mahout has.
>>
>> Speaking of which: how do the various subprojects negotiate for slots? Is
>> there a central spreadsheet, or an IRC meeting to attend? Or did I miss the
>> email detailing this?
>>
>>
>> On 4/4/13 2:43 PM, Dan Filimon wrote:
>>
>>> Any news on this front? Did we get approved/assigned a slot/anything?
>>>
>>>
>>> On Fri, Mar 29, 2013 at 7:44 PM, Dan Filimon <dangeorge.filimon@gmail.com
>>>> **wrote:
>>>   Ok, updated!
>>>>
>>>> On Fri, Mar 29, 2013 at 7:36 PM, Andy Twigg <an...@gmail.com>
>>>> wrote:
>>>>
>>>>   Dan,
>>>>> I think what you've written is fine (I wanted to edit to remove the
>>>>> '?' around random forests but couldn't).
>>>>>
>>>>> ok?
>>>>>
>>>>>
>>>>>
>>>>> On 29 March 2013 11:14, Dan Filimon <da...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> I added Andy's first suggestion and Ted's suggestion as ideas.
>>>>>>
>>>>>> Andy, could you flesh out your second suggestion into a project and
>>>>>>
>>>>> make an
>>>>>
>>>>>> issue please?
>>>>>>
>>>>>>
>>>>>> On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
>>>>>>
>>>>> wrote:
>>>>>
>>>>>> It should be possible to view a Lucene index as a matrix.  This would
>>>>>>> require that we standardize on a way to convert documents to rows.
>>>>>>>
>>>>>>    There
>>>>>> are many choices, the discussion of which should be deferred to the
>>>>>> actual
>>>>>> work on the project, but there are a few obvious constraints:
>>>>>>> a) it should be possible to get the same result as dumping the term
>>>>>>>
>>>>>> vectors
>>>>>> for each document each to a line and converting that result using
>>>>>> standard
>>>>>> Mahout methods.
>>>>>>> b) numeric fields ought to work somehow.
>>>>>>>
>>>>>>> c) if there are multiple text fields that ought to work sensibly as
>>>>>>>
>>>>>> well.
>>>>>>    Two options include dumping multiple matrices or to convert the
>>>>>>> fields
>>>>>>> into a single row of a single matrix.
>>>>>>>
>>>>>>> d) it should be possible to refer back from a row of the matrix to
>>>>>>>
>>>>>> find the
>>>>>> correct document.  THis might be because we remember the Lucene doc
>>>>>> number
>>>>>> or because a field is named as holding a unique id.
>>>>>>> e) named vectors and matrices should be used if plausible.
>>>>>>>
>>>>>>> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
>>>>>>>
>>>>>> dangeorge.filimon@gmail.com
>>>>>> wrote:
>>>>>>>> ...
>>>>>>>> Ted, could you explain a bit more what you mean by "simplify the
>>>>>>>>
>>>>>>> connection
>>>>>>>
>>>>>>>> to Lucene for clustering and classification"? It's too vague for an
>>>>>>>>
>>>>>>> idea
>>>>>> proposal.
>>>>>>>>
>>>>> --
>>>>> Dr Andy Twigg
>>>>> Junior Research Fellow, St Johns College, Oxford
>>>>> Room 351, Department of Computer Science
>>>>> http://www.cs.ox.ac.uk/people/**andy.twigg/<http://www.cs.ox.ac.uk/people/andy.twigg/>
>>>>> andy.twigg@cs.ox.ac.uk | +447799647538
>>>>>
>>>>>


Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
I can confirm Apache got in! :)
The slot assignment is not yet clear however.

And, because mailing people to death is what I do, volunteers for mentoring?


On Thu, Apr 4, 2013 at 9:49 PM, Shannon Quinn <sq...@gatech.edu> wrote:

> According to the GSoC calendar, accepted organizations aren't posted until
> April 8 (Monday), at which point (assuming Apache is accepted...I can't
> imagine it wouldn't be) slots will be doled out internally. This will
> probably take at least a day or two, so probably by middle of next week
> we'll know how many slots Mahout has.
>
> Speaking of which: how do the various subprojects negotiate for slots? Is
> there a central spreadsheet, or an IRC meeting to attend? Or did I miss the
> email detailing this?
>
>
> On 4/4/13 2:43 PM, Dan Filimon wrote:
>
>> Any news on this front? Did we get approved/assigned a slot/anything?
>>
>>
>> On Fri, Mar 29, 2013 at 7:44 PM, Dan Filimon <dangeorge.filimon@gmail.com
>> >**wrote:
>>
>>  Ok, updated!
>>>
>>>
>>> On Fri, Mar 29, 2013 at 7:36 PM, Andy Twigg <an...@gmail.com>
>>> wrote:
>>>
>>>  Dan,
>>>>
>>>> I think what you've written is fine (I wanted to edit to remove the
>>>> '?' around random forests but couldn't).
>>>>
>>>> ok?
>>>>
>>>>
>>>>
>>>> On 29 March 2013 11:14, Dan Filimon <da...@gmail.com>
>>>> wrote:
>>>>
>>>>> I added Andy's first suggestion and Ted's suggestion as ideas.
>>>>>
>>>>> Andy, could you flesh out your second suggestion into a project and
>>>>>
>>>> make an
>>>>
>>>>> issue please?
>>>>>
>>>>>
>>>>> On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
>>>>>
>>>> wrote:
>>>>
>>>>> It should be possible to view a Lucene index as a matrix.  This would
>>>>>> require that we standardize on a way to convert documents to rows.
>>>>>>
>>>>>   There
>>>>
>>>>> are many choices, the discussion of which should be deferred to the
>>>>>>
>>>>> actual
>>>>
>>>>> work on the project, but there are a few obvious constraints:
>>>>>>
>>>>>> a) it should be possible to get the same result as dumping the term
>>>>>>
>>>>> vectors
>>>>
>>>>> for each document each to a line and converting that result using
>>>>>>
>>>>> standard
>>>>
>>>>> Mahout methods.
>>>>>>
>>>>>> b) numeric fields ought to work somehow.
>>>>>>
>>>>>> c) if there are multiple text fields that ought to work sensibly as
>>>>>>
>>>>> well.
>>>>
>>>>>   Two options include dumping multiple matrices or to convert the
>>>>>> fields
>>>>>> into a single row of a single matrix.
>>>>>>
>>>>>> d) it should be possible to refer back from a row of the matrix to
>>>>>>
>>>>> find the
>>>>
>>>>> correct document.  THis might be because we remember the Lucene doc
>>>>>>
>>>>> number
>>>>
>>>>> or because a field is named as holding a unique id.
>>>>>>
>>>>>> e) named vectors and matrices should be used if plausible.
>>>>>>
>>>>>> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
>>>>>>
>>>>> dangeorge.filimon@gmail.com
>>>>
>>>>> wrote:
>>>>>>> ...
>>>>>>> Ted, could you explain a bit more what you mean by "simplify the
>>>>>>>
>>>>>> connection
>>>>>>
>>>>>>> to Lucene for clustering and classification"? It's too vague for an
>>>>>>>
>>>>>> idea
>>>>
>>>>> proposal.
>>>>>>>
>>>>>>>
>>>>
>>>> --
>>>> Dr Andy Twigg
>>>> Junior Research Fellow, St Johns College, Oxford
>>>> Room 351, Department of Computer Science
>>>> http://www.cs.ox.ac.uk/people/**andy.twigg/<http://www.cs.ox.ac.uk/people/andy.twigg/>
>>>> andy.twigg@cs.ox.ac.uk | +447799647538
>>>>
>>>>
>>>
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Shannon Quinn <sq...@gatech.edu>.
According to the GSoC calendar, accepted organizations aren't posted 
until April 8 (Monday), at which point (assuming Apache is accepted...I 
can't imagine it wouldn't be) slots will be doled out internally. This 
will probably take at least a day or two, so probably by middle of next 
week we'll know how many slots Mahout has.

Speaking of which: how do the various subprojects negotiate for slots? 
Is there a central spreadsheet, or an IRC meeting to attend? Or did I 
miss the email detailing this?

On 4/4/13 2:43 PM, Dan Filimon wrote:
> Any news on this front? Did we get approved/assigned a slot/anything?
>
>
> On Fri, Mar 29, 2013 at 7:44 PM, Dan Filimon <da...@gmail.com>wrote:
>
>> Ok, updated!
>>
>>
>> On Fri, Mar 29, 2013 at 7:36 PM, Andy Twigg <an...@gmail.com> wrote:
>>
>>> Dan,
>>>
>>> I think what you've written is fine (I wanted to edit to remove the
>>> '?' around random forests but couldn't).
>>>
>>> ok?
>>>
>>>
>>>
>>> On 29 March 2013 11:14, Dan Filimon <da...@gmail.com> wrote:
>>>> I added Andy's first suggestion and Ted's suggestion as ideas.
>>>>
>>>> Andy, could you flesh out your second suggestion into a project and
>>> make an
>>>> issue please?
>>>>
>>>>
>>>> On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
>>> wrote:
>>>>> It should be possible to view a Lucene index as a matrix.  This would
>>>>> require that we standardize on a way to convert documents to rows.
>>>   There
>>>>> are many choices, the discussion of which should be deferred to the
>>> actual
>>>>> work on the project, but there are a few obvious constraints:
>>>>>
>>>>> a) it should be possible to get the same result as dumping the term
>>> vectors
>>>>> for each document each to a line and converting that result using
>>> standard
>>>>> Mahout methods.
>>>>>
>>>>> b) numeric fields ought to work somehow.
>>>>>
>>>>> c) if there are multiple text fields that ought to work sensibly as
>>> well.
>>>>>   Two options include dumping multiple matrices or to convert the fields
>>>>> into a single row of a single matrix.
>>>>>
>>>>> d) it should be possible to refer back from a row of the matrix to
>>> find the
>>>>> correct document.  THis might be because we remember the Lucene doc
>>> number
>>>>> or because a field is named as holding a unique id.
>>>>>
>>>>> e) named vectors and matrices should be used if plausible.
>>>>>
>>>>> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
>>> dangeorge.filimon@gmail.com
>>>>>> wrote:
>>>>>> ...
>>>>>> Ted, could you explain a bit more what you mean by "simplify the
>>>>> connection
>>>>>> to Lucene for clustering and classification"? It's too vague for an
>>> idea
>>>>>> proposal.
>>>>>>
>>>
>>>
>>> --
>>> Dr Andy Twigg
>>> Junior Research Fellow, St Johns College, Oxford
>>> Room 351, Department of Computer Science
>>> http://www.cs.ox.ac.uk/people/andy.twigg/
>>> andy.twigg@cs.ox.ac.uk | +447799647538
>>>
>>


Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
Any news on this front? Did we get approved/assigned a slot/anything?


On Fri, Mar 29, 2013 at 7:44 PM, Dan Filimon <da...@gmail.com>wrote:

> Ok, updated!
>
>
> On Fri, Mar 29, 2013 at 7:36 PM, Andy Twigg <an...@gmail.com> wrote:
>
>> Dan,
>>
>> I think what you've written is fine (I wanted to edit to remove the
>> '?' around random forests but couldn't).
>>
>> ok?
>>
>>
>>
>> On 29 March 2013 11:14, Dan Filimon <da...@gmail.com> wrote:
>> > I added Andy's first suggestion and Ted's suggestion as ideas.
>> >
>> > Andy, could you flesh out your second suggestion into a project and
>> make an
>> > issue please?
>> >
>> >
>> > On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
>> wrote:
>> >
>> >> It should be possible to view a Lucene index as a matrix.  This would
>> >> require that we standardize on a way to convert documents to rows.
>>  There
>> >> are many choices, the discussion of which should be deferred to the
>> actual
>> >> work on the project, but there are a few obvious constraints:
>> >>
>> >> a) it should be possible to get the same result as dumping the term
>> vectors
>> >> for each document each to a line and converting that result using
>> standard
>> >> Mahout methods.
>> >>
>> >> b) numeric fields ought to work somehow.
>> >>
>> >> c) if there are multiple text fields that ought to work sensibly as
>> well.
>> >>  Two options include dumping multiple matrices or to convert the fields
>> >> into a single row of a single matrix.
>> >>
>> >> d) it should be possible to refer back from a row of the matrix to
>> find the
>> >> correct document.  THis might be because we remember the Lucene doc
>> number
>> >> or because a field is named as holding a unique id.
>> >>
>> >> e) named vectors and matrices should be used if plausible.
>> >>
>> >> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
>> dangeorge.filimon@gmail.com
>> >> >wrote:
>> >>
>> >> > ...
>> >> > Ted, could you explain a bit more what you mean by "simplify the
>> >> connection
>> >> > to Lucene for clustering and classification"? It's too vague for an
>> idea
>> >> > proposal.
>> >> >
>> >>
>>
>>
>>
>> --
>> Dr Andy Twigg
>> Junior Research Fellow, St Johns College, Oxford
>> Room 351, Department of Computer Science
>> http://www.cs.ox.ac.uk/people/andy.twigg/
>> andy.twigg@cs.ox.ac.uk | +447799647538
>>
>
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
Ok, updated!


On Fri, Mar 29, 2013 at 7:36 PM, Andy Twigg <an...@gmail.com> wrote:

> Dan,
>
> I think what you've written is fine (I wanted to edit to remove the
> '?' around random forests but couldn't).
>
> ok?
>
>
>
> On 29 March 2013 11:14, Dan Filimon <da...@gmail.com> wrote:
> > I added Andy's first suggestion and Ted's suggestion as ideas.
> >
> > Andy, could you flesh out your second suggestion into a project and make
> an
> > issue please?
> >
> >
> > On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com>
> wrote:
> >
> >> It should be possible to view a Lucene index as a matrix.  This would
> >> require that we standardize on a way to convert documents to rows.
>  There
> >> are many choices, the discussion of which should be deferred to the
> actual
> >> work on the project, but there are a few obvious constraints:
> >>
> >> a) it should be possible to get the same result as dumping the term
> vectors
> >> for each document each to a line and converting that result using
> standard
> >> Mahout methods.
> >>
> >> b) numeric fields ought to work somehow.
> >>
> >> c) if there are multiple text fields that ought to work sensibly as
> well.
> >>  Two options include dumping multiple matrices or to convert the fields
> >> into a single row of a single matrix.
> >>
> >> d) it should be possible to refer back from a row of the matrix to find
> the
> >> correct document.  THis might be because we remember the Lucene doc
> number
> >> or because a field is named as holding a unique id.
> >>
> >> e) named vectors and matrices should be used if plausible.
> >>
> >> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <
> dangeorge.filimon@gmail.com
> >> >wrote:
> >>
> >> > ...
> >> > Ted, could you explain a bit more what you mean by "simplify the
> >> connection
> >> > to Lucene for clustering and classification"? It's too vague for an
> idea
> >> > proposal.
> >> >
> >>
>
>
>
> --
> Dr Andy Twigg
> Junior Research Fellow, St Johns College, Oxford
> Room 351, Department of Computer Science
> http://www.cs.ox.ac.uk/people/andy.twigg/
> andy.twigg@cs.ox.ac.uk | +447799647538
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Andy Twigg <an...@gmail.com>.
Dan,

I think what you've written is fine (I wanted to edit to remove the
'?' around random forests but couldn't).

ok?



On 29 March 2013 11:14, Dan Filimon <da...@gmail.com> wrote:
> I added Andy's first suggestion and Ted's suggestion as ideas.
>
> Andy, could you flesh out your second suggestion into a project and make an
> issue please?
>
>
> On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com> wrote:
>
>> It should be possible to view a Lucene index as a matrix.  This would
>> require that we standardize on a way to convert documents to rows.  There
>> are many choices, the discussion of which should be deferred to the actual
>> work on the project, but there are a few obvious constraints:
>>
>> a) it should be possible to get the same result as dumping the term vectors
>> for each document each to a line and converting that result using standard
>> Mahout methods.
>>
>> b) numeric fields ought to work somehow.
>>
>> c) if there are multiple text fields that ought to work sensibly as well.
>>  Two options include dumping multiple matrices or to convert the fields
>> into a single row of a single matrix.
>>
>> d) it should be possible to refer back from a row of the matrix to find the
>> correct document.  THis might be because we remember the Lucene doc number
>> or because a field is named as holding a unique id.
>>
>> e) named vectors and matrices should be used if plausible.
>>
>> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <dangeorge.filimon@gmail.com
>> >wrote:
>>
>> > ...
>> > Ted, could you explain a bit more what you mean by "simplify the
>> connection
>> > to Lucene for clustering and classification"? It's too vague for an idea
>> > proposal.
>> >
>>



-- 
Dr Andy Twigg
Junior Research Fellow, St Johns College, Oxford
Room 351, Department of Computer Science
http://www.cs.ox.ac.uk/people/andy.twigg/
andy.twigg@cs.ox.ac.uk | +447799647538

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
I added Andy's first suggestion and Ted's suggestion as ideas.

Andy, could you flesh out your second suggestion into a project and make an
issue please?


On Fri, Mar 29, 2013 at 3:53 AM, Ted Dunning <te...@gmail.com> wrote:

> It should be possible to view a Lucene index as a matrix.  This would
> require that we standardize on a way to convert documents to rows.  There
> are many choices, the discussion of which should be deferred to the actual
> work on the project, but there are a few obvious constraints:
>
> a) it should be possible to get the same result as dumping the term vectors
> for each document each to a line and converting that result using standard
> Mahout methods.
>
> b) numeric fields ought to work somehow.
>
> c) if there are multiple text fields that ought to work sensibly as well.
>  Two options include dumping multiple matrices or to convert the fields
> into a single row of a single matrix.
>
> d) it should be possible to refer back from a row of the matrix to find the
> correct document.  THis might be because we remember the Lucene doc number
> or because a field is named as holding a unique id.
>
> e) named vectors and matrices should be used if plausible.
>
> On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <dangeorge.filimon@gmail.com
> >wrote:
>
> > ...
> > Ted, could you explain a bit more what you mean by "simplify the
> connection
> > to Lucene for clustering and classification"? It's too vague for an idea
> > proposal.
> >
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Ted Dunning <te...@gmail.com>.
It should be possible to view a Lucene index as a matrix.  This would
require that we standardize on a way to convert documents to rows.  There
are many choices, the discussion of which should be deferred to the actual
work on the project, but there are a few obvious constraints:

a) it should be possible to get the same result as dumping the term vectors
for each document each to a line and converting that result using standard
Mahout methods.

b) numeric fields ought to work somehow.

c) if there are multiple text fields that ought to work sensibly as well.
 Two options include dumping multiple matrices or to convert the fields
into a single row of a single matrix.

d) it should be possible to refer back from a row of the matrix to find the
correct document.  THis might be because we remember the Lucene doc number
or because a field is named as holding a unique id.

e) named vectors and matrices should be used if plausible.

On Thu, Mar 28, 2013 at 4:58 PM, Dan Filimon <da...@gmail.com>wrote:

> ...
> Ted, could you explain a bit more what you mean by "simplify the connection
> to Lucene for clustering and classification"? It's too vague for an idea
> proposal.
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
I made an issue for Ted's first suggestion about reforming the clustering
APIs. [1]

Ted, could you explain a bit more what you mean by "simplify the connection
to Lucene for clustering and classification"? It's too vague for an idea
proposal.

Also, everyone, don't hesitate to post new ideas and volunteer. :)
Tomorrow (March 29) is the deadline!

[1] https://issues.apache.org/jira/browse/MAHOUT-1177

On Wed, Mar 27, 2013 at 5:08 PM, Isabel Drost-Fromm <is...@apache.org>wrote:

> On Tuesday, March 26, 2013 07:26:22 PM Dan Filimon wrote:
> > Makes a lot of sense. Maybe you can give some advice to this year's
> > mentors though?
>
> Helping out and providing advice is no problem.
>
> Isabel
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Isabel Drost-Fromm <is...@apache.org>.
On Tuesday, March 26, 2013 07:26:22 PM Dan Filimon wrote:
> Makes a lot of sense. Maybe you can give some advice to this year's
> mentors though?

Helping out and providing advice is no problem.

Isabel

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Ted Dunning <te...@gmail.com>.
I can help peripherally, but my travel schedule is heinous and would
prevent full on mentoring.

On Tue, Mar 26, 2013 at 8:44 PM, Dan Filimon <da...@gmail.com>wrote:

> Okay, we just need to add JIRA issues that have the tags "gsoc2013"
> and "mentors" and we're good.
>
> The deadline for the ideas is March 29 and the mentor selection comes
> after.
>
> On Tue, Mar 26, 2013 at 7:26 PM, Dan Filimon
> <da...@gmail.com> wrote:
> > Makes a lot of sense. Maybe you can give some advice to this year's
> > mentors though?
> >
> > I contacted the ComDev list to ask for what we need to do. But, any
> > volunteers? :D
> >
> > On Tue, Mar 26, 2013 at 6:32 PM, Isabel Drost <is...@apache.org> wrote:
> >> On Tue, Mar 26, 2013 at 5:17 PM, Dan Filimon <
> dangeorge.filimon@gmail.com>wrote:
> >>
> >>> So, Isabel, do you want to be a mentor?
> >>>
> >>
> >> As much as I'd love to and as much as I've enjoyed it in previous years
> I
> >> know that I cannot put in as much time as I would like to. I've once
> made
> >> the mistake of committing to too much between March and June in 2011 -
> it
> >> didn't turn out to be a good decision. I need this year to free up more
> of
> >> my time before committing to mentor again.
> >>
> >> Isabel
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Ted Dunning <te...@gmail.com>.
Here are some ideas:

- reform and simplify the clustering API's.  All of our main-line
clustering systems should work identically and have good and simple
diagnostics.

- simplify the connection to Lucene for clustering and classification.


On Tue, Mar 26, 2013 at 8:44 PM, Dan Filimon <da...@gmail.com>wrote:

> Okay, we just need to add JIRA issues that have the tags "gsoc2013"
> and "mentors" and we're good.
>
> The deadline for the ideas is March 29 and the mentor selection comes
> after.
>
> On Tue, Mar 26, 2013 at 7:26 PM, Dan Filimon
> <da...@gmail.com> wrote:
> > Makes a lot of sense. Maybe you can give some advice to this year's
> > mentors though?
> >
> > I contacted the ComDev list to ask for what we need to do. But, any
> > volunteers? :D
> >
> > On Tue, Mar 26, 2013 at 6:32 PM, Isabel Drost <is...@apache.org> wrote:
> >> On Tue, Mar 26, 2013 at 5:17 PM, Dan Filimon <
> dangeorge.filimon@gmail.com>wrote:
> >>
> >>> So, Isabel, do you want to be a mentor?
> >>>
> >>
> >> As much as I'd love to and as much as I've enjoyed it in previous years
> I
> >> know that I cannot put in as much time as I would like to. I've once
> made
> >> the mistake of committing to too much between March and June in 2011 -
> it
> >> didn't turn out to be a good decision. I need this year to free up more
> of
> >> my time before committing to mentor again.
> >>
> >> Isabel
>

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
Okay, we just need to add JIRA issues that have the tags "gsoc2013"
and "mentors" and we're good.

The deadline for the ideas is March 29 and the mentor selection comes after.

On Tue, Mar 26, 2013 at 7:26 PM, Dan Filimon
<da...@gmail.com> wrote:
> Makes a lot of sense. Maybe you can give some advice to this year's
> mentors though?
>
> I contacted the ComDev list to ask for what we need to do. But, any
> volunteers? :D
>
> On Tue, Mar 26, 2013 at 6:32 PM, Isabel Drost <is...@apache.org> wrote:
>> On Tue, Mar 26, 2013 at 5:17 PM, Dan Filimon <da...@gmail.com>wrote:
>>
>>> So, Isabel, do you want to be a mentor?
>>>
>>
>> As much as I'd love to and as much as I've enjoyed it in previous years I
>> know that I cannot put in as much time as I would like to. I've once made
>> the mistake of committing to too much between March and June in 2011 - it
>> didn't turn out to be a good decision. I need this year to free up more of
>> my time before committing to mentor again.
>>
>> Isabel

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
Makes a lot of sense. Maybe you can give some advice to this year's
mentors though?

I contacted the ComDev list to ask for what we need to do. But, any
volunteers? :D

On Tue, Mar 26, 2013 at 6:32 PM, Isabel Drost <is...@apache.org> wrote:
> On Tue, Mar 26, 2013 at 5:17 PM, Dan Filimon <da...@gmail.com>wrote:
>
>> So, Isabel, do you want to be a mentor?
>>
>
> As much as I'd love to and as much as I've enjoyed it in previous years I
> know that I cannot put in as much time as I would like to. I've once made
> the mistake of committing to too much between March and June in 2011 - it
> didn't turn out to be a good decision. I need this year to free up more of
> my time before committing to mentor again.
>
> Isabel

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Isabel Drost <is...@apache.org>.
On Tue, Mar 26, 2013 at 5:17 PM, Dan Filimon <da...@gmail.com>wrote:

> So, Isabel, do you want to be a mentor?
>

As much as I'd love to and as much as I've enjoyed it in previous years I
know that I cannot put in as much time as I would like to. I've once made
the mistake of committing to too much between March and June in 2011 - it
didn't turn out to be a good decision. I need this year to free up more of
my time before committing to mentor again.

Isabel

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Dan Filimon <da...@gmail.com>.
So, Isabel, do you want to be a mentor?

On Tue, Mar 26, 2013 at 6:12 PM, Isabel Drost <is...@apache.org> wrote:
> On Tue, Mar 26, 2013 at 4:24 PM, Dan Filimon <da...@gmail.com>wrote:
>>
>> [1]
>> http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page#1._How_does_a_mentoring_organization
>> [2] http://en.flossmanuals.net/GSoCMentoring/what-makes-a-good-mentor/
>> [3] http://en.flossmanuals.net/GSoCMentoring/making-your-ideas-page/
>> [4] http://www.google-melange.com/gsoc/homepage/google/gsoc2013
>
>
> Please make sure to also check with Apache ComDev. Apache is going to be
> registered globally as an organisation with Google - so no need to do that
> from our side. However IIRC we need to make sure that people in our project
> that are willing to mentor are signed up with Melange and their Melange IDs
> can be matched to their Apache user names (you need to be a committer for
> that) by the ComDev people. Please check the ComDev mailing list archive
> and documentation for the exact details as I may not remember all of them.
>
> Also keep in mind that slots are assigned to all of Apache though students
> apply to individual projects. Only those proposals are going to be accepted
> that receive a high enough rating across all Apache student proposals.
>
>
> Isabel

Re: GSOC proposals and mentors [was Call to action – Mahout needs your help]

Posted by Isabel Drost <is...@apache.org>.
On Tue, Mar 26, 2013 at 4:24 PM, Dan Filimon <da...@gmail.com>wrote:
>
> [1]
> http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page#1._How_does_a_mentoring_organization
> [2] http://en.flossmanuals.net/GSoCMentoring/what-makes-a-good-mentor/
> [3] http://en.flossmanuals.net/GSoCMentoring/making-your-ideas-page/
> [4] http://www.google-melange.com/gsoc/homepage/google/gsoc2013


Please make sure to also check with Apache ComDev. Apache is going to be
registered globally as an organisation with Google - so no need to do that
from our side. However IIRC we need to make sure that people in our project
that are willing to mentor are signed up with Melange and their Melange IDs
can be matched to their Apache user names (you need to be a committer for
that) by the ComDev people. Please check the ComDev mailing list archive
and documentation for the exact details as I may not remember all of them.

Also keep in mind that slots are assigned to all of Apache though students
apply to individual projects. Only those proposals are going to be accepted
that receive a high enough rating across all Apache student proposals.


Isabel