Skip to content

GSoC-2026 community bonding blog by Parth Dagia#845

Open
parthdagia05 wants to merge 2 commits into
sugarlabs:mainfrom
parthdagia05:gsoc-26-parth-dagia-community-bonding
Open

GSoC-2026 community bonding blog by Parth Dagia#845
parthdagia05 wants to merge 2 commits into
sugarlabs:mainfrom
parthdagia05:gsoc-26-parth-dagia-community-bonding

Conversation

@parthdagia05
Copy link
Copy Markdown

📝 Description

Adds my GSoC '26 community bonding blog post as a new page on the Sugar Labs website, along with my one-time author profile.

This is my introductory post for the GSoC '26 program, where I'll be working on the Music Blocks 4 Program Builder under mentors Anindya Kundu, Justin Charles, and Safwan Sayeed. The post introduces me to the community, gives an overview of the project, and outlines my plan for the first two weeks of the coding period.

Files added:

  • src/constants/MarkdownFiles/authors/parth-dagia.md author profile (one-time setup)
  • src/constants/MarkdownFiles/posts/2026-05-23-gsoc-26-parth-dagia-community-bonding.md community bonding blog post

cc mentors: @meganindya @justin212407 @sa-fw-an

🔗 Related Issue

N/A GSoC '26 weekly blog post submission, not tied to an issue.

🔄 Type of Change

  • 📖 Content Update (text changes, documentation)

📷 Visual Changes

No visual changes. This PR only adds two markdown content files; no components, styles, or layouts are modified.

🧪 Testing Performed

📱 Browser Compatibility

N/A - content-only change, no rendering logic touched.

🖥️ Responsive Design

N/A - content-only change, no layout modified.

✅ Test Cases

  1. Frontmatter follows the official GSoC blog post template (title, excerpt, category, date, slug, author, tags, image).
  2. Author profile is referenced correctly via author: "@/constants/MarkdownFiles/authors/parth-dagia.md".
  3. Filename follows the convention YYYY-MM-DD-gsoc-26-username-*.md.
  4. Markdown lint disable comment (<!-- markdownlint-disable -->) is present.

♿ Accessibility

N/A - no UI changes. Markdown headings follow a proper hierarchy (H1 → H2).

📋 PR Checklist

  • My code follows the project's coding style guidelines
  • I have tested these changes locally
  • My changes generate no new warnings or console errors
  • I have checked for and resolved any merge conflicts
  • I have validated all links are working correctly

💭 Additional Notes

This is my first weekly blog post for GSoC '26, submitted ahead of the May 24 deadline per Devin's email. I plan to follow up with weekly updates throughout the coding period using the same blog post template.


📚 Reviewer Resources

Thank you for contributing to the Sugar Labs website! 🎉

Signed-off-by: Parth Dagia <parth.24bcs10414@sst.scaler.com>
@github-actions
Copy link
Copy Markdown

🎉 All Checks Passed!

Status: ✅ Ready to merge

✅ Completed Workflows

Workflow Status Details
🔨 Continuous Integration ✅ Passed Build completed successfully
📝 Code Linting ✅ Passed All formatting and style checks passed

🚀 This PR is ready for review and can be safely merged to main branch!

Great work! Your code meets all quality standards. 👏

@sa-fw-an
Copy link
Copy Markdown
Member

@pikurasa Please have a look at this.


# Community Bonding Period Report by Parth Dagia

**Project:** [Music Blocks 4 Program Builder](https://github.com/sugarlabs/musicblocks-v4)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Add an additional space to force a line break, here and after all lines in this section.

Right now, it renders like this:
Image


## Introduction & About Me

Hi everyone, I'm Parth Dagia, a second-year Computer Science student. I'll be working on the **Music Blocks 4 Program Builder** at Sugar Labs this summer as a Google Summer of Code 2026 contributor.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Instead of making "Music Blocks 4 Program Builder" bold, I think you should link to something, like its GH repo

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

or you could link to one of its initial announcements, like https://musicblocks.net/2022/02/12/public-release-of-music-blocks-v4-0-for-testing/, since you link to the GH repo at the end.


## About the Project

Music Blocks v4 is a redesign of v3 in TypeScript, React, and Vite. A lot of the pieces already exist: an editor, a p5.js painter, a Tone.js singer, a compiler, and an interpreter. There is also the Masonry brick editor, built over GSoC 2024 and 2025, with hundreds of bricks and drag-and-drop support.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This paragraph could also use some external links.


---

## Plan for Weeks 1 & 2 (May 25 – Jun 7)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it's fine to write the plan for the first two weeks, but to be clear these blogposts are expected weekly.

@parthdagia05 parthdagia05 changed the title GSoC-2026 community bonding blog GSoC-2026 community bonding blog by Parth Dagia May 26, 2026
Signed-off-by: Parth Dagia <parth.24bcs10414@sst.scaler.com>
@github-actions
Copy link
Copy Markdown

🎉 All Checks Passed!

Status: ✅ Ready to merge

✅ Completed Workflows

Workflow Status Details
🔨 Continuous Integration ✅ Passed Build completed successfully
📝 Code Linting ✅ Passed All formatting and style checks passed

🚀 This PR is ready for review and can be safely merged to main branch!

Great work! Your code meets all quality standards. 👏

@parthdagia05
Copy link
Copy Markdown
Author

@pikurasa done with the changes ,can you take a look again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants