[erlang-questions] Learn you some Erlang for great good!

[Fred Hebert (MononcQc)]

For the text I'm going for the Creative Commons Attribution Non-Commercial
No Derivative License (http://creativecommons.org/licenses/by-nc-nd/3.0/)

If people bring good arguments in order to allow derivative work, I'm open
to switching to the Attribution-Noncommercial-Share Alike Creative Commons
license (http://creativecommons.org/licenses/by-nc-sa/3.0/).

As for the code in the book itself, it's surely going to end up under the
EPL (Erlang Public License). I thought of the MIT license but will probably
use the EPL as it's what the whole Erlang distribution uses as far as I
know.

Does this answer the question?

On Tue, Jul 28, 2009 at 7:59 PM, Richard Andrews <bflatmaj7th@REDACTED>wrote:

> Can you define the license under which the work will be available so
> others can make a more informed decision on whether to contribute
> their time.
>
> On Wed, Jul 29, 2009 at 3:03 AM, Fred Hebert
> (MononcQc)<mononcqc@REDACTED> wrote:
> > Some of the readers of this list may be familiar with
> > http://learnyouahaskell.com/, an online book/tutorial dedicated to
> teaching
> > Haskell in a lighthearted way.
> > I've always thought Erlang had a steep learning curve unless you decide
> to
> > pay for books (the few of them are excellent, though). A good while ago,
> I
> > took time to discuss with the author of Learn You a Haskell and I decided
> to
> > start a version specifically for Erlang with his agreement. The
> objectives
> > are pretty much the same (lighthearted tutorials for beginners, free of
> > charge) and so is the concept.
> > I've written a few chapters already (Introduction, how to install, basic
> > shell commands, some of the basic data types) and although the text is
> still
> > very short, I've got a website up and running.
> > I'm looking for a few people with different levels of knowledge of Erlang
> in
> > order to review the first chapters. I'm looking to validate:  a. the
> > accessibility of information; b. if the information is right; c. gather
> > comments and criticism. I find it important to do a first review early in
> > the writing in order to fix flaws or improve on parts of the writing
> before
> > having to change too much stuff.
> > If you feel like giving me a helping hand in making the first chapters as
> > good as possible through your reviews, just send me an email back. I'll
> > forward the URL and user/password needed to see the info (I'm protecting
> > everything until reviewed, in order not to broadcast false or
> inappropriate
> > information).
> > Of course, once the first chapters are pushed in production, I'll keep
> > writing and might ask for some more help, if you don't mind the
> occasional
> > email.
> > Thanks in advance.
> >
>