El 11/5/25 a las 13:08, Rinku Hasija escribió:
My name is Rinku Hasija, and I’m writing to express my interest in joining the
Debian QA team as a contributor. I have a background in backend development and
have been actively learning and contributing to open-source projects. I'm
particularly passionate about software quality, reliability, and the
open-source philosophy that Debian embodies.
I’ve worked with tools and technologies such as JavaScript, Node.js,
TypeScript, Python, SQL, Git, and CI/CD workflows, and I’m currently deepening
my skills in testing and automation. I’m eager to contribute to Debian’s
quality assurance efforts—whether it’s through bug triaging, writing test
scripts, or improving package stability.
Please let me know how I can get started or if there are any current areas
where contributions are most needed. I’d be grateful for any guidance,
onboarding materials, or opportunities to collaborate with experienced
contributors.
Hello. There is not a QA Team as such (at least not from the Constitution
point of view as a delegated body), but there are plenty of places
where you can contribute.
Since we are aiming at releasing trixie "soon" this year, I suggest you
take a look at the list of RC issues and see if you can provide
fixes for any of them, particularly those who have not been diagnosed yet.
For the packages hosted in salsa (probably most of them) you can also create
an account in salsa and test your fixes before submitting them, either in the
BTS
or as a Merge Request.
If you have plenty of time, you can also try subscribing to
debian-bugs...@lists.debian.org and see the RC bugs being filed in real time.
Thanks.
