[Haskell] Call for Contributions - Haskell Communities and
Activities Report, May 2008 edition
voigt at tcs.inf.tu-dresden.de
Thu Apr 24 10:01:36 EDT 2008
so much has happened in the Haskell world in the past months.
Therefore, we would very much like to collect contributions for
the 14th edition of the
Haskell Communities & Activities Report
Submission deadline: 10 May 2008
(please send your contributions to hcar at haskell.org, in
plain text or LaTeX format)
This is the short story:
* If you are working on any project that is in some way related
to Haskell, please write a short entry and submit it to the us. Even if
the project is very small or unfinished or you think it is not important
enough -- please reconsider and submit an entry anyway!
* If you are interested in any project related to Haskell that has not
previously been mentioned in the HC&A Report, please tell us, so that we
can contact the project leaders and ask them to submit an entry.
* Feel free to pass on this call for contributions to others that
might be interested.
More detailed information:
The Haskell Communities & Activities Report is a bi-annual overview of
the state of Haskell as well as Haskell-related projects over the
last, and possibly the upcoming 6 months. If you have only recently
been exposed to Haskell, it might be a good idea to browse the
December 2007 edition -- you will find interesting topics described as
well as several starting points and links that may provide answers to
Contributions will be collected until the submission deadline. They
will then be compiled into a coherent report that is published online
as soon as it is ready. As always, this is a great opportunity to
update your webpages, make new releases, announce or even start new
projects, or to talk about developments you want every Haskeller to
As the purpose of the report is to collect recent or current
activities, we encourage you to update all existing summaries and
reports. We will probably drop any topics that have not had any
activity for the past year, i.e., since May 2007, but we would
very much prefer you to present an updated description of the
topic. Of course, new entries are more than welcome. Reports should
generally be kept brief and informative, ranging from a few sentences
to a few hundred words, to keep the whole report reasonably sized.
Looking forward to your contributions,
Andres and Janis (current editors)
Q: Which topics are relevant?
A: *All* topics which are related to Haskell in some way are relevant. We
usually had reports from users of Haskell (private, academic, or
commercial), from authors or contributors to projects related to Haskell,
from people working on the Haskell language, libraries, on language
extensions or variants. We also like reports over distributions of Haskell
software, Haskell infrastructure, books and tutorials on Haskell. Reports
on past and upcoming events related to Haskell are also relevant. Finally,
there might be new topics we don't even think about. As a rule of thumb: if
in doubt, then it probably is relevant and has a place in the HCAR. You can
also ask the editors.
Q: Is unfinished work relevant? Are ideas for projects relevant?
A: Yes! You can use the HCAR to talk about projects you are currently
working on. You can use it to look for other developers that might help
you. You can use it to write ``wishlist'' items for libraries and language
features you would like to see implemented.
Q: How much should I write?
A: There's no formal limit. But generally, entries should be short and
to the point. A general introduction is helpful. Apart from that, you
should focus on recent or upcoming developments. There also is no minimum
length of an entry! The report aims at being as complete as possible, so
please consider writing an entry, even if it's only a few lines long.
Q: If I don't update my entry, but want to keep it in the report, what
should I do?
A: Tell us that there are no changes. We will reuse the old entry in this
case, but we might drop it if it's older than a year, to give more room and
more attention to projects that change a lot. Don't resent complete entries
if you haven't changed them.
Q: What format should I write in?
A: The best format is a LaTeX source file, adhering to the template
that's available at:
There's also a LaTeX style file at
that you can use to preview your entry. If you don't know LaTeX, then use
plain text. If you modify an old entry, we will send you your old entry as a
template within the next hours (provided we have your valid email address).
Please modify that template, rather than using your own version of the old
entry as a template. Don't worry about writing correct LaTeX, we will be
able to handle your file. Please don't use HTML or even DOC.
Dr. Janis Voigtlaender
mailto:voigt at tcs.inf.tu-dresden.de
More information about the Haskell