adjust development partner

[janetmoreno]

User description

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

Codify rules for the development partner and clear time requirements for this level of sponsorship

Motivation and Context

Inspired on https://github.com/appium/appium/blob/master/GOVERNANCE.md#sponsorship

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

Documentation

---

Description

• Clarify development partner sponsorship requirements

• Specify 50% time commitment for full-time employees

---

Diagram Walkthrough

flowchart LR
  A["Current Requirements"] --> B["Updated Requirements"]
  B --> C["Full-time Employee"]
  B --> D["50% Time Commitment"]
  C --> E["Active Contribution"]
  D --> E

Loading

File Walkthrough

	Relevant files
Documentation	_index.html Specify development partner time commitment requirements  website_and_docs/content/sponsor/_index.html Updated development partner sponsorship requirements Changed from "at least one employee" to "at least one full-time employee" Added specific 50% time commitment requirement for active contribution +3/-2

---

[CLAassistant]

All committers have signed the CLA.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Clarity The phrase "devoted 50% of their time actively contributing" could be clarified to avoid ambiguity (e.g., specify a time window like per week/month and define what counts as "actively contributing"). of making a monetary contribution, at least one full-time employee from your company needs to be devoted 50% of their time actively contributing to the project. Consistency Ensure terminology aligns across the site (e.g., "full-time employee" vs "employee", "Selenium level" reference remains accurate after this change) and that this requirement is reflected wherever sponsorship levels are documented. of making a monetary contribution, at least one full-time employee from your company needs to be devoted 50% of their time actively contributing to the project.

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Clarify time commitment period The phrase "devoted 50% of their time actively contributing" is ambiguous (e.g., over what period?). Specify a clear minimum time window to avoid disputes and ensure consistent enforcement. Clarify that the 50% commitment is averaged over a defined period. website_and_docs/content/sponsor/_index.html [114-116] instead of making a monetary contribution, at least one full-time employee -from your company needs to be devoted 50% of their time actively contributing +from your company needs to be devoted at least 50% of their working time, averaged over a rolling 3-month period, actively contributing to the project. [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies ambiguity in the sponsorship requirement and proposes a specific clarification, which aligns with the PR's intent to make the rules more precise.	Medium
Update

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	9b9a308
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/690ca623a97d2d000827bfa3
😎 Deploy Preview	https://deploy-preview-2423--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[qodo-merge-pro]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Not applicable: The PR only updates static sponsorship text with no code paths or actions to audit; no audit trail logic is added or required in this diff. Referred Code <li> This level has the same benefits as the Selenium level above, but instead of making a monetary contribution, at least one full-time employee from your company needs to be devoted 50% of their time actively contributing to the project. </li> <li> Currently limited to 3 companies but reviewed yearly. </li>
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Not applicable: The changes are static content updates without executable logic; no error handling is introduced or required by this diff. Referred Code <li> This level has the same benefits as the Selenium level above, but instead of making a monetary contribution, at least one full-time employee from your company needs to be devoted 50% of their time actively contributing to the project. </li> <li> Currently limited to 3 companies but reviewed yearly. </li>

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label