-
Notifications
You must be signed in to change notification settings - Fork 0
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
Clean up GDrive #84
Comments
Thanks @alyssadai! I like the structure! I would differentiate between "Projects" and "Collaborations":
wdyt? |
Ah, another point: I'd like some high-level organization to keep the first level clean. How about
|
that sounds fine, in that case we can probably move/merge the subdirectories for the different nodes currently under "Projects" (https://drive.google.com/drive/folders/1bt9JwSByVIIQ9wZIyKc0rkaG8Ih_pOEk) into the "Collaborations" directory. There does seem to be a lot of subdirectories under Collaborations (I think only a portion of which has been actively ongoing, at least since Arman/I have joined): to make it easier to find content for our currently active ones like the Douglas, OpenNeuro, etc., can we organize these into:
?
Sure - this sounds like what I have under
That's fine with me, although personally I feel like too many levels of traversal gets a bit tedious (many clicks) - since we're pretty much the only ones using the directory, I think as long as we can find our way around it should be okay. If we do want to keep the top-level dirs you suggested, I'd go for:
I think having a separate Minutes subdirectory per collaboration could be very helpful as we can basically then share the entire directory (or even the collaboration subdirectory as a whole) with whoever's involved, and we're not left having to dig through a bunch of unrelated minutes to find the one we need. Our Internal Minutes could contain things like notes from our advisory board meetings, internal comments on meetings with collaborators, etc. |
@surchs, @rmanaem, I've updated the issue description with the new directory structure I've implemented, including what each directory is expected to contain. Please have a read through/look and let me know if anything seems unreasonable. The new structure also specifies where different types of meeting minutes should go, which I also lay out in the I've kept 5 top-level directories as my sense is any more levels of depth will make it too tedious to find what we're looking for (since there are already many subdirectories for different projects, years/dates of presentations, etc.). Presentations + Collaborations are among our most visited locations I think, so I have kept those among the 5. If you agree with the structure, please gives a thumbs up or otherwise let me know - and hopefully we can close this issue this week! |
Thanks @alyssadai! The new structure looks good to me. I only have one note, I believe we can remove |
Looks good @alyssadai, I'm all in favor. For the Internal/Research portion, I think it can still make sense to have a GDrive for this, because we need to have a place to collect our findings and collaborate on things before they go into the wiki. We should definitely move things into the wiki whenever we can, but I'd say let's keep this folder around for a bit and see if we use it. |
🧑🍳 I think this is good to close now |
https://drive.google.com/drive/folders/1RzEXyYQ3cB4fPmpMZroqN6R5k3D-mXDo?usp=drive_link is a bit of a mess right now. One of the things we need and don't have is a nice place for meeting minutes that is easy to find and reuse, so we all know where to look for the newest info on projects.
I think we should:
some other thingNEW DIRECTORY STRUCTURE (see our Drive)
Collaborations/
: under the relevant category folder, there's a subdirectory for each project containing * shared meeting minutes * and other notes about the collaborationActive/
Archive/
Prospective/
Conferences/
Graphics/
Presentations/
Lab/advisory meetings/
Internal/
: team-facing notesDesign/
: catch-all subdirectory for notes from issue planning/data modeling/Neurobagel tool documentation drafts, etc. that is part of our process but that we probably won't revisit in the futureResources/
: Developer-facing notes of things learned from the various software/tools we use (e.g., GitHub tips and tricks)Research/
: Notes from research on Neurobagel-adjacent stuff (e.g. similar projects, non-for-profit info), that serves as a reference for the teamMinutes (internal)/
: Meeting minutes from our team meetings, advisory board meetings, copies of team-facing notes on external meetings"I need to create some meeting minutes - where do they go?"
Is the meeting with non-team members for a collaboration?
Collaborations/
, either add to the running minutes document if it exists, or create a new meeting minutes document (which you will continue adding to in the future). If the minutes for the meeting must be a standalone document in the directory, make sure it is dated.Collaborations/
(either underProspective/
orActive/
) with the name of the collab. Inside the subdirectory, create a new running meeting minutes document.** If you need to also take notes on the meeting that are only team-facing/internal, save it into a doc in
Internal/Minutes (internal)/
with the name of the collab in the document titleInternal/Minutes (internal)
directoryThe text was updated successfully, but these errors were encountered: