A summary of my contributions to the Githru project during the OSCCA master phase, including UI improvements, issues, and Pull Requests.
The password you enter is used to open, edit, and delete secret comments.
No comments yet.
링크 정보를 불러오는 중...
Master activity period (9 weeks)
Aug 10, 2024 – Nov 2, 2024
In the Design system renewal team, we proposed tasks to work on and distributed responsibilities among ourselves. We revisited earlier ideas I had suggested—such as the color picker, back button UX, and UI framework—and discussed which direction would work best for the project.
When I thought about these problems alone, it was difficult to find the best solution. However, discussing them with teammates who were interested in the same topics made it much easier to decide on a clear direction.
Around that time I was also feeling stressed in another team project because it sometimes felt like I was the only one pushing the work forward. In contrast, everyone in the renewal team actively participated, which gave me a lot of motivation and energy.
Just like during the challenge phase, I raised several issues and solved some of them through Pull Requests.
Unfortunately, the first major issue I proposed had already been solved by another contributor. Most of the issues I raised focused less on deep architectural changes and more on small UI improvements or bug fixes.
Since my background is in UI/UX, it felt natural to focus on those areas. At first I wondered whether I should have attempted more technical contributions, but I eventually decided to think positively: these were areas that might not have been improved easily without someone focusing on UI details.
One issue I wrote while introducing MUI might still be helpful for future contributors, so I’ll leave the link here.
링크 정보를 불러오는 중...
Previously I had mainly focused on building UI components from scratch rather than using frameworks, so this was a good opportunity to learn technologies I hadn’t explored before.
Based on the issues I raised, I continued contributing through Pull Requests. While I did modify some code directly, most of my work involved refactoring existing code and removing unnecessary files.
One of the biggest tasks for our team was the color picker feature. Due to time constraints I only worked on the design and color selection, and another teammate implemented the actual functionality.
I had really wanted to implement it myself, so I was a bit disappointed. Still, once it was implemented I was able to tweak some parts of the code that didn’t quite match what I had imagined.
Doesn’t it look nice?
The global theme persistence issue had been something I previously raised as an issue. Because the plugin interacts with the VSCode backend, another teammate later fixed it.
I don’t think I fully understand that part yet, so I made a note to revisit it later.
링크 정보를 불러오는 중...
I met the View team members offline about twice for networking.
During those meetings I realized that I probably had the least experience among the group. I wasn’t a computer science major nor a working developer yet, so it motivated me to study harder.
At the same time, the mentor always shared helpful advice whenever we met, which gave me a lot of encouragement.
About a week before the final ceremony we worked on editing the presentation slides and script for the team presentation.
This happened to coincide with the final evaluation period for my graduation exhibition, so I was extremely busy. Even so, I was happy that I could continue contributing whenever I found spare time.
The mentor actually suggested that I take the role of lead mentee, but my schedule was too tight and I worried it might affect the team negatively, so I reluctantly declined. Still, preparing the presentation gave me a chance to reflect on the team’s entire journey.
Also—Google Slides was surprisingly uncomfortable to use. I kept feeling the urge to move everything into Figma.
I arrived slightly late to the ceremony and missed the moment on stage, but I still took photos and joined the final networking session.
Seeing how hard each teammate was working in their own environment made me realize that I should finish my graduation project quickly and return to focusing on development.
Applause to our team who worked together for about 13 weeks.
 |  |
|---|
Open source used to feel like something only extremely skilled developers could do, but it turned out to be much closer and more approachable than I expected.
I still don’t fully understand every part of the project structure, and balancing this program with my graduation project meant I couldn’t contribute as much as I would have liked.
Even so, the experience itself was very meaningful.
Like many others who participated in OSCCA 2024, I hope this experience helps me continue enjoying and exploring development.
