Skip to content

Comments

LFX-2025[term 1] website migration blog#271

Closed
jayesh9747 wants to merge 2 commits intokmesh-net:mainfrom
jayesh9747:lfx_2025_website_migration_blog
Closed

LFX-2025[term 1] website migration blog#271
jayesh9747 wants to merge 2 commits intokmesh-net:mainfrom
jayesh9747:lfx_2025_website_migration_blog

Conversation

@jayesh9747
Copy link
Contributor

No description provided.

Signed-off-by: jayesh9747 <112215167@cse.iiitp.ac.in>
Copilot AI review requested due to automatic review settings February 14, 2026 08:40
@netlify
Copy link

netlify bot commented Feb 14, 2026

Deploy Preview for kmesh-net failed.

Name Link
🔨 Latest commit f299cda
🔍 Latest deploy log https://app.netlify.com/projects/kmesh-net/deploys/69903d1ac3b67a0008c634f8

@kmesh-bot
Copy link
Collaborator

[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 ask for approval from jayesh9747. 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:

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

@gemini-code-assist
Copy link

Summary of Changes

Hello @jayesh9747, I'm Gemini Code Assist1! 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 introduces a new blog post that chronicles the author's LFX mentorship experience and their progression to becoming a project maintainer. It also updates the author configuration to include the new author's details, enabling proper attribution for the newly published content.

Highlights

  • New Author Added: A new author entry for 'jayesh9747' (Jayesh Savaliya) has been added to the blog/authors.yml file, including their name, title as 'Kmesh Maintainer', GitHub URL, and avatar image URL.
  • New Blog Post Published: A new blog post titled 'From Contributor to Maintainer: My LFX Mentorship Journey (Or How I Accidentally Became Responsible for Things)' has been added. This post details the author's experience with open source, LFX mentorship, and their journey to becoming a Kmesh maintainer, offering advice for aspiring contributors.

🧠 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
  • blog/authors.yml
    • Added a new author entry for 'jayesh9747'.
  • blog/lfx_2025_website_migration/index.md
    • Added a new blog post about an LFX mentorship journey.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new blog post detailing an LFX mentorship experience and adds the corresponding author information. The content of the blog post is well-written. I have provided a couple of review comments. One addresses the file path of the new blog post to align it with the project's conventions and improve URL clarity. The other is a minor suggestion to ensure consistency in the authors.yml file. Additionally, please note that the Chinese translation file for authors (i18n/zh/docusaurus-plugin-content-blog/authors.yml) has not been updated with the new author, which should be addressed to maintain synchronization.

name: Jayesh Savaliya
title: Kmesh Maintainer
url: https://github.com/jayesh9747
image_url: https://avatars.githubusercontent.com/u/123955234

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency with other author entries in this file, it's recommended to add the ?v=4 query parameter to the image_url. This parameter helps with cache busting when the avatar image is updated.

  image_url: https://avatars.githubusercontent.com/u/123955234?v=4

Comment on lines 1 to 7
---
title: "From Contributor to Maintainer: My LFX Mentorship Journey (Or How I Accidentally Became Responsible for Things)"
authors:
- jayesh9747
date: 2025-02-14
sidebar_position: 2
---

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The file path for this blog post seems inconsistent with the project's guidelines and the content of the post. The project's guide, docs/developer-guide/website/create-blog.md, recommends a file naming convention of YYYY-MM-DD-title.md. The current folder name lfx_2025_website_migration will also create a confusing URL slug, as the blog post is about a mentorship journey, not website migration.

It is recommended to rename the file to better reflect its content and adhere to the project's conventions. For example: blog/2025-02-14-from-contributor-to-maintainer-lfx-journey.md. Since a file rename cannot be suggested directly, please consider this change for better maintainability and user experience.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new blog post documenting Jayesh Savaliya's experience as an LFX Mentorship 2025 (Term 1) participant working on the Kmesh project. The blog post describes his journey from contributor to maintainer, sharing practical advice for aspiring open source contributors.

Changes:

  • Added a new blog post about LFX 2025 mentorship experience with Kmesh
  • Added author entry for Jayesh Savaliya to the authors configuration

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
blog/lfx_2025_website_migration/index.md New blog post documenting the author's journey through LFX Mentorship 2025, including strategies for getting selected, working with Kmesh, and eventually becoming a maintainer
blog/authors.yml Added author entry for jayesh9747 (Jayesh Savaliya) with title "Kmesh Maintainer"

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

name: Jayesh Savaliya
title: Kmesh Maintainer
url: https://github.com/jayesh9747
image_url: https://avatars.githubusercontent.com/u/123955234
Copy link

Copilot AI Feb 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing "v=4" query parameter in the image URL. Other author entries in authors.yml include this parameter (e.g., line 4, 10, 16, 22, 28), so for consistency, this URL should be "https://avatars.githubusercontent.com/u/123955234?v=4".

Suggested change
image_url: https://avatars.githubusercontent.com/u/123955234
image_url: https://avatars.githubusercontent.com/u/123955234?v=4

Copilot uses AI. Check for mistakes.
sidebar_position: 2
---

### 👋 Plot Twist: I'm Now a Maintainer
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are there so many emojis inthis blog?
In my experience, ChatGPT-generated articles tend to exhibit this characteristic.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes correct ,i have used ai. but not only gpt use too many emojies. any ai now using too much emojies. i will remove it from blog.

Updated the blog post to refine the title and improve clarity throughout the content. Enhanced the introduction and various sections for better readability and engagement.
@jayesh9747 jayesh9747 closed this Feb 14, 2026
@jayesh9747
Copy link
Contributor Author

linting and singoff issues in prev commit

@jayesh9747 jayesh9747 deleted the lfx_2025_website_migration_blog branch February 14, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants