News: GSoC 2025 - Work ongoing: Make links in quoted text work

Author: tillkamppeter

_posts/2025-08-21-OpenPrinting News - Google Summer of Code 2025 - The amazing work is going on.md

@@ -36,7 +36,7 @@ He writes:
 > - Applied Gaurav's CPDB patch to Qt 6.8
 > - All testing passed (printer enumeration, IPP communication)
 > - IPP emulator verified: "Get-Printer-Attributes successful-ok"
-> - PR created: https://github.com/qt/qtbase/pull/122
+> - PR created: [https://github.com/qt/qtbase/pull/122](https://github.com/qt/qtbase/pull/122)
 >
 > 🔧 CURRENT STATUS:
 > - CLA signed ✅
@@ -49,7 +49,7 @@ He writes:
 > - Print job submission: ✅ Success
 > - cpdb-text-frontend consistency: ✅ Confirmed
 >
-> 🔗 VIEW PR: https://github.com/qt/qtbase/pull/122
+> 🔗 VIEW PR: [https://github.com/qt/qtbase/pull/122](https://github.com/qt/qtbase/pull/122)
 > 
 > Next: Resolve conflicts → Qt maintainer review → Begin modernization phase
 
@@ -181,9 +181,9 @@ Mentors: **Jiongchi Yu**, **George-Andrei Iosif**, Dongge Liu, Till Kamppeter, S
 >
 > The biggest flaw is that when a YAML defines multiple functions, OSS-Fuzz-Gen creates a separate fuzzer for each function. This makes it hard to capture the relationships of functions called —— which limits coverage. Besides, OSS-Fuzz-Gen is highly encapsulated and heavy. Even minor issues like network instability can cause the entire pipeline to fail. It also generates many redundant Docker images. 
 >
-> To address these issues, I developed light-fuzz-gen (https://github.com/pushinl/light-fuzz-gen), with the aim of eventually integrating it back into OSS-Fuzz-Gen. (Since the workflow of OSS-Fuzz-Gen is overly complex at the moment, light-fuzz-gen is being used separately for now.)
+> To address these issues, I developed light-fuzz-gen ([https://github.com/pushinl/light-fuzz-gen](https://github.com/pushinl/light-fuzz-gen)), with the aim of eventually integrating it back into OSS-Fuzz-Gen. (Since the workflow of OSS-Fuzz-Gen is overly complex at the moment, light-fuzz-gen is being used separately for now.)
 >
-> In addition, I experimented with combining OSS-Fuzz-Gen, light-fuzz-gen, and AI-assisted IDE tools. This approach allowed me to generate a large number of harnesses and seeds, which significantly improved the code coverage of the OpenPrinting project. So far, I have generated a large number of fuzzers and actually added 6 effective. In particular, coverage for cups increased from 11% to 30%, and coverage for libcups improved from 14% to 17%. (https://introspector.oss-fuzz.com/project-profile?project=cups)
+> In addition, I experimented with combining OSS-Fuzz-Gen, light-fuzz-gen, and AI-assisted IDE tools. This approach allowed me to generate a large number of harnesses and seeds, which significantly improved the code coverage of the OpenPrinting project. So far, I have generated a large number of fuzzers and actually added 6 effective. In particular, coverage for cups increased from 11% to 30%, and coverage for libcups improved from 14% to 17%. ([https://introspector.oss-fuzz.com/project-profile?project=cups](https://introspector.oss-fuzz.com/project-profile?project=cups))
 >
 > The biggest challenge remains ensuring that fuzzers generated by LLMs can pass compilation and linking successfully. At present, I am encountering difficulties with the Makefile build process of cups-filters, and I am actively working on resolving this issue.
 
@@ -220,8 +220,8 @@ Mentors:  **Jiongchi Yu**, **George-Andrei Iosif**, Dongge Liu, Till Kamppeter,
 > This new setup now runs without the earlier importability or linking issues and keeps the fuzzing pipeline entirely black-box while still targeting key functionality in ipp-usb. I have created a PR to OSS-Fuzz for this integration.
 >
 > Links:<BR>
-> OSS-Fuzz PR: https://github.com/google/oss-fuzz/pull/13815<BR>
-> IPP-over-USB emulation: https://github.com/OpenPrinting/go-mfp/tree/master/proto/usbip
+> OSS-Fuzz PR: [https://github.com/google/oss-fuzz/pull/13815](https://github.com/google/oss-fuzz/pull/13815)<BR>
+> IPP-over-USB emulation: [https://github.com/OpenPrinting/go-mfp/tree/master/proto/usbip](https://github.com/OpenPrinting/go-mfp/tree/master/proto/usbip)
 
 Mohammed's work is going as pull requests into [OpenPrinting's "fuzzing" repository](https://github.com/OpenPrinting/fuzzing). Here are the [pull requests which are already merged](https://github.com/OpenPrinting/fuzzing/pulls?q=is%3Apr+is%3Aclosed). Mohammed's user name on GitHub is "mdimado".