MobileRead Forums - View Single Post - Looking to get started helping out with Calibre dev

Jeremy_D · 01-16-2020, 05:38 PM

Hi all,

TL; DR: I'm looking for suggestions on where my efforts could best be directed to help out, particularly with the py3 port. Also looking for further resources to assist me to get up to speed ASAP.

I've searched the forums here and also had a brief look at existing dev page. I found a few forum threads/posts that seemed relevant and suggest working on py3 bug testing and plugin dev/p3-porting, but ideally I'd like some more specific pointers on where is best to get started. Also clarity on where I'd find any outstanding py3 related bugs (searching the LaunchPad bug-tracker for "python3" and "py3" came up blank...).

My current skills, strengths and limitations/shortcomings

Somewhat novice python programmer; mostly experienced with python3; including porting (CLI/headless) py2 -> py3 scripts/apps.
No experience with GUI app dev; extremely limited experience with webUI dev.
Debian "daily driver", particularly experienced with headless/CLI admin.
Experienced with git & GitHub.
Aversion to LaunchPad (I know it's what Calibre uses for bug-tracking and I promise I won't whinge - too much... )
Keen to learn more/better python.
Committed to open source.
Only have access to very limited eReader hardware (i.e. don't imagine I'll be able help much with debugging hardware related issues).

Elaboration/context

Ultimately, I have some wishlist items I'd love to see implemented in the future, but I understand that there is lots of other stuff that is much higher priority (and likely required), particularly getting the py3 port completed and 100% reliable.

Also, before I could even begin to think about my personal desires, I need to get up to speed with the Calibre codebase, hone my python skills a bit and get a better understanding of the coding requirements/desires of the existing devs. So starting small seems like the way to go. Judging from other posts I've read, bug-hunting py3 builds and/or porting plugins to py3 are probably the best place to start?! Is that correct and if so, are there good places to find what specifically is best to work on? E.g. plugins that still need porting, py3 related bugs, etc.

Also is there a place (i.e. somewhere a bit more targeted that these forums) where developers coordinate on what everybody is working on? Ideally I don't want to tread on any body else's toes and would like to maximise the value of my contribution (so don't want to double up on stuff that is already in progress).

FYI - My longer term wishlist

My wishlist items are related to the server side of things. Ultimately, I'd like to see support for multiple GUI clients connecting to a single minimalist headless server backend. As noted above, headless Debian/Linux servers is my thing!

(optional) MySQL (&/or similar) DB backend support.
ability to run a simplified standalone headless server (without all the GUI deps) - ideally with webUI.

I understand that these things have been requested multiple times all over the internet and are unrealistic in the short term, but ultimately, that's what I'd love to see (and assist push forward as/when the time is right).

Thanks for reading (if you got this far...

)

01-16-2020, 05:38 PM	#1
Jeremy_D Junior Member Posts: 5 Karma: 10 Join Date: Jan 2020 Location: Australia Device: kindle (very old)	Looking to get started helping out with Calibre dev Hi all, TL; DR: I'm looking for suggestions on where my efforts could best be directed to help out, particularly with the py3 port. Also looking for further resources to assist me to get up to speed ASAP. I've searched the forums here and also had a brief look at existing dev page. I found a few forum threads/posts that seemed relevant and suggest working on py3 bug testing and plugin dev/p3-porting, but ideally I'd like some more specific pointers on where is best to get started. Also clarity on where I'd find any outstanding py3 related bugs (searching the LaunchPad bug-tracker for "python3" and "py3" came up blank...). My current skills, strengths and limitations/shortcomings Somewhat novice python programmer; mostly experienced with python3; including porting (CLI/headless) py2 -> py3 scripts/apps. No experience with GUI app dev; extremely limited experience with webUI dev. Debian "daily driver", particularly experienced with headless/CLI admin. Experienced with git & GitHub. Aversion to LaunchPad (I know it's what Calibre uses for bug-tracking and I promise I won't whinge - too much... ) Keen to learn more/better python. Committed to open source. Only have access to very limited eReader hardware (i.e. don't imagine I'll be able help much with debugging hardware related issues). Elaboration/context Ultimately, I have some wishlist items I'd love to see implemented in the future, but I understand that there is lots of other stuff that is much higher priority (and likely required), particularly getting the py3 port completed and 100% reliable. Also, before I could even begin to think about my personal desires, I need to get up to speed with the Calibre codebase, hone my python skills a bit and get a better understanding of the coding requirements/desires of the existing devs. So starting small seems like the way to go. Judging from other posts I've read, bug-hunting py3 builds and/or porting plugins to py3 are probably the best place to start?! Is that correct and if so, are there good places to find what specifically is best to work on? E.g. plugins that still need porting, py3 related bugs, etc. Also is there a place (i.e. somewhere a bit more targeted that these forums) where developers coordinate on what everybody is working on? Ideally I don't want to tread on any body else's toes and would like to maximise the value of my contribution (so don't want to double up on stuff that is already in progress). FYI - My longer term wishlist My wishlist items are related to the server side of things. Ultimately, I'd like to see support for multiple GUI clients connecting to a single minimalist headless server backend. As noted above, headless Debian/Linux servers is my thing! (optional) MySQL (&/or similar) DB backend support. ability to run a simplified standalone headless server (without all the GUI deps) - ideally with webUI. I understand that these things have been requested multiple times all over the internet and are unrealistic in the short term, but ultimately, that's what I'd love to see (and assist push forward as/when the time is right). Thanks for reading (if you got this far... )