[Pharo-users] Re: [Pharo-dev] Omnibase/Monibase repository removal

[Norbert Hartl]

Hi Dale,

thanks for the pointer.  I always admired what the GemStone people did and do. 
But I'm looking for something more lightweight and more easy to handle approach 
this time. Well, from the github page I could not derive what it really does to 
be honest.

Hope to see you at ESUG,

Norbert

> Am 08.08.2022 um 18:44 schrieb Dale Henrichs 
> :
> 
> Norbert,
> Before you go off and invent a data base, you might take a look at GemStone 
> and RemoteServiceReplication[1] ...
> 
> Dale
> 
> [1] https://github.com/GemTalk/RemoteServiceReplication 
> 
> On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl  > wrote:
> To all Omnibase and Monibase users. 
> 
> It turned out that neither of those are open source. The author of the 
> database contacted me clarifying the situation that he has the copyright and 
> never released something open source. This means that I will remove the 
> Omnibase repositories in few weeks from 
> 
> https://github.com/ApptiveGrid/MoniBase 
> 
> 
> and 
> 
> https://github.com/pharo-nosql/OmniBase 
> 
> 
> I'm very sorry about that but someone just took the code 9 years before, 
> copied it on github and put illegally an MIT license to the repository. We 
> only want free software in our repositories and hence the above will go away.
> 
> As we see it essential to have a good OO database in pharo we will see how 
> much effort it will be build a small and simple OO database that can replace 
> Omnibase. 
> 
> regards,
> 
> Norbert

[Pharo-users] Re: [Pharo-dev] Omnibase/Monibase repository removal

[Norbert Hartl]

Dale,

there is really no need for an excusion :) I found your pointer really 
informative and what you are saying is always interesting. But yeah, Yanni has 
a point here. I was pretty satisified with Omnibase because it is easy to 
handle being smalltalk and running in the same image. Supporting ACID 
transactions with MVCC is even a strong point. 
Performance is an important point. But performance is mostly defined by the use 
case and the architecture you choose for that. And our setup can scale out 
quite well I suppose.

Norbert

> Am 08.08.2022 um 22:34 schrieb Dale Henrichs 
> :
> 
> Sorry to have interrupted ... I just remember that folks have moved from 
> OmniBase to GemStone in the past for "performance reasons" and understand 
> that those aren't the only reasons for having an OmniBase replacement ...
> 
> Dale
> 
> On Mon, Aug 8, 2022 at 10:22 AM Yanni Chiu  > wrote:
> Dale,
> 
> It’s not about inventing a “database”, it’s a requirement to persist data 
> beyond image start/stop, along with intangibles like having the full source 
> code to tune for individual requirements. In my case the top (desired) 
> requirements are single directory or file per user (scaling), and no 
> additional server process(es) to be monitored for failure mode.
> 
> Yanni 
> 
> On Mon, Aug 8, 2022 at 12:44 PM Dale Henrichs 
> mailto:dale.henri...@gemtalksystems.com>> 
> wrote:
> Norbert,
> Before you go off and invent a data base, you might take a look at GemStone 
> and RemoteServiceReplication[1] ...
> 
> Dale
> 
> [1] https://github.com/GemTalk/RemoteServiceReplication 
> 
> On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl  > wrote:
> To all Omnibase and Monibase users. 
> 
> It turned out that neither of those are open source. The author of the 
> database contacted me clarifying the situation that he has the copyright and 
> never released something open source. This means that I will remove the 
> Omnibase repositories in few weeks from 
> 
> https://github.com/ApptiveGrid/MoniBase 
> 
> 
> and 
> 
> https://github.com/pharo-nosql/OmniBase 
> 
> 
> I'm very sorry about that but someone just took the code 9 years before, 
> copied it on github and put illegally an MIT license to the repository. We 
> only want free software in our repositories and hence the above will go away.
> 
> As we see it essential to have a good OO database in pharo we will see how 
> much effort it will be build a small and simple OO database that can replace 
> Omnibase. 
> 
> regards,
> 
> Norbert

[Pharo-users] Re: Omnibase/Monibase repository removal

[vinref]

Hi Norbert

Posting this here in pharo-users as I am not a member of pharo-dev.

I also emailed David Gorisek late last year regarding the license (for Dolphin 
Smalltalk) and this was his reply. He wrote that I needed only to mark the repo 
as a fork and attach the copyright notice:

