Skip to content

GSoC '26 Community Bonding Blog by Shreya Saxena#846

Open
ssz2605 wants to merge 2 commits into
sugarlabs:mainfrom
ssz2605:gsoc-26-shreya-saxena-community-bonding
Open

GSoC '26 Community Bonding Blog by Shreya Saxena#846
ssz2605 wants to merge 2 commits into
sugarlabs:mainfrom
ssz2605:gsoc-26-shreya-saxena-community-bonding

Conversation

@ssz2605
Copy link
Copy Markdown

@ssz2605 ssz2605 commented May 22, 2026

📝 Description

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

This is my introductory post for GSoC '26, where I'll be working on Music Blocks Performance under mentors Walter Bender and Om Santosh Suneri. 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/shreya-saxena.md — author profile (one-time setup)
  • src/constants/MarkdownFiles/posts/2026-05-23-gsoc-26-shreya-saxena-community-bonding.md — community bonding blog post

cc mentors: @walterbender @omsuneri

🔗 Related Issue

N/A — GSoC '26 community bonding 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 as content-only change, no rendering logic touched.

🖥️ Responsive Design

N/A as 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/shreya-saxena.md".
  3. Filename follows the convention YYYY-MM-DD-gsoc-26-username-*.md.
  4. Markdown lint disable comment (<!-- markdownlint-disable -->) is present.
  5. npm run lint — passed with no errors.
  6. npm run build — built successfully in 11.23s.

♿ Accessibility

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

📋 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 community bonding blog post for GSoC '26. 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! 🎉

@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. 👏

@ssz2605
Copy link
Copy Markdown
Author

ssz2605 commented May 22, 2026

@pikurasa can you please review and let me know any changes?

@ssz2605 ssz2605 force-pushed the gsoc-26-shreya-saxena-community-bonding branch from b187019 to d134d8e Compare May 24, 2026 06:28
@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. 👏

@ssz2605 ssz2605 changed the title GSoC '26 Community Bonding Report by Shreya Saxena GSoC '26 Community Bonding Blog by Shreya Saxena May 24, 2026

## About Me

Hello everyone, I'm Shreya Saxena, a second-year B.Tech student in Smart Manufacturing at IIIT Jabalpur. I'll be working on **Music Blocks Performance** 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.

I recommend making "Music Blocks Performance" a link to something relevant, such as the GSoC ideas page.


Music Blocks v3 is a browser-based visual programming environment used by students and educators worldwide. As projects grow in complexity, with more voices, larger block graphs, and MIDI imports, users hit a wall: the interface freezes with no indication of whether it's working, stuck, or crashed. Students in time-limited classroom sessions often end up force-refreshing the browser and losing their work.

The core problem is that long-running operations like LilyPond export, MIDI import, and complex block graph execution all run synchronously on the main thread with no yielding, no progress feedback, and no way to cancel. On top of that, there's no systematic measurement of where things degrade, so optimization efforts have historically been reactive rather than evidence-based.
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.

A lot of people reading this won't know what Lilypond is. I recommend linking to it. Maybe link to a good description of MIDI as well.

## Community Bonding Activities
The community bonding period has focused on connecting with the Music Blocks community, discussing project direction and expectations with mentors, collaborating with contributors, and helping newcomers get familiar with the codebase and contribution workflow. Alongside this, I’ve been building the instrumentation and profiling foundation required for the project.

A major focus has been `crabcanon-plot.html`, which Walter suggested as an initial benchmark due to noticeable performance regressions over time. The project plays a melody forwards and backwards simultaneously across parallel voices, with rendering and execution tightly coupled on the main thread.
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 would be good to also link to crabcanon, either the MB link from the planet, or to its place in the repo via GH in examples folder.

To analyze this, I built a Phase 1 instrumentation layer (`performanceTracker.js`) with operation-scoped timing hooks, along with a Playwright headless benchmark setup that exports JSON baseline results.

<a href="https://postimg.cc/w3VhyhQd">
<img src="https://i.postimg.cc/65szPc7T/Crabcanon-plot-research.jpg" alt="Crabcanon Performance Profiling Baseline Results" border="0">
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 offloading the image to another site, I recommend downloading it to the assets folder and calling it from there.

@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. 👏

@ssz2605
Copy link
Copy Markdown
Author

ssz2605 commented May 26, 2026

@pikurasa I addressed all review comments. Please take a look!

@ssz2605 ssz2605 force-pushed the gsoc-26-shreya-saxena-community-bonding branch from 4cda643 to 9f7c89c Compare May 26, 2026 05:19
@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. 👏

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.

2 participants