Sustainability & Adoption Cluster

Report OutSeptember 10-11, 2013

ISEES Classes of Stakeholders

• Researchers (multi-sector)• Meta Organizations (professional societies,

networks)• Institutions (libraries, academic computing)• Funders (agencies, foundations, corporate)• Data Repositories• Software Community (developers, users, code

repositories)

Incentives to Participate in ISEES

• Access to Reusable Resources• Collaboration• Reputation Building - Recognition• Access to Expertise• Reduce Risk of Failure• Efficiencies

Where ISEES Should Engage

• Professional societies• Blogosphere• Social Media Feeds• Meet Ups & Hackathons• Online Classes• Academic Technology Centers

ISEES Values – Year 1

• Results-Oriented– Responsive– Catalyst for Productivity– SW as the Outcome of Design

• Transparent– Communicative

• Collaborative• Community-Driven• Useful

Day 2

ISEES Structure

• Lean & Mean – funds toward community• Light weight structure (admin)• Honest Broker-Director• Fellows (sabbatical; doing the work)• Limiting the scale in Year 1 – small community to start to

build the network• Membership model (members have a say in governance but

all can benefit from ISEES assets)• Thematically-oriented steering committees that would

report into a governing board• Governance development takes time

ISEES Processes

• Governance takes time• Phased Approach– More centralized at beginning– Moving toward community-driven model in out

years– Build community interest early

• Proposals solicited thru Announcements of Opportunity; Fellowship models

• Early on, Benevolent Dictator model

ISEES Code Sustainability

• NO Peer Review of Code– But technical review okay

• Identify best practices for software development

• Use existing code repositories• Focus on the culture

ISEES Community & Financial Sustainability

• Income Streams– Swag– Membership Fees– Corporate Partnerships– Etc…

• Activities/Relevance– Brand building– Success stories– Active/provocative blogging– Etc…

• Policies– Transparent interactions with community– Mission development – leads to policies

• Metrics for Success– Use of software– How many participate– Assessment of success