pharo-users@lists.pharo.org

Any question about pharo is welcome

View all threads

Omnibase/Monibase repository removal

NH
Norbert Hartl
Mon, Aug 8, 2022 1:18 PM

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 https://github.com/ApptiveGrid/MoniBase

and

https://github.com/pharo-nosql/OmniBase 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

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 <https://github.com/ApptiveGrid/MoniBase> and https://github.com/pharo-nosql/OmniBase <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
DH
Dale Henrichs
Mon, Aug 8, 2022 4:44 PM

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 norbert@hartl.name 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

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 <norbert@hartl.name> 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 >
YC
Yanni Chiu
Mon, Aug 8, 2022 5:22 PM

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 <
dale.henrichs@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 norbert@hartl.name 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

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 < dale.henrichs@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 <norbert@hartl.name> 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 >> >
DH
Dale Henrichs
Mon, Aug 8, 2022 8:34 PM

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 yannix7db@gmail.com 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 <
dale.henrichs@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 norbert@hartl.name 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

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 <yannix7db@gmail.com> 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 < > dale.henrichs@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 <norbert@hartl.name> 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 >>> >>
NH
Norbert Hartl
Tue, Aug 9, 2022 10:20 AM

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 dale.henrichs@gemtalksystems.com:

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 https://github.com/GemTalk/RemoteServiceReplication
On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl <norbert@hartl.name mailto:norbert@hartl.name> 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 https://github.com/ApptiveGrid/MoniBase

and

https://github.com/pharo-nosql/OmniBase 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

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 <dale.henrichs@gemtalksystems.com>: > > 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 <https://github.com/GemTalk/RemoteServiceReplication> > On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> 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 <https://github.com/ApptiveGrid/MoniBase> > > and > > https://github.com/pharo-nosql/OmniBase <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
NH
Norbert Hartl
Tue, Aug 9, 2022 10:37 AM

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 dale.henrichs@gemtalksystems.com:

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 <yannix7db@gmail.com mailto:yannix7db@gmail.com> 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 <dale.henrichs@gemtalksystems.com mailto:dale.henrichs@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 https://github.com/GemTalk/RemoteServiceReplication
On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl <norbert@hartl.name mailto:norbert@hartl.name> 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 https://github.com/ApptiveGrid/MoniBase

and

https://github.com/pharo-nosql/OmniBase 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

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 <dale.henrichs@gemtalksystems.com>: > > 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 <yannix7db@gmail.com <mailto:yannix7db@gmail.com>> 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 <dale.henrichs@gemtalksystems.com <mailto:dale.henrichs@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 <https://github.com/GemTalk/RemoteServiceReplication> > On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> 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 <https://github.com/ApptiveGrid/MoniBase> > > and > > https://github.com/pharo-nosql/OmniBase <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
DH
Dale Henrichs
Tue, Aug 9, 2022 1:44 PM

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 norbert@hartl.name 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 dale.henrichs@gemtalksystems.com:

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 norbert@hartl.name 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

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 <norbert@hartl.name> 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 <dale.henrichs@gemtalksystems.com>: >> >> 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 <norbert@hartl.name> 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 >
DH
Dale Henrichs
Tue, Aug 9, 2022 1:53 PM

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 norbert@hartl.name 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 dale.henrichs@gemtalksystems.com:

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 norbert@hartl.name 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

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 <norbert@hartl.name> 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 <dale.henrichs@gemtalksystems.com>: >> >> 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 <norbert@hartl.name> 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 >
DH
Dale Henrichs
Tue, Aug 9, 2022 2:38 PM

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 dale.henrichs@gemtalksystems.com 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 norbert@hartl.name 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 dale.henrichs@gemtalksystems.com:

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 norbert@hartl.name 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

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 <dale.henrichs@gemtalksystems.com> 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 <norbert@hartl.name> 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 <dale.henrichs@gemtalksystems.com>: >>> >>> 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 <norbert@hartl.name> 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 >>
KH
Konrad Hinsen
Tue, Aug 9, 2022 2:48 PM

Hi Norbert,

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

Hi Norbert, > This means that I will remove the Omnibase repositories in few weeks from > > https://github.com/ApptiveGrid/MoniBase <https://github.com/ApptiveGrid/MoniBase> > > and > > https://github.com/pharo-nosql/OmniBase <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