From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=15.241.140.78; helo=g4t3425.houston.hpe.com; envelope-from=brian.johnson@hpe.com; receiver=edk2-devel@lists.01.org Received: from g4t3425.houston.hpe.com (g4t3425.houston.hpe.com [15.241.140.78]) (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 4AAB121A07A92 for ; Tue, 27 Nov 2018 13:55:54 -0800 (PST) Received: from g9t2301.houston.hpecorp.net (g9t2301.houston.hpecorp.net [16.220.97.129]) by g4t3425.houston.hpe.com (Postfix) with ESMTP id 3C14B92; Tue, 27 Nov 2018 21:55:53 +0000 (UTC) Received: from [10.33.153.4] (bjj-laptop1.americas.hpqcorp.net [10.33.153.4]) by g9t2301.houston.hpecorp.net (Postfix) with ESMTP id E149648; Tue, 27 Nov 2018 21:55:52 +0000 (UTC) To: Laszlo Ersek , Jeremiah Cox , stephano Cc: "edk2-devel@lists.01.org" References: <4330857f-4e27-632f-6f82-6fc6ec636b2e@linux.intel.com> <76cb4d25-7eff-b19b-0dd5-2fcc3a1e7d82@redhat.com> From: "Brian J. Johnson" Message-ID: Date: Tue, 27 Nov 2018 15:55:52 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <76cb4d25-7eff-b19b-0dd5-2fcc3a1e7d82@redhat.com> Subject: Re: [edk2-announce] Research Request 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: Tue, 27 Nov 2018 21:55:54 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit On 11/27/18 6:53 AM, Laszlo Ersek wrote: > On 11/26/18 22:43, Jeremiah Cox via edk2-devel wrote: >> Feedback on GitHub as follows… >> >> >>> 1. No Lock-In - What automated data export is available? >>> We want to be able to leave and take all our data with us. "Data" here >>> includes: review comments, pull requests / patches (including metadata), >>> old (rejected) pull requests and metadata, issue tracker entries and >>> comments (if issue tracker included). This archiving should be >>> automated, not something we do by hand. >> Untested, but might these all be easily satisfied by subscribing a mailing list to GitHub notifications? >> https://help.github.com/articles/about-notifications/#watching-notifications >> https://help.github.com/articles/about-email-notifications/ > No, they are insufficient. > > Following the last link above ("about-email-notifications"), one finds > several other links; and one of those is: > > https://help.github.com/articles/about-notifications/ > > This article says, > > GitHub sends participating notifications when you're directly > involved in activities or conversations within a repository or a > team you're a member of. You'll receive a notification when: > > [...] > > - You open, comment on, or close an issue or pull request. > > [...] > > This is demonstrably false. I'm a member of the TianoCore organization, > I have commented on, and closed (rejected): > > https://github.com/tianocore/edk2/pull/133 > > and I *never* received an email notification about my *own* comment / > action. I only received the initial email, about the pull request being > opened (attached for reference). Try going to the "Settings" item under the menu in the top-right corner, and clicking on the "Notifications" tab on the left. Under "Email notification preferences" there should be a checkbox for "Include your own updates". That may do what you need. -- Brian J. Johnson Enterprise X86 Lab Hewlett Packard Enterprise