Difference between revisions of "Haskell.org infrastructure"

From HaskellWiki
Jump to navigation Jump to search
m (Remove unnecessary underscore in link)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
Haskell.org sub-domains are hosted on a variety of machines. Various machines have individuals responsible for them, and various services in turn have individuals responsible for those services.
 
Haskell.org sub-domains are hosted on a variety of machines. Various machines have individuals responsible for them, and various services in turn have individuals responsible for those services.
   
In general, the policy on the usage of the Haskell.org domain name and subdomains is set by the [[Haskell.org_committee]]. The committee also manages a small amount of funds, generally garnered from Google Summer of Code payments, and uses them towards the maintenance of Haskell community infrastructure. It therefore also determines the policy on the uses of those machines that it pays for.
+
In general, the policy on the usage of the Haskell.org domain name and subdomains is set by the [[Haskell.org committee]]. The committee also manages a small amount of funds, generally garnered from Google Summer of Code payments, and uses them towards the maintenance of Haskell community infrastructure. It therefore also determines the policy on the uses of those machines that it pays for.
   
 
Many people responsible for managing and helping with maintenance of Haskell.org servers are aliased at "admin [at the domain] haskell.org".
 
Many people responsible for managing and helping with maintenance of Haskell.org servers are aliased at "admin [at the domain] haskell.org".
   
If there are problems with infrastructure, it is good to check [https://status.haskell.org status.haskell.org] to see if they are already known. If not, emailing the admin at h.org mail alias and the #haskell-infrastructure irc channel on freenode are all good ways to get in touch.
+
If there are problems with infrastructure, it is good to check [https://status.haskell.org status.haskell.org] to see if they are already known. If not, emailing the admin at h.org mail alias and the #haskell-infrastructure irc channel on freenode are all good ways to get in touch. Automated uptime and status information is provided at [https://auto-status.haskell.org auto-status.haskell.org].
   
 
The centralized location on infrastructure is now maintained at [https://phabricator.haskell.org/w/ the Haskell Phabricator Wiki], cataloging machines, responsibilities, etc.
 
The centralized location on infrastructure is now maintained at [https://phabricator.haskell.org/w/ the Haskell Phabricator Wiki], cataloging machines, responsibilities, etc.
   
  +
See also: [[Haskell Governance]]
== Haskell Core Teams/Lists/Bodies/Committees ==
 
 
* [[Haskell.org committee]]
 
* [[Core Libraries Committee]]
 
* [https://phabricator.haskell.org/w/infrastructure/ Haskell Infrastructure Team]
 
* [https://ghc.haskell.org/trac/ghc/wiki/TeamGHC GHC Team]
 
* [http://hackage.haskell.org/trac/haskell-prime/wiki/Committee Haskell 'prime' Committee]
 
 
 
   
 
[[Category:Community]]
 
[[Category:Community]]

Latest revision as of 23:49, 17 May 2018

Haskell.org sub-domains are hosted on a variety of machines. Various machines have individuals responsible for them, and various services in turn have individuals responsible for those services.

In general, the policy on the usage of the Haskell.org domain name and subdomains is set by the Haskell.org committee. The committee also manages a small amount of funds, generally garnered from Google Summer of Code payments, and uses them towards the maintenance of Haskell community infrastructure. It therefore also determines the policy on the uses of those machines that it pays for.

Many people responsible for managing and helping with maintenance of Haskell.org servers are aliased at "admin [at the domain] haskell.org".

If there are problems with infrastructure, it is good to check status.haskell.org to see if they are already known. If not, emailing the admin at h.org mail alias and the #haskell-infrastructure irc channel on freenode are all good ways to get in touch. Automated uptime and status information is provided at auto-status.haskell.org.

The centralized location on infrastructure is now maintained at the Haskell Phabricator Wiki, cataloging machines, responsibilities, etc.

See also: Haskell Governance