Skip to end of metadata
Go to start of metadata

This will be the VIVO community's first time joining this open science community's Global Sprint event!

We discussed some ideas for June 4 and 5 on our May 21 weekly call, with follow up on our May 28 call. See the permanent notes at https://wiki.duraspace.org/x/5AkdB or the temporal Google doc at https://goo.gl/Smhzjq

Getting Started

Getting VIVO installed locally? See Vagrant and Docker solutions...

Getting a VIVO dev environment configured quickly?

If you don't already have a DuraSpace wiki or JIRA login, how do you get one? (Answer:  See the link on the home page of this wiki.  Or click here:  https://wiki.duraspace.org/signup.action)

Logistics

  • Signing up for VIVO sprints
  • IRC chat for reach max number of Global Sprint vs a VIVO-focused channel?

Thursday June 4th VIVO Call

How might we best leverage our normal weekly Thursday 1pm EDT call, since it falls on the first day of the Global Sprint?
  • Could we extend the call to more than one hour or shift the time to accommodate participants in Europe? Is this an option given we're using Cornell's WebEx account which might be scheduled by other groups?

2015 Sprint Candidates

By default, VIVO community's participation would be self-organizing. Below are some suggestions to help organize individuals that prefer that approach. We welcome any assistance. If you and one or more colleagues would like to host a sprint site, you can add it to the list of 30+ global sites on the Global Sprint etherpad: https://etherpad.mozilla.org/sciencelab-2015globalsprint

ORCID to VIVO

https://github.com/gwu-libraries/orcid2vivo

Give it a try at http://gw-orcid2vivo.wrlc.org/orcid2vivo/

To participate:

  1. Grab a ticket.  (Either assign to yourself or add a note.)
  2. Clone the repo.
  3. Make the change.  PEP8 / comments / unit tests required.
  4. Send a pull request.  Include a comment that says "I agree to assign my copyright to GWU for the contents of this pull request according to the LICENSE." (The lawyer makes us do this.)
  5. Bask in the gratitude of the VIVO community.

Question?  Email justinlittman@gmail.com.

Other Sprint Ideas

VIVO Documentation

Jon suggested that the Global Sprint could be a good opportunity to focus on our active VIVO Task Forces. Bring together task force volunteers for one or more remote working sessions and possibly new participants with novel feedback, questions, and ideas.

Other VIVO Task Forces

Jon suggested that the Global Sprint could be a good opportunity to focus on our active VIVO Task Forces. Bring together task force volunteers for one or more remote working sessions and possibly new participants with novel feedback, questions, and ideas.

Other VIVO Apps & Tools

VIVO tools and apps – catalog of tools and maintainers at Apps and Tools Interest Group

Brainstorming

  • Abby notes: The taxonomy for Mozilla Science Labs’ Contributorship Badges project was based on the VIVO-ISF Ontology

  • Eric: DavidE and I are paying a dev to setup a pump.io server to support their cross-linking project… we’re certainly ready for ideas… we’re building this! Could add this to the VIVO wiki page.

  • Jon: Hear what questions new people ask, e.g. “Where’s the roadmap?” and point them to our historical roadmap and current process that the new Tech Lead will be coordinating

  • Eric: wondering with DavidE would think about this… has ideas to build services, e.g. you call service with a VIVO URI, and service returns content like “new grant opportunities that match the expertise expressed on your VIVO profile page?” Bill: we like projects around machine readable data.

  • Alexandre: wonder if you expect contributions from people not familiar with VIVO, given its complexity? what could categorize a good project from a complex project like VIVO? Bill: that’s an important observation -- for a project with a large code base its hard for new contributors to spin up quickly in two days… so things like user testing and documentation sprints… getting more pairs of eyes on things like usability and documentation. Abby: Bringing in new contributors during these two days, this is an opportunity to give them an intro to our community. AlexR: try to enlist some satellite projects -- call for apps & tools is coming up… Alex: is the Call for Apps coming out before June 4th?

  • Alex: what are the ways that we all can communicate with the broader community of Global Sprint participants during the event (or in the days leading up to it)?

    • Bill: get our project listed on Etherpad, and in weeks leading up to sprint MSL spins up social media effort to highlight projects -- happy to have a guest post on their blog also… anything we want to highlight to the open science community. There is an IRC channel -- it should be on the Etherpad page. #sciencelab

  • open JIRA issues - link to JIRA

  • open GitHub pull requests

  • No labels

2 Comments

  1. Perhaps we can use this to write code.  We need some exercise in working together "sprint style." (two groups of three?) Happy to help in any way I can.  I write python and english sentences.  My Java is rusty.