Skip to content

Write / Build Code review guide/site/app/video/something #429

Open
@SallyMcGrath

Description

@SallyMcGrath

We expect that trainees' work is being reviewed by mentors, but there isn't a decoupled way to get people involved in that project.

We've set up a substantial barrier between code and review by expecting everyone to onboard to CYF before getting involved with it. But the code is all FOSS so any qualified person could do it, if they knew what we wanted.

We need to create an engaging, low friction way for qualified reviewers to help our trainees.

We need to find ways to help our trainees respond to those reviews effectively (or at all)

How can we make this rewarding dialogue discoverable, accessible, and clear? What is the simplest thing that can possibly work?

@illicitonion I have set up this framing as a ticket and would be super grateful if you would brain on it for a bit.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Needs discussion

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions