From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=134.134.136.31; helo=mga06.intel.com; envelope-from=stephano.cetola@linux.intel.com; receiver=edk2-devel@lists.01.org Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id B9A1B2118F341 for ; Fri, 16 Nov 2018 12:46:10 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Nov 2018 12:46:10 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,241,1539673200"; d="scan'208";a="106947256" Received: from scetola-mobl1.amr.corp.intel.com (HELO [10.254.182.85]) ([10.254.182.85]) by fmsmga004.fm.intel.com with ESMTP; 16 Nov 2018 12:46:09 -0800 To: "Kinney, Michael D" , "edk2-devel@lists.01.org" References: <6535b4dd-57ac-856c-e013-ae8b3203c550@linux.intel.com> <3FEC98D0C33031D6.0465ECFF-1E41-4227-B64B-45BCF39396EA@mail.outlook.com> <76DE84138CBE89489874B70B432D8F9BC7EBA888@ORSMSX105.amr.corp.intel.com> From: stephano Message-ID: <8a7fa4f2-2a6a-6af3-943b-e64395df270b@linux.intel.com> Date: Fri, 16 Nov 2018 12:46:09 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: [edk2-announce][RFC] Collaboration Software X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2018 20:46:11 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit This looks great. I'm going to dig in a bit and see if we can export discussions for logging purposes or if they are locked into Github. git clone git://tianocore.discussion ? :) On 11/16/2018 11:55 AM, Kinney, Michael D wrote: > Hi Stephano, > > GitHub supports discussions for teams. > > If we added a new team to the GitHub TianoCore > organization for all developers that want to be > involved in community topics and design discussions > (which should closely match the current members of > edk2-devel) then that may be a simple option that > uses services that already there. > > Another option is to use discussions for one of the > exiting teams (e.g. Tianocore Maintainers) and make > posts for these discussion topics public. > > https://blog.github.com/2017-11-20-introducing-team-discussions/ > > https://help.github.com/articles/about-team-discussions/ > > Best regards, > > Mike > > > > >> -----Original Message----- >> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] >> On Behalf Of stephano >> Sent: Friday, November 16, 2018 11:14 AM >> To: Zimmer, Vincent ; edk2- >> devel@lists.01.org >> Subject: Re: [edk2] [edk2-announce][RFC] Collaboration >> Software >> >> The only reason I didn't include Slack is that it will >> only log so much >> information before things start falling off into the >> ether. >> >> Does anyone in the community currently use Slack and know >> of an easy way >> of archiving conversations publicly? >> >> >> On 11/16/2018 9:56 AM, Zimmer, Vincent wrote: >>> https://slack.com/ >>> >>> -----Original Message----- >>> From: edk2-devel [mailto:edk2-devel- >> bounces@lists.01.org] On Behalf Of Kevin D Davis >>> Sent: Friday, November 16, 2018 9:35 AM >>> To: stephano ; edk2- >> devel@lists.01.org >>> Subject: Re: [edk2] [edk2-announce][RFC] Collaboration >> Software >>> >>> >>> >>> >>> >>> >>> If we get to vote, I’d vote against Google >> Groups.  Their interface is very geared toward their >> internal work flow and seems to change on a whim. >> Thanks,Kevin >>> >>> >>> >>> >>> >>> On Fri, Nov 16, 2018 at 11:08 AM -0600, "stephano" >> wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> We are looking to augment our current communication >> methods (mailing list / IRC) with a modern solution for >> group collaboration. The goal is to allow folks to >> communicate effectively without interrupting the current >> patch review system, as well as enabling any future >> systems with more robust options. >>> >>> Specific features we are looking for include >> attachments (currently blocked by the list), robust >> logging, modern chat, and integration with tools like bug >> trackers and source repositories (APIs, or better yet, >> pre-rolled plugins). >>> >>> Our current contenders are Google Groups and Groups.io. >> This RFC is in hopes of finding other options to >> evaluate. >>> >>> Cheers, >>> Stephano >>> _______________________________________________ >>> edk2-devel mailing list >>> edk2-devel@lists.01.org >>> https://lists.01.org/mailman/listinfo/edk2-devel >>> >>> >>> >>> >>> >>> _______________________________________________ >>> edk2-devel mailing list >>> edk2-devel@lists.01.org >>> https://lists.01.org/mailman/listinfo/edk2-devel >>> >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel