Naming accounts consistently

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

还没有人认领这个 Issue。

评估

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

调研方向

该 issue 提供了关于名称、用户名和个人资料图片一致性的课程作业指导，但没有指定文件或测试。检查这些 onboarding 内容在哪里维护，然后将已发布的指导与 issue 中的要求进行比较，并确认完成的文本涵盖了所述的账户命名检查。

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

描述

🏕 Priority Mandatory 📅 Sprint 1 Core Submit:None 🦔 Size Tiny
Link to the coursework

Your own accounts!

Why are we doing this?
Consistency in online account names

During the CYF course you will make accounts online. (Such as Slack, GitHub, Google, LinkedIn...)

You should always use your real name. It must always be the same name. Don't use any other words apart from your name. Do not ever put your birth year or age in your user name. These things can harm your job prospects so start as you mean to go on.

Trainees use the same name everywhere in their work with CYF.

[!NOTE]
CYF recognises you may need to keep your birth name private. When we say real name, we mean the name you go by. It does not have to match your birth certificate or any other legal document.

Your profile picture does not have to be a picture of you. It must be safe for work, consistent and unique, so you don't get mixed up with other people. If you need to keep your photo private, you can use Robohash to make a unique profile picture.

Summary

Don't use cute handles or put the year of your birth in your username.

Use the same username and picture across all CYF accounts. This also means professional profiles like Linkedin and GitHub.

Maximum time in hours

.1

How to get help

Swap with a classmate and check their profile. Ask yourself:

If you didn't know them, would you know this was their Slack account? If you didn't know them, would you know this was their LInkedIn? If you were a recruiter reading their GitHub, could you find their LinkedIn within six seconds? If you wanted to invite them to an opportunity, could you do that without asking them first?

主要语言
没有语言数据
星标
0
派生
0
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

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

CodeYourFuture/Module-Onboarding 的其他 Issue

查看 CodeYourFuture/Module-Onboarding 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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