Skip to content

Open Source: close the two honour-system steps (3 of 6 hands-on) #86

Description

@Jolah1

Part of #76.

Three hands-on missions out of six, and the graduation mission (105) is arguably the strongest exercise in the whole app: the backend asks GitHub whether your PR is really merged and really yours. Nothing to fix structurally here. The two gaps are small and worth closing.

Proposals

Mission 101 (read a real codebase) currently ends at "the button credits you when you have looked around", which is an honour-system step wearing a knowledge label. Ask for something specific instead: the file and line where a named function is defined in rust-bitcoin or BDK, or the number of tests in a given module. Checkable against the GitHub API, and it forces the search the lesson is actually teaching.

Mission 104 (tests are contributions too) teaches the arrange/act/assert shape and then asks nothing. Have the learner paste the test they wrote, or link the file they added it to. paste-value covers this today.

Mission 100 is framing and is fine as a knowledge mission.

Notes

Metadata

Metadata

Assignees

No one assigned

    Labels

    curriculumMission content: lessons, quizzes, hands-on stepsgood first issueGood for newcomers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions