From: Guinevere Larsen <guinevere@redhat.com>
To: 7SRIVISHNU <108srivishnu1008@gmail.com>, gdb-patches@sourceware.org
Subject: Re: Regarding TODO List
Date: Wed, 16 Jul 2025 08:53:05 -0300 [thread overview]
Message-ID: <dfdfa249-6dc8-4c90-bfe8-a89c2ee9e4fa@redhat.com> (raw)
In-Reply-To: <CAFEOrbTuAuvq-yi-5iwEUCSGDOWWDNfPO29N-qg7a+hnk0joWw@mail.gmail.com>
On 7/16/25 2:21 AM, 7SRIVISHNU wrote:
> Dear developers team,
>
> I would like to contribute to this open source community as a fresher
> / less experience, and would like to know about the small
> contributions to be done as initially. I have hands on experience on
> embedded, c, python and c++. Kindly guide us if there is any TODO list.
> Thank you,
Hello!!
I'm always happy to see new contributors :D. For a TODO list, the best
suggestion is to check our bugtracker, and for initial contributions I
recommend checking for the good-first-bug keyword (link for
convenience[1]). We haven't been very good at tagging things with it,
though, so if nothing in that list really looks interesting, feel free
to look through the larger bug list, I usually think that being
interested in what you're solving is much more important than how easy
it is. And, should you have any questions about the bugs or how the code
works but worry about asking it publicly, feel free to reach out to me
privately (through email or IRC - guinevere on libera.chat, mostly
during Brazil work hours).
Happy Hacking :)
[1]
https://sourceware.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&keywords=good-first-bug%2C%20&keywords_type=allwords&list_id=93955&order=Importance&product=gdb&query_format=advanced
--
Cheers,
Guinevere Larsen
She/Her/Hers
>
>
> Regards,
>
> Sri Vishnu A
> +91 9962111636
next prev parent reply other threads:[~2025-07-16 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 5:21 7SRIVISHNU
2025-07-16 11:53 ` Guinevere Larsen [this message]
2025-07-17 16:19 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfdfa249-6dc8-4c90-bfe8-a89c2ee9e4fa@redhat.com \
--to=guinevere@redhat.com \
--cc=108srivishnu1008@gmail.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox