If it is already stable, high quality, and useful, then why does it
need to be in trunk? This seems like exactly the kind of package that
we want to be easily found and installed through something like SqueakMap.

Or maybe it would be better to handle it like the git tooling by making
JSON an installation option in the Preference Wizard.

I am perfectly happy if JSON is added to trunk, but I do want to point
out that we are not very consistent in these matters. One day we are
complaining about image bloat and lack of modularity, and the next day
we're all trying to add our favorite packages into trunk. We can't
have it both ways.

Dave


On Tue, Jul 06, 2021 at 03:06:29PM +0200, Marcel Taeumel wrote:
> Hi all!
> 
> I think it would be nice to have JSON as part of Squeak Trunk. This would make parsing the content of web requests easier. Recently, I got lucky to find the last-modified date in the HTTP header for the public TravisCI badge. But usually, one would have to query the official endpoint/API to then get XML or JSON content.
> 
> http://www.squeaksource.com/JSON
> 
> 
> What do you think? The project is
> + Self-contained
> + Stable since 2016
> + Not that big
> o Adding the extension #jsonWriteOn: to the system
> 
> Latest maintainers seem to be:
> Hannes Hirzel (hjh, 2010)
> Levente??Uzonyi (ul, 2010)
> Tony Garnock-Jones (tonyg, 2016)
> Fabio Niephaus (FabN, 2016)
> 
> Best,
> Marcel
>