Smalltalk › Frameworks & Tools › Moose

FW: EyeSee license

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

9 messages Options

Peter Goessaert

FW: EyeSee license

Hello Moose developers,

Trying this list, because it looks like [hidden email] 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

[hidden email]
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: '[hidden email]'
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.

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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

stepharo

Re: FW: EyeSee license

Hello Moose developers,

Trying this list, because it looks like [hidden email] 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

[hidden email]
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: '[hidden email]'
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Tudor Girba-2

Re: FW: EyeSee license

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 <[hidden email]> wrote:

Hello Moose developers,

Trying this list, because it looks like [hidden email] 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 <a href="tel:%2B32%202%20467%2034%2030" value="+3224673430" target="_blank">+32 2 467 34 30

't Hofveld 6E 3

1702 Groot-Bijgaarden - Belgium

[hidden email]
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: '[hidden email]'
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

www.tudorgirba.com

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

stepharo

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 <[hidden email]> wrote:
Hello Moose developers,

Trying this list, because it looks like [hidden email] 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 <a moz-do-not-send="true" href="tel:%2B32%202%20467%2034%2030" value="+3224673430" target="_blank">+32 2 467 34 30

't Hofveld 6E 3

1702 Groot-Bijgaarden - Belgium

[hidden email]
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: '[hidden email]'
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--

www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Peter Goessaert

Re: FW: EyeSee license

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: [hidden email] [mailto:[hidden email]] 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 <[hidden email]> wrote:
Hello Moose developers,

Trying this list, because it looks like [hidden email] 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 <a href="tel:%2B32%202%20467%2034%2030" target="_blank">+32 2 467 34 30

't Hofveld 6E 3

1702 Groot-Bijgaarden - Belgium

[hidden email]
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: '[hidden email]'
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--

www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

abergel

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 <[hidden email]> 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: [hidden email] [[hidden email]] 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 <[hidden email]> wrote:
Hello Moose developers,

Trying this list, because it looks like [hidden email] 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 <a href="tel:%2B32%202%20467%2034%2030" target="_blank" style="color: purple; text-decoration: underline;">+32 2 467 34 30
't Hofveld 6E 3
1702 Groot-Bijgaarden - Belgium

[hidden email]
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: '[hidden email]'
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Peter Goessaert

Re: FW: EyeSee license

| GraphET is available on VW. GraphET is a revamp of EyeSee.

Aha, thanks for that tip, Alexandre!

Peter Goessaert

Software Engineer

T +32 2 467 34 30

't Hofveld 6E 3

1702 Groot-Bijgaarden - Belgium

[hidden email]
www.mediagenix.tv

From: [hidden email] [mailto:[hidden email]] 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 <[hidden email]> 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: [hidden email] [[hidden email]] 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 <[hidden email]> wrote:
Hello Moose developers,

Trying this list, because it looks like [hidden email] 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 <a href="tel:%2B32%202%20467%2034%2030" target="_blank">+32 2 467 34 30

't Hofveld 6E 3

1702 Groot-Bijgaarden - Belgium

[hidden email]
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: '[hidden email]'
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--

www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

davidm

Re: FW: EyeSee license

In reply to this post by abergel

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

abergel

Re: EyeSee license

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 http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Jul 22, 2014, at 4:50 AM, davidm <[hidden email]> wrote:

> 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.
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev