Re: [GSoC] Draft Proposal (Convert submodule to builtin)

From: Christian Couder <christian.couder@gmail.com>
Date: Apr 2, 2021, 06:31 UTC
Message-ID: <CAP8UFD1PC=vQCXLLoECPzFc8BGGfQxptHE5+Et11F-=3-twZYg@mail.gmail.com>
In-Reply-To: <f5b9ea24-e2f7-6c54-b4ff-86cef27527f7@gmail.com>

On Fri, Apr 2, 2021 at 7:44 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:

Show 9 quoted lines

>
> On 01/04/21 18.40, Chinmoy Chakraborty wrote:
> > Greetings mentors,
> >
> > This is my draft proposal for the GSoC project, Convert submodule to builtin.
> >
> > It would be really helpful if you could review the draft and present your
> >
> > views on it :).

Thanks for letting us know about your proposal!

> > Link: https://github.com/chinmoy12c/GSoC/blob/master/GSoC_Git_proposal.pdf

[...]

> Anyway, I copy-pasted the quotation above from your proposal in PDF format.
> but when I pasted it into text-only mail, it looks rather ugly.
> So next time when sending GSoC proposal for Git, I would like to see
> proposals in Markdown format (as well as PDF) for the reason above.

I agree that proposals should be sent to the mailing list in a textual format inline. It's ok if you also send a link to a better formatted version of your proposal, so that people who prefer to read the better formatted version can do so. It's ok too, of course, if the final version uploaded into the GSoC web site is the better formatted version.

Sending the textual version to the mailing list inline could make it easier for people who want to comment and discuss it, like patches are, which will help you make a better proposal. Later it might also help people searching the mailing list.

Best, Christian.