From: Kritika Rag <kritikarag.kr@gmail.com>
To: gcc@gcc.gnu.org
Subject: GSOC 2023 Contribution Request
Date: Wed, 22 Feb 2023 17:18:51 +0530 [thread overview]
Message-ID: <CACRj7T3OOumhOB5PtG3A3fpEmsEptQ3JyLDYz0A_m3YeyYQHwA@mail.gmail.com> (raw)
Hello Everyone!
I’m Kritika Rag, a Computer Science pre-final year undergraduate
student from India. I’m quite passionate about web development and
competitive programming and now I’m looking forward to contributing to
open-source projects. I believe that GSOC 2023 would provide me with
the best way to start my open-source contribution journey. Since I’m a
competitive programmer, I have excellent command over Data Structures
& Algorithms and my primary language is C++, so C++ and GCC are
something that I use daily, therefore I would love to make my
contributions to GCC projects. I sincerely hope that this community
will provide me with the opportunity to do so and to work alongside
them.
I’m proficient in various coding languages like C/C++, HTML, CSS,
JavaScript, React, and Python, and have experimented with Git, Linux,
APIs, etc. I have also been fortunate enough to secure 3 internships,
2 as a DSA problem setter and 1 as a research intern. I have also
participated in a few open-source programs like Hack October Fest 2022
and GWoC 2022 and contributed to web development and data science
projects.
I had been checking up on recent project proposals listed in GCC wiki
for the past 3 weeks and was interested in working either on the
project which aims to improve the utility routine library used by GCC
or related to Bug Patrol especially analyzing failing test cases (this
was present over the site a while ago but now I can't see it anywhere)
so I just wanted to ask can I choose it as my GSoC 2023 project? If
yes can anyone guide me to whom to connect to discuss it?
And if I can't work on the above ideas then I have also gone through
the selected project ideas and want to work on the project "Implement
comp built-in traits for the standard library traits" so would be
grateful if anyone could guide me here also.
Thank you so much and I hope to hear from you soon.
next reply other threads:[~2023-02-22 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 11:48 Kritika Rag [this message]
2023-02-28 20:12 ` Patrick Palka
-- strict thread matches above, loose matches on Subject: below --
2023-02-13 13:34 Kritika Rag
2023-02-19 5:48 ` Kritika Rag
2023-02-19 8:43 ` Ankur Saini
2023-02-22 16:16 ` Martin Jambor
2023-02-22 16:34 ` Kritika Rag
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=CACRj7T3OOumhOB5PtG3A3fpEmsEptQ3JyLDYz0A_m3YeyYQHwA@mail.gmail.com \
--to=kritikarag.kr@gmail.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).