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

Orgs please make Contributor Guidelines pages more clear for potential contributors

未关闭
  • 哪里不对？
#19 0 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
文档
描述清晰度
需要澄清
活跃度
停滞
领域
documentation

调研方向

首先查看网站的 Contributor Guidance 页面以及 issue 中列出的示例指南链接。检查每个页面是否说明了首次联系的步骤、提供了明确无歧义的社区或导师链接，并包含当前日期；完成意味着指南清晰、欢迎贡献者且保持最新。

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

描述

documentation enhancement help wanted

We are past the stage in which this is relevant for GSoC '22 but let's make sure we address it early for '23.

I was doing a quick look through the Contributor Guidance sections of about 30 orgs and quickly noticed that it isn't clear what the contributor should do first for about 80% of them. Many of you are still tweaking these during this first week and that is fine but we have really been trying to push interested contributors to reach out to you now (rather than waiting until apps open April 4) so you can expect to get many folks coming to your page and wanting to talk to you over these next few weeks. Having the information as accessible as possible as soon as possible is very important.

Some of the issues I have seen with the Contributor Guidelines links:

  • An Org has information in there but you don't explicitly say reach out to us via our chat channel, xyz or whatever that first contact should be.
  • Org has a link to their forum but there are 4 or 5 different lists for the contributors to choose from on your page. It isn't clear to someone coming in to your org for the first time which of those they should choose.
  • Saying talk to the mentor about the project idea but not giving information on how/where they would do that (some orgs have the mentor contact details on the project ideas page so it's more obvious but many do not so I am guessing you want them to reach out via a chat channel or forum but you don't say that).
  • Linking to your project ideas where there is no additional information on what to do, just the list of Ideas isn't actual guidance.
  • Having wrong info on your page (2021 dates, etc.) There were some that had great info but the pages haven't been updated with the 2022 info so I couldn't list them as the great examples that they were otherwise.
  • If you are going to list the student application dates on your pages (which is helpful to do) be sure the dates are correct (should be April 4-19 1800 UTC for 2022).

A few good examples that make it clear what a GSoC contributor should do first with your org:
ArduPilot
GNOME
Performance Co-Pilot
RoboComp
Wikimedia Foundation

Remember you want to make reaching out to your community as easy and welcoming as possible for interested contributors.

主要语言
JavaScript
星标
6
派生
39
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

CCExtractor/website 的其他 Issue

查看 CCExtractor/website 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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