On Mon, 07 Mar 11 Neel Sheyal wrote: > > Not to contradict Ted, but we do have some qualifying tasks, they > > just aren't formalized. > > > Are we expecting a formal and published list for the qualifying task?
As what students do before applying for GSoC differs depending on their experience and general interest I doubt there will be *the* list of qualifying tasks. > Are Mahout patches encourage/requirement? If you successfully submitted patches to Mahout before starting GSoC that certainly is a huge plus, but it is no requirement. The usual process is something like... * get yourself familiar with Mahout, * find a project you are interested in working on based on your previous experience * get in touch with the community on the mailing list and discuss your ideas (obviously you are doing that already) * come up with a more formal proposal and work on that on the mailing list * post your proposal to our JIRA as well as to the GSoC web app * start working on it. > I am looking at JIRA (issue > 363) and playing with Mahout but how do I get myself an assigned task > (JIRA issue) that no one is working on? > I am aware of > https://cwiki.apache.org/confluence/display/MAHOUT/How+To+Contribute First of all, even if someone is working on an existing issue there is still room to get involved by reviewing patches, making additions, proposing to split work and solve sub tasks. Other than that, expressing your interest in working on an issue and submitting patches regularly not much later probably is the most certain way to avoid duplicate work. Isabel
