[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?]]]

[Bob Ippolito]

It is important to have the ability to create private package indexes and
repository mirrors for security/performance/redundancy.

I don't think that making GitHub the de facto option for the public index
and package hosting is a bad idea, as long as it's obvious how to use an
alternative index. There are services that could be used to help power
testing/CI that layer well on top of GitHub, such as Travis-CI. Rackspace
is also known to donate time on their cloud for open source projects,
although that would require some central administration.



On Mon, Feb 17, 2014 at 4:52 PM, Anthony Ramine <n.oxyde@REDACTED> wrote:

> My own opinion is that any Erlang package manager relying on GitHub for
> whatever more than hosting a simple Git repository is doomed to fail. Feel
> free to disprove me through making one.
>
> Companies make money around Erlang, if they want such a thing, money will
> need to be thrown at it for the infrastructure, there is just no way around
> it. If an index should be, the applications going into the main one are
> going to need some level of validation, otherwise it’s just a garbage bin
> which language zealots will use to tell the world we have 66,000 packages
> available.
>
> Validation means testing, continuous integration and all that entails.
> GitHub will not help you here.
>
> --
> Anthony Ramine
>
> Le 18 févr. 2014 à 00:12, Ludovic Demblans <ludovic@REDACTED> a écrit
> :
>
> > "Who handles the repository index"
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140217/7eabf214/attachment.htm>