Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Make text on the website friendlier and less off-putting

未关闭
#216 2 条评论 14 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞

调研方向

在网站源代码中搜索位于 /、/whitepaper/ 和 /guidelines-for-respectful-communication/ 的页面,并定位引用的文本。审查拟议的措辞和 URL 更改,包括可能移除对 Stallman 的引用。相关页面上出现约定的语言,并且指向重命名页面的链接能够正常工作,即表示完成。

由索引模型根据 Issue 内容生成。

描述

Duplicating an issue from the previous version of website about difficult and unfriendly language by presenting highlighted by @sjakobi changes in a more structured format and incorporating changes by @simonpj and @goldfirere.

Additionally adding a few more suggestions on my own.

Note: The previous website repo was archived but issues weren't transferred to the new one. I care about this particular issue but I don't have the capacity or motivation to transfer the remaining issues.

The main motivation is the the website is difficult to read for non-native English speakers and it sounds unnecessary convoluted or even hostile in many places. This implicitly sends the message "You're not welcome in Haskell if you're not smart enough".


Where: https://haskell.foundation/
Old: Our Ethos
New: Our Values
Motivation: The word "ethos" itself is rather unclear. It's not a common choice of words for naming this section so the language sounds alien.


Where: https://haskell.foundation/
Old: Haskell’s design puts principle ahead of expediency by cleaving closely to the principles of purely functional programming.
New: Haskell's design puts principle ahead of what is easy or popular by being firmly guided by the principles of purely functional programming.
Motivation: The word "expediency" is rather uncommon as well the expression "to cleave closely to sth.".


Where: https://haskell.foundation/
Old: HF augments, celebrates, and coordinates the contributions and leadership of Haskell’s vibrant community.
New: HF sees itself as a means to celebrate, coordinate, and make more powerful and effective, the contributions and leadership of Haskell’s vibrant community.
Motivation: The word "augment" as a verb is a rather obscure word.


Where: https://haskell.foundation/
Old: Haskell embodies a radical and elegant attack on the entire enterprise of writing software.
New: Haskell embodies an innovative and elegant approach on the entire enterprise of writing software.
Motivation: The word "attack" is too hostile and off-putting. I don't want to be associated with the language that "attacks" others. We change the wording here to a friendlier version.


Where: https://haskell.foundation/whitepaper/
Old: https://haskell.foundation/whitepaper/
New: https://haskell.foundation/mission-statement/
Motivation: The word "whitepaper" sounds too academic. It gives an impression of some academic research. It may look really weird that formulating a mission and reasons behind an organisation requires scientific research.

Side note: I wasn't able to find a link that directs to whitepaper from any of the pages on the main website. Maybe I just missed it but in any case is a bit odd to have a resource on the website not linked from anywhere. It gives the impression that it's not supposed to be found.


Where: https://haskell.foundation/guidelines-for-respectful-communication/
Old: The GNU Kind Communication Guidelines, published in October 2018, also express the positive tone we seek; Stallman’s post explains the intent.
New:
Motivation: Richard Stallman is a controversial figure. Despite their outstanding technical contributions, their views are not aligned with Diversity and Inclusion in tech. Keeping reference to Stallman's statements in the official guidelines to respectful communication simply stops almost everyone who associates themselves as minority in tech from joining the Haskell community or at least affiliating with HF. So I propose to remove the reference to their statements from Guidelines for Respectful Communication

主要语言
CSS
星标
44
派生
53
平均合并
1 天 9 小时
30 天内合并 PR
7

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

haskellfoundation/haskellfoundation.github.io 的其他 Issue

查看 haskellfoundation/haskellfoundation.github.io 的全部 Issue

相似的 Issue

更多 Content Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。