[Moose-dev] Re: FW: EyeSee license

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jul 2, 2014, at 5:51 AM, Peter Goessaert 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.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.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 > www.mediagenix.tv > <image001.png> > > 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 > > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > -- > 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 > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev