Skip to content

Diversity & Inclusion policies #7

@dthaler

Description

@dthaler

Here's what the CCC recommends projects adopt, I don't know if LFN has similar guidance for its projects:

Training
Maintainers are recommended to take the Linux Foundation course: Inclusive Open Source Community Orientation

Any contributor who may present in a CCC sponsored forum is recommended (and in some cases may be required) to take the Linux Foundation course: Inclusive Speaker Orientation

Inclusive writing style guides
An open source best practice is to document style requirements. This makes it easier for new contributors to conform to community norms without guessing and reduces unproductive practices like "bike shedding". Example style guides include: https://github.com/torvalds/linux/blob/a5f526ecb075a08c4a082355020166c7fe13ae27/Documentation/process/coding-style.rst#4-naming https://docs.microsoft.com/en-us/style-guide/bias-free-communication https://developers.google.com/style/inclusive-documentation

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions