public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <sean.brogan@microsoft.com>
To: Purma, Kondal R <kondal.r.purma@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] EDK II Python development process specification -draft
Date: Sat, 07 Mar 2020 13:35:38 -0800	[thread overview]
Message-ID: <10736.1583616938364039740@groups.io> (raw)
In-Reply-To: <55pT.1583540823516683908.5KzJ@groups.io>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

This looks fine but it seems focused on writing a new module/project.  Most python work going into edk2 is part of existing code.
I would like to see additional documentation about how this applies to edk2 basetools.

* A flake8 config file could be added to basetools python.
* Documentation of developer workflows with edk2 basetools
* A plan for how to get edk2 basetools to meet these requirements
* A plan for automated patch verification of meeting these rules.

I have a rule of thumb for code guidelines.  I don't make any rules unless I can enforce them without un-manageable burden.

I also would rather see this type of documentation in the basetools python folder.  There is no reason a developer should have to go looking for this somewhere else within the tianocore site.

Finally, I would suggest we leverage an auto-formatter and provide the config file for that.  This reduces significant burden on the developer and keeps all contributes aligned.

Thanks
Sean

[-- Attachment #2: Type: text/html, Size: 1124 bytes --]

  reply	other threads:[~2020-03-07 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07  0:27 EDK II Python development process specification -draft Purma, Kondal R
2020-03-07 21:35 ` Sean [this message]
2020-03-07 23:26   ` [edk2-devel] " Purma, Kondal R
  -- strict thread matches above, loose matches on Subject: below --
2020-03-10 20:05 Rebecca Cran
2020-03-11 16:52 ` Purma, Kondal R
2020-03-14 19:07   ` Purma, Kondal R
2020-03-16 10:21     ` Bob Feng
2020-03-24 20:22       ` Purma, Kondal R
2020-03-25 21:23         ` Purma, Kondal R

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=10736.1583616938364039740@groups.io \
    --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