-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate & Update Google Drives #185
Comments
Proposed file naming conventions:
|
Made comments and recommendations onto onto Secondary Drive Please review and add a comment with questions/suggestions below: I will make adjustments to Research files on the secondary drive accordingly once the comments are reviewed. |
Thank you @myrandi ! I replied to some of your comments in the sheet but I agree with your assessments. |
Update:
Next:
|
Finished updating Secondary tab. Next step:rename files according to updated conventions on communications style guide. |
Went through secondary drive and renamed and organized folders and files according to the inventory sheet. When I finished that, I invited all active team members to the primary drive and moved all of the folders from the secondary drive into the primary. I then consolidated the folders from both drives according to the inventory sheet and deleted any duplicate files. I gave dates to as many files as I felt made sense. Some living documents are continually used for years, like the Team Roster, Onboarding Doc, etc. and date created does not apply. Other documents may have a YYYY or YYYY-MM date if it was used & edited over weeks or months (or I just didn't know the exact date it was made). This naming structure sorts the docs well, and it makes it easier to find docs from a given time because you can search "2021-02" to find all dated docs from that month, for example. I updated the Google Drive links in the README and project wiki. |
Overview
There are two Google Drives for the Record Clearance Project, but we should have just one that is connected to the greater Hack for LA Drive so that the org doesn't risk losing our project information.
Action Items
Resources/Instructions
The text was updated successfully, but these errors were encountered: