[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [recommenders-dev] About the license issue of the incubator project

Hi Marcel,

I think we can get around it w/o a separate popup. It will just not show up immediately as it does ATM.
I'll try to sketch a proposal while heading back to Darmstadt later today.

 That will be great, looking forward to your proposal. Thanks!
 
BTW: They are hiring up to 3 JDT developers. Anyone? ;)


Thank you for the information :) 
Is there any further information we could find on this? On the Eclipse official website or somewhere else?

I think there is no official job description. I just heard it from Deepak some weeks ago and from Dani yesterday. If you interested you should contact Dani Megert or Deepak Azad by email for more details. Email addresses can be found in Eclipse Bugzilla I guess :)


I see, I will do the search for email addresses ;)
 

Another news:
The incubator is currently in provisioning phase, i.e., we will be soon ready to go. 
If you like you can prepare your code and attach it to Bugzilla for IP Check?

I see, I will contact other guys, who contributed code, for their collaboration.
Hope we can finish the preparation soon.

Great. Worst case all parts not written by yourself will just drop out and rewritten at Eclipse with the newer APIs.

One question regarding your the mining: 
Where do you get the data from? Do you analyze the existing Eclipse workspace using the Eclipse JDT Parser - or is there something else happening behind the scenes?


The data is extracted from all the projects using SWT, in the Eclipse (Classic v3.7) code base. 
Some extra code of SWT examples provided by SWT itself may also be used for data collection (I can make it sure if necessary).
So what is your concern on the data or mining? 

Best,
Cheng    
  
 


On 23.06.2012, at 03:49, Cheng Zhang wrote:

Hi Marcel,

Really exciting to hear that. Thank you for your great effort!
So let's work them out for Kepler ;)

Btw, what is the schedule of Kepler (if there is any)?

Best,
Cheng

On Sat, Jun 23, 2012 at 8:02 AM, Marcel Bruch <marcel.bruch@xxxxxxxxx> wrote:
Hi,

just to let you guys know:

It was fun to present the ideas on code search, stacktrace search, annotations recommenders, parameter guessing, and code snippet mining to ~70 people tonight and look at their amazed faces... there are actually no clear candidates for Kepler (I asked people to vote for one of them and actually got almost the same number of votes for all tools) - but people where *very* excited. So the only thing I can say ATM is "I'm looking forward to see them all in action for Kepler" ;)

I've attached the slides of today's talk - although I wasn't able to show them all today. But I've at least presented all tool prototypes in the tool demo. But 20 minutes are just too short...

Best,
Marcel





On 19.06.2012, at 03:09, Cheng Zhang wrote:


Hi Marcel,


great to hear you want to continue the development of Precise at Eclipse! As I follow your project since a while now, I'd be pretty happy if we could support you and your  group's project here at Eclipse. 

Just a couple of questions out of curiosity and to learn a bit more about your ideas:
Is this project also backed up by your research group or mostly developed by you? As you have almost finished your PhD (hopefully ;)) what are your future plans with Precise? Will it be continued by you even with a new job or will your research group continue the work on it? 


The existing code was originally developed by two students and me, then improved by another three students in my group. 
Since the whole project is not that large, I think I know almost all the code well.
Because I am personally interested in this project and Eclipse Code Recommenders, I will certainly keep doing it even after I get a real job ;)
As for my research group, I am not totally sure how many people will join in in the long term. For now I am likely to get one or two excellent 
guys to help.
 

Answer to #1:
The Apache License of Mahout is fine. The only issue with Mahout is that it has a huge set of dependencies to other libraries (the distribution is 65MB large) which may need to be IP checked before it can be shipped from eclipse.org. Do you need Mahout for generating models only or also at runtime to compute proposals? 
BTW: What algorithms are you using?

Currently we are using k-NN search, so Weka (or Mahout) is just used for computing proposals.
As k-NN is an instance-based scheme, we do not have to build models using Weka (or Mahout).
 

To answer #2:
We have our own implementation of Bayesian Networks to compute recommendations which is at eclipse.org and free to reuse.
The models are generated by some self-written code which will move to o.e.r.rdk soon. Early versions are in the o.e.r.mining but it's very specific to our call recommender and not very reusable for other usages. But we'd like to use Mahout for clustering code search results in the near future. So we should strive for having Mahourt

Let me ask Wayne how to get Mahout (or a subset of it) through IP check.
 
Marcel


Great to hear that. Then we are planning to replace Weka with Mahout :)
Thank you very much for your help!


Cheng
 


On 18.06.2012, at 18:03, Cheng Zhang wrote:

Hi,

I am Cheng Zhang, a PhD student from Shanghai Jiao Tong University, who is very interested in the Eclipse Code Recommenders project. 

My colleagues and I have developed a prototype of a parameter guessing engine, named Precise, and now we are trying to make it an Ecilpse Recommenders Incubator project as described in: 

The project is current maintained by two undergraduates and the code still needs refinement.
But in the first place, I have a problem with the license: our project is using Weka as the machine learning engine, but Weka is under GPL license.

It seems that we have to replace Weka with other machine learning tools or implement the algorithms by ourselves. So far we have come up with two possible solutions:
1. Use Apache Mahout. Mahout is under Apache License, Version 2.0. Since we have little knowledge about license issues, we are not sure whether this license is permissible in the incubator project or not. Could anyone give some guidance?
2. Reuse the machine learning component in Eclipse Code Recommenders. Also I am wondering whether this solution is feasible.

Any comment or suggestion will be appreciated. Thank you!

Best,
Cheng
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev

-- 


_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev


_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev


_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev


_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev


_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev


_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev

-- 


_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev