On 11/27/18 22:55, Brian J. Johnson wrote:
> 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.

That did the trick. I checked the box and then went on to close PR#134.
I got two separate emails shortly after (attached), one about the
closure and another about the comment.

In my opinion, the default value for the setting in question is broken
(it should be "on" by default). However, to me anyway, it's a big plus
for GitHub that it actually supports this feature. If we are going to
adopt GitHub, then we can highlight the knob in our docs.

Regarding GitHub, what remains to be seen (for me) is if & how it
preserves old (unmerged) topic branches, and review comments made for
them, after the pull requestor rebases or deletes those branches in
his/her repo.

Can someone please send an artificial/test PR against my personal repo,
at <https://github.com/lersek/edk2>? Just change some lines in
OvmfPkg/README or something like that.

Thank you!
Laszlo