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

[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?