Author Topic: O2 Licensing policy  (Read 7326 times)

0 Members and 1 Guest are viewing this topic.

Mike Lobanovsky

  • Guest
Re: O2 Licensing policy
« Reply #30 on: November 20, 2018, 12:01:31 AM »
It would be sad if we never knew who created the Mona Lisa.

In the Louvre, there is a spacious hall anteceding the relatively small cubicle that hosts the Mona Lisa portrait behind a sheet of bullet proof glass.

There are a few dozens of Leonardo's other paintings hanging on the walls in that hall. Most paintings are portraits of Leonardo's contemporaries of both genders, individually and in groups. The portrait sizes vary greatly from as small as the Mona Lisa itself up to really huge ones, perhaps several square yards each.

And you know what? All the human faces painted in the portraits are spitting images of Mona Lisa's "unique" face and smile. Evidently, that particular face type was the one Leonardo was able to depict best of all.

So, it wouldn't be too difficult to attribute the Mona Lisa to its genuine author had Leonardo overlooked to sign the portrait with his own hand. :D

JRS

  • Guest
Re: O2 Licensing policy
« Reply #31 on: November 20, 2018, 09:30:32 PM »
There should be a contest with the winner being who can expose the most undocumented features O2 offers that Chares keeps a secret unless asked.

Charles Pegge

  • Guest
Re: O2 Licensing policy
« Reply #32 on: November 21, 2018, 08:19:27 PM »
Derivative works :)



Marcel Duchamp

JRS

  • Guest
Re: O2 Licensing policy
« Reply #33 on: November 21, 2018, 08:41:03 PM »
You must have hit a milestone. Humor has returned.

Brian Alvarez

  • Guest
Re: O2 Licensing policy
« Reply #34 on: November 22, 2018, 10:06:15 AM »
Permission is hereby granted [...] to [..] merge, publish, distribute [...] subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

Charles, i am thinking that since you are still actively working on Oxygen, there is a high chance that
one of the updates breaks some of the functionality that i have already tested, taking me unaware of
it.

 I would like to merge your dll, into mine, to make 100% sure that the code i am generating is exactly
what the version of Oxygen can handle, and making sure it is already tested.

 According to your licensing, is this possible? and if so, how can the above copyright notice be included
in substantial portions of the software if it is in DLL form?


JRS

  • Guest
Re: O2 Licensing policy
« Reply #35 on: November 22, 2018, 10:28:19 AM »
Looks like O2 is getting a new wardrobe.  :)

Charles Pegge

  • Guest
Re: O2 Licensing policy
« Reply #36 on: November 23, 2018, 09:53:56 PM »
Brian,

If you want to merge DLLs, that is fine, but it will have to be a version of the self-compiled o2, since the DLL you are currently using is written in FreeBasic, and also it won't have the updates.

The license notice should go somewhere in your public documentation. The main purpose is to provide attribution so that other developers can refer back to o2. It's like having a citation in an academic paper.


Brian Alvarez

  • Guest
Re: O2 Licensing policy
« Reply #37 on: November 23, 2018, 10:51:19 PM »

Maybe that will have to wait. I am hoping i can compile PluriBASIC to 64 bit using itself one day.
In the meantime, a separate dll will do. Of course there is already a dialog stating the copyright
notice and the permission notice. :)

 Thanks!