[Pharo-users] Re: [ANN] Badges

2022-08-23 Thread Pierre Misse Chanabier

This is super cool, thanks a lot Hernán !

On 8/17/2022 8:55 AM, Hernán Morales Durand wrote:

Dear all,

I'd like to share a new Spec app for building badges made with Pharo 
10. It is based on the Shields.io badge service provider. Select the 
badges you want, complete the required variables, and get your 
badge(s). You can also save and load commonly used variables, so it 
may help a bit to automate presenting your project's README.


See the install instructions and usage video at:

https://github.com/hernanmd/shield-badges

Please note that this is a 0.1 release, so there is certainly a lot of 
room for improvement.


Cheers,

Hernán


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

2022-08-23 Thread Esteban Maringolo
There is a comment in one of the commits from 2005 (OmniBase-jf.2) that
suggests that OmniBase had a free with restrictions license:

http://www.squeaksource.com/@dZ70JMB-R7RDi4-m/Ox-ysyAT

Also, licensing was messier these days, some of that mess creeps up until
today.


Esteban A. Maringolo


On Tue, Aug 23, 2022 at 2:30 PM PAUL DEBRUICKER  wrote:

> From my reading, it seems like whoever posted OmniBase to github 9 years
> ago added the MIT license without permission and the OmniBase library
> remains closed source.
>
>
>
>
> > On Aug 23, 2022, at 6: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?
> >
>


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

2022-08-23 Thread PAUL DEBRUICKER
From my reading, it seems like whoever posted OmniBase to github 9 years ago 
added the MIT license without permission and the OmniBase library remains 
closed source.  




> On Aug 23, 2022, at 6: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?
> 


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

2022-08-23 Thread Yanni Chiu
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  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?
>


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

2022-08-23 Thread sean
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?


[Pharo-users] Breaking news: Esug - Angela Bragagnolo

2022-08-23 Thread Santiago Bragagnolo
Thanks a lot to all of you to show all the care you had these last days and
for helping this much with everything: calling ambassies, universities,
directives etc.

Special thanks to Gordana whom barely slept since Sunday trying and finally
achieving to find the solution, and simulationeusly dealt  with my stress.
And to the university vice dean and dean, without whom we wouldn't have any
political power nor any idea on how to react.

Also to the medics and guards those that helped her in need.



It has been a really f***ed up days . I wish you all a great time. I regret
to not be there this year.

Best for all of you!

Santiago.

On Sun, Aug 21, 2022, 15:41 Santiago Bragagnolo <
santiagobragagn...@gmail.com> wrote:

> Hello everyone, my wife Angela was going to assist esug this year as a
> student volunteer. She has been stopped in the airport since the
> information in the ambassy website "was outdated" (really really dickmove.
> i am starting to hate) and she was actually needing a visa.
> By the time being she was set into a cell-dorm with only her phone and no
> electric-socket to charge (so soon incommunicated). She was told to be sent
> back to paris in 3 days. Meaning that she is going to be in jail for 3 days
> because the ambassy is not able to keep their website updated.
>
> 1st- know that she is not attending.
> 2nd- please if you know someway to help contact me.
>
> Thanks all.
>
> santiago
>
>