Skip to content
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

Closed
3 of 4 tasks
surchs opened this issue Dec 4, 2023 · 8 comments
Closed
3 of 4 tasks

Clean up GDrive #84

surchs opened this issue Dec 4, 2023 · 8 comments
Assignees

Comments

@surchs
Copy link
Contributor

surchs commented Dec 4, 2023

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:

  • have only a few top-level directories
  • have one main dir for all projects
  • have the minutes for all active projects in an easily accessible place
  • some other thing

NEW 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 collaboration
    • Active/
    • Archive/
    • Prospective/
    • Contents potentially shared with external collaborators? YES
  • Conferences/
    • Abstracts, posters, and other conference materials, each organized in a separate subdirectory with the conference name + year
  • Graphics/
    • Miscellaneous tool screenshots, our logo, funder logos, + other images that can be reused in slideshows, conference posters, etc.
  • Presentations/
    • Slideshows for meetings, organized by year
    • One dedicated subdirectory for Lab/advisory meetings/
  • Internal/ : team-facing notes
    • Design/: 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 future
    • Resources/: 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 team
    • Minutes (internal)/: Meeting minutes from our team meetings, advisory board meetings, copies of team-facing notes on external meetings
    • Contents potentially shared with external collaborators? NO

"I need to create some meeting minutes - where do they go?"

Is the meeting with non-team members for a collaboration?

  • YES
    • Is it for an existing collaboration?
      • YES: Under the appropriate collaboration subdirectory in 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.
      • NO: Create a subdirectory under Collaborations/ (either under Prospective/ or Active/) 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 title
  • NO
    • Assuming the meeting is either with team members or an advisory board meeting, use the Internal/Minutes (internal) directory
@surchs surchs added this to Neurobagel Dec 4, 2023
@surchs surchs converted this from a draft issue Dec 4, 2023
@surchs surchs added the flag:schedule Flag issue that should go on the roadmap or backlog. label Dec 4, 2023
@alyssadai alyssadai moved this to Backlog in Neurobagel Dec 6, 2023
@alyssadai alyssadai removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Dec 6, 2023
@surchs
Copy link
Contributor Author

surchs commented Dec 6, 2023

Thanks @alyssadai! I like the structure! I would differentiate between "Projects" and "Collaborations":

  • Projects - internal things like the federation API or designing some architecture?
  • Collaborations - something longer-term outside of the lab / team, e.g. Douglas, NIMHANS, ...

wdyt?

@surchs
Copy link
Contributor Author

surchs commented Dec 6, 2023

Ah, another point: I'd like some high-level organization to keep the first level clean. How about

  • Communications
    • Talks
    • Conferences
    • Blogposts (or similar in the future)
  • Collaborations
    • proj1
    • proj2
    • Minutes (with all of the symlinked minutes)
  • Internal as you have it but also:
    • Admin
    • Documentation
    • Graphics

@alyssadai
Copy link
Contributor

alyssadai commented Dec 6, 2023

@surchs

I would differentiate between "Projects" and "Collaborations"

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:

  • Collaborations
    • Active
    • Prospective/other

?

Projects - internal things like the federation API or designing some architecture?

Sure - this sounds like what I have under Internal/Brainstorming right now, so maybe we can merge those (i.e., get rid of "Projects") and maybe rename the subdirectory to "Design" or "Planning".

I'd like some high-level organization to keep the first level clean.

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:

  • Communications
    • Talks
    • Conferences
    • Blogposts (or similar in the future)
    • Graphics (here instead of internal since talks + conferences use them, and collaborators may need them as well)
  • Collaborations
    • Active
      • Douglas
        • Minutes
      • OpenNeuro
        • Minutes
      • ...
    • Prospective
    • Archive
  • Internal:
    • Admin
    • Design/Planning
    • Documentation
    • Research
    • Minutes

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.

@alyssadai alyssadai moved this from Backlog to Implement - Active in Neurobagel Dec 6, 2023
@alyssadai alyssadai self-assigned this Dec 6, 2023
@alyssadai
Copy link
Contributor

@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 need to create some meeting minutes - where do they go?" section at the bottom of the issue.

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!

@alyssadai alyssadai moved this from Implement - Active to Implement - Done in Neurobagel Dec 10, 2023
@rmanaem
Copy link
Contributor

rmanaem commented Dec 12, 2023

Thanks @alyssadai! The new structure looks good to me. I only have one note, I believe we can remove Internal/Research as it has been replaced by our wiki.

@surchs
Copy link
Contributor Author

surchs commented Dec 14, 2023

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.

@surchs surchs moved this from Implement - Done to Review - Active in Neurobagel Dec 15, 2023
@surchs
Copy link
Contributor Author

surchs commented Dec 15, 2023

🧑‍🍳 I think this is good to close now

@alyssadai
Copy link
Contributor

Thanks for the feedback @surchs and @rmanaem!

I'll keep the Internal/Research directory for now then both as an archive and in case we need somewhere to drop more drafty/unorganized notes of topics we're researching.

Happy to amend the structure in future as needed.

@github-project-automation github-project-automation bot moved this from Review - Active to Review - Done in Neurobagel Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants