[Pharo-dev] Github API on github
roniesalg at gmail.com
Tue Oct 31 13:38:33 EDT 2017
This looks interesting. Maybe I should migrate Thermite into using some of
this bindings. In Thermite I am using my custom wrapper for the GitHub API,
2017-10-30 13:50 GMT-03:00 Torsten Bergmann <astares at gmx.de>:
> Hi Guille,
> nice. Instead of just two we can merge all three into a single solution.
> As I proposed
> it should be made available for instance on a general URL like:
> so we could work and improve on it all together.
> Gesendet: Montag, 30. Oktober 2017 um 17:24 Uhr
> Von: "Guillermo Polito" <guillermopolito at gmail.com>
> An: "Pharo Development List" <pharo-dev at lists.pharo.org>
> Betreff: Re: [Pharo-dev] Github API on github
> Hi all,
> So I talked with Skip (Balletie) and he's not planning on supporting the
> github api he hosted because he's not doing pharo any time soon. So he has
> for the moment transferred the ownership of his project to me:
> I'll work soon in merging both
> to have a single solution.
> To answer Esteban and Norbert, I try to keep it small and modular :) But
> those are really high-level goals. What do you want to "not load" or what
> is bothering?
> Because I'll not cut the library so you can load services in a 'per-class'
> basis. That will be impossible to maintain in the long term... We need to
> find an equilibrium between modularity and reuse. Right now the github API
> embedded in Iceberg is not completely reusable either.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev