public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Guptha, Soumya K" <soumya.k.guptha@intel.com>,
	"announce@edk2.groups.io" <announce@edk2.groups.io>
Subject: Re: Tianocore community page on who we are - please review
Date: Sat, 26 Sep 2020 05:09:29 +0000	[thread overview]
Message-ID: <CY4PR11MB1288119E7C6D6E621FD4C0388C370@CY4PR11MB1288.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MWHPR1101MB2366113F1EBE83AD1A799D30A7360@MWHPR1101MB2366.namprd11.prod.outlook.com>

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

Thanks Soumya. I think this is a good start.

Recently we are discussing the maintainer's work in EDKII mailing list, with title "more development process failure".

I feel the process mentioned in https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process is not clear enough to follow, especially for the maintainer who is not full time working on EDKII.

I wish we can have this opportunity to revisit the "Follow the EDK II development process<https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process>" and make "the process" simpler and clearer.

Then all maintainers can sign to follow one rule. The rule we define and the rule we agree with.

Thank you
Yao Jiewen


From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Soumya Guptha
Sent: Saturday, September 26, 2020 6:35 AM
To: announce@edk2.groups.io; devel@edk2.groups.io
Subject: [edk2-devel] Tianocore community page on who we are - please review


Dear Community members,



I have drafted a document "who we are", explaining Tianocore community structure, members of the community, their role and the current development process. I have drafted this document with the help of the Tianocore Stewards.

We view this as a living document, as our development processes evolve, I will keep this document updated.



Please review the draft version of the document (link below) and provide your feedback. Please send it to me, no need to reply all.

I appreciate your input by Friday, Oct 2. After this, I plan on make it live on our TianoCore wiki site.



Link: https://github.com/tianocore/tianocore.github.io/wiki/Who-we-are

Thanks,
Soumya

Soumya Guptha
TianoCore Community Manager





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

  reply	other threads:[~2020-09-26  5:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 22:35 Tianocore community page on who we are - please review Soumya Guptha
2020-09-26  5:09 ` Yao, Jiewen [this message]
     [not found] ` <16383D375E5994D7.27235@groups.io>
2020-09-26  5:32   ` [edk2-devel] " Yao, Jiewen
2020-09-27  2:32     ` 回复: " gaoliming
2020-09-27  3:25       ` [edk2-announce] " Yao, Jiewen
2020-09-28 12:01         ` [EXTERNAL] " Leif Lindholm
2020-09-30  2:11           ` Yao, Jiewen
2020-09-30  9:25             ` 回复: " gaoliming
2020-09-30 10:13               ` Leif Lindholm
2020-10-01  8:44                 ` Laszlo Ersek
2020-10-01  8:45                   ` Laszlo Ersek
2020-10-01 10:22                   ` Leif Lindholm
2020-10-01 23:52                     ` Soumya Guptha
2020-10-02  8:25                       ` Laszlo Ersek
2020-10-01  8:29               ` 回复: [EXTERNAL] RE: [edk2-announce] 回复: [edk2-devel] " Laszlo Ersek
2020-10-01  8:26             ` Laszlo Ersek
2020-09-28 11:56       ` Leif Lindholm
2020-09-28 16:19         ` Soumya Guptha
2020-09-29  1:05           ` 回复: " gaoliming
2020-09-28 17:15       ` Laszlo Ersek
2020-09-29  1:03         ` 回复: " gaoliming

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=CY4PR11MB1288119E7C6D6E621FD4C0388C370@CY4PR11MB1288.namprd11.prod.outlook.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