Date: Thu, 28 Mar 2024 08:42:59 -0400 (EDT)
Message-ID: <1933928520.27746.1711629779306@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_27745_574440533.1711629779306"
------=_Part_27745_574440533.1711629779306
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Meeting notes are blended inline with the agenda=
Conference=
Reflections
- Adventures getting home (delays, some drove instead of flying, but =
people made it)
- Highlights of sessions and/or workshops (too many conflicts, especi=
ally for developers wanting to see all the mini-grant presentations)=
li>
- Contacts made
- New tools =E2=80=93 (_e.g., node.js http://nodejs.org, http://json-ld.org=
_)
Recap of the Open Source Next Steps session
Speakers =E2=80=93 Chris Barnes, Richard Outten, Mummi Thorisson, Alex V=
iggio, Jon Corson-Rikert
Topics raised
- Release process and timing (aiming for quarterly would be nice=
)
- Enterprise hosting =E2=80=93 e.g., availability of software as a servic=
e
- Platforms and tools =E2=80=93 e.g., more documentation on Windows
- Increase our community surface area through efforts su=
ch as http://vivobuff.tumblr.com (Alex is trying to see if he =
can make it possible for others to submit)=20
- Integration =E2=80=93 "information bridges"=20
- with eagle-i
- with HUBzero
- with repositories (Penn State)
- Outreach=20
- Speaking at broader interest conferences such as Educause and CNI (=
Maybe regional Educause conferences?)
- Articulate what problems we are solving =E2=80=93 bigger than our "prod=
uct"=20
- Compiling driving use cases (_related discussion on today's implementat=
ion call =E2=80=93 http://issues.library.cornel=
l.edu/browse/VIVOIMPL is one place this could happen that would allow c=
loser linking to development issues, or we could try a more purpose-built a=
pproach at sites like http://vivo.ideascale.com_
- Conference attendee mentioned using https://podio.com to coordinate=
and plan their community work =E2=80=93 but there is a $4/user/mo=
nth fee
- Adoption guide
- Sharing data expertise
- Participation=20
- addressing developer learning curves
- make sure implementation-focused people feel welcome
- keep the 2 major listservs going =E2=80=93 dev and implementation=20
- include some ontology discussions in implementation calls
Other useful models for open source development
- HUBzero community boards (https://hubzero.org/groups/com=
munity) =E2=80=93 user reference group and tech reference group, each w=
ith monthly telcons
- Kuali Foundation (http://kuali.org/) =E2=80=93 free software, instituti=
onal memberships to participate in development
- JASIG (http://www.jasig.org/jasig/contribute)
- Sakai (http://sakaiproject.org/contribute)=20
- The CLE Technical Coordination Committee ensures a timely, quality rele=
ase
- The CLE Maintenance Team addresses issues after release
- The Sakie OAE Steering Group oversees the managed development project=
li>
- REDCap (http://www.project-redcap.org/)
- DuraSpace (http://www.duraspace.org/) =E2=80=93 Projects includ=
e DSpace, Fedora and DuraCloud. Open source software and services to help e=
nsure 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)=20
- not academia specific? Linux (Ubuntu vs Debian vs RedHat), Drupal, Ruby=
on Rails, Apache =E2=80=93 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, feature=
s, and priorities.
Is overall size relevant?
There may be useful processes we can learn from in other projects or pro=
ducts, such as the Mendeley advisors (http://www.mendeley.com/a=
dvisors/)
A=
ny attending institution updates
- Cornell University
- Indiana
- UF=20
- Harvester 1.3 released
- Amazon EC2 instance published
- Weill Cornell
- Colorado
- Duke=20
- Pittsburgh
- Stony Brook=20
- 2nd web service under development to return UMLS CUIs for a publication=
by submitting the Pubmed Id
Wrappin=
g up the mini-grants
- reports
- code check-ins
- building on what has been done so far=20
- Strong interest at Indiana in working with Eric Meeks from UCSF on Open=
Social widgets
Concerns / Req=
uests
Is there a better meeting time =E2=80=93 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 Europ=
e =E2=80=93 morning better than afternoon, but 1 pm better than 3 pm. Jon w=
ill set up a Doodle poll for a standard meeting time and circulate it to th=
e vivo-dev-all list
1. Please join my meeting. https://www1.gotomeetin=
g.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 no=
t expecting to be talking.
Dial 630-869-1015
Access Code: 232-787-753
Audio PIN: Shown after joining the meeting
Meeting ID: 232-787-753
last meeting=
| next mee=
ting
------=_Part_27745_574440533.1711629779306--