From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mx.groups.io with SMTP id smtpd.web12.7598.1601627119961222199 for ; Fri, 02 Oct 2020 01:25:20 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=C+rES8sp; spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1601627119; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7wrdHM53i5nqIH/ByYt/bL7mc5lyu0OU+2cDDiLOgt4=; b=C+rES8spj0cEJsCALrzndPOSnWD/qZDwzEqZm+eyhwZHANdxUvX91fBQFbqK/mqHXL7wUb qdx+fEmVr6CFs8d5HZ0Iu1QrxjM41I9D0+1CO9N1siVAtX/GGGDB2PGwQEgbDkQV9HUuZ0 afBtLcUXNIUBLhzXF4BO0BQ5EBshsxU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-265-eK_G8ULxPpWI0QtBJsczFw-1; Fri, 02 Oct 2020 04:25:15 -0400 X-MC-Unique: eK_G8ULxPpWI0QtBJsczFw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1F40764087; Fri, 2 Oct 2020 08:25:13 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-188.ams2.redhat.com [10.36.113.188]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2130F73677; Fri, 2 Oct 2020 08:25:10 +0000 (UTC) From: "Laszlo Ersek" Subject: Re: Tianocore community page on who we are - please review To: Soumya Guptha References: <16383D375E5994D7.27235@groups.io> <005f01d69476$81768bd0$8463a370$@byosoft.com.cn> <20200928120131.GA5623@vanye> <009a01d6970b$a8d60100$fa820300$@byosoft.com.cn> <20200930101325.GE5623@vanye> <6aeab706-9191-af72-c16f-bae0924880d7@redhat.com> <20201001102218.GF5623@vanye> Cc: "Leif Lindholm (Nuvia address)" , edk2-devel-groups-io , Jiewen Yao , edk2-announce-groups-io , Michael Kinney , Andrew Fish , "Liming Gao (Byosoft address)" Message-ID: <98ee6f06-1265-7750-a8fb-cafcd2d7eb97@redhat.com> Date: Fri, 2 Oct 2020 10:25:10 +0200 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit (Resending; my previous attempt to post this response failed, and I even lost the original version of my response, so I'm rewriting it again from a draft. I've also cleaned up the garbage in the address list now -- I think that may have contirbuted to me failing to send the message at first.) Hello Soumya, On 10/02/20 01:52, Guptha, Soumya K wrote: > Hi Folks, > > Thanks for good discussions around this topic. > > The purpose of this document "Who we are" is intended to remain high > level to introduce the community members and their roles. Please note > that some of the feedback is very detailed that probably fits into the > TianoCore development > process > document. > > Below are my proposed changes to the document based on the emails. > > Please review and let me know if you see any issues by Oct 5. Please > also directly edit the document and let us know what you edited in the > document. > > Fyi.. my plan is for this page to go live on Oct 9th. This will be a > living document and we can make changes as we discover more. > > I have added a new member "Release Manager", added TianoCore admin > role, added responsibilities to the Maintainer and Reviewer section. I'm confused -- I understood the document was published already in the wiki: https://github.com/tianocore/tianocore.github.io/wiki/Who-we-are and the other day Liming even posted a patch for it, introducing the Release Manager Role: https://edk2.groups.io/g/devel/message/65765 I reviewed the patch (I suggested some improvements): https://edk2.groups.io/g/devel/message/65784 In other words, the document is already as "live" as it gets. It's up on the wiki for anyone to read and to propose updates for. Importantly, it's going to be difficult if we edit the document through multiple channels. Before publication, we edited the document through Google Docs -- that was an acceptable collaboration tool at that stage. Now that the document resides in the Wiki, the preferred format for proposing changes, and discussing those changes, is the usual patch review workflow on edk2-devel. We've followed this method for a long time now, for important wiki articles. For trivial changes to important articles, and for all kinds of changes to low visibility / low impact articles, using the WebUI is acceptable. But this is an important change to an important document. Furthermore, for wiki contributors that do not have wiki accounts (with write access anyway), posting patches to edk2-devel is the *only* way to contribute to the wiki. In the future, we might want to rebase that workflow *too* to github.com pull requests, but even then, the preferred format to express / propose a wiki change will still remain "patch". Apologies if I misunderstood something; my point is, if I'm supposed to review a change to the "Who we are" article in the wiki, please point me to a patch on edk2-devel. Thanks, Laszlo