Closed vincenzospaghetti closed 1 year ago
This seems like an interesting issue. I believe I can be of help
That would be great! We need some help here organizing this as a project.
Need to coordinate with owners of Drives, design new document organization structure, organize docs, and inform organization of the change.
Valerie Spina
On Mon, Jul 11, 2022, 12:53 PM Woodrow Jackson @.***> wrote:
This seems like an interesting issue. I believe I can be of help
— Reply to this email directly, view it on GitHub https://github.com/smartcontractresearchforum/engagement/issues/72#issuecomment-1180752008, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWHXYZZNW56CXWBPYZWI25LVTRUUHANCNFSM52K3ISHQ . You are receiving this because you authored the thread.Message ID: @.***>
Yea sounds good and where would you want this document organization structure placed in?
This would be for organizing the shared SCRF Google Drive.
May also apply to GitHub but Maria and Victoria are already working on public facing documents.
Valerie Spina
On Mon, Jul 11, 2022, 1:30 PM Woodrow Jackson @.***> wrote:
Yea sounds good and where would you want this document organization structure placed in?
— Reply to this email directly, view it on GitHub https://github.com/smartcontractresearchforum/engagement/issues/72#issuecomment-1180782943, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWHXYZ2IIGFSD4F2GUQNDJDVTRY3ZANCNFSM52K3ISHQ . You are receiving this because you authored the thread.Message ID: @.***>
Ok sounds good and just need the link and I can take a look at it
@zubepaul - can you decide if Woodrow can work on this?
It would require a scrf.io email and the access levels to view all shared scrf drives. The purpose is to reorganize SCRF Drive so it is accessible and transparent by the internal team.
Why do we need this?
What I am looking for Woodrow to do is essentially this: https://www.creativepl.com/blog/organize-files-boost-productivity
Ok I see the file structure in the article
@vincenzospaghetti I am not certain that an overhaul of the structure is necessary so much as a sorting of role permissions and communicating the structure in place. This does seem like something that @SirAh0 and @Wood-Jack could collaborate on. The communicating of roles and what permissions those roles have is something necessary not just in the file structure but across the org.
Hey I just talked to Brian. He said I need to give this link: https://github.com/smartcontractresearchforum/IT/issues/new?assignees=SirAh0&labels=github&template=google-onboard.yml&title=%F0%9F%97%84%EF%B8%8F+-+Onboard
to the project lead or person in charge of engagement. So they can file it as IT issue and issue me an scrf.io
I do think we need an overhaul. I'm not sure the current drive organization is user-focused or intuitive. Access needs organization for sure, but for example, with Onboarding, most of those documents and presentations should be public (lowest access level) along with anything that explains the functions, operations, or organization of SCRF. Right now the default SCRF Drive is 3 folders with nothing in them.
[image: image.png]
On Tue, Jul 12, 2022 at 8:00 AM Woodrow Jackson @.***> wrote:
Hey I just talked to Brian. He said I need to give this link: https://github.com/smartcontractresearchforum/IT/issues/new?assignees=SirAh0&labels=github&template=google-onboard.yml&title=%F0%9F%97%84%EF%B8%8F+-+Onboard
to the project lead or person in charge of engagement. So they can file it as IT issue and issue me an scrf.io
— Reply to this email directly, view it on GitHub https://github.com/smartcontractresearchforum/engagement/issues/72#issuecomment-1181797289, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWHXYZZ2VURB7NLNCVXTML3VTV26JANCNFSM52K3ISHQ . You are receiving this because you were mentioned.Message ID: @.***>
Here is my plan so far for organizing the documents in SCRF Drive. https://docs.google.com/document/d/1WJfn6fLG1-DboAmoRce2DDAI0DhgudG-Exd5-8WfB8M/edit?usp=sharing . Would you please look over @zubepaul and @vincenzospaghetti I would like to hear your thoughts on the draft.
Great start! Added some comments in the doc. Generally I would like to see it built out more.
On Wed, Jul 27, 2022 at 6:56 AM Woodrow Jackson @.***> wrote:
Here is my plan so far for organizing the documents in SCRF Drive. https://docs.google.com/document/d/1WJfn6fLG1-DboAmoRce2DDAI0DhgudG-Exd5-8WfB8M/edit?usp=sharing . Would you please look over @zubepaul https://github.com/zubepaul and @vincenzospaghetti https://github.com/vincenzospaghetti I would like to hear your thoughts on the draft.
— Reply to this email directly, view it on GitHub https://github.com/smartcontractresearchforum/engagement/issues/72#issuecomment-1196692637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWHXYZYOYRYQSPVY22BP5HLVWEWXTANCNFSM52K3ISHQ . You are receiving this because you were mentioned.Message ID: @.***>
Current update:
[x] @Wood-Jack getting file folder structure information frm Twan
[x] @0xAngle getting file folder structure infromation from Eugene and Maria
[x] Reconvene at a time and add last remaining file structure into documentation
Also don't forget to ask which files they want public or private.
The focus of this is to make sure that our onboarding materials are all in one place, that we can all access it as we need to for onboarding, and the that documents support the onboarding goals.
This is primarily done, but suggests there are more documents to make in the future.
This is a project to organize all of the documents (public and private) in an Onboarding/Engagement or overall SCRF folder. The community needs easy access to documents as they acquire the need for them and internal to have a centralized location for documents. The problem today is that everything exists in individual contributors' heads and is shared as needed through links. This is often confusing and disorienting as everyone is then in charge of personally managing document organization for themselves. This lacks cohesion and makes it difficult to share information and onboard both internal folks and the community.