From: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
To: git@vger.kernel.org
Cc: derrickstolee@github.com, vdye@github.com, gitster@pobox.com,
Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
Subject: [GSoC v1 0/1] GSoC 2022 proposal rough draft
Date: Wed, 6 Apr 2022 16:09:19 +0800 [thread overview]
Message-ID: <20220406080920.1220183-1-shaoxuan.yuan02@gmail.com> (raw)
Hi community, I wrote a rough draft of my GSoC 2022 proposal.
According to the General-Application-Information [1], I should
be sending this draft early to get reviews and comments. And I also
submitted one draft to official GSoC 2022 website.
This rough draft is not yet polished in terms of grammar and vocabulary,
and its content/detail is quite, well, rough. So, please give it more suggestions,
thanks a lot :-)
In addition to this patch-like draft, I also composed one on docs.google.com,
feel free to also comment on that one [2], in fact, it is preferable since it
has stylings, formats, and the final proposal should be in PDF.
A quick question: the idea page says this idea's "difficulty" is medium [3], are
we on the same page with Google's wording of "project size"? [4] Since the idea
page says: "Expected Project Size: 175 hours or 350 hours", I'm a bit confused
if this is a medium or large sized project.
[1] https://git.github.io/General-Application-Information/
[2] https://docs.google.com/document/d/1VZq0XGl-wCxECxJamKN9PGVPXaBhszQWV1jaIIvlFjE/edit?usp=sharing
[3] https://git.github.io/SoC-2022-Ideas/#more-sparse-index-integrations
[4] https://developers.google.com/open-source/gsoc/faq#how_much_time_does_gsoc_participation_take
Thanks,
Shaoxuan
Shaoxuan Yuan (1):
draft
proposal.txt | 133 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 133 insertions(+)
--
2.35.1
next reply other threads:[~2022-04-06 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 8:09 Shaoxuan Yuan [this message]
2022-04-06 8:09 ` [GSoC v1 1/1] draft Shaoxuan Yuan
2022-04-06 12:05 ` [GSoC v1 0/1] GSoC 2022 proposal rough draft Shaoxuan Yuan
2022-04-06 21:09 ` Abhradeep Chakraborty
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=20220406080920.1220183-1-shaoxuan.yuan02@gmail.com \
--to=shaoxuan.yuan02@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vdye@github.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).