Hello Moose developers,
Trying this list, because it looks like info@moosetechnology.orgmailto:info@moosetechnology.org is not so actively read ;-)
This was my question:
The EyeSee project caught our interest, and we are investigating if we can use it in our product. But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement. Is this correct? And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
All answers or pointers to the correct people are welcome.
Greetings, Peter
Peter Goessaert
Software Engineer
T +32 2 467 34 30
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium
peter.goessaert@mediagenix.tvmailto:peter.goessaert@mediagenix.tv www.mediagenix.tvhttp://www.mediagenix.tv
[cid:logomediagenix2013-106pxdc2753]http://www.mediagenix.tv
This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately.
From: Peter Goessaert Sent: vrijdag 27 juni 2014 11:38 To: 'info@moosetechnology.org' Subject: EyeSee license
Hello,
The EyeSee project caught our interest, and we are investigating if we can use it in our product. But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement. Is this correct? And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
Greetings, Peter
Hello Moose developers,
Trying this list, because it looks like info@moosetechnology.org mailto:info@moosetechnology.org is not so actively read ;-)
:)
This was my question:
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
Excellent!
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement.
I thought that all the Moose Components where BSD (but the impact is the same). With BSD and MIT you can do what you want to the code (but should mentioned the original license).
Is this correct?
Normally BSD. Pharo is MIT, Moose BSD. You can also improve it and give back the enhancements to the community :)
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
I would say where it is simple for you and for people to know it. May be in a about.
All answers or pointers to the correct people are welcome.
Greetings,
Peter
*Peter Goessaert*
Software Engineer
T+32 2 467 34 30
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium
*peter.goessaert@mediagenix.tv mailto:peter.goessaert@mediagenix.tv** www.mediagenix.tv http://www.mediagenix.tv*
/This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately./
*From:*Peter Goessaert *Sent:* vrijdag 27 juni 2014 11:38 *To:* 'info@moosetechnology.org' *Subject:* EyeSee license
Hello,
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement.
Is this correct?
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
Greetings,
Peter
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
We are happy to see you interested.
Are you asking about the VW or the Pharo version of EyeSee?
Cheers, Doru
On Wed, Jul 2, 2014 at 11:00 AM, stepharo stepharo@free.fr wrote:
Hello Moose developers,
Trying this list, because it looks like info@moosetechnology.org is not so actively read ;-)
:)
This was my question:
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
Excellent!
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement.
I thought that all the Moose Components where BSD (but the impact is the same). With BSD and MIT you can do what you want to the code (but should mentioned the original license).
Is this correct?
Normally BSD. Pharo is MIT, Moose BSD. You can also improve it and give back the enhancements to the community :)
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
I would say where it is simple for you and for people to know it. May be in a about.
All answers or pointers to the correct people are welcome.
Greetings,
Peter
*Peter Goessaert*
Software Engineer
T +32 2 467 34 30
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium
*peter.goessaert@mediagenix.tv peter.goessaert@mediagenix.tv*
- www.mediagenix.tv http://www.mediagenix.tv*
*This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately.*
*From:* Peter Goessaert *Sent:* vrijdag 27 juni 2014 11:38 *To:* 'info@moosetechnology.org' *Subject:* EyeSee license
Hello,
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement.
Is this correct?
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
Greetings,
Peter
Moose-dev mailing listMoose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
We are happy to see you interested.
Are you asking about the VW or the Pharo version of EyeSee?
probably the VW I forgot.
Stef
Cheers, Doru
On Wed, Jul 2, 2014 at 11:00 AM, stepharo <stepharo@free.fr mailto:stepharo@free.fr> wrote:
Hello Moose developers, Trying this list, because it looks like info@moosetechnology.org <mailto:info@moosetechnology.org> is not so actively read ;-):)This was my question: The EyeSee project caught our interest, and we are investigating if we can use it in our product.Excellent!But first some license questions need an answer. As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement.I thought that all the Moose Components where BSD (but the impact is the same). With BSD and MIT you can do what you want to the code (but should mentioned the original license).Is this correct?Normally BSD. Pharo is MIT, Moose BSD. You can also improve it and give back the enhancements to the community :)And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?I would say where it is simple for you and for people to know it. May be in a about.All answers or pointers to the correct people are welcome. Greetings, Peter *Peter Goessaert* Software Engineer T+32 2 467 34 30 <tel:%2B32%202%20467%2034%2030> 't Hofveld 6E 3 1702 Groot-Bijgaarden - Belgium *peter.goessaert@mediagenix.tv <mailto:peter.goessaert@mediagenix.tv>** www.mediagenix.tv <http://www.mediagenix.tv>* <http://www.mediagenix.tv> /This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately./ *From:*Peter Goessaert *Sent:* vrijdag 27 juni 2014 11:38 *To:* 'info@moosetechnology.org <mailto:info@moosetechnology.org>' *Subject:* EyeSee license Hello, The EyeSee project caught our interest, and we are investigating if we can use it in our product. But first some license questions need an answer. As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement. Is this correct? And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software? Greetings, Peter _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev-- www.tudorgirba.com http://www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Indeed. VW 7.9 to be specific.
Thanks for the answers so far!
One question still open: what is the exact text we should add in our about? Is that something like "We use EyeSee from Moose Technology" with a pointer to http://www.moosetechnology.org, or should that contain more information/links/contact information to Moose or Bern university?
Greetings, Peter
From: moose-dev-bounces@iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] On Behalf Of stepharo Sent: woensdag 2 juli 2014 11:19 To: Moose-related development Subject: [Moose-dev] Re: FW: EyeSee license
We are happy to see you interested.
Are you asking about the VW or the Pharo version of EyeSee?
probably the VW I forgot.
Stef
Cheers, Doru
On Wed, Jul 2, 2014 at 11:00 AM, stepharo <stepharo@free.frmailto:stepharo@free.fr> wrote:
Hello Moose developers,
Trying this list, because it looks like info@moosetechnology.orgmailto:info@moosetechnology.org is not so actively read ;-) :)
This was my question:
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
Excellent!
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement. I thought that all the Moose Components where BSD (but the impact is the same). With BSD and MIT you can do what you want to the code (but should mentioned the original license).
Is this correct? Normally BSD. Pharo is MIT, Moose BSD. You can also improve it and give back the enhancements to the community :)
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software? I would say where it is simple for you and for people to know it. May be in a about.
All answers or pointers to the correct people are welcome. Greetings, Peter
Peter Goessaert
Software Engineer
T +32 2 467 34 30tel:%2B32%202%20467%2034%2030
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium
peter.goessaert@mediagenix.tvmailto:peter.goessaert@mediagenix.tv www.mediagenix.tvhttp://www.mediagenix.tv
[cid:image001.png@01CF95EB.B58F14E0]http://www.mediagenix.tv
This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately.
From: Peter Goessaert Sent: vrijdag 27 juni 2014 11:38 To: 'info@moosetechnology.orgmailto:info@moosetechnology.org' Subject: EyeSee license
Hello,
The EyeSee project caught our interest, and we are investigating if we can use it in our product. But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement. Is this correct? And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
Greetings, Peter
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.comhttp://www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch
Hello Peter,
GraphET is available on VW. GraphET is a revamp of EyeSee.
Cheers, Alexandre
| GraphET is available on VW. GraphET is a revamp of EyeSee.
Aha, thanks for that tip, Alexandre!
p.
Peter Goessaert
Software Engineer
T +32 2 467 34 30
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium
peter.goessaert@mediagenix.tvmailto:peter.goessaert@mediagenix.tv www.mediagenix.tvhttp://www.mediagenix.tv
[cid:logomediagenix2013-106px0d5c0e]http://www.mediagenix.tv
This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately.
From: moose-dev-bounces@iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] On Behalf Of Alexandre Bergel Sent: woensdag 2 juli 2014 15:54 To: Moose-related development Subject: [Moose-dev] Re: FW: EyeSee license
Hello Peter,
GraphET is available on VW. GraphET is a revamp of EyeSee.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jul 2, 2014, at 5:51 AM, Peter Goessaert <peter.goessaert@mediagenix.tvmailto:peter.goessaert@mediagenix.tv> wrote:
Indeed. VW 7.9 to be specific.
Thanks for the answers so far!
One question still open: what is the exact text we should add in our about? Is that something like "We use EyeSee from Moose Technology" with a pointer to http://www.moosetechnology.orghttp://www.moosetechnology.org/, or should that contain more information/links/contact information to Moose or Bern university?
Greetings, Peter
From: moose-dev-bounces@iam.unibe.chmailto:moose-dev-bounces@iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] On Behalf Of stepharo Sent: woensdag 2 juli 2014 11:19 To: Moose-related development Subject: [Moose-dev] Re: FW: EyeSee license
We are happy to see you interested.
Are you asking about the VW or the Pharo version of EyeSee?
probably the VW I forgot.
Stef
Cheers, Doru
On Wed, Jul 2, 2014 at 11:00 AM, stepharo <stepharo@free.frmailto:stepharo@free.fr> wrote:
Hello Moose developers,
Trying this list, because it looks like info@moosetechnology.orgmailto:info@moosetechnology.org is not so actively read ;-) :)
This was my question:
The EyeSee project caught our interest, and we are investigating if we can use it in our product.
Excellent!
But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement. I thought that all the Moose Components where BSD (but the impact is the same). With BSD and MIT you can do what you want to the code (but should mentioned the original license).
Is this correct? Normally BSD. Pharo is MIT, Moose BSD. You can also improve it and give back the enhancements to the community :)
And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software? I would say where it is simple for you and for people to know it. May be in a about.
All answers or pointers to the correct people are welcome. Greetings, Peter
Peter Goessaert
Software Engineer
T +32 2 467 34 30tel:%2B32%202%20467%2034%2030
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium
peter.goessaert@mediagenix.tvmailto:peter.goessaert@mediagenix.tv www.mediagenix.tvhttp://www.mediagenix.tv/
<image001.png>http://www.mediagenix.tv/
This e-mail and any files attached to it are confidential and intended only for the use of the individuals or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately.
From: Peter Goessaert Sent: vrijdag 27 juni 2014 11:38 To: 'info@moosetechnology.orgmailto:info@moosetechnology.org' Subject: EyeSee license
Hello,
The EyeSee project caught our interest, and we are investigating if we can use it in our product. But first some license questions need an answer.
As far as I can see, it is MIT licensed so that would mean that we can load the EyeSee code into our product and deploy/sell that product commercially, but that we have to keep the copyright statement. Is this correct? And if we need to add the copyright for this specific package (EyeSee), what and where should it be presented in our software?
Greetings, Peter
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.comhttp://www.tudorgirba.com/
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.chmailto:Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hello Alexandre,
Could you point me to where exactly I can find the GraphET packages for VW? So far I have been able to get it working in Pharo but I cant seem to find it for VW. I was able to load Roassal from the Cincom Store, but that does not seem to include the GraphET packages, or am I overlooking something?
Thanks alot.
David
-- View this message in context: http://forum.world.st/FW-EyeSee-license-tp4766030p4769270.html Sent from the Moose mailing list archive at Nabble.com.
Hi David,
Here is the archive. https://dl.dropboxusercontent.com/u/31543901/online/ObjectProfileToolsVW.zip
Milton, in Cc:, is in charge to packaging our tools.
Cheers, Alexandre
-
Alexandre Bergel -
davidm -
Peter Goessaert -
stepharo -
Tudor Girba