Hi Sebastian, thanks for our comments.
I think you as the original author and Henning as top contributor in
recent years should decide that. My personal feeling is GPL. And parts
of the software (autotrack -h) states already that it is GPL'ed.
I will talk to Henning, but GPL would be fine with me.
haskell.org/haskore is indeed out of date, and there is unfortunately
no official home for Haskore. Although the haskellwiki is fairly
limited, my preference would be that the official site be wiki-like,
so perhaps it can be expanded.
This is #1. To build a community you need a place where ppl can come to
for questions. A Wiki is ideal. It shouldnt be to much work to redirect
haskell.org/haskore to the wiki page. And the wikipage can easily be
worked out a bit more, telling ppl about the rest of the infrastructure.
Right, that was what I was hoping to do. I don't have any experience
setting up a wiki, but I'm sure that we could find someone willing to help.
Haskore was originally created by me and my students at Yale, but in
recent years Henning Theilmann has created the darcs version of
Haskore, an ambitious re-engineering of the original ideas with lots
of modifications and extensions.
So in fact, it is already a community work. And I bet that for CS
students that are interested in "music" this will stay a really
interesting project, so we could expect contributions of motivated young
fellows.
Yes, I agree!
Henning and I have recently decided to refactor darcs Haskore in an
attempt to re-capture the simplicity of the original Haskore, while
not losing any of the extended functionality. Henning and I have
barely gotten started on this project, but I am optimistic that the
outcome will be good.
I would be really glad if I could join this. As I said, im just
learning haskell for some weeks, but I am doing my PhD in software
engineering and have some practical experience in refactoring large
systems and setting up an open project infrastructure. IMHO
everything needed is already there, but it needs to be organized a bit
better:
* Homepage wikipage
* Darcs RCS
* Mailinglist
* Build system (in two flavors: Make and Cabal)
* Docs: literate tutorial, how about haddock?
* Tests
And of course to get more ppl into it, it is a must that one can
install/use the package without too much pain. (To learn how all these
things work (from a social point of view) in the F/OSS world, I suggest
reading the book http://producingoss.com by Karl Fogel)
There is a nice description of how to create Haskell project here:
http://www.haskell.org/haskellwiki/How_to_write_a_Haskell_program
I would like to follow these guidelines as much as possible. Henning
and I would love some help with all this, although I have two grad
students who will also be helping.
Also, I am teaching a full term course on computer music at Yale this
fall, so I will be generating a lot of pedagogical material.
Here lilypond pops up immediatly: On the wikipage and the "Tutorial"
there are some notes of "work in progress", but I couldt find anything.
As you can see, my motivation rises ...
It would be really nice to have a lilypond interface to Haskore. Jeff
Lewis did something along these lines about 10 years ago, and I had a
master's student who did a rudimentary interface a few years ago, but I
don't think that either of them got very far. If you or anyone else
would like to take a shot at this, I can send you my student's code.
This would be a great stand-alone project.
Best, Paul
_______________________________________________
haskell-art mailing list
[email protected]
http://lists.lurk.org/mailman/listinfo/haskell-art
