public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: Pedro Falcato <pedro.falcato@gmail.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc)
Date: Tue, 6 Apr 2021 07:24:05 +0000	[thread overview]
Message-ID: <9CCF7D19-9C63-48B3-B3A4-1D69A36BE400@intel.com> (raw)
In-Reply-To: <19876.1617533421134769104@groups.io>

Hi Pedro,

I agree with Andrew Fish. I’d say for the first half try to have an initial (but probably broken) implementation of the driver done. Then your second half can be fixing bugs, writing tests, and documenting your work.

Thanks,
Nate

From: Pedro Falcato <pedro.falcato@gmail.com>
Date: Sunday, April 4, 2021 at 3:50 AM
To: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>, "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc)

Hi,

Sounds great! You may be right about that, although I believe I read somewhere that you need to set a milestone for each evaluation? If so, I'm out of ideas as to what can be tangible enough to be a milestone; if not, specifying a read-only driver as project's objective and having write support as a stretch goal is certainly the way to go.

Thanks,
Pedro 


  parent reply	other threads:[~2021-04-06  7:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 13:07 [edk2-devel] GSoC 2021 (MinPlatform, Ext2, ACPICA, etc) pedro.falcato
2021-03-13  0:51 ` Andrew Fish
2021-03-13 17:01   ` Pedro Falcato
2021-03-16  0:25 ` Nate DeSimone
2021-03-23 14:16   ` Pedro Falcato
2021-03-28 22:31     ` Nate DeSimone
2021-03-28 22:42       ` Bret Barkelew
2021-03-31 20:45         ` Pedro Falcato
2021-03-31 20:43       ` Pedro Falcato
2021-03-31 23:13         ` Nate DeSimone
2021-04-04 10:50           ` Pedro Falcato
2021-04-04 15:33             ` Andrew Fish
2021-04-06  7:24             ` Nate DeSimone [this message]
2021-04-06 18:51               ` Pedro Falcato

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-list 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=9CCF7D19-9C63-48B3-B3A4-1D69A36BE400@intel.com \
    --to=devel@edk2.groups.io \
    /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