[Pharo-dev] Github API on github

Ronie Salgado roniesalg at gmail.com
Tue Oct 31 13:38:33 EDT 2017


Hi,

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,

Best regards,
Ronie

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:
>
>  https://github.com/pharo-vcs/github-api
>
> so we could work and improve on it all together.
>
> Thanks
> Torsten
>
>
> 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:
>
> https://github.com/guillep/Github
>
> I'll work soon in merging both
>
> https://github.com/guillep/Github[https://github.com/guillep/Github]
>
> and
>
> https://github.com/guillep/github-api[https://github.com/
> guillep/github-api]
>
> 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...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20171031/a8d0061d/attachment-0002.html>


More information about the Pharo-dev mailing list