Skip to content

Doc contribution requirements #50

@mapedraza

Description

@mapedraza

In 2024, and with all the improvements that GitHub has included in terms of documentation and markdown, does it still make sense for RtD documentation to be mandatory? Maintaining it is an extra effort that doesn't always make sense.

The clearest example is the Orion Context Broker documentation. This was simplified exponentially when the single page document was made. In this case, the RtD documentation does not make as much sense, and often provides old or outdated versions when it appears on google.

For that reason, we think this requirement:

- Accurate, current Documentation **MUST** be available on Read the Docs and as GitHub content.

Should be changed to something like this:

  • Accurate, current Documentation MUST be available on Read the Docs OR as GitHub content.

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