Erlang projects association

[Mickael Remond]

* Luke Gorrie <luke@REDACTED> [2003-02-03 18:04:51 +0100]:

> Mickael Remond <mickael.remond@REDACTED> writes:
> 
> > That's why we have decided to create an association to pragmatically
> > work on those issues. The main goal of this association is to gather
> > users and developers, both individuals and companies to work on projects
> > that are needed to help us spread Erlang.
> > 
> > The first tasks will be to identify the major domains for which Erlang
> > should shine. We will then start dedicated workgroups that will have to
> > identify existing relevant projects and to help them go further.
> 
> For this to work I think you will have to do something radical. I say
> this after seeing a zillion similar projects with the best of
> intentions never generate any code -- I'm not aware of even one that's
> actually worked. I can give you any number of references if you like,
> where you can relive their fizzling-out through mailing list archives
> :-). So not to say it's a bad idea, but it will have to be done
> somehow different to all the others to have a chance IMHO.

Yes, you are right. This is project has a lot of chance to die very
quickly ... if we are the only one enthousiastic about the idea ;-)

I do not pretend that I have some particularly good idea of vision for
Erlang ... but I think one should and could emerge collectively.

> On a personal note, by far the most important thing I've learned over
> the past few years is to try not to talk about programs until I've
> written them. Since I want to talk about them, I end up doing lots
> more fun little hacks, instead of just talking about the ideas and
> moving on.

Hum. We were not necessarily speaking about coding. I have partipated in
many open source projects and I know that a vast majority of them die
very soon (mainly because it was a way of learning new things for the
developers and when his "formation" is over, the developer need to go to
something else) One the one that are successfull, they do not rely on a
big community neither, very often, one to three developers are pushing
the software further.

But what also matter in sucessfull is promotion, knowledge, comments,
etc. Even motivated developers needs feedback at some points.

That is why the object of the association is to help existing projects.
By help I mean that this could be code, but also feedback, promotion by
promoting the work that is being done, encouragements, documentations of
the software, tests, feature request, etc.
If the association is very lucky and very successful, it might even
start new project but this is more a matter of sharing infrastructure
with some members that have a good ideas.

For example, having the opportunity to experiment with an Erlang server
on the web could be interesting for some developers. However ISP does
not (yet) offer Erlang hosting. We could share a machine for those
experiments.

Do not forget that the competition between languages is also a matter of
visibility. Really a lot of things are already happenning is the Erlang
world. I feel that the language is spreading well these days, but this
might not be obvious for the people that are not already "gained" to the
Erlang "virus". 

> If I ever learn not to talk about programs until I've written manuals
> for them, I might just become a professional programmer. :-)

And, do not forget that association are also a way to have regularly
have a drink with friendly people (I am quite sure you will like this last
argument ;-)

> Cheers,
                  \ /
As I said, cheers  v   ;-)
                   |
		   -

-- 
Mickaeël Rémond