Membership Policy of Planet Haskell

Planet Haskell is an aggregator of Haskell people's blogs and other Haskell-related news sites. As of mid-November 2007 content from 78 blogs and other sites is being republished in a common format.

A common misunderstanding about Planet Haskell is that it republishes only Haskell content. That is not its mission. A Planet shows what is happening in the community, what people are thinking about or doing. Thus Planets tend to contain a fair bit of "off-topic" material. Think of it as a feature, not a bug.

A blog is eligible to Planet if it is being written by somebody who is active in the Haskell community, or by a Haskell celebrity; also eligible are blogs that discuss Haskell-related matters frequently, and blogs that are dedicated to a Haskell topic (such as a software project written in Haskell). Note that at least one of these conditions must apply, and virtually no blog satisfies them all. However, blogs will not be added to Planet without the blog author's consent.

As a practical matter, all feeds need to use primarily the English language. This means that while non-English content is not forbidden per se, a person who knows no other natural language than English needs to be able to read the main points of every entry. The reason for this is that the Planet is an international medium, and English happens to be the lingua franca of our time.

The above rule is primarily concerned about languages used in the narration of the entries. Code and images are exempted, though it is desirable that most entries do contain narration in English.

To get a blog added, email the contact person (see the sidebar) and provide evidence that the blog author consents to this (easiest is to get the author send the email, but any credible method suffices). Note that addition requests are processed in batches, so don't expect an immediate reply.

Currently Planet Haskell runs PlanetPlanet 2.0-6 as distributed by Debian and is administered by Antti-Juhani Kaijanaho. If you want to help, send email to the contact address given in the sidebar, and expect to have a conversation about this policy and the reasons behind it, first.