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 and 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. On Fri, Oct 27, 2017 at 8:59 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 27 Oct 2017, at 08:55, Norbert Hartl <norbert@hartl.name> wrote:
Am 26.10.2017 um 15:54 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
On 26 Oct 2017, at 15:51, Norbert Hartl <norbert@hartl.name> wrote:
Now the interesting question....
*drumroll*
Will iceberg use this library???
what Guille did is an extract of Iceberg github api which at the time was a reinterpretation of Torstenâs api. I guess is possible, but my original intention was to keep it small⦠so it depends :)
From time to time we should try to make our software modular. Doesnât that mean guille should provide a minimal package you can integrate in iceberg?
right now it is modular and small :) to use the extracted api, it just needs to stay like that :P
Esteban
Norbert
Esteban
Norbert
Am 26.10.2017 um 15:06 schrieb Tudor Girba <tudor@tudorgirba.com>:
Even more awesomeness :). Thanks for doing this!
Doru
On Oct 26, 2017, at 2:02 PM, Torsten Bergmann <astares@gmx.de>
wrote:
I already contacted Guille in a private message on this one.
Because now we have three (sorted in order of appearance):
1. https://balletie.github.io/GitHub/ (from Balletie, very complete) 2. https://github.com/astares/GitHub-API (a wrapper I wrote to play
with the API)
3. https://github.com/guillep/github-api (Guille)
If time permits we should consolidate this into a single one (maybe on https://github.com/pharo-vcs/github-api).
Guille will contact Balletie as a next step.
Thanks T.
Gesendet: Donnerstag, 26. Oktober 2017 um 13:32 Uhr Von: "Tudor Girba" <tudor@tudorgirba.com> An: "Pharo Development List" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] Github API on github
Awesome.
Doru
On Oct 20, 2017, at 10:07 AM, Guillermo Polito < guillermopolito@gmail.com> wrote:
Hi guys,
I extracted and extended some of the github API from iceberg, so it can be used as a standalone project. Maybe this is useful for somebody.
https://github.com/guillep/github-api
It should be easy to extend and add new functionalities, so don't hesitate if you need some missing request :)
Guille
--
Guille Polito Research Engineer
Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - http://www.cnrs.fr
Web: http://guillep.github.io Phone: +33 06 52 70 66 13
-- www.tudorgirba.com www.feenk.com
âThe smaller and more pervasive the hardware becomes, the more physical the software gets."
-- www.tudorgirba.com www.feenk.com
"Presenting is storytelling."
-- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13