Define exactly what information needs to be preserved (that is not already in GitHub emails)

[makubacki]

All updates the PR.

• PR subject
• PR body
• Commit message information for commits in the PR
• Commit content for commits in the PR
• PR comments
• PR push updates (revision information)

[makubacki]

@mdkinney, can you double check the list above? That's my understanding from the recent meeting. I don't recall if PR approval state was going to be exported or just captured in the PR.

[makubacki]

We noted the following about the export process:

• Captures history of changes
• Not needed for immediate review
• Read-only
• The content will be formatted in an email-like representation in a git repo similar to that of the edk2 mailing list
  • The history of activity in edk2.groups.io would need to be imported to create a seamless transition from the mailing list model to the PR model
• The git repo will reside on GitHub in the tianocore organization
  • The last commit in the repo can be used to know where processing last left off and where to resume processing
• The GitHub GraphQL API can be used to capture PR information
• The format of the file in the repo should be Year/Month/PR#.txt
  • The file will receive updates based on PR activity