|Fedora Vision and Strategy Summary and Guiding Principles document|
|Note: see lines 36-46 below for list of roadmap verbs to use in "Now - Soon - Later"|
See the "How to use this Template" tab for some brief instructions on how the Roadmap works.
|Also see "changelog" below for differences from CNI meeting version|
|Fedora Commons is dedicated to persisting knowledge through a graph-based, linked data framework|
|Product Technology (steward: David)||Now||Soon||Later||Desired Future Condition|
|GUIDING PRINCIPLE (Higher Purpose)||Fedora API||VALIDATE|
Spec with major clients and two servers using test suite
v1.0 of the spec
regular maintenance program
with other standards communities
API specification in light of long term product vision
|Multiple client and server implementations with engagement from other standards communities|
A repository technology that provides a framework for managing digital content and integrating it with services
|Fedora API Implementations||SUPPORT/ENGAGE|
One alternate implementation
2-3 outstanding alternative implementations
|One main implementation with several other implementions serving different use cases.|
|Community-supported Fedora Implementation||DESIGN/REVIEW|
Alternative technology for main, community-supported implementation
New base technology
Existing users to the new base technology
|One well-adopted, community-supported, sustainable implementation that satisfies the majority of use cases.|
|Long-term preservation and access||PROTOTYPE/|
OCFL-compliant Fedora implementation
OCFL Fedora implementation in the context of long term preservation and access
|Objects and binaries persisted in a performant, scalable, application-independent way with an automated fixity service.|
Release schedule policy, semantic versioning, API release/change policy
Technical Roadmap with priority list of features, LTS timetable
Roadmaps, LTS releases, and policies.
|Reliable technology with a clear development road map and messaging patterns about breaking API changes along with Long Term Support releases.|
|Ease of installation||IDENTIFY|
Gaps in documentation and challenging concepts
Improved documentation with concrete examples.
Installation and deployment tools
More installation and deployment tools
|Fedora can be installed as a standard web application on a variety of platforms with detailed, up-to-date documentation, including common deployment architectures for repository ecosystems that use Fedora.|
|Ease of Hosting as a Service Offering||INVESTIGATE|
requirements for hosted, cloud-based, autoscaling, multi-tenant shared infrastructure
Advanced scaling options
|Support for hosted, cloud-based, multi-tenant shared infrastructure|
Migration tools to work with Fedora 5.x.
Commitment to migration support for all future versions.
Migration tools to work with Fedora 6.x
Migration support for all future versions of Fedora.
|Full, well-documented migration support for Fedora 3.x onward that can be completed in a manageable, plannable amount of time.|
|Compliance with international standards and services||OAI-PMH support, COAR NGR features, NDSA levels of preservation compliance|
|HIGH LEVEL GOAL:||Draft idea: Replace modeshape, and tool implementation of OCFL, with an institutional demonstration project (possibly at Emory?).|
|Product Position (steward: Rosalyn & Robin R.)||Now||Soon||Later||Desired Future Condition|
|GUIDING PRINCIPLE (Higher Purpose)||Ecosystem Role/Integration||DEFINE|
Fedora's role as a tool that enables preservation and persistence.
A prioritized list of features for enabling preservation and persistence.
Appropriate features aimed at preservation and persistence.
|Fedora enables persistence and preservation in the knowledge management and cultural heritage ecosystem. Through its API it offers flexible and well-documented integration capabilities with other key ecosystem components.|
|A set of functionality that creates flexible, predictable ways to store, integrate, and interact with repository content.||Integrated Applications (Islandora/Samvera/Custom/VIVO/etc.)||IDENTIFY|
Common needs for applications and communities utilizing Fedora.
The product roadmap based on identified common needs.
With the major community supported applications to ensure Fedora's place in their roadmaps.
Improved architectural alignment based on the roadmap
|Fedora and major community supported applications (e.g. Islandora) have clearly defined roles and responsibilities in the software stack(s). A majority of community supported applications interoperating with Fedora are running a recent, supported version of Fedora. Product roadmaps are shared and understood across the communities, with opportunities for input on product direction and shared commitments.|
|Flexible Modeling Support||DEFINE|
Our position on flexible modeling support
Appropriate levels of support for the different models
Guidance and/or levels of support for the different models
|Fedora supports a flexible content model to ensure integration with a diversity of digital object models. Implementers have the ability to extract digital object information stored in Fedora via the API.|
Preservation metadata stored within Fedora and its framework for preservation.
|IDENTIFY AND PRIORITIZE|
Features necessary for storing preservation metadata in Fedora.
Identified preservation metadata features
|Fedora facilitates the curation of digital objects by providing a framework for preservation actions. It performs supported preservation actions while also providing a template for implementing non-standard or custom preservation actions. The results of preservation actions are stored by Fedora and can be outputted via its API for a variety of use cases.|
OCFL as a specification used by Fedora.
Next steps for implementing OCFL in Fedora.
OCFL in Fedora
|Fedora provides a standards based method for persisting digital objects (e.g. OCFL).|
|HIGH LEVEL GOAL:||Draft idea: Brainstorm a transparent and thoughtful framing of Fedora's desired preservation affordances and capacities, informed by perspectives from preservation practitioners (preservation librarians, collections librarians, community stakeholders)|
|Communication, Outreach, and Marketing (steward: Dustin & Jon)||Now||Soon||Later||Desired Future Condition|
|GUIDING PRINCIPLE (Higher Purpose)||(Product) Positioning Statement||INVESTIGATE|
Market share & competition
|Clearly articulated product positioning statements, based on our vision and mission and guided by a marketing strategy, that our community and potential users understand and embrace.|
Particular clarity around areas open to interpretation (e.g. role in digital preservation)
|A well-defined target group, with well-defined communication channels and methodologies||Training||INVESTIGATE|
Community training needs
Gaps in current training materials
New training materials to fill gaps
with broader outreach strategy
Use cases to support introductory information
A broad range of workshops and camps tailored to community needs
Effects on adoption & community activity over time
|Modular, diversified programs capable of responding to the diverse needs of the community.|
A tool to sustain user base and gather feedback (mutual knowledge exchange)
Reflect partnerships with external communities: provide guidance for strongly related technologies (PCDM, etc.)
|Conferences & Events||IDENTIFY|
Key venues, topics of interest & audiences
Presentation templates with consistent key messages
Community members to deliver presentations
Presentations at key events around the world
Effects on adoption & community activity over time
|Consistent, international presence at key events, featured in presentations by a variety of community members, well-recognized and established brand.|
|Marketing Strategy|| INVESTIGATE|
Goals of a marketing strategy
Partner(s) (e.g. a company) to develop a strategy with
|A coherent and active strategy that includes such components as logo and slogan, advertising, and web site strategy which results in strong brand recognition.|
Transparently in line with vision.
|Targeting and outreach to new communities||INVESTIGATE|
communities potentially interested in Fedora
Channels and modes of approach
survey to potential Fedora users
To community representatives
|A documented understanding of the needs and landscape of potential users, with active use amongst new communities|
|HIGH LEVEL GOAL:|
|Community (steward: Este)||Now||Soon||Later||Desired Future Condition|
|GUIDING PRINCIPLE (Higher Purpose)||Fedora Active User Community||INVESTIGATE|
effective methods to grow the non-developer community (e.g. SIGs)
The results of the implemented methods
|Measured increase in overall participation of user community.|
|A vibrant community of GLAM professionals committed to the adoption, development, and maintenance of Fedora||Grow the tactical development community||INVESTIGATE|
effective methods to grow developer community
The results of the implemented methods
|Stable commitment of 3 FTE, with articulated short cycle goals, and ways to assess process and product.|
|Strategic Partnerships||IDENTIFY the range of initiatives, projects and communities the Fedora community should follow and advise issues related to Fedora development||ENHANCE existing partnerships with external partners through communication around Fedora strategy and vision and recommendations related to product technology.||Define recommended roles and processes for sharing, advising, and communicating with external partners||Advancing the work of Fedora project/community vision with attention to key strategic partnerships in decision-making, and communication about strategy, vision, and technological guidance shared with key partners.|
|Interaction with stakeholder communities (including all levels of funding and support)||CREATE liaison structure between Fedora and key communities||DEVELOP mechanism for broad-based input on technical direction and strategy from key communities||Build a regular process of informing technical direction with input from key communities||An engaged and committed group of stakeholders, with an understanding of how Fedora influences and is influenced by individual stakeholder groups. Stakeholders feel included, rewarded by participation, and the community supports innovation.|
|Diversity and Inclusion||INVESTIGATE practices for fostering diverse user communities in open source and technology projects||IDENTIFY |
ways to increase diversity and inclusion in the Fedora community
|Implement systematic practices to ensure the Fedora community is creating an open, welcoming, and engaging environment for all current and potential community members||Enable and foster participation by the widest user community, representing all members of the community, extending beyond North America, and especially surfacing non-majority populations and diverse perspectives, in a welcoming environment.|
|HIGH LEVEL GOAL:|
|Governance & Business Model (steward: Jennifer)||Now||Soon||Later||Desired Future Condition|
|GUIDING PRINCIPLE (Higher Purpose)||Fedora Leadership||ARTICULATE|
The current governance process
Metrics for assessing leadership's engagement with governance
Leadership's engagement with governance
|An actively engaged governance group that stewards a healthy organization and helps to create coherence between the major community software projects.|
|Developing and onboarding new members||ADOPT|
Onboarding and mentorship processes
|An engaged, inclusive, democratic, transparent, international governance group, with well-defined onboarding and mentorship processes for new members.|
|An engaged, inclusive, democratic, transparent, international governance group organized around a clear structure and model, including charters, relationships, and assessment guidelines.||Financial Sustainability Plan||INVESTIGATE|
Viability of business model
Recommendations to the DuraSpace board.
|A clearly articularted business model with diverse, sustainable funding streams|
|Programmatic Budgeting / Fiscal Strategy||DEFINE|
fiscal strategy and budget
|An adaptable fiscal strategy and budget that aligns with our financial sustainability plan and supports our strategic plan, goals, and intiatives.||Find a way to shift more resources towards expanding the programming/development base. How to align resources to our needs.|
A membership strategy and implementation plan (including risk assessment) that supports the financial sustainability of Fedora
The strategy and implementation plan
A diverse foundation of contributing members with an expanded, international, actively-contributing membership base
|Our membership supports the financial sustainability of Fedora. We have a diverse foundation of contributing members with an expanded, international, actively-contributing membership base.|
|Assessment Plans as needed for strategies and processes listed in this Governance section.||DOCUMENT|
metrics for assessing each of the governance areas
Assessment procedures for each area, including external review where appropriate
Regular assessments based on defined procedures
|Regular internal and external assessment rhythms for governance, product, staff, membership, and community, that inform an active, adaptive approach to updating the strategic roadmap streams|
|Strategic Planning|| DEVELOP|
A process for regular planning and review of Fedora strategy and the well-functioning of the Leadership Group.
A strategic plan, with mission and vision statements, that encompases topics listed in this Governance section (Leadership, financial sustainability, fiscal strategy, etc.)
The effectiveness of the strategic planning process/es and retool as needed.
|We have established regular processes for high-level planning and review of Fedora strategy, mission, and vision, the well-functioning of the Leadership Group, and other strategic plans and initiatives that fall within the governance responsibilities of the Leadership Group.|
|HIGH LEVEL GOAL:|
|LIST OF ROADMAP VERBS||STATEMENTS FROM VALUE PROPOSITION|
|Investigate / Study / Pilot||Standards-based|
|Test & Verify|
|Audit / Assess|