Project Meeting -- 05/15/2019 @ 13:00

[callahantiff]

Meeting Date: 05/08/2019 Topic: Abra-Collaboratory Enhancements Attendees: @tuh8888

Proposed Agenda:

• [x] issue #15
• [x] issue #16
• [x] issue #14

[magic-lantern]

@callahantiff - I'm available to attend, though I do have another meeting at 14:00. What is the location for this meeting?

[callahantiff]

That works well, we also have a lab meeting at 14:00. We were planning to meet in our lab, which is where you and I first met (RC1 South - L18-6400A). Will that work with the location of your next meeting?

[magic-lantern]

That works for me. My 14:00 meeting is at the CU Medicine Building (formerly UPI) so I just need maybe 10 minutes to walk there.

[callahantiff]

OK, great! We can make sure end in time. Glad you can make it!

[callahantiff]

@magic-lantern Changing the meeting to the 15th at the same time, does that work?

[magic-lantern]

@callahantiff - Not sure I replied to your last update; May 15th works just fine for me. If that's the set date, I recommend updating the issue title to match.

[callahantiff]

@magic-lantern, thanks for the suggestion! Title has been updated!

[tuh8888]

Additional agenda item: discuss use of Abra-Collaboratory for class management

[callahantiff]

Additional Agenda item: discuss creating the first release of the repository so A DOI can be assigned.

[tuh8888]

• [x] Add release information to guidelines document since version is not kept track of otherwise.
• [x] Add update script (assumes initial script was run and updates based on version)

[callahantiff]

Meeting Minutes:

Thank you guys for a great meeting today! 👍 👏 😺 Here is a brief recap of what was discussed:

• [x] Create an initial release of the repository and add a DOI number. This task has been completed and a Zenodo badge has been added to the README.
• Discussion of trying to publish the repository. There are several steps that would be involved with this task (see issue: #14):
• Recruiting additional people to adopt the platform (see issue: #24)
  • Consider sending email to AMIA working groups
  • Consider trying to advertise at the NLM training grant conference
• Creating a project logo (see issue: #26)
• Discussed creating a database to track who uses Abra-Collaboratory (see issue: #25)
  • Need to understand if the GitHub API can be used to track all of the different ways someone might clone, download, fork this repo.
  • Consider adding a request for users to add specific tags to their repo (e.g. "Abra-Collaboratory", "Python", "Mechanistic Inference", etc).
• Investigate whether or not Overleaf can be embedded to a wiki page (see issue: #16 )

  ---

  Other Notes: @tuh8888 I have created the following issues for these:

  • [ ] Add release information to guidelines document since version is not kept track of otherwise.

issue: #22

• [ ] Add update script (assumes initial script was run and updates based on version)

issue: #23

---

If I have covered all of the topics discussed, I move that we close this issue and focus on addressing the individual referenced issues.