Haskell Libraries Wishlist

Olaf Chitil O.Chitil at kent.ac.uk
Tue Oct 19 11:22:12 EDT 2004

Manuel M T Chakravarty wrote:

>>We could wait to see if an organization will emerge from the wiki, and
>>I encourage someone to start to move the content over... It could also
>>be broken up into more than one page if the current wiki structure
>>doesn't work for some reason.  I, personally am not wedded to the
>>layout of the wiki page, fwiw.
>I think we should come up with a template of what information we would
>like to be available in the wiki.  We might start from the format
>currently used on the wiki and the information that's supposed to be in
>Cabal descriptions.
I agree that using the Wiki is a sensible compromise.

I do not quite see why more people would be willing to edit a Wiki page 
than send an email to John and me, but it is worth trying. To make this 
clear: John and I are perfectly able to handle the incoming emails about 
desired additions and changes to the pages; there simply are very few of 
them. Most entries actually are written by ourselves, just from coming 
across things on the various Haskell mailing lists or otherwise. This 
activity is too time consuming (especially writing short descriptions 
when it is unclear to me what the library actually does) and I only do 
it occasionally.

I agree with Manuel that first we need to make some changes to the Wiki 
page before we can expect other people to make entries there. After that 
is done, I'm happy to place a big forward link onto the libraries page 
to the Wiki libraries page. Later the old page can go when all 
information has been transferred.

As Manuel says we should come up with a template and explain it on the 
Wiki page. Each entry should certainly be short, not much more than the 
current: name, URL, paragraph of description. For further information 
there could optionally be a Wiki link to a library specific page. I 
don't know what to do with all the version numbers on the current Wiki 
page. Are they really up to date?

The page needs to be broken into several pages, because it is hard to 
edit a huge page with the Wiki editor. On the other hand the hierarchy 
should not be too deep, requiring too many pages to select and load. 
Basically I think we could use the existing top level of the hierarchy 
of the libraries&tools page. Naturally, if we want to change this 
hierarchy later, this will be more complicated.

In principle everything said about the libraries&tools page is also 
valid for the applications page and the bookshelf. But we should 
certainly first do one.


More information about the Libraries mailing list