Google Summer of Code 2024 Reports: Test root device and root file system selection
#NetBSD #gsoc2024
#gsoc2024
New post at the #Typelevel Blog: https://typelevel.org/blog/2024/12/22/gsoc24-going-feral-on-the-cloud.html
This describes Ching Hian’s Google Summer of Code project, to take the Feral library and extend it to additional serverless cloud providers, so that applications can be more flexible, and less tied to specific clouds.
It's a great enhancement, and shows the way towards future work. Check it out!
Ziming Yuan tells how a Beginner Built an RSS Feed Provider in Volto at #ploneconf2024 #pythoncerrado2024 #GSoC2024 https://maurits.vanrees.org/weblog/archive/2024/11/ziming-yuan-how-a-beginner-built-an-rss-feed-provider-in-volto
🎉 GSoC 2024 is a wrap! Four successful projects, and we’re continuing our showcase series. Today: wh201906’s native mobile encryption upgrade with faster speeds and a secure 256-bit key! 🔐📱 #GSoC2024 #OpenSource
In our series of GSoC 2024 projects, today we look at Alice's work on the Joplin update manager! Full post on the forum! https://discourse.joplinapp.org/t/gsoc-2024-seamless-updates-for-joplin-desktop-application/41494/1 #gsoc2024 #gsoc
Google Summer of Code 2024 Reports: ALTQ refactoring and NPF integration
#NetBSD #gsoc2024
https://blog.netbsd.org/tnf/entry/google_summer_of_code_2024
I had a good conversation with @karen this weekend at the Google Summer of Code Mentor Summit.
Thank you again, Karen, for all you do!
#SoftwareFreedom #GSoC2024 #FreeSoftware #FOSS #FLOSS #OpenSource
Today, Sameer Verma and I met at a mall near San Francisco State University (SFSU). We talked about OLPC and Sugar. We also talked about Jazz, Country, and Hindustani music while listening to The Headhunters.
Any open source folks in the bay area want to meet up?
I'm in San Jose / Mountain View today and tomorrow for the #gsoc2024 #GSoC dinner. I'm going to miss the mentor summit, but @karen will be there.
Thursday: I'll be hanging out in the Tetra Hotel lobby or bar area, from 3 pm to 5:30 pm today. Then I'm off to the GSoC celebration dinner.
On Thursday, I'll be wearing a gray @conservancy t-shirt and might be doing some needle work.
Friday morning, I'll also be hanging out in the hotel breakfast area or lobby.
Friday afternoon, you'll find me in the mentor meetup room for a few hours before my flight.
On Friday, look for the person in a purple flowered shirt and burgundy shorts.
Krita's 2024 Google Summer of Code project has been a success! Ken Lo has been working on pixel perfect ellipses, and his code has already been merged and will be in Krita 5.3, this year!
#gsoc2024 news, really a biggie:
https://mixxx.org/news/2024-08-26-stem-mixing/
Mixxx is implementing stem support in Version 2.6.
Tomorrow, August 30, we will be hosting the final of our series of work by summer interns. The focus tomorrow will be showcasing the work done by DMP students of Code for GovTech (C4GT). They worked on Music Blocks, Math Games, and Raspberry Pi projects. Watch the live stream and learn more about their accomplishments this summer: https://youtube.com/live/0yMqz3GW3rY
#Code4GovTech #RaspberryPi #Math #Maths #MusicBlocks #GoogleSummerofCode #GSoC2024 #Development
Hitesh Kumar Saini details his accomplishments during his Google Summer of Code 2024 project. He enhanced the enviroCar Android application by adding support for multiple map providers. This new extensible and independent map module enables the selection of a preferred map provider and style, both during compile-time and run-time of the application. Check out his blog post: https://blog.52north.org/2024/08/26/envirocar-mapbox-to-maplibre-migration-gsoc-final-blog-post/
#GSoC2024 #envirocar #Android #java
Haiku OS [GSoC 2024] Hardware Virtualization: Final Report
https://www.haiku-os.org/blog/dalme/2024-08-19_gsoc_2024_hardware_virtualization_final_report/
#ycombinator #gsoc #gsoc2024 #qemu #nvmm
[What did I do?]
-> Enhanced the chat functionality by adding new features.
-> Previously, service messages in the chat were sent whenever a collaborator made changes to the flight path in an operation, cluttering the chat and reducing readability. I resolved this by creating a separate channel exclusively for service messages.
-> The collaborator list in the chat used to display only names and roles. I improved this by integrating the custom profile images feature I previously implemented, so now members are shown with their profile pictures.
-> Additionally, I updated the collaborator list to indicate active members with a green dot. I leveraged my earlier work on tracking active users within an operation to achieve this.
[Where did I get stuck?]
-> The service message currently only displays "{username} saved changes," but it needs to be more specific, such as "{username} updated a waypoint," "inserted a new waypoint," "deleted a waypoint," etc. I struggled with understanding the relevant code to make this change. My mentor guided me on which file to modify and provided an idea of how to implement it. I still have more work to do on this, which I plan to tackle this week.
[What's planned for the upcoming week?]
-> Get this PR merged and proceed with testing all these changes.
[What did I do?]
-> Resolved a couple of more comments on the PR about the inconsistent size of the label.
-> Solved a bug while manually testing this feature, in which if the user permissions were revoked in the operation which was not selected by the other user, the counter would still decrement.
-> The PR was approved and merged after resolving some merge conflicts.
-> Updated my GSOC branch with develop branch by merging develop into GSOC branch, and then uploading a PR for the same (which was merged).
[Where did I get stuck?]
-> I did not have any clue on how the next feature would be implemented. My mentors helped me out regarding this by telling me exactly what they want.
[What's planned for the upcoming week?]
-> The next feature - a separate channel
for service messages in the chat - is the only feature left to implement now. I am positive and hopeful that I would be able to complete it before the Final Evaluations and thereby completing 100% of my project.
Link to the merged PR : https://github.com/Open-MSS/MSS/pull/2437
[What did I do?]
-> Wrote the tests for the newly implemented feature - visualize active users in an operation.
-> I was also able to fix the bug that when a user was removed from an operation, it did not update the active users label (thanks to my mentor who sorted out the multiple socket_manager instances problem which I wrote about last week).
[Where did I get stuck?]
-> Different socket_manager instances were also leading to inconsistency in tests, so my mentor fixed the issue with a couple of PRs. I was told to integrate those changes and the tests are working as expected now.
-> Got stuck at UI testing on how to open and operate multiple windows at once. I have still not figured out that part yet.
[What's planned for the upcoming week?]
-> The PR is under review, I aim to resolve all the comment, and get this PR merged.
[What did I do?]
-> Wrote the tests for profile image upload feature and created its pull request. There was some confusion initially about how to write tests and/or how testing is done in general since I had little to no experience with it. But my mentors guided me through it.
-> Worked in parallel on the new feature i.e. to create a UI element for displaying the number of active users in a selected mscolab operation, and created a pull request for it too. The implementation is nearly complete, it just needs some refinement.
[Where did I get stuck?]
-> Got stuck for a couple of days, on a bug i.e. whenever a user is removed from an active operation, the active users label was not updated. After discussing it with my mentors, it came out that there were some architectural problem where the same instance is not being used for socketManager at the server and the socket manager. It has been put on a #ToDo for now.
[What's planned for the upcoming week?]
-> Hopefully get done with this feature, get this PR merged, and write complete tests for it.
There's a new post on our blog:
GSoC 2024: New release for Project Libremesh Pirania – Part II
https://blog.freifunk.net/2024/07/12/gsoc-2024-new-release-for-project-libremesh-pirania-part-ii/
[What did I do this week?]
-> Realised that I did not write the code for deleting the old user profile images. So now when a user uploaded a new image, the old one gets deleted. This saves memory and prevent DOS attacks. Also, updated the function responsible for deletion of the account to also delete the user's profile image.
-> Made my code a bit more modular, this also reduces the repeated code lines.
-> Resolved bugs and errors which were occurring during manual testing.
-> And after a lot of comments resolution (I mean a lot) and a lot of commits, my Pull Request was finally approved and got merged. Now anyone can try out this new feature as it was also merged in the develop branch.
[Where did I get stuck?]
-> Got stuck a bit here and there but my mentors helped me through it. My mentor even helped me over the weekend which I highly appreciate and am grateful for.
[What's planned for the upcoming week?]
-> Create a Pull Request of tests for this feature, get it reviewed, get it merged and start writing code for the next feature : visualise the concurrent active users of the selected operation.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst