Repository navigation
Looking for maintainers for python-docx-template #631
Description
Activity
Hi @elapouya
Myself and my team would be interested in helping to maintain this project. We have been using
python-docxandpython-docx-templatefor a number of years and we have produced over 130,000 documents with these two packages, and have a long term plan to continue the use of both.I submitted a PR for the
python-docx-templateproject recently to improve the performance when working with very large documents. Please see #630I have sent you a LinkedIn request to connect, feel free to message me there to discuss in more detail.
Looking forward to hearing from you.
Reacted by Robin Bennett, František Gič, James Sinton, Alexander Goryushkin, Felipe Raimann and Alessandro RanellucciReacted by Ana Paula GomesI can step in this weekend. We use the library at work pretty extensively so I will bring it up at standup in the AM. I'll be in touch.
I too connected with you on LinkedIn, and I have a fellow co-worker that is willing to put some time in as a maintainer a well. I'll be looking at PR's this weekend.
@subtubes-io I need a contribution from you before I can elect you as maintainer : a PR would be nice.
@JackByrne I just sent you an invitationReacted by James SintonHi maintainers — I'm Kushal (@KushalLukhi). I'd like to volunteer as a maintainer/contributor for this project.
I can help with:
- issue triage and reproduction
- reviewing/fixing open bugs
- dependency/security updates
- release/support chores
Happy to start with PR-based contributions and earn trust progressively. If you're open, please share the preferred onboarding path and first tasks.
Hi @elapouya, I continued with another focused bug fix in #640 for #516, making the module CLI read JSON input as UTF-8 and adding regression coverage for Unicode data under an ASCII locale.
I am happy to keep working through reproducible bug reports and help with issue triage or PR review if maintainer help is still needed.
Hi Eric,
I'm interested in helping with maintenance. I opened #652 as a small first PR to make the existing test runner more reliable.
I'm still getting familiar with the project, but I'd be happy to help triage issues and review small PRs first.
Reacted by Carl GleisnerHi Eric, I would like to help maintain the project if you are still looking.
I started by reproducing the core-properties corruption in #471 on current
masterand opened #657 with a regression test. I also independently tested and approved the runner fix in #652, found a Python 3.7/3.8 path problem while reviewing #655, and rechecked the stale packaging report in #611 against an exact current-master sdist.I am happy to keep earning trust through issue reproduction, pull request review, and test verification. If there is a particular area of the backlog that needs consistent ownership, please point me at it and I can take responsibility for working through it.
Reacted by Carl GleisnerHi Eric — I'd like to help maintain the project too. My open PR is #655, fixing the Windows-locale UTF-8 crash from #516: two explicit-encoding fixes plus a regression script that reruns the suite under a forced non-UTF-8 locale. JackSpiece reviewed it, found a Python 3.8 path bug in the test harness, and I've pushed the fix with verification on CPython 3.8, 3.9 and 3.12. Beyond PRs, the open-issue backlog looks like it needs triage more than anything — I'd be glad to take a first pass at labelling reproducible bugs vs. usage questions if that helps you.
Reacted by Carl GleisnerHi Eric — I would like to help with a bounded maintenance area if help is still needed.
I have opened #662 with an exact issue fixture and Python 3.9/3.13/package verification. I also independently tested third-party PRs #642, #648, and #661 before submitting changes-request or approval reviews, and reproduced the narrow no-break-space behavior in issue #627 without turning it into an unsupported fix.
A useful starting responsibility for me would be reproducing incoming rendering/CLI/package reports and independently validating small pull requests with exact-head tests. I am happy to keep doing that through normal contributions before any permission change. If another backlog area is more useful, please point me to it.
OpenAI Codex assisted with the reproducibility and test work; I reviewed the public claims and remain responsible for the contribution.
Reacted by Carl GleisnerHi Eric, I'm interested in helping with maintenance. I opened #664 with a focused regression test and verified the fix against the reporter's attached DOCX.
I'd be happy to start by reproducing and triaging open issues, testing pending pull requests, and preparing small, reviewable fixes. I understand that trust and write access should follow demonstrated contributions, so please let me know which part of the backlog would be most useful to focus on next.
Reacted by Carl GleisnerCorrection to my note above: an independent backlog audit found that #656 already covers the same #559 fix more comprehensively. I closed my #664 as a duplicate immediately rather than leave redundant work for maintainers. I'll focus next on testing/reviewing existing PRs and on issues with no overlapping work.
Reacted by Carl GleisnerHi Eric — a brief follow-up to my September 1 note.
Since then I have opened two focused, independently tested fixes: #665 improves the actionable error when the optional subdocument dependency is missing, and #666 fixes inline-image reuse after an image-bearing subdocument merge. Both are deliberately narrow and ready for review.
I would be glad to keep contributing through reproducible bug reports, targeted regression coverage, and small PR validation, and to take on a bounded recurring maintenance area once that is useful. No permission change is expected before the work has earned trust.
Reacted by Carl Gleisner
Hi all, I am the owner of python-docx-template project. I have received a lot of contributions from the community and I am truly grateful for that. However, today I no longer have enough time to maintain it. I am therefore looking for maintainers who can take over the management of this project. This would involve handling issues and pull requests and running the tests to ensure that python-docx-template works properly. I will continue to publish the code to PyPI. Ideally, I am looking for maintainers who have already submitted at least one pull request. If you are interested, please feel free to contact me.