The notes below reflect a summary of the March 13 open forum discussion answer the proposed questions.

Wednesday, March 13, morning sessions (cmm)

James Hilton kick-off and presentation


JH Short overview of Fedora past

Institutions and foundations invested heavily in DSpace and Fedora and it was good. Millions of dollars were spent. Institutions and foundations said they were done. "You must be self-sustaining". There was no spigot with millions of dollars coming out of it. How do we make the organization self-sustaining was a DuraSpace board question. How to sustain community open source projects is a community issue. Revenue was diversified over a number of years with the sponsorship program and grants along with service revenue. This is the moment to take up the question sustainability for open source projects.

Michele and Jonathan Myths and Debunks (see slides)


What are the interrelationships among our efforts?

How is governance going to come out of this somewhat new perspective (for this group)?

Tyler Walters (see slides)


Does DPN need DuraSpace?

Does Tyler have an idea of how much that $$ would buy without the community efforts and projects?

Sayeed, We need to put a timeframe around this. There is an urgency. Data is being destroyed right now. It is being destroyed now--what was wrong with those people (us).

Wednesday, March 13, afternoon sessions

Attendees were asked to have table discussions and report out their answers to the following questions:

  1. What did you hear today?
  2. What do you have concerns about?
  3. What has inspired you?
  4. What unanswered questions do you have?

Table reports


Fedora Futures session

Eddie via Skype from Singapore: "The sun never sets on the Fedora empire."

Jonathan: Why are we talking about FF now?

 Tom Cramer, Project overview 

Eddie Shin, Tech overview


Thursday, March 14, morning sessions 

DSpace Session

Initial Discussion Questions:

Greatest needs in the community summary:

1) Need a roadmap - need a vision of what DSpace should be in the next 3 to 5 years

2) Need governance for stakeholders to go along with additional funding and long term roadmap

DSpace Futures 

How do we energize the DSpace community?

Should DSpace be UI that sits on top of Fedora?

DSpace community is bifurcated community


not an enterprise system, doesn't scale


VIVO Breakout Session  Mike Conlon, recorder

Attendees: Mike Conlon (UF), Bill Barnett (IU),  Hal Warren (APA), Julia Trimmer (Duke), Mike Bolton (Texas A&M), Dean Krafft (Cornell), Robert McDonald (Indiana), Mike Winkler (Penn), Daniel Calto (Elsevier), Jonathan Breeze (Symplectic), Alex Viggio (Digital Science), Paul Albert (Weill Cornell), Delphine Canno (Temple, by Skype), Andrew Ashton (Brown), Jon Corson-Rikert (Cornell, by video)

Three discussion areas:

  1. VIVO Roadmap – Dean Krafft, facilitator
  2. VIVO Strategy – Jonathan Markow, Facilitator
  3. VIVO Strategy – Bill Barnett, Facilitator

VIVO Roadmap -- Dean Krafft, Facilitator

Vivo 1.6 -- VIVO-ISF, CTSAConnect, Eagle-I, bidirectional API via SPARQL, HTTP caching, search indexing, developer tools, landing page improvements.  1.6.1 running through tests.

If a grant or other sponsor can pay for a specific feature that does not take away from the strategy or roadmap, and gifts back the feature to the vivo core, there is general support.  

A collection of architectural use cases -- VIVO as an engine, an aggregator, an information representation, as data store used for external apps,  Balance use cases in the development road map.

Need for documentation.  Using, installing, adding code.  To build development community -- Internal code needs documentation.  Architecture documents. Development process. On boarding documentation.

Some possible new features:

There will be an annual survey at the Implementation Fest.

How is the roadmap developed?  Users, sponsors, technical. Interaction with grant funded effort.  Community of developers. Balancing allocation.  Sponsors, steering.  Ideas -> proposals -> vetting -> deciding 

Time-based vs feature-based release? Most prefer time-based release.  Easier to plan.  Possibly bi-annual.


Action items

Project Director hire.  Community assessment of desirable features before Austin?  Time at Austin to disucss? Roadmap proposal. Goals: Functioning organization, roadmap development


Governance -- Jonathan Markow, Facilitator

Reviewed the project charter describing governance and membership.

Spending incubation period developing governance and membership.  Founding members are Platinum members with designation as Founders.  Other levels range from bronze at $2500 to Diamond at $30,00. Membership campaign in the spring -- we have a handful of non-founders currently.

Recognize in-kind contributions.  1/2 developer would be same as platinum, on the leadership group.

Steering committee -- Bill, Paul, Dean, Jon, Mike, Kristi, Robert, Jonathan, Project Director.  Should be elected by the leadership group.

Leadership group -- platinum and above.  Elect the steering group. Clarify the role of the leadership group regarding strategy, budget.  Intended to function as a board.

Project members -- submit requests, vote for two at large leadership group members

Work groups – largely volunteer effort with focus on an aspect of VIVO – implementation, core development, apps & tools, ontology, outreach

Duraspace – shepard the development of all things VIVO – software, community, process

Use cases for governance.  How do we create a roadmap?  How do we develop a strategic plan?  How do we develop and approve a budget? Allocate resources?  How (when/process) do we name the steering committee?  

Input rights -- bronze and silver

Decision rights -- platinum and diamond

Project members at the bronze level.  Consortia membership is possible to encourage participation outside the US. Learn from other projects and Duraspace.


VIVO Strategy -- Bill Barnett, Facilitator

VIVO business model -- membership, committed people, project director, Duraspace, alignment with institutuonal interests.

Kernel, application, ontology, applications


What is our business?  competitors?  Public, shareable, Machine consumable, human attribute storage.  With lineage, trust. Create and Share data about scholarly work.

Alliances.  People who create and share scholarly work.  We're not in the publishing business, nor administrative function, nor repository businesses.

The concept of VIVO data and promoting the production of VIVO data by any means.

Spurring adoption --early adopters, secondary messaging, early middle (value propositions), late middle (everyone else is doing it, compliance). Enabling implementation, changing the ROI. Having usage and implementation stories at various scales.