Hi Kayla,
welcome!
I have checked your two patches and I’m afraid they don’t count.
The „two patches rule" is in place for applicants to demonstrate their ability to work with the C/C++ code, preferably (but not required) in the area of the chosen project. Your first patch removes a dependency from build scripts, the second one changes some labels in SVG files. Both are valuable contributions and appreciated, but they do not demonstrate your abilities to work with C/C++.
In order for you to be eligible to apply to GSoC you need to create two meaningful (read: non-trivial) contributions to the C/C++ code. I’m sorry if that wasn’t clear before.
All the best,
René
Am 01.04.2024 um 10:01 schrieb Witchi Kitti Kat witchikittikat@gmail.com:
Hello everyone,
My name is Kayla, I go by kpowkitty online. I have tried to reach out a couple of times on IRC about feedback on my proposal; I missed this emailing list. My apologies! I hope that does not take away from my standing with Inkscape.
I have already made two patches: Patch 1, Patch 2.
I have also created a drawing with Inkscape.
I have submitted my proposal to GSoC. Feedback would be much appreciated. I am proposing a refactor and renewal of Inkscape. Here is my project summary:
Inkscape has been pieced together since 2003; a rocky C to C++ transition, the implementation of GTK (now GTK4!), and much more. Inkscape is sitting on a somewhat unstable foundation. To improve this foundation, the remaining C code will be transitioned to C++, redundant code and rough implementations will be reversed and renewed, and there will be documentation added. By implementing these things, Inkscape will have a better foundation for development, making it easier to expand upon. It will also bring better memory management and efficiency. Most importantly, the documentation will make it easier for new developers to approach Inkscape. All of these factors combined will not only help old developers, by providing them with a stronger foundation and reliable documentation, but it will also make Inkscape approachable to new developers, through shorter, clearer code and better instructions. Deliverables are: Refactored ui/tools/tool-base.cpp. SPDrawAnchor removed → SPKnot implemented. src/line-geometry.h/.cpp officially in lib2geom. Divided display directory. Inkscape’s handling of URIs and file names sorted. Inkscape::URIReference and derived classes simplified. Optional: Decide when and where to use Inkscape::URI / Inkscape::IO::UriInputStream and clean them up. Optional: Unified error/status message output. Reorganized file tree. Clear, concise directory names and file names. Doxygen commenting. One-line file descriptors. READMEs for all directories.
Please let me know if there are any changes I need to make. Thank you for taking the time to look at my proposal, and I look forward to hearing from you all!
Sincerely,
Kayla Powell witchikittikat@gmail.com _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org