Create how_we_meet

[ed-yolo]

Sub page under 'People' - focusing on meeting best practices.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Adds a new "How we meet" guide outlining Ultralytics best practices for effective meetings.

📊 Key Changes

• Introduces meeting guidance covering preparation, setup, participation, and follow-up.
• Recommends clear objectives, agendas, mindful scheduling, focused attendance, and punctuality.
• Documents expectations for hybrid and virtual meeting etiquette, including camera, audio, and background practices.
• Encourages AI notetakers, prompt notes, assigned owners, deadlines, and centralized meeting materials.

🎯 Purpose & Impact

• Helps team members run more focused, inclusive, and productive meetings.
• Reduces unnecessary meetings and passive attendance while improving accountability after meetings.
• Provides a shared reference for collaboration across locations and time zones.

[UltralyticsAssistant]

👋 Hello @ed-yolo, thank you for submitting a ultralytics/handbook 🚀 PR! This automated message provides a checklist for a smooth review; an engineer will assist with any follow-up questions. Please review the following:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/handbook main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee
  For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

The meeting guidance itself is well structured, but the new source file is not a renderable or navigable MkDocs page in its current form.

💬 Posted 1 inline comment

[UltralyticsAssistant]

⚠️ HIGH: This filename has no Markdown extension, so MkDocs treats it as a static asset and copies it unrendered rather than generating a handbook page. The explicit nav in mkdocs.yml also has no People entry for this page, so the requested subpage cannot be reached from the site. Rename it to docs/en/people/how_we_meet.md and add it to the People & Benefits navigation.