Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haskell-org-committee: merge in content from the wiki #1

Closed
wants to merge 4 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added 2015-11-10-Haskell-Org-Board-Resolution.pdf
Binary file not shown.
63 changes: 45 additions & 18 deletions haskell-org-committee.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,20 @@ Haskell.org is a 501(c)(3) non-profit organization that oversees the Haskell.org
* [Discourse][discourse]
* [Hoogle], a type-aware Haskell search engine

Haskell.org also organizes Haskell's participation in the [Google Summer of Code program][summer].
Its purpose is to promote educational and scientific progress relating to the Haskell programming language and related technologies.
ketzacoatl marked this conversation as resolved.
Show resolved Hide resolved


Some particular aspects of the work of Haskell.org include producing and maintaining material regarding the Haskell language on haskell.org and other associated websites; hosting and maintaining shared assets and infrastructure for the benefit of the Haskell community; coordinating educational activities including mentorship programs; and potentially organizing event regarding the Haskell language.

Haskell.org also organizes Haskell's participation in the [Google Summer of Code program][gsoc].

### Contact

* [[email protected]][email]: directly email the committee
* [haskell-community mailing list][list]: public discussions about the committee and Haskell community infrastructure
* [GitHub][github]: issues, suggestions and pull requests for the website
* [Haskell.org proposals][repo]: submit community proposals for Haskell.org

[summer]: https://summer.haskell.org/
[wiki]: https://wiki.haskell.org/Haskell
[mailing]: https://www.haskell.org/mailing-lists/
[discourse]: https://discourse.haskell.org
[Hoogle]: https://hoogle.haskell.org/
[Hackage]: https://hackage.haskell.org/
[GHC]: https://www.haskell.org/ghc/

## Haskell.org Committee

Expand All @@ -44,25 +49,47 @@ The committee consists of 7 members serving 3-year terms. The current members ar
* Rebecca Skinner (term ends 2022)
* Alexandre Garcia de Oliveira (term ends 2022)
ketzacoatl marked this conversation as resolved.
Show resolved Hide resolved

In November of each year—or if a member steps down before their term is over—the committee holds an open call for new members, encouraging self-nominations. Committee members whose terms are over are eligible for renomination.
ketzacoatl marked this conversation as resolved.
Show resolved Hide resolved

Committee members do not need to be deep technical Haskell experts. Instead we look for enthusiasm towards improving the Haskell community. We aim to represent the different facets of the community. We aim to be diverse in terms of industry or research, and in terms of gender, race and location.

After nominations have been solicited, the current committee—including any outgoing members—selects new members with a simple majority vote.
### Process

* The committee's governing rules are laid out in the [Board Resolution](/2015-11-10-Haskell-Org-Board-Resolution.pdf) of that month.
* The committee uses the [haskell-community mailing list][list] for public discussion, where all interested parties may participate.
* Proposals and meeting notes are stored in a [public repository][repo].
* The committee will seek to reach consensus among its membership on its decisions. Ultimately, the committee will make decisions by more than half of the membership voting for a particular outcome.
* These rules of operation may also be changed in the same way.

#### Committee Membership

The committee consists of 7 members. Members are expected to serve a 3 year term, and terms are staggered so that 2 or 3 members step down each year, at the end of October.

The members will elect one of their number to be chair each year. The chair is responsible for making sure that things keep moving, and to ensure that a conclusion is reached on any issues raised.

In November of each year—or if a member steps down before their term is over—the committee holds an open call for new members, encouraging self-nominations. Committee members whose terms are over are eligible for renomination.

After nominations have been solicited, the current committee—including any outgoing members not seeking reelection—selects new members with a simple majority vote.

While this has never occurred in the past, Committee members can also be removed by majority vote.

### Process

The Committee uses the [haskell-community][list] for public discussion. Proposals and meeting notes are stored in a [public repository][repo].
### History

### Contact
Haskell.org is incorporated in the state of New York as of November 2015.

* [[email protected]][email]: directly email the committee
* [haskell-community mailing list][list]: public discussions about the committee and Haskell community infrastructure
* [GitHub][github]: issues, suggestions and pull requests for the website
The Haskell.org committee was [initially formed in November 2010](https://mail.haskell.org/pipermail/haskell/2010-November/022375.html). As described there:

In recent years, haskell.org has started to receive assets, e.g. Google Summer Of Code funds, donations for Hackathons, and a Sparc machine for use in GHC development. We have also started spending this money: on the community server, on a server to take over hosting haskell.org itself, and on the haskell.org domain name. There is also interest in running fundraising drives for specific things such as Hackathon sponsorship and hosting fees.

To resolve who is responsible for haskell.org’s infrastructure development, open nominations were held to form a haskell.org committee, based on representatives from the open source Haskell community.

[discourse]: https://discourse.haskell.org
[email]: mailto:[email protected]
[list]: https://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community
[Hackage]: https://hackage.haskell.org/
[Hoogle]: https://hoogle.haskell.org/
[GHC]: https://www.haskell.org/ghc/
[github]: https://github.com/haskell-infra/www.haskell.org/
[list]: https://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community
[mailing]: https://www.haskell.org/mailing-lists/
[repo]: https://github.com/haskell-org/committee
[gsoc]: https://summer.haskell.org/
[wiki]: https://wiki.haskell.org/Haskell
4 changes: 4 additions & 0 deletions site.hs
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@ main = mkContext >>= \ctx -> hakyll $ do
route cleanRoute
compile $ mdCompiler ctx

match "*.pdf" $ do
route idRoute
compile copyFileCompiler

match "templates/*" $
compile templateCompiler

Expand Down