search

zowe / zac

Zowe Leadership Committee collaboration
Creative Commons Attribution 4.0 International
14 stars 14 forks source link

Review of Zowe code backups #178

Closed armstro closed 4 years ago

armstro commented 4 years ago

In an internal meeting we briefly discussed the state of backup with github and learned releases are backed up but other extended/optional" code is not necessarily backed up - would we agree we need to have someone review the backup practices and make recommendations.

We know Marist agreement does not entitle the project to backups but they might accommodate snapshot backup of key environment.

MarkAckert commented 4 years ago

Do we have particular examples of the extended/optional code in mind? Is like the community repository, conformance guidelines, etc? Website, docs-site, other code materials not related to Zowe PAX or CLI Archive? All of the above 😄?

armstro commented 4 years ago

I would think we need to do an inventory first of what we have. (I had not even thought about website.) What I have heard is "Zowe Releases" are backed up ...but code not in "core" is not and that triggered by question..

Github? Website? Doc? Samples? Build/test (Marist) - not incremental but "could" do a snapshot backup for point in time disaster recovery Automated Test cases? What does CII require?

Item is to think about - know the gaps and decide if gaps need filled and how......

Bruce Armstrong IBM System Z Offering Manager- zowe.org 4205 S MIAMI BLVD, DURHAM NC 27703-9141 Email: armstrob@us.ibm.com Tel: 919-254-8773 Cell: 919-931-3132

From: Mark Ackert notifications@github.com To: zowe/zlc zlc@noreply.github.com Cc: Bruce Armstrong armstrob@us.ibm.com, Author author@noreply.github.com Date: 04/22/2020 09:33 AM Subject: [EXTERNAL] Re: [zowe/zlc] Review of Zowe code backups (#178)

Do we have particular examples of the extended/optional code in mind? Is like the community repository, conformance guidelines, etc? Website, docs-site, other code materials not related to Zowe PAX or CLI Archive? All of the above 😄? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

MarkAckert commented 4 years ago

Drafted our backup coverage here: https://github.com/zowe/zlc/blob/user/markackert/code-backups/tracking/Backups.md

1000TurquoisePogs commented 4 years ago

Github recently did an archive and their explanation reveals that there are groups that backup github, so in effect there are multiple layers of protection on code that exists in github. https://archiveprogram.github.com/ By tagging the releases (we do), releases can be recreated from a github backup as long as the instructions are also present.