There is no need to transfer any repo. Since it’s git-based, every forked repo is as good as the original. I’ve updated the license info on my fork. At some future point, I may delete my fork.
IANAL. For a hobby project, the current non-open-source license would probably suffice. Not that long ago, a lot of effort was done to get Squeak (and therefore Pharo) properly Apache/MIT-licensed so as to make the licensing clear for commercial use. Recently I got a new Droplet on Digital Ocean, and a few weeks later I got a Copyright takedown notice. They were going to block my server because they got a report that Copyrighted material was hosted on that machine. The URL they supplied was not my DNS. Seems some automated scanner had flagged the content, but then took two weeks to send out the takedown request, which got sent to me (the new owner of the machine). I’m not saying that a takedown for Omnibase is going to happen, but the fact that it *could* happen is a sufficient deterrent for commercial use, IMHO. On Tue, Aug 23, 2022 at 9:46 AM <s...@clipperadams.com> wrote: > I’m not fully understanding the issue. > > > Is it that: > > - > > The repos are violating the library license (other than the erroneous > MIT license, which could easily be updated)? > - > > The fact that OmniBase is not open source violates a principle you > have in continuing to host it? > > If the latter, may I suggest you offer to transfer the repo(s) to a > willing party? >
