Skip to content

A developer guide #4

@alessandrofelder

Description

@alessandrofelder

Maybe this should be in a developers guide. What do you think? We can have a separate DEVELOPER.md with coding standards, architecture design and repository rules.

Originally posted by @arielleleon in #2 (comment)

Note that this guide would be very high-level, linking to repositories' specific architecture design and standards (that should ideally refine the org level ones).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions