-
Notifications
You must be signed in to change notification settings - Fork 0
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
Conversation
As outlined in haskell-infra#59, there are two pages which describe the Haskell.org committee and it's roles, responsibilities, process, history, etc. One is here on haskell.org, the other is on the wiki at https://wiki.haskell.org/Haskell.org_committee. Both pages appear authoritative, but differ in their content. At the same time, the general consensus is to move content off the wiki (particularly the more "official" content such as this). We would then replace that wiki article with a link to the this page. This is a first attempt which is more of a "bulk import" (or "merge") of the existing content. Note that there are a few places where the differences in content on the haskell.org page and wiki article may seem to be in conflict (or where one does not go as far as the other). These discrepancies and conflicts should be reviewed and updated. Some of the wiki content is more verbose than that on this page, and may still deserve some word-smithing. A rough list of changes: * collected the full list of links at the bottom of the page * move the list of "committee members" a little lower in the page, bumping contact info and responsibilities above * Included (merged) process, history and responsibilities content (from the wiki) that was missing here on this page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for putting this together! I left a few suggestions.
Also, could you point this PR back to the haskell-infra repo? It's currently set to merge into the master
branch of your fork instead.
Thanks!
Thank you for reviewing and helping me get it done :)
Yes, sorry, I overlooked that before. And it looks like I'll need to create a new PR to target the other remote. |
Sounds good. Shame GitHub doesn't make it easy to point a PR to a different repo :/. I'm going to be super busy for a few days, but if you set up a new PR, I should be able to review it early next week. After that it'll need one more approval from somebody on the committee—we have a two-approval process for website changes—and it should be ready to go. Thanks! |
OK, thank you for the heads up on all of that. I will probably pick this back up on the weekend, and will aim to sync up again next week. |
Co-authored-by: Tikhon Jelvis <[email protected]>
This was downloaded from the Haskell Wiki at: https://wiki.haskell.org/wikiupload/9/9c/Haskell-org-board-res.pdf
5091b1d
to
0caba3a
Compare
This PR has been replaced by haskell-infra#64. |
As outlined in haskell-infra#59, there are two pages which describe the Haskell.org committee and it's roles, responsibilities, process, history, etc. One is here on haskell.org, the other is on the wiki at https://wiki.haskell.org/Haskell.org_committee. Both pages appear authoritative, but differ in their content. At the same time, the general consensus is to move content off the wiki (particularly the more "official" content such as this). We would then replace that wiki article with a link to the this page. This is a first attempt which is more of a "bulk import" (or "merge") of the existing content. Note that there are a few places where the differences in content on the haskell.org page and wiki article may seem to be in conflict (or where one does not go as far as the other). These discrepancies and conflicts should be reviewed and updated. Some of the wiki content is more verbose than that on this page, and may still deserve some word-smithing.
A rough list of changes:
I can make additional updates to this, but would need feedback on that. cc @TikhonJelvis