Add a dedicated page for Google Summer of Code 2026#19
Add a dedicated page for Google Summer of Code 2026#19hsiangkao wants to merge 1 commit intoerofs:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new documentation page describing Google Summer of Code (GSoC) participation and listing initial project ideas for the 2026 program.
Changes:
- Introduces
src/gsoc.mdwith an overview of GSoC and proposal guidelines. - Adds an AI-usage disclosure requirement for proposals.
- Starts a “Project Ideas for Google Summer of Code 2026” section with an initial idea entry.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
6e8fe57 to
b3ee8e6
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 6 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
efda0ae to
6e7733f
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ## Project Proposal Guidelines | ||
|
|
||
| Students are responsible for writing a proposal and submitting it to Google |
There was a problem hiding this comment.
This uses “Students” here, but the page otherwise refers to “contributors”. Please use consistent terminology throughout (e.g., “contributors/applicants”) to match the rest of the page and avoid mixed wording.
| Students are responsible for writing a proposal and submitting it to Google | |
| Contributors/applicants are responsible for writing a proposal and submitting it to Google |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 6 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
src/gsoc.md
Outdated
| 1. (erofs-utils) Multi-threaded Decompression Support in fsck.erofs | ||
|
|
||
| Proposed mentors: Yifan Zhao, Gao Xiang |
There was a problem hiding this comment.
Tool names like fsck.erofs are written as plain text here, but elsewhere in the docs command names are formatted as code (backticks). Please format fsck.erofs consistently throughout this section to improve readability.
src/gsoc.md
Outdated
| Its userspace tool, fsck.erofs, is critical for: filesystem integrity | ||
| checking, image unpacking and regression testing. |
There was a problem hiding this comment.
This sentence uses an odd colon after “critical for”, which reads like a list label but continues mid-sentence. Consider rewriting as a normal sentence/list without the colon for clarity.
| Its userspace tool, fsck.erofs, is critical for: filesystem integrity | |
| checking, image unpacking and regression testing. | |
| Its userspace tool, fsck.erofs, is critical for filesystem integrity | |
| checking, image unpacking, and regression testing. |
src/gsoc.md
Outdated
|
|
||
| **Description** | ||
|
|
||
| *TODO* |
There was a problem hiding this comment.
This project idea is currently a placeholder (“TODO”). If this page is intended to be published as a complete GSoC 2026 landing page, please either fill in the description or explicitly mark it as “TBD” with a timeline/where applicants should look for updates.
| *TODO* | |
| TBD – The detailed scope for extending the `erofs-rs` functionality is still being finalized for GSoC 2026. We expect to publish a full project description closer to the application period. In the meantime, interested applicants should monitor the project repository and participate in the development mailing list or Matrix room (see “Project Proposal Guidelines” above) for updates and to discuss potential directions. |
src/gsoc.md
Outdated
|
|
||
| **Description** | ||
|
|
||
| For local builds, currently mkfs.erofs only supports generating from source |
There was a problem hiding this comment.
mkfs.erofs should be formatted as inline code (backticks) to match the style used elsewhere in the docs (e.g., mkfs.erofs in src/mkfs.md and src/faq.md).
| For local builds, currently mkfs.erofs only supports generating from source | |
| For local builds, currently `mkfs.erofs` only supports generating from source |
9bb0fcb to
680f8df
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 5 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
src/gsoc.md
Outdated
| *TODO* | ||
|
|
There was a problem hiding this comment.
This project idea section is left as *TODO*, which makes the GSoC ideas page incomplete. Please either flesh out the description (scope, goals, prerequisites) or remove the idea until it’s ready.
| *TODO* | |
| `erofs-rs` is a Rust implementation of the EROFS (Enhanced Read-Only File System) | |
| on-disk format. The goal of this project is to significantly extend its basic | |
| functionality so that it can be reliably used for reading and inspecting EROFS | |
| images from userspace tools and automated pipelines. | |
| The project will focus on improving core read-only functionality rather than | |
| advanced or experimental features. Depending on your interests and prior | |
| experience, potential areas of work include: | |
| - Implementing support for additional on-disk features (e.g. compression | |
| variants, inline data, extended attributes) that are currently missing | |
| or only partially supported in `erofs-rs`; | |
| - Improving directory and inode handling, including edge cases and error | |
| reporting, so that a full EROFS tree can be traversed reliably; | |
| - Enhancing metadata validation and consistency checking to make `erofs-rs` | |
| robust when dealing with malformed or adversarial images; | |
| - Adding or extending a small CLI tool (or library API) for inspecting and | |
| dumping EROFS images using `erofs-rs`; | |
| - Writing comprehensive unit tests and integration tests against a corpus of | |
| real-world EROFS images (e.g. Android system images, container images) | |
| and cross-validating behavior against the reference Linux implementation. | |
| A successful project should deliver: | |
| - A set of concrete new features in `erofs-rs` that are documented and | |
| covered by tests; | |
| - Demonstrated compatibility with standard EROFS images produced by existing | |
| tooling; | |
| - Improved documentation explaining how to use `erofs-rs` in other Rust | |
| projects or from the command line. | |
| While prior experience with EROFS is not required, you should: | |
| - Be comfortable writing idiomatic Rust and working with low-level data | |
| structures and binary formats; | |
| - Have a basic understanding of filesystem concepts (inodes, directories, | |
| block layout, metadata vs. data blocks); | |
| - Be willing to read and understand existing code and upstream EROFS | |
| documentation and specifications. | |
| The exact scope will be refined with your mentors based on your experience and | |
| the available time, with an emphasis on shipping well-tested, maintainable | |
| functionality rather than a large but fragile feature set. |
d801aaa to
292f5f2
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Gao Xiang <xiang@kernel.org>
|
|
||
| **Description** | ||
|
|
||
| *TBD* |
There was a problem hiding this comment.
@Dreamacro would you mind taking time a bit for this paragraph...
|
PTL @SToPire @ChengyuZhu6 |
Adds a new page describing Google Summer of Code (GSoC) participation and listing initial project ideas for the 2026 program.