> David Gorisek  \
> \
> 12:35 AM (9 hours ago) \
> \
> to me \
> \
> Dear Vince, \
> \
> OmniBase is most definitely not abandonware because it is actively being 
> used, improved and even supported for paying customers. We also have a 
> version for D7 but since OmniBase is used as a DB repository for STS we don't 
> use Github. In my company we use a central STS repository which is accessible 
> over HTTPS and we keep all our code there so I haven't had time to try Github 
> yet. \
> \
> There are many versions and forks of OmniBase circling around because many 
> people have done re-porting on their own for whatever reasons but these ports 
> were not approved and are not supported by us. So, if you want to place your 
> fork on Github you just need to indicate that it is a fork and that the 
> original code is Copyright (c) by David Gorisek and then write what changes 
> you made in your fork. \
> \
> Thank yout and best regards, \
> \
> David Gorisek \
> E-RACUNI d.o.o. \
> Maribor, Slovenia

Vince

[Pharo-users] Re: [Pharo-dev] Re: Omnibase/Monibase repository removal

[Dale Henrichs]

Norbert,

Ooops you are right! 

RSR is an object replication framework that replicates objects between Pharo, 
Dolphin, and GemStone images. Kurt Kilpela will be giving a talk at ESUG this 
year so if you are going to ESUG you can get more details right from the 
horse’s s mouth:)

Dale

[1] 
https://downloads.gemtalksystems.com/docs/GemStone64/3.6.x/GS64-GemBuilderforC-3.6.pdf
Sent from my iPhone

> On Aug 9, 2022, at 3:21 AM, Norbert Hartl  wrote:
> 
> Hi Dale,
> 
> thanks for the pointer.  I always admired what the GemStone people did and 
> do. But I'm looking for something more lightweight and more easy to handle 
> approach this time. Well, from the github page I could not derive what it 
> really does to be honest.
> 
> Hope to see you at ESUG,
> 
> Norbert
> 
>> Am 08.08.2022 um 18:44 schrieb Dale Henrichs 
>> :
>> 
>> Norbert,
>> Before you go off and invent a data base, you might take a look at GemStone 
>> and RemoteServiceReplication[1] ...
>> 
>> Dale
>> 
>> [1] https://github.com/GemTalk/RemoteServiceReplication
>> 
>> On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl  wrote:
>>> To all Omnibase and Monibase users. 
>>> 
>>> It turned out that neither of those are open source. The author of the 
>>> database contacted me clarifying the situation that he has the copyright 
>>> and never released something open source. This means that I will remove the 
>>> Omnibase repositories in few weeks from 
>>> 
>>> https://github.com/ApptiveGrid/MoniBase
>>> 
>>> and 
>>> 
>>> https://github.com/pharo-nosql/OmniBase
>>> 
>>> I'm very sorry about that but someone just took the code 9 years before, 
>>> copied it on github and put illegally an MIT license to the repository. We 
>>> only want free software in our repositories and hence the above will go 
>>> away.
>>> 
>>> As we see it essential to have a good OO database in pharo we will see how 
>>> much effort it will be build a small and simple OO database that can 
>>> replace Omnibase. 
>>> 
>>> regards,
>>> 
>>> Norbert
> 

[Pharo-users] Re: [Pharo-dev] Re: Omnibase/Monibase repository removal

[Dale Henrichs]

Norbert,

I won’t be going to ESUG this year … travel to Europe has always been tough for 
me and at my age 👨‍🦳I want to limit my exposure to COVID… Perhaps next year🤞.

Dale

Sent from my iPhone

> On Aug 9, 2022, at 3:21 AM, Norbert Hartl  wrote:
> 
> Hi Dale,
> 
> thanks for the pointer.  I always admired what the GemStone people did and 
> do. But I'm looking for something more lightweight and more easy to handle 
> approach this time. Well, from the github page I could not derive what it 
> really does to be honest.
> 
> Hope to see you at ESUG,
> 
> Norbert
> 
>> Am 08.08.2022 um 18:44 schrieb Dale Henrichs 
>> :
>> 
>> Norbert,
>> Before you go off and invent a data base, you might take a look at GemStone 
>> and RemoteServiceReplication[1] ...
>> 
>> Dale
>> 
>> [1] https://github.com/GemTalk/RemoteServiceReplication
>> 
>> On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl  wrote:
>>> To all Omnibase and Monibase users. 
>>> 
>>> It turned out that neither of those are open source. The author of the 
>>> database contacted me clarifying the situation that he has the copyright 
>>> and never released something open source. This means that I will remove the 
>>> Omnibase repositories in few weeks from 
>>> 
>>> https://github.com/ApptiveGrid/MoniBase
>>> 
>>> and 
>>> 
>>> https://github.com/pharo-nosql/OmniBase
>>> 
>>> I'm very sorry about that but someone just took the code 9 years before, 
>>> copied it on github and put illegally an MIT license to the repository. We 
>>> only want free software in our repositories and hence the above will go 
>>> away.
>>> 
>>> As we see it essential to have a good OO database in pharo we will see how 
>>> much effort it will be build a small and simple OO database that can 
>>> replace Omnibase. 
>>> 
>>> regards,
>>> 
>>> Norbert
> 

[Pharo-users] Re: [Pharo-dev] Re: Omnibase/Monibase repository removal

[Dale Henrichs]

Here’s Kurt’s talk from Camp Smalltalk Supreme[1].

Dale

[1] https://www.youtube.com/watch?v=uLF2S6fq5a4

Sent from my iPhone

> On Aug 9, 2022, at 6:53 AM, Dale Henrichs  
> wrote:
> 
> Norbert,
> 
> I won’t be going to ESUG this year … travel to Europe has always been tough 
> for me and at my age 👨‍🦳I want to limit my exposure to COVID… Perhaps next 
> year🤞.
> 
> Dale
> 
> Sent from my iPhone
> 
>>> On Aug 9, 2022, at 3:21 AM, Norbert Hartl  wrote:
>>> 
>> Hi Dale,
>> 
>> thanks for the pointer.  I always admired what the GemStone people did and 
>> do. But I'm looking for something more lightweight and more easy to handle 
>> approach this time. Well, from the github page I could not derive what it 
>> really does to be honest.
>> 
>> Hope to see you at ESUG,
>> 
>> Norbert
>> 
>>> Am 08.08.2022 um 18:44 schrieb Dale Henrichs 
>>> :
>>> 
>>> Norbert,
>>> Before you go off and invent a data base, you might take a look at GemStone 
>>> and RemoteServiceReplication[1] ...
>>> 
>>> Dale
>>> 
>>> [1] https://github.com/GemTalk/RemoteServiceReplication
>>> 
 On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl  wrote:
 To all Omnibase and Monibase users. 
 
 It turned out that neither of those are open source. The author of the 
 database contacted me clarifying the situation that he has the copyright 
 and never released something open source. This means that I will remove 
 the Omnibase repositories in few weeks from 
 
 https://github.com/ApptiveGrid/MoniBase
 
 and 
 
 https://github.com/pharo-nosql/OmniBase
 
 I'm very sorry about that but someone just took the code 9 years before, 
 copied it on github and put illegally an MIT license to the repository. We 
 only want free software in our repositories and hence the above will go 
 away.
 
 As we see it essential to have a good OO database in pharo we will see how 
 much effort it will be build a small and simple OO database that can 
 replace Omnibase. 
 
 regards,
 
 Norbert
>> 

[Pharo-users] Re: Omnibase/Monibase repository removal

[Konrad Hinsen]

Hi Norbert,

> This means that I will remove the Omnibase repositories in few weeks from 
>
> https://github.com/ApptiveGrid/MoniBase 
> 
>
> and 
>
> https://github.com/pharo-nosql/OmniBase 
> 

I hope you are aware that all of GitHub is archived by Software
Heritage. MoniBase doesn't seem to be in there yet, but there are a few
repositories called OmniBase, some of which belong to accounts
associated with Pharo:

   
https://archive.softwareheritage.org/browse/search/?q=OmniBase&with_visit=true&with_content=true

Deleting a repository from GitHub doesn't delete its archival copy
on Software Heritage. Removal there has to be requested explicitly:

   https://www.softwareheritage.org/legal/content-policy/

Cheers,
  Konrad

[Pharo-users] Re: Omnibase/Monibase repository removal

[danhunfeldz]

This is on the Cincom site regarding OmniBase:

 Licence Agreement

The OmniBase object database is provided as it is and with all faults, known or 
unknown. The source code and other information contained in the source code 
package is COPYRIGHT (C) by David Gorisek (the author). Portions of the source 
code can not be used without prior author’s written permission. OmniBase object 
database is licenced and sold under a ‘per developer sit’ licence model. You 
may install and use an unlimited number of copies of OmniBase object database 
on computers, including workstations, terminals  or other digital electronic 
devices to design, develop, and test your software application(s), however, you 
must acquire and  dedicate a license for each separate developer who is 
developing software using OmniBase. A license for the OmniBase object database 
may not be shared or used concurrently by different users. In no event shall 
the author be liable for any special, incidental, indirect, punitive or 
consequential damages whatsoever arising out of or in any way related to the 
use of or inability to use the OmniBase object database. By using the OmniBase 
object database you accept this licence agreement and the fact that you are 
using the database at your own risk. The author reserves all rights not 
expressly granted to you in this License agreement. The OmniBase object 
database is protected by copyright laws of the Republic of Slovenia and other 
intellectual property laws and treaties.

[Pharo-users] Re: Omnibase/Monibase repository removal

[Yanni Chiu]

Vince,

Thanks for this clarification. For me it means I can use my fork for the
short term. (I can walk to the exit instead of run). Since the license is
clearly not MIT, the rug can be pull at whim, so this code can’t be a long
term solution.

Yanni


On Tue, Aug 9, 2022 at 7:13 AM  wrote:

> Hi Norbert
>
> Posting this here in pharo-users as I am not a member of pharo-dev.
>
> I also emailed David Gorisek late last year regarding the license (for
> Dolphin Smalltalk) and this was his reply. He wrote that I needed only to
> mark the repo as a fork and attach the copyright notice:
>
>
> David Gorisek 
>
> 12:35 AM (9 hours ago)
>
> to me
>
> Dear Vince,
>
> OmniBase is most definitely not abandonware because it is actively being
> used, improved and even supported for paying customers. We also have a
> version for D7 but since OmniBase is used as a DB repository for STS we
> don't use Github. In my company we use a central STS repository which is
> accessible over HTTPS and we keep all our code there so I haven't had time
> to try Github yet.
>
> There are many versions and forks of OmniBase circling around because many
> people have done re-porting on their own for whatever reasons but these
> ports were not approved and are not supported by us. So, if you want to
> place your fork on Github you just need to indicate that it is a fork and
> that the original code is Copyright (c) by David Gorisek and then write
> what changes you made in your fork.
>
> Thank yout and best regards,
>
> David Gorisek
> E-RACUNI d.o.o.
> Maribor, Slovenia
>
>
> Vince
>

[Pharo-users] Re: Omnibase/Monibase repository removal

[Norbert Hartl]

> Am 09.08.2022 um 16:56 schrieb Yanni Chiu :
> 
> Vince,
> 
> Thanks for this clarification. For me it means I can use my fork for the 
> short term. (I can walk to the exit instead of run). Since the license is 
> clearly not MIT, the rug can be pull at whim, so this code can’t be a long 
> term solution.
> 
Yes, that's what I wrote in discord to you. Sorry for making you panicking ;)

Norbert

> Yanni
> 
> 
> On Tue, Aug 9, 2022 at 7:13 AM mailto:vin...@gmail.com>> 
> wrote:
> Hi Norbert
> 
> Posting this here in pharo-users as I am not a member of pharo-dev.
> 
> I also emailed David Gorisek late last year regarding the license (for 
> Dolphin Smalltalk) and this was his reply. He wrote that I needed only to 
> mark the repo as a fork and attach the copyright notice:
> 
> 
> 
> David Gorisek  
> 
> 12:35 AM (9 hours ago) 
> 
> to me 
> 
> Dear Vince, 
> 
> OmniBase is most definitely not abandonware because it is actively being 
> used, improved and even supported for paying customers. We also have a 
> version for D7 but since OmniBase is used as a DB repository for STS we don't 
> use Github. In my company we use a central STS repository which is accessible 
> over HTTPS and we keep all our code there so I haven't had time to try Github 
> yet. 
> 
> There are many versions and forks of OmniBase circling around because many 
> people have done re-porting on their own for whatever reasons but these ports 
> were not approved and are not supported by us. So, if you want to place your 
> fork on Github you just need to indicate that it is a fork and that the 
> original code is Copyright (c) by David Gorisek and then write what changes 
> you made in your fork. 
> 
> Thank yout and best regards, 
> 
> David Gorisek 
> E-RACUNI d.o.o. 
> Maribor, Slovenia
> 
> 
> 
> Vince
> 

[Pharo-users] Re: Omnibase/Monibase repository removal

[Yanni Chiu]

You did say to get a fork, but it wasn’t clear whether it was legit to use
it. I’ll probably just update the license, and eventually remove the fork.

On Tue, Aug 9, 2022 at 10:59 AM Norbert Hartl  wrote:

>
>
> Am 09.08.2022 um 16:56 schrieb Yanni Chiu :
>
> Vince,
>
> Thanks for this clarification. For me it means I can use my fork for the
> short term. (I can walk to the exit instead of run). Since the license is
> clearly not MIT, the rug can be pull at whim, so this code can’t be a long
> term solution.
>
> Yes, that's what I wrote in discord to you. Sorry for making you panicking
> ;)
>
> Norbert
>
> Yanni
>
>
> On Tue, Aug 9, 2022 at 7:13 AM  wrote:
>
>> Hi Norbert
>>
>> Posting this here in pharo-users as I am not a member of pharo-dev.
>>
>> I also emailed David Gorisek late last year regarding the license (for
>> Dolphin Smalltalk) and this was his reply. He wrote that I needed only to
>> mark the repo as a fork and attach the copyright notice:
>>
>>
>> David Gorisek 
>>
>> 12:35 AM (9 hours ago)
>>
>> to me
>>
>> Dear Vince,
>>
>> OmniBase is most definitely not abandonware because it is actively being
>> used, improved and even supported for paying customers. We also have a
>> version for D7 but since OmniBase is used as a DB repository for STS we
>> don't use Github. In my company we use a central STS repository which is
>> accessible over HTTPS and we keep all our code there so I haven't had time
>> to try Github yet.
>>
>> There are many versions and forks of OmniBase circling around because
>> many people have done re-porting on their own for whatever reasons but
>> these ports were not approved and are not supported by us. So, if you want
>> to place your fork on Github you just need to indicate that it is a fork
>> and that the original code is Copyright (c) by David Gorisek and then write
>> what changes you made in your fork.
>>
>> Thank yout and best regards,
>>
>> David Gorisek
>> E-RACUNI d.o.o.
>> Maribor, Slovenia
>>
>>
>> Vince
>>
>
>

[Pharo-users] Re: Using pharo in a cloud native environment

[Bob Nemec]

 We use Azure with our GS Seaside app for single sign-on. Once we have the 
Azure Graph token we then use that token for Graph API calls. Works nicely. I 
find MS Graph documentation to be excellent, as are all the supporting YouTube 
videos.
Here's a short Seaside summary of the steps we use...
1 - initialRequest: -> redirect to https://login.microsoftonline.com/ with your 
Azure application id and redirection URL, which for use is our app URL + 
?authenticate 2 - initialRequest: with 'authenticate' -> send request to 
https://login.microsoftonline.com/ with the authentication token provided by 
the MS redirect 3 - extract the Graph access token from the response 4 - use 
the Graph access token for Graph web service calls. In our case we use 
https://graph.microsoft.com/v1.0/me + Bearer  to get the 
authenticated user's Graph ID, which we then use to find the application user 
object.5 - refresh the token before it expires, which is usually under and 
hour, by checking the expires_in value
We've been running this way for a few months now. Next step is to expand our 
use of MS Graph with Outlook, Teams and SharePoint. 
Hope that helps,Bob Nemec

On Friday, August 5, 2022 at 11:39:48 a.m. EDT, Stefan Krecher 
 wrote:  
 
 Hi,every now and then I get back to smalltalk/ pharo to find out if there's a 
practical way to use pharo to manage cloud resources, e.g. by calling Azure- or 
AWS APIs.I know there have been efforts to implement a Smalltalk binding to use 
the AWS API at least for some of their services but it looks like there's 
support for only a few, eg S3.I'd love to use pharo to build a seaside app with 
a nice UI to make calls to Azure and/ or AWS to start/ stop ec2 instances 
etc.Of course I could create Azure functions that do the API calls and then 
just call those functions from pharo - but I ask myself if there's a nicer way 
do do this ...Any recommendations?RegardsStefan