docs: professionalize site messaging and add project governance

[yoursanonymous]

• Please check if the PR fulfills these requirements

• The commit message follows our guidelines

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

/kind documentation

• What this PR does / why we need it:

This PR enhances the Volcano website by improving core project branding, removing development placeholders, and establishing essential project governance documentation to ensure the project meets CNCF standards.

• Which issue(s) this PR fixes:

issue #481

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign k82cn for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[volcano-sh-bot]

Welcome @yoursanonymous! It looks like this is your first PR to volcano-sh/website 🎉

[gemini-code-assist]

Summary of Changes

Hello @yoursanonymous, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the Volcano project's website by professionalizing its public-facing content and establishing crucial governance documentation. The changes aim to improve the project's branding, replace development placeholders with official information, and integrate essential guides for contributors and security vulnerability reporting, thereby ensuring the project meets CNCF standards for open-source projects.

Highlights

• Project Governance Documentation: New CONTRIBUTING.md and SECURITY.md files have been added to provide clear guidelines for community contributions and a formal process for reporting security vulnerabilities, aligning with CNCF standards.
• Website Branding and Professionalism: The website's metadata, contact information, and core messaging have been updated to reflect professional branding. This includes replacing placeholder contact details with official Volcano channels and refining the project's description.
• Documentation Refinements: Minor typos in README.md and doc/quickstart.md have been corrected, and the hero section's description has been updated for accuracy.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• .gitignore
  • Added rules to ignore VSCode AI instructions, specifically .github/instructions/codacy.instructions.md.
• CONTRIBUTING.md
  • New file added, detailing guidelines for contributing to the Volcano website, including Hugo installation, local development, PR workflow, and documentation standards.
  • Includes a reference to the CNCF Code of Conduct.
• README.md
  • Corrected a typo from 'organisation' to 'organization'.
• SECURITY.md
  • New file added, outlining the security policy for Volcano, including supported versions, the vulnerability reporting process (via volcano-security@googlegroups.com), and the disclosure process.
  • References the CNCF security policy.
• config/_default/params.toml
  • Added a description for social sharing and search engines: 'Volcano is a batch container computing engine for Kubernetes.'
  • Updated the contact email from a placeholder to volcano-sh@googlegroups.com.
  • Cleared phone and address fields.
  • Cleared office_hours field.
  • Updated contact_links to include official Volcano Twitter, GitHub, and Mailing List, removing generic links.
• content/en/home/hero.md
  • Changed the hero section's description from 'Edge computing' to 'Batch container computing'.
• doc/quickstart.md
  • Corrected a typo from 'prorortion' to 'proportion'.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request significantly improves the project's website by adding key governance documents (CONTRIBUTING.md, SECURITY.md), updating site configuration to use real project information instead of placeholders, and refining the project's messaging. The changes are well-done and professional. I have one suggestion to further improve the new security policy for long-term clarity.

[gemini-code-assist]

The table of supported versions is a great start. To avoid it becoming outdated and to provide clarity for future releases, consider stating the project's version support policy explicitly. For example, you could mention how many recent minor versions are supported (e.g., 'The two most recent minor versions receive security updates.'). This would make the policy clearer for users and contributors as new versions of Volcano are released.