{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigqkuy5numcodepgmx63dlrvswqvz3c7dvyrmw4lfdmzxrp6cgj7i",
    "uri": "at://did:plc:46ti67tc37qcmwp2vaynk6fq/app.bsky.feed.post/3mg4dzvi47ke2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreifqaymphlhaou7ymuxlsdcq46k6c4k27dbs2lrqq2rxp5ioaxmdoy"
    },
    "mimeType": "image/jpeg",
    "size": 8554
  },
  "path": "/2026/03/02/wrapping-up-my-outreachy-internship-at-debian/",
  "publishedAt": "2026-03-02T22:56:36.063Z",
  "site": "https://isokenibizugbe.wordpress.com",
  "textContent": "##\n\nTwelve weeks ago, I stepped into the Debian ecosystem as an Outreachy intern with a curiosity for Quality Assurance. It feels like just yesterday, and time has flown by so fast! Now, I am wrapping up that journey, not just with a completed project, but with improved technical reasoning.\n\nI have learned how to use documentation to understand a complex project, how to be a good collaborator, and that learning is a continuous process. These experiences have helped me grow much more confident in my skills as an engineer.\n\n### **My Achievements**\n\nAs I close this chapter, I am leaving a permanent “Proof-of-Work” in the Debian repositories:\n\n  * **Full Test Coverage:** I automated apps_startstop tests for Cinnamon, LXQt, and XFCE, covering both Live images and Netinst installations.\n  * **Synergy:** I used symbolic links and a single Perl script to handle common application tests across different desktops, which reduces code redundancy.\n  * **The Contributor Style Guide:** I created a guide for future contributors to make documentation clearer and reviews faster, helping to reduce the burden on reviewers.\n\n\n\n### **Final Month: Wrap Up**\n\nIn this final month, things became easier as my understanding of the project grew. I focused on stability and finishing my remaining tasks:\n\n  * I spent time exploring different QEMU video options like VGA, qxl, and virtio on KDE desktop environment . This was important to ensure screen rendering remained stable so that our “needles” (visual test markers) wouldn’t fail because of minor glitches.\n  * I successfully moved from familiarizing to test automation for the XFCE desktop. This included writing “prepare” steps and creating the visual needles needed to make the tests reliable.\n  * One of my final challenges was the app launcher function. Originally, my code used else if blocks for each desktop. I proposed a unified solution, but hit a blocker: XFCE has two ways to launch apps (App Finder and the Application Menu). Because using different methods sometimes caused failures, I chose to use the application menu button across the board.\n\n\n\n### **What’s Next?**\n\nI don’t want my journey with Debian to end here. I plan to stay involved in the community and extend these same tests to the **LXDE** desktop to complete the coverage for all major Debian desktop environments. I am excited to keep exploring and learning more about the Debian ecosystem.\n\n### **Thank You**\n\nThis journey wouldn’t have been possible without the steady guidance of my mentors: **Tassia Camoes Araujo, Roland Clobus, and Philip Hands.** Thank you for teaching me that in the world of Free and Open Source Software (FOSS), your voice and your code are equally important.\n\nTo my fellow intern **Hellen** and the entire Outreachy community, thank you for the shared learning and support. It has been an incredible 12 weeks.",
  "title": "Isoken Ibizugbe: Wrapping Up My Outreachy Internship at Debian",
  "updatedAt": "2026-03-02T20:51:19.000Z"
}