From: Christian Couder <email@example.com> To: Shourya Shukla <firstname.lastname@example.org> Cc: git <email@example.com>, Johannes Schindelin <firstname.lastname@example.org>, Junio C Hamano <email@example.com>, Eric Sunshine <firstname.lastname@example.org> Subject: Re: [GSoC] Introduction Date: Thu, 23 Jan 2020 12:02:32 +0100 Message-ID: <CAP8UFD2Fo=2suQDLwzLM-Wg3ZzXpqHw-x0brPtPV0d4dRsgs9A@mail.gmail.com> (raw) In-Reply-To: <email@example.com> Hi Shourya, On Wed, Jan 22, 2020 at 9:45 PM Shourya Shukla <firstname.lastname@example.org> wrote: > > Greetings everyone! > > I am Shourya Shukla, a Computer Science And Engineering student from IIT Roorkee. > I am very keen on contributing to Git via Google Summer of Code 2020 (GSoC 2020). Nice! > I have worked on a microproject(I saw it here and thought I'd give it a shot) > and submitted a patch regarding the same, which has been accpeted by Junio C Hamano > and will be queued shortly. Nice that you have already done a microproject! It would have been better if you already added [GSoC] to the title of your patches so that we could more easily find them. > I have become familiar with mailing lists as well now so it isn't > an issue. I want to know in which direction should I proceed now. In https://git.github.io/SoC-2019-Microprojects/ you can find the following: "If you’ve already done a microproject and are itching to do more, then get involved in other ways, like finding and fixing other problems in the code, or improving the documentation or code comments, or helping to review other people’s patches on the mailing list, or answering questions on the mailing list or in IRC, or writing new tests, etc., etc. In short, start doing things that other Git developers do! Alternatively you can of course focus on your project proposal." So I would suggest you follow the above advice. As we haven't proposed projects yet, you can perhaps look for a project that you would be interested in. As we say in https://git.github.io/SoC-2019-Ideas/ the ideas we will propose will be just … ideas, and the list we will propose will not be exhaustive, and also we are more than happy to receive proposals for other ideas related to Git. Be sure to read the "Note about refactoring projects versus projects that implement new features" though. Best, Christian.
next prev parent reply other threads:[~2020-01-23 11:02 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-22 20:42 Shourya Shukla 2020-01-23 11:02 ` Christian Couder [this message] 2020-01-23 18:04 ` Shourya Shukla 2020-01-23 22:51 ` Christian Couder -- strict thread matches above, loose matches on Subject: below -- 2020-01-01 13:02 [GSOC] Introduction Hariom verma 2020-01-23 11:16 ` Christian Couder 2020-01-23 20:18 ` Hariom verma 2020-01-23 22:38 ` Christian Couder 2019-02-24 10:05 [GSoC] Introduction Rohit Ashiwal 2019-02-24 14:47 ` Johannes Schindelin 2019-02-25 6:50 ` Christian Couder 2019-02-25 11:35 ` Rohit Ashiwal 2019-02-25 20:21 ` Christian Couder 2019-02-25 21:09 ` Eric Sunshine 2015-03-07 11:25 [GSOC] Introduction karthik nayak
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAP8UFD2Fo=2suQDLwzLM-Wg3ZzXpqHw-x0brPtPV0d4dRsgs9A@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
email@example.com list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ firstname.lastname@example.org public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git