Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

πŸ§‘πŸΎβ€βš–οΈ Check module success criteria

Open
#128 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale

Research direction

Read the linked module success criteria first, then discuss with the cohort how they will meet them. In week 4, use the progress-report template in the issue, replace the placeholder criteria and cohort details, and submit the cohort's decision about progressing or taking a consolidation week.

Written by the indexing model from the issue text.

Description

🎯 Topic Code Review 🎯 Topic Communication 🎯 Topic Delivery 🎯 Topic Requirements 🎯 Topic Teamwork 🎯 Topic Testing 🎯 Topic Time Management πŸ• Priority Mandatory πŸ“… Servers πŸ“… Week 1 πŸ“… Week 4 πŸ¦” Size Tiny
Link to the coursework

https://curriculum.codeyourfuture.io/node/success/

Why are we doing this?

πŸ”‘ The most important thing is that you are secure in your understanding.

At the end of the course, we will expect you to build novel applications using your understanding. If you cannot build things, we cannot put you forward for jobs. It is in your personal interest to make sure you have properly understood this module.

To progress to the next module you need to meet the success criteria for this module. How will you as a cohort meet the module success criteria? Discuss it in your class channel and make a plan together.

πŸ§‘πŸΏβ€πŸŽ€ good strategies
  • asking volunteers to review your code
  • helping each other with coursework blockers
  • arranging midweek study sessions
  • using Saturday time to review code and cohort tracker
πŸ™…πŸΏ bad strategies
  • opening empty PRs
  • copying and pasting
  • breaking the Trainee Agreement
  • mistaking the measure for the target
Maximum time in hours

.5

How to get help

Discuss with your cohort. Support each other.

How to submit

In week 4 of your module you will need a representative to report to the organisation. Here's your template, fill in your details and delete as appropriate:

πŸ“ˆ Cohort Progress Report from @cohort-name to @programme-team

  • criterion
  • criterion
  • criterion
  • criterion

βœ… We are progressing to the next module.
β›” We are taking a consolidation week to meet our targets.

Dominant language
JavaScript
Stars
0
Forks
74
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up β€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Servers

All issues in CodeYourFuture/Module-Servers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.