| Variable | Value |
|---|
Edit count of the user (user_editcount) | 163 |
Name of the user account (user_name) | 'Slyfox' |
Age of the user account (user_age) | 254236225 |
Page ID (page_id) | 2647 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'Haskell' |
Full page title (page_prefixedtitle) | 'Project:Haskell' |
Action (action) | 'edit' |
Edit summary/reason (summary) | 'drop slyfox@' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=Haskell
|Description=Support Haskell programming language ecosystem on Gentoo systems.
|Email=haskell@gentoo.org
|IRC=#gentoo-haskell
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2019-05-26
|Members={{Project Member
|Developer=User:Slyfox
|IsLead=Yes
}}{{Project Member
|Developer=User:Gienah
|IsLead=No
}}
}}
The Haskell project maintains the packages for Haskell implementations, libraries, and development tools. We support [http://www.haskell.org/ghc/ GHC] and [http://www.open.ou.nl/bhr/HeliumCompiler.html Helium] though GHC is the best supported. The library packages work only with GHC.
There is an overlay where we work on Haskell ebuilds before getting them into the main ::gentoo git tree. You can get the overlay using layman.
All development discussion takes place on the {{IRC|gentoo-haskell}} IRC channel. This channel is the appropriate place to report bugs in packages that are in the overlay. They should not be reported in Bugzilla, that's the place to report bugs about packages in the main ::gentoo git tree.
Further instructions and tips can be found in the [[Haskell]] article.
== Developers ==
All developers can be reached by e-mail using nickname@gentoo.org.
== Policies ==
While adding new packages to the tree overlay we follow next rules: we keep in tree end user applications and their depends plus [[Haskell:haskell-platform|haskell-platform]]. We are keeping all development libs in overlay. In overlay we do not have 'stable-' / 'testing' partitioning, and all packages are marked as testing.
== Goals ==
=== Long-term ===
* Support for the haskell-ecosystem in the Gentoo.
=== Short-term ===
* Stabilizing Haskell Platform in Gentoo tree: [https://bugs.gentoo.org/show_bug.cgi?id=472634|related bug tracker].
* Fixing USE flags metadata entries in overlay.
* Fix packages test in overlay.
=== Pending tasks ===
== Contribution ==
* Ebuilds contribution. For more information see [https://github.com/gentoo-haskell/gentoo-haskell/blob/master/projects/doc/HOWTO-contribute.rst overlay documentation]
* Contribute to project programs (hackport, haskell-updater, etc.)
== TODO list ==
* [easy-to-hard] Add packages requested by people to the overlay. HackPort is a nice tool to do it fast.
* [easy-to-moderate] Keep up-to-date upstream versions in overlay, fix depends broken by package updates and upstream fixes. HackPort can help in tracking: hackport status --from-hackage.
* Improve HackPort tool.
* [easy] Some packages are patched on top of upstream. Ideally they should not :]. Your goal is to push nice patches upstream. Haskell world is very eager in getting feedback, so it's a source of pleasure to work with upstream!
* Some code snippets on scanning the tree for such patched packages:
* [moderate] Some packages have their testuites, but ebuilds don't utilize it or have tests blocked. Blocked tests are easy to find with git grep RESTRICT.
* Here is some notes to say: upstream tests are sometimes unportable hacks, so your aim is to rework ill written testsuites by using Cabal recently introduced testing interface and/or using libraries helping in testing (HUnit, QuickCheck, test-framework-*). See tests in darcs as an advanced example.
* [moderate] Get ghc bugs fixed upstream, send patches
* [easy-to-moderate] Help fix & improve cabal. Improve cabal-install.
* [easy] Write a program to check for build errors of package in overlay.
* [easy] run repoman full on the overlay and provide fixes for found QA notices. Or check out our [https://travis-ci.org/gentoo-haskell/gentoo-haskell travis-ci dashboard]' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=Haskell
|Description=Support Haskell programming language ecosystem on Gentoo systems.
|Email=haskell@gentoo.org
|IRC=#gentoo-haskell
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2019-05-26
|Members={{Project Member
|Developer=User:Gienah
|IsLead=No
}}
}}
The Haskell project maintains the packages for Haskell implementations, libraries, and development tools. We support [http://www.haskell.org/ghc/ GHC] and [http://www.open.ou.nl/bhr/HeliumCompiler.html Helium] though GHC is the best supported. The library packages work only with GHC.
There is an overlay where we work on Haskell ebuilds before getting them into the main ::gentoo git tree. You can get the overlay using layman.
All development discussion takes place on the {{IRC|gentoo-haskell}} IRC channel. This channel is the appropriate place to report bugs in packages that are in the overlay. They should not be reported in Bugzilla, that's the place to report bugs about packages in the main ::gentoo git tree.
Further instructions and tips can be found in the [[Haskell]] article.
== Developers ==
All developers can be reached by e-mail using nickname@gentoo.org.
== Policies ==
While adding new packages to the tree overlay we follow next rules: we keep in tree end user applications and their depends plus [[Haskell:haskell-platform|haskell-platform]]. We are keeping all development libs in overlay. In overlay we do not have 'stable-' / 'testing' partitioning, and all packages are marked as testing.
== Goals ==
=== Long-term ===
* Support for the haskell-ecosystem in the Gentoo.
=== Short-term ===
* Stabilizing Haskell Platform in Gentoo tree: [https://bugs.gentoo.org/show_bug.cgi?id=472634|related bug tracker].
* Fixing USE flags metadata entries in overlay.
* Fix packages test in overlay.
=== Pending tasks ===
== Contribution ==
* Ebuilds contribution. For more information see [https://github.com/gentoo-haskell/gentoo-haskell/blob/master/projects/doc/HOWTO-contribute.rst overlay documentation]
* Contribute to project programs (hackport, haskell-updater, etc.)
== TODO list ==
* [easy-to-hard] Add packages requested by people to the overlay. HackPort is a nice tool to do it fast.
* [easy-to-moderate] Keep up-to-date upstream versions in overlay, fix depends broken by package updates and upstream fixes. HackPort can help in tracking: hackport status --from-hackage.
* Improve HackPort tool.
* [easy] Some packages are patched on top of upstream. Ideally they should not :]. Your goal is to push nice patches upstream. Haskell world is very eager in getting feedback, so it's a source of pleasure to work with upstream!
* Some code snippets on scanning the tree for such patched packages:
* [moderate] Some packages have their testuites, but ebuilds don't utilize it or have tests blocked. Blocked tests are easy to find with git grep RESTRICT.
* Here is some notes to say: upstream tests are sometimes unportable hacks, so your aim is to rework ill written testsuites by using Cabal recently introduced testing interface and/or using libraries helping in testing (HUnit, QuickCheck, test-framework-*). See tests in darcs as an advanced example.
* [moderate] Get ghc bugs fixed upstream, send patches
* [easy-to-moderate] Help fix & improve cabal. Improve cabal-install.
* [easy] Write a program to check for build errors of package in overlay.
* [easy] run repoman full on the overlay and provide fixes for found QA notices. Or check out our [https://travis-ci.org/gentoo-haskell/gentoo-haskell travis-ci dashboard]' |
Unified diff of changes made by edit (edit_diff) | '@@ -8,7 +8,4 @@
|LeadElectionDate=2019-05-26
|Members={{Project Member
-|Developer=User:Slyfox
-|IsLead=Yes
-}}{{Project Member
|Developer=User:Gienah
|IsLead=No
' |
Old page size (old_size) | 3636 |
Lines added in edit (added_lines) | [] |
Lines removed in edit (removed_lines) | [
0 => '|Developer=User:Slyfox',
1 => '|IsLead=Yes',
2 => '}}{{Project Member'
] |
New page text, stripped of any markup (new_text) | '
Haskell
Description
Support Haskell programming language ecosystem on Gentoo systems.
Project email
haskell@gentoo.org
IRC channel
#gentoo-haskell (webchat)
Lead(s)
Sergei Trofimovich
(slyfox) Last elected: 2019-05-26
Member(s)
Mark Wright
(gienah)
Subproject(s)(and inherited member(s))
(none)
Parent Project
Gentoo
Project listing
The Haskell project maintains the packages for Haskell implementations, libraries, and development tools. We support GHC and Helium though GHC is the best supported. The library packages work only with GHC.
There is an overlay where we work on Haskell ebuilds before getting them into the main ::gentoo git tree. You can get the overlay using layman.
All development discussion takes place on the #gentoo-haskell (webchat) IRC channel. This channel is the appropriate place to report bugs in packages that are in the overlay. They should not be reported in Bugzilla, that's the place to report bugs about packages in the main ::gentoo git tree.
Further instructions and tips can be found in the Haskell article.
Contents
1 Developers
2 Policies
3 Goals
3.1 Long-term
3.2 Short-term
3.3 Pending tasks
4 Contribution
5 TODO list
Developers[edit | edit source]
All developers can be reached by e-mail using nickname@gentoo.org.
Policies[edit | edit source]
While adding new packages to the tree overlay we follow next rules: we keep in tree end user applications and their depends plus haskell-platform. We are keeping all development libs in overlay. In overlay we do not have 'stable-' / 'testing' partitioning, and all packages are marked as testing.
Goals[edit | edit source]
Long-term[edit | edit source]
Support for the haskell-ecosystem in the Gentoo.
Short-term[edit | edit source]
Stabilizing Haskell Platform in Gentoo tree: bug tracker.
Fixing USE flags metadata entries in overlay.
Fix packages test in overlay.
Pending tasks[edit | edit source]
Contribution[edit | edit source]
Ebuilds contribution. For more information see overlay documentation
Contribute to project programs (hackport, haskell-updater, etc.)
TODO list[edit | edit source]
[easy-to-hard] Add packages requested by people to the overlay. HackPort is a nice tool to do it fast.
[easy-to-moderate] Keep up-to-date upstream versions in overlay, fix depends broken by package updates and upstream fixes. HackPort can help in tracking: hackport status --from-hackage.
Improve HackPort tool.
[easy] Some packages are patched on top of upstream. Ideally they should not :]. Your goal is to push nice patches upstream. Haskell world is very eager in getting feedback, so it's a source of pleasure to work with upstream!
Some code snippets on scanning the tree for such patched packages:
[moderate] Some packages have their testuites, but ebuilds don't utilize it or have tests blocked. Blocked tests are easy to find with git grep RESTRICT.
Here is some notes to say: upstream tests are sometimes unportable hacks, so your aim is to rework ill written testsuites by using Cabal recently introduced testing interface and/or using libraries helping in testing (HUnit, QuickCheck, test-framework-*). See tests in darcs as an advanced example.
[moderate] Get ghc bugs fixed upstream, send patches
[easy-to-moderate] Help fix & improve cabal. Improve cabal-install.
[easy] Write a program to check for build errors of package in overlay.
[easy] run repoman full on the overlay and provide fixes for found QA notices. Or check out our travis-ci dashboard' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tbody><tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Haskell</big>
</th></tr>
<tr valign="top">
<th>Description
</th>
<td style="text-align: justify;">Support Haskell programming language ecosystem on Gentoo systems.
</td></tr>
<tr>
<th><span title="Mails to member(s) listed below.">Project email</span>
</th>
<td><a rel="nofollow" class="external text" href="mailto:haskell@gentoo.org">haskell@gentoo.org</a>
</td></tr>
<tr>
<th><span title="The link opens an IRC client to libera.chat IRC channel.">IRC channel</span>
</th>
<td><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-haskell">#gentoo-haskell</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-haskell">webchat</a></span>)
</td></tr>
<tr valign="top">
<th>Lead(s)
</th>
<td><ul><li><a href="/wiki/User:Slyfox" title="User:Slyfox">Sergei Trofimovich</a>
(slyfox)</li></ul> <br />Last elected: 2019-05-26
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td><ul><li><a href="/wiki/User:Gienah" title="User:Gienah">Mark Wright</a>
(gienah)</li></ul>
</td></tr>
<tr valign="top">
<th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td>(none)
</td></tr>
<tr>
<th>Parent Project
</th>
<td><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Gentoo</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></tbody></table>
<p>The Haskell project maintains the packages for Haskell implementations, libraries, and development tools. We support <a rel="nofollow" class="external text" href="http://www.haskell.org/ghc/">GHC</a> and <a rel="nofollow" class="external text" href="http://www.open.ou.nl/bhr/HeliumCompiler.html">Helium</a> though GHC is the best supported. The library packages work only with GHC.
</p><p>There is an overlay where we work on Haskell ebuilds before getting them into the main ::gentoo git tree. You can get the overlay using layman.
</p><p>All development discussion takes place on the <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-haskell">#gentoo-haskell</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-haskell">webchat</a></span>) IRC channel. This channel is the appropriate place to report bugs in packages that are in the overlay. They should not be reported in Bugzilla, that's the place to report bugs about packages in the main ::gentoo git tree.
</p><p>Further instructions and tips can be found in the <a href="/wiki/Haskell" title="Haskell">Haskell</a> article.
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Developers"><span class="tocnumber">1</span> <span class="toctext">Developers</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Policies"><span class="tocnumber">2</span> <span class="toctext">Policies</span></a></li>
<li class="toclevel-1 tocsection-3"><a href="#Goals"><span class="tocnumber">3</span> <span class="toctext">Goals</span></a>
<ul>
<li class="toclevel-2 tocsection-4"><a href="#Long-term"><span class="tocnumber">3.1</span> <span class="toctext">Long-term</span></a></li>
<li class="toclevel-2 tocsection-5"><a href="#Short-term"><span class="tocnumber">3.2</span> <span class="toctext">Short-term</span></a></li>
<li class="toclevel-2 tocsection-6"><a href="#Pending_tasks"><span class="tocnumber">3.3</span> <span class="toctext">Pending tasks</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-7"><a href="#Contribution"><span class="tocnumber">4</span> <span class="toctext">Contribution</span></a></li>
<li class="toclevel-1 tocsection-8"><a href="#TODO_list"><span class="tocnumber">5</span> <span class="toctext">TODO list</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="Developers">Developers</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=1" class="mw-editsection-visualeditor" title="Edit section: Developers">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=1" title="Edit section: Developers">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>All developers can be reached by e-mail using nickname@gentoo.org.
</p>
<h2><span class="mw-headline" id="Policies">Policies</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=2" class="mw-editsection-visualeditor" title="Edit section: Policies">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=2" title="Edit section: Policies">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>While adding new packages to the tree overlay we follow next rules: we keep in tree end user applications and their depends plus <a href="/index.php?title=Haskell:haskell-platform&action=edit&redlink=1" class="new" title="Haskell:haskell-platform (page does not exist)">haskell-platform</a>. We are keeping all development libs in overlay. In overlay we do not have 'stable-' / 'testing' partitioning, and all packages are marked as testing.
</p>
<h2><span class="mw-headline" id="Goals">Goals</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=3" class="mw-editsection-visualeditor" title="Edit section: Goals">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=3" title="Edit section: Goals">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<h3><span class="mw-headline" id="Long-term">Long-term</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=4" class="mw-editsection-visualeditor" title="Edit section: Long-term">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=4" title="Edit section: Long-term">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li>Support for the haskell-ecosystem in the Gentoo.</li></ul>
<h3><span class="mw-headline" id="Short-term">Short-term</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=5" class="mw-editsection-visualeditor" title="Edit section: Short-term">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=5" title="Edit section: Short-term">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li>Stabilizing Haskell Platform in Gentoo tree: <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/show_bug.cgi?id=472634%7Crelated">bug tracker</a>.</li>
<li>Fixing USE flags metadata entries in overlay.</li>
<li>Fix packages test in overlay.</li></ul>
<h3><span class="mw-headline" id="Pending_tasks">Pending tasks</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=6" class="mw-editsection-visualeditor" title="Edit section: Pending tasks">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=6" title="Edit section: Pending tasks">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<h2><span class="mw-headline" id="Contribution">Contribution</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=7" class="mw-editsection-visualeditor" title="Edit section: Contribution">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=7" title="Edit section: Contribution">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li>Ebuilds contribution. For more information see <a rel="nofollow" class="external text" href="https://github.com/gentoo-haskell/gentoo-haskell/blob/master/projects/doc/HOWTO-contribute.rst">overlay documentation</a></li>
<li>Contribute to project programs (hackport, haskell-updater, etc.)</li></ul>
<h2><span class="mw-headline" id="TODO_list">TODO list</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Haskell&veaction=edit&section=8" class="mw-editsection-visualeditor" title="Edit section: TODO list">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Haskell&action=edit&section=8" title="Edit section: TODO list">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li>[easy-to-hard] Add packages requested by people to the overlay. HackPort is a nice tool to do it fast.</li>
<li>[easy-to-moderate] Keep up-to-date upstream versions in overlay, fix depends broken by package updates and upstream fixes. HackPort can help in tracking: hackport status --from-hackage.</li>
<li>Improve HackPort tool.</li>
<li>[easy] Some packages are patched on top of upstream. Ideally they should not :]. Your goal is to push nice patches upstream. Haskell world is very eager in getting feedback, so it's a source of pleasure to work with upstream!</li>
<li>Some code snippets on scanning the tree for such patched packages:</li>
<li>[moderate] Some packages have their testuites, but ebuilds don't utilize it or have tests blocked. Blocked tests are easy to find with git grep RESTRICT.</li>
<li>Here is some notes to say: upstream tests are sometimes unportable hacks, so your aim is to rework ill written testsuites by using Cabal recently introduced testing interface and/or using libraries helping in testing (HUnit, QuickCheck, test-framework-*). See tests in darcs as an advanced example.</li>
<li>[moderate] Get ghc bugs fixed upstream, send patches</li>
<li>[easy-to-moderate] Help fix & improve cabal. Improve cabal-install.</li>
<li>[easy] Write a program to check for build errors of package in overlay.</li>
<li>[easy] run repoman full on the overlay and provide fixes for found QA notices. Or check out our <a rel="nofollow" class="external text" href="https://travis-ci.org/gentoo-haskell/gentoo-haskell">travis-ci dashboard</a></li></ul>
' |
Unix timestamp of change (timestamp) | 1628109738 |
Wiki