[erlang-questions] Erlang 3000?

[Dale Harvey]

I think visibility is the main concern when looking at the maturity of
non otp libraries, the lack of a central release repository is a hinderance,

but a single repository is unlikely to breakthrough very soon. I think
a good alternative would be to allow the code / project to exist anywhere,
but have a central place to find and document these libraries.

I have been planning to set up a public fork to the erlang
docs once they were fully released. I originally planned it to sort out
simple usability apects, like a function overview at the top of a
module page, an as you type filter of libraries /
modules. I also wanted feedback / comment options as
with php / flex docs,
(http://se2.php.net/manual/en/function.socket-set-option.php)

But it sounds like setting up a global documentation repository
would be a perfect extension.

an interface can be built to standard repositories (faxien / github etc)
that could be used to pull in documentation from to be included
alongside the standard/otp docs, categorised (alpha / beta / stable) etc.

users would  then have a central source for finding user libraries,
along side searching the otp documentation, search within versions,
compare functionality, comment on libraries quirky features etc.

I can start building the integration stuff now, but the site wont really be
useful
until the rest of the doc builder ala I can build everything up to
http://www.erlang.org/doc/ is released, hopefully thats the stuff planned
for R13

2008/11/19 Robert Virding <rvirding@REDACTED>

> 2008/11/19 Thomas Lindgren <thomasl_erlang@REDACTED>
>
>>
>> Maybe Erlang/OTP needs, dare I say it, a chief architect? Or at least
>> someone with (sine qua non) good taste in APIs, a strong conviction, and the
>> raw hacking power to rewrite all submitted code to follow The One True Way
>> :-)
>
>
> Yes, something like that. Although he/she shouldn't have to do all the
> hacking, just enforce that the submitted code follow The One True Way.
>
> Robert
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20081119/43729d4e/attachment.htm>