|
| 1 | +# Express.js Official Partnership Guidelines |
| 2 | + |
| 3 | +## Purpose |
| 4 | + |
| 5 | +This document outlines the process and expectations for companies or organizations seeking to establish a formal partnership or collaboration with the Express.js project. The goal is to ensure productive, transparent, and mutually beneficial relationships that help advance the health and growth of the Express.js ecosystem. |
| 6 | + |
| 7 | +## Scope of Partnership |
| 8 | + |
| 9 | +Partnerships may include but are not limited to: |
| 10 | + |
| 11 | +* Sponsorships (financial or in-kind) |
| 12 | +* Engineering support (e.g., contributing maintainers or developers) |
| 13 | +* Promotional collaborations (e.g., joint announcements, branding) |
| 14 | +* Ecosystem integration (e.g., offering Express-compatible platforms or tooling) |
| 15 | +* Security initiatives (e.g., dedicated security audits or coordinated disclosure programs) |
| 16 | + |
| 17 | +## How to Initiate a Partnership |
| 18 | + |
| 19 | +### Step 1: Contact |
| 20 | + |
| 21 | +All partnership requests must be submitted via email to: |
| 22 | + |
| 23 | +📧 a-specific-email@we-want-to.use |
| 24 | + |
| 25 | +Include the following in your message: |
| 26 | + |
| 27 | +* Organization name |
| 28 | +* Point(s) of contact with email and GitHub profile |
| 29 | +* Nature of the proposed partnership |
| 30 | +* Any specific expectations or commitments |
| 31 | +* Relevant timelines (if applicable) |
| 32 | + |
| 33 | +Alternatively, you may open a private issue via the Express.js GitHub Discussions marked with #partnership-request, and a core maintainer will follow up. |
| 34 | + |
| 35 | +### Step 2: Acknowledgment & Review |
| 36 | + |
| 37 | +* You will receive an acknowledgment within 5 business days. |
| 38 | +* Express core maintainers will review the proposal and may request further information or clarification. |
| 39 | +* Depending on complexity, the review period may take up to 15 business days. |
| 40 | + |
| 41 | +### Step 3: Decision & Agreement |
| 42 | + |
| 43 | +If the partnership is approved, Express.js will provide a simple agreement document outlining: |
| 44 | + |
| 45 | +* Objectives |
| 46 | +* Roles & responsibilities |
| 47 | +* Duration (if applicable) |
| 48 | +* Branding guidelines and limitations |
| 49 | +* Code of conduct and open source contribution standards |
| 50 | + |
| 51 | +Both parties must review and confirm the agreement before the partnership is publicly acknowledged. |
| 52 | + |
| 53 | +## Expectations for Partners |
| 54 | + |
| 55 | +All partners are expected to: |
| 56 | + |
| 57 | +* Uphold the Express.js Code of Conduct |
| 58 | +* Align with the OpenJS Foundation principles |
| 59 | +* Engage constructively with the Express.js team and community |
| 60 | +* Avoid exerting influence over the project’s governance or roadmap unless explicitly agreed |
| 61 | + |
| 62 | +## Use of Express.js Name and Logo |
| 63 | + |
| 64 | +The Express.js name and logo are trademarks of the OpenJS Foundation. Use of the name or branding must follow the OpenJS Trademark Policy and must be approved before publication or marketing. |
| 65 | + |
| 66 | +## Termination of Partnership |
| 67 | + |
| 68 | +Express.js or the partner may terminate the agreement at any time with written notice (email acceptable). Grounds for early termination include: |
| 69 | + |
| 70 | +* Breach of agreement |
| 71 | +* Code of conduct violations |
| 72 | +* Misuse of the Express.js name or reputation |
| 73 | +* Cessation of activity from either party |
| 74 | + |
| 75 | +## Questions |
| 76 | + |
| 77 | +For any questions about these guidelines or ongoing partnerships, contact: |
| 78 | + |
| 79 | +📧 a-specific-email@we-want-to.use |
| 80 | + |
| 81 | +Or reach out to the Express.js maintainers via GitHub Discussions. |
0 commit comments