Before offering a customer path, determine what software, shared contributions and customer material the agreement covers. Keep public knowledge, attribution and version history distinct from confidential documents. Establish which permissions and technical access controls would be necessary; do not assume a current view provides them. Use public material for initial tests while those terms are unresolved. Ask whether customers will pay for hosting, review coordination or implementation while existing community contributions remain available on whatever terms are confirmed to govern them.