Re: Cassandra on Google Summer of Code 2017

[Yuki Morishita]

Hi,

I co-mentored GSoC last year with Paulo Motta for Apache Cassandra project.
Here is what we did last year:

* Marked streaming related issues as
"gsoc2016"(https://issues.apache.org/jira/browse/CASSANDRA-8110?jql=project%20%3D%20CASSANDRA%20AND%0A%20labels%20%3D%20gsoc2016).
These issues were presented in GSoC website so that students can
submit their proposal to them.
* Candidate student contacted us and showed interest. We advised the
student for proposal review.
* Candidate submitted the proposal, and we evaluated his ability to
accomplish the task. (Interview included).
* Note that not all candidates are accepted. Google assigns certain
number of students per organization, and since ASF has tons of
projects, it can be competitive.

* Initial plan for mentee to work was CASSANDRA-8928
(https://issues.apache.org/jira/browse/CASSANDRA-8928). Though the
work amount that we (mentors) found after GSoC started was way more
than what we estimated initially, so we switched the target issue to
technically related issue.
* Mentee finished two issues that related to streaming
(CASSANDRA-10810 and CASSANDRA-12008) in timely manner with the
quality we expected, so he passed the final evaluation.

As an organizaiton, ASF will participate to GSoC as usual this year,
but if Apache Cassandra project wants to participate, we need to start
marking JIRA issue as "gsoc2017" by 2/9.
Think before marking issue, though, that  the issue can be tackled
within GSoC period. :)

I'm still not sure if I have time to mentor this year, but I'm willing
to answer any GSoC related question.

On Mon, Feb 6, 2017 at 7:38 PM, Nate McCall  wrote:
> Sorry for the top post, but just want to make sure everyone has the details:
> If any committers want to be involved in this, the ASF is filling this
> out as a whole so we don't need to do too much on a project level.
>
> ASF details for mentorship (including GSoC) can be found here:
> http://community.apache.org/guide-to-being-a-mentor.html
>
> On Tue, Feb 7, 2017 at 2:14 PM, Русак Максим  wrote:
>> Hello, developers of Cassandra. I'm really interested in the Cassandra 
>> project (especially in distributed metadata components(like gossip)) and 
>> eager to take part in GSoC, dive deep into Cassandra internals and make a 
>> contribution under mentorship.
>> Currently I'm working on my undergrad diploma in Yandex YT (analog of 
>> Hadoop). My work is related to distributed metadata and anomalous nodes 
>> detection.
>> So I have few questions:
>> 1. Does Cassandra plan to take part in GSoC this year?
>> 2. Are anyone willing to mentor? (not necessarily relating to distributed 
>> metadata)
>> It'll be nice to see wide range of Cassandra projects and ideas. In this way 
>> Cassandra could attract new talents and accelerate development :)
>> (Mentoring organization application deadline is February 9, 16:00 UTC, so it 
>> need to be done as soon as possible)
>>
>> Regards, Maxim Rusak

Re: Cassandra on Google Summer of Code 2017

[Nate McCall]

Sorry for the top post, but just want to make sure everyone has the details:
If any committers want to be involved in this, the ASF is filling this
out as a whole so we don't need to do too much on a project level.

ASF details for mentorship (including GSoC) can be found here:
http://community.apache.org/guide-to-being-a-mentor.html

On Tue, Feb 7, 2017 at 2:14 PM, Русак Максим  wrote:
> Hello, developers of Cassandra. I'm really interested in the Cassandra 
> project (especially in distributed metadata components(like gossip)) and 
> eager to take part in GSoC, dive deep into Cassandra internals and make a 
> contribution under mentorship.
> Currently I'm working on my undergrad diploma in Yandex YT (analog of 
> Hadoop). My work is related to distributed metadata and anomalous nodes 
> detection.
> So I have few questions:
> 1. Does Cassandra plan to take part in GSoC this year?
> 2. Are anyone willing to mentor? (not necessarily relating to distributed 
> metadata)
> It'll be nice to see wide range of Cassandra projects and ideas. In this way 
> Cassandra could attract new talents and accelerate development :)
> (Mentoring organization application deadline is February 9, 16:00 UTC, so it 
> need to be done as soon as possible)
>
> Regards, Maxim Rusak

Cassandra on Google Summer of Code 2017

[Русак Максим]

Hello, developers of Cassandra. I'm really interested in the Cassandra project 
(especially in distributed metadata components(like gossip)) and eager to take 
part in GSoC, dive deep into Cassandra internals and make a contribution under 
mentorship.
Currently I'm working on my undergrad diploma in Yandex YT (analog of Hadoop). 
My work is related to distributed metadata and anomalous nodes detection.
So I have few questions:
1. Does Cassandra plan to take part in GSoC this year?
2. Are anyone willing to mentor? (not necessarily relating to distributed 
metadata)
It'll be nice to see wide range of Cassandra projects and ideas. In this way 
Cassandra could attract new talents and accelerate development :)
(Mentoring organization application deadline is February 9, 16:00 UTC, so it 
need to be done as soon as possible)

Regards, Maxim Rusak

Re: cassandra-3.X branch, 3.x version, cleanup

[Michael Shuler]

Thank you for working on this, Ay, I appreciate it.

-- 
Michael

On 02/05/2017 11:56 AM, Aleksey Yeschenko wrote:
> A handy filter to see if you’ve got any JIRAs as assignee/reviewer
> that need correction:
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Cassandra%20and%20fixVersion%20%3D%203.x%20and%20statusCategory%20%3D%20Complete%20and%20((reviewer%20%3D%20currentUser())%20or%20(assignee%20%3D%20currentUser()))
>
>  -- AY
> 
> On 5 February 2017 at 17:47:33, Aleksey Yeschenko
> (alek...@apache.org) wrote:
> 
> HI all.
> 
> Now that 3.10 has finally been released, I’ve cleaned up several
> things, as promised:
> 
> 1. Cherry-picked bug fixes from cassandra-3.X branch into
> cassandra-3.11 branch 2. Fixed up CHANGES.txt in both cassandra-3.11
> branch and trunk 3. Dropped cassandra-3.X branch altogether 4. Added
> 3.11.x version placeholder, got rid of 3.12 version
> 
> What remains to be done:
> 
> 1. Get rid of 3.x version in JIRA, by relabelling all affected
> issues
> 
> For uncommitted future 3.11 bug fixes, please use the new 3.11.x
> fixver on JIRA.
> 
> Current merge order: 2.1 -> 2.2 -> 3.0 -> 3.11 -> trunk.
> 
> P.S. While cleaning things up, I’ve noticed a lot of resolved JIRA
> issues with .x version placeholders. To committers: please, set the
> fixver to a concrete version when resolving the JIRA. Don’t make
> others dig through git log to determine where the patch went into
> eventually.
> 
> Also, when resolving as Duplicate or Won’t Fix or Not a Problem,
> please remove the version in fixversion field altogether.
> 
> Thank you.
> 
> -- AY
>