Skip to content

Suggest to include "open source strategy" within the requirements section #14

Description

@anajsana

There is a never ending pain point shared in TODO community about the importance of having the open source operations being aligned with the organization's goals to build effective contribution programs. Because of this, having an open source strategy that aligns with organization's goals could be a requirement to include in order to build a contribution specification.

This guide shares useful knowledge on this area: https://todogroup.org/guides/outbound-oss/#define-your-open-source-goal-and-strategy

What do people think?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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