Olà!
I'm not sure whether I'll have enough time or energy to do continued
guidance/mentoring. But we can try. :)
Thank you :)
Once you think you've good these covered, you could check:
<https://wiki.debian.org/Teams/Dpkg/Contribute>
Personally I find that scratching your own itch works best, but if you
are not maintaining packages, that might be difficult to come by.
Yes, I understand. I think that it will come naturally, in time
Perhaps a good way to get started with the code base could be to
improve the coverage by adding/extending unit tests?
<https://www.dpkg.org/coverage/scripts/coverage.html>
Yes, I'm a fan of unit testing and code coverage.
I also use Devel::Cover in my projects.
I find that writing tests is an excellent way to dive into a new project.
I did that many times. That would be the place to start, great.
Otherwise perhaps a good initial task might be the Dpkg::Checksums
one from?
<https://wiki.debian.org/Teams/Dpkg/Task/PerlAPICleanup>
I'll have a look into it, during my unit testing, and understand the issue
In general, I find that email requires more energy, as it feels more
formal and final, so perhaps you might want to join the #debian-dpkg
IRC channel on OFTC if you are into that.
I have never used IRC before but I will give it a try, during next week
Thanks,
Guillem
Thanks
Joao