Change zoology to ecosystem

[seanlaii]

• 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 cleanup

• What this PR does / why we need it:
  Change zoology to ecosystem.

• Which issue(s) this PR fixes:

[gemini-code-assist]

Summary of Changes

Hello @seanlaii, 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 performs a cleanup operation by standardizing a key term within the project's documentation and configuration. The change involves globally replacing the identifier 'zoology' with 'ecosystem', primarily affecting the Chinese language content and menu structures. This ensures that the categorization and navigation within the documentation are more accurate and consistent, enhancing the user experience.

Highlights

• Terminology Update: The term 'zoology' has been replaced with 'ecosystem' across various configuration and documentation files to improve clarity and consistency.
• Configuration File Changes: The config/_default/languages.toml file was updated to reflect the new 'ecosystem' identifier in multiple Chinese menu sections for different documentation versions.
• Documentation File Changes: Numerous Chinese documentation markdown files (e.g., flink_on_volcano.md, kubeflow_on_volcano.md) across various version directories had their parent field updated from 'zoology' to 'ecosystem'.

🧠 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.

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 performs a simple but important cleanup by renaming zoology to ecosystem across various configuration and documentation files. The change improves clarity and consistency, as 'ecosystem' is a more appropriate term for this context. The changes have been applied consistently across all relevant files, including versioned documentation. The pull request is well-executed and ready for merging.

[seanlaii]

cc @JesseStutler

[JesseStutler]

/approve
/lgtm
Thanks!

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JesseStutler

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [JesseStutler]

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