| Re: [eclipse-scripting-dev] EScriptMonkey birth |
|
Hi John, First of all thank you for your advice. What you have suggested would be perfect for us because it will really help us through the IP process.
However, we have some issues that might make this solution impossible:
1.
After some technical discussions we decided to use a new project which is the fusion of Eclipse Monkey et EScript as a starting point.
EScrit is not a an eclipse project so it integrates some code from non eclipse committers.
2.
In the new project we want to embed some interpreters such as Jython. The Jython project is under the Python Software License (http://www.jython.org/license.html)
and I am not sure whether we can directly integrate it in eclipse. We already discussed it with Sharon Corbett which should give us a hint to know whether it is possible and how to do it.
3.
All the committers are not already Eclipse committers so I do not know if their work can be directly integrated. If those points do not appear to you as blocking points, I would be glad to migrate all the code to a E4 repository. We can also think of a way
to solve them. Arthur Daussy Atos arthur.daussy@xxxxxxxx +33 5 34 36 32 90
De : eclipse-scripting-dev-bounces@xxxxxxxxxxx
[mailto:eclipse-scripting-dev-bounces@xxxxxxxxxxx]
De la part de John Arthorne I urge you to be careful about creating a GitHub project as the starting point for this investigation. If your starting point is code from existing
Eclipse projects, then it is already IP clean code. If you take it outside, and make/accept contributions there, then it will become a complicated process to get that accepted back within Eclipse at a later date. I think we can fairly quickly create you a
git repository in e4 to do some early investigation if you are interested. That way the IP provenance stays clean and it doesn't become a roadblock later on. If you are interested in this approach I can help you through this process.
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel.
Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien
que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis. |
