Meeting notes are blended inline with the agenda
- Adventures getting home (delays, some drove instead of flying, but people made it)
- Highlights of sessions and/or workshops (too many conflicts, especially for developers wanting to see all the mini-grant presentations)
- Contacts made
- New tools – (_e.g., node.js http://nodejs.org, http://json-ld.org_)
Recap of the Open Source Next Steps session
Speakers – Chris Barnes, Richard Outten, Mummi Thorisson, Alex Viggio, Jon Corson-Rikert
- Release process and timing (aiming for quarterly would be nice)
- Enterprise hosting – e.g., availability of software as a service
- Platforms and tools – e.g., more documentation on Windows
- Increase our community surface area through efforts such as http://vivobuff.tumblr.com (Alex is trying to see if he can make it possible for others to submit)
- A VIVO development blog _I want to see what our community developers blogging about, even if it's not about VIVO, Maybe a blog aggregation planet.vivoweb.org (like http://planetdjango.org/, http://planet.gnome.org, or http://community.prometheanplanet.com/en/blog/b/blog/default.aspx?)_
- Integration – "information bridges"
- with eagle-i
- with HUBzero
- with repositories (Penn State)
- Speaking at broader interest conferences such as Educause and CNI (Maybe regional Educause conferences?)
- Articulate what problems we are solving – bigger than our "product"
- Harvester, the web of VIVO data, the ontology, Vitro (VIVO software with different ontologies) _like OCRe http://rctbank.ucsf.edu/home/ocre_
- Compiling driving use cases (_related discussion on today's implementation call – http://issues.library.cornell.edu/browse/VIVOIMPL is one place this could happen that would allow closer linking to development issues, or we could try a more purpose-built approach at sites like http://vivo.ideascale.com_
- Conference attendee mentioned using https://podio.com to coordinate and plan their community work – but there is a $4/user/month fee
- Adoption guide
- Sharing data expertise
- addressing developer learning curves
- make sure implementation-focused people feel welcome
- keep the 2 major listservs going – dev and implementation
- include some ontology discussions in implementation calls
Other useful models for open source development
- HUBzero community boards (https://hubzero.org/groups/community) – user reference group and tech reference group, each with monthly telcons
- Kuali Foundation (http://kuali.org/) – free software, institutional memberships to participate in development
- JASIG (http://www.jasig.org/jasig/contribute)
- Sakai (http://sakaiproject.org/contribute)
- The CLE Technical Coordination Committee ensures a timely, quality release
- The CLE Maintenance Team addresses issues after release
- The Sakie OAE Steering Group oversees the managed development project
- REDCap (http://www.project-redcap.org/)
- DuraSpace (http://www.duraspace.org/) – Projects include DSpace, Fedora and DuraCloud. Open source software and services to help ensure that current and future generations have access to digital heritage. Currently power more than 1,000 repository instances in 90 countries.
- (add others you think we should look at)
- not academia specific? Linux (Ubuntu vs Debian vs RedHat), Drupal, Ruby on Rails, Apache – which are like VIVO or not?
It would be helpful to have people familiar with these or any other open source efforts to briefly describe their governance, especially as related to development and operational processes to enable input on tasks, features, and priorities.
Is overall size relevant?
There may be useful processes we can learn from in other projects or products, such as the Mendeley advisors (http://www.mendeley.com/advisors/)
Any attending institution updates
- Cornell University
- Harvester 1.3 released
- Amazon EC2 instance published
- Weill Cornell
- Any experience with Shindig (http://shindig.apache.org/), the reference implementation of the open social container spec?
- Stony Brook
- 2nd web service under development to return UMLS CUIs for a publication by submitting the Pubmed Id
Wrapping up the mini-grants
- code check-ins
- building on what has been done so far
- Strong interest at Indiana in working with Eric Meeks from UCSF on Open Social widgets
Concerns / Requests
Is there a better meeting time – e.g., 1 pm Thursday would make it easier for Mummi Thorisson to participate from Iceland
Meeting earlier in the day would facilitate participation from Europe – morning better than afternoon, but 1 pm better than 3 pm. Jon will set up a Doodle poll for a standard meeting time and circulate it to the vivo-dev-all list
Call Information (note this is different from recent meetings)
1. Please join my meeting. https://www1.gotomeeting.com/join/232787753
2. Call in using your telephone if possible, or use your microphone and speakers (VoIP) - a headset is recommended, and please mute when you are not expecting to be talking.
Access Code: 232-787-753
Audio PIN: Shown after joining the meeting
Meeting ID: 232-787-753