[erlang-questions] What problem are we trying to solve here? [was Erland users group [was re: languages in use? [was: Time for OTP to be Renamed?]]]

[Anthony Ramine]

I stopped reading at « GitHub ».

Do people realize it is a closed proprietary platform?

What if I force push a new tag on my repos, btw? Automation, robust packaging and Git do not play together.

Note that I have nothing against using Git to *host* things (but I do think tarballs are better and simpler to manage), I specifically said « GitHub », your mail suggests using its proprietary API to do fancy stuff.

-- 
Anthony Ramine

Le 18 févr. 2014 à 10:20, André Graf <andre.graf@REDACTED> a écrit :

> I think the PHP community took a huge step when the tools 'composer'
> (PHP's rebar) and 'packagist.org' came out. The way packagist work is
> straight forward, you provide a repository url (Git/Svn/Hg) and it
> crawls the package that contains a composer.json file (could be a
> rebar.config, an *.app.src file, or something else, but common ground is
> needed here). The package is typically crawled once a day or if e.g a
> GitHub hook gets triggered. Package versions are managed on the
> repository side using tags. The combo Packagist/Composer is certainly
> not the holy grail, but it solves many problems, it is easy to use (for
> maintainers as well as for the users of the package), and it looks
> straightforward to be implemented in Erlang. ;)
> 
> 
> On 02/17/2014 11:21 PM, Garrett Smith wrote:
>> On Mon, Feb 17, 2014 at 4:19 PM, Mark Allen <mallen@REDACTED> wrote:
>>> On 2/17/14 1:51 PM, "Vixo" <gordon@REDACTED> wrote:
>>>> My suggestion would be a manifest file of Erlang terms at the root level
>>>> of a GitHub page (they will *all* be on GitHub) that can be polled and
>>>> turned into a static site. The logical thing to do would be combine thus
>>>> with the revived erldocs site IMHO (as I have said to Francesco)
>>> 
>>> I love this idea. I'm going to give this a think and maybe implement a
>>> prototype to do some testing of how it works.
>>> 
>>> Thanks!  Sometimes yak shaving discussions are kind of awesome.
>> 
>> Does this require that all of github be crawled?
>> 
>> Would a github based index make sense? Complete with a liberal pull
>> request policy?
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>> 
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions