The FOLIO wiki contains the project roadmap.
Some of the important forums to collaborate, discuss FOLIO, interact with other participants, and find starting points for documentation.
|discuss.folio.org||The discussion area and mailing lists is via Discuss.||How to | Join at front page|
|wiki.folio.org||Position papers, roadmaps, meeting agendas and minutes, Special Interest Group (SIG) spaces, other guidelines.||How to | Join at front page (same account as Issues)|
|dev.folio.org||Developer documentation. Also leads to documentation at each repository.||How to|
|issues.folio.org||The issue tracking and bug tracking system.||How to | Join at front page | Guidelines|
|github.com/folio-org||The source-code repositories are via GitHub.||How to | List of repos | Contributing|
|folio-project.slack.com||Real-time chat is via Slack.||How to | Join|
|Other secondary communication channels.||How to|
The FOLIO community consists of many significant contributors. Among them are community representatives which include:
- Sebastian Hammer, Index Data
- Christopher Spalding, EBSCO
- Michael Winkler, OLE
The FOLIO developer community consists of:
- Index Data, which leads the technical development of the FOLIO software
- Several software engineering teams
- Contributing developers from the community
- Many supporting individuals whose contributions feed into and guide the development process
Here we list the engineering roles and contacts for the various parts of the project. Team members can be contacted via the collaboration tools listed above.
Engineering core team
The engineering core team sets strategic direction for technical architecture in the FOLIO software:
- Sebastian Hammer (project lead)
- Nassib Nassar (project lead - technical)
- Jakub Skoczen (technical project manager)
- Adam Dickmeiss
- Vince Bareau
- Peter Murray (community)
Subproject core teams
Several components of the FOLIO software are distinct subprojects and have a core team of software engineers with commit-level access to the source code repositories. Each subproject generally has a lead developer who is responsible for selecting new core team members from the community.
- okapi: Adam Dickmeiss (lead), Heikki Levanto, Jakub Skoczen, John Malconian, David Crossley
- mod-auth, mod-users: Kurt Nordstrom (lead)
- mod-metadata: Marc Johnson (lead), Ian Ibbotson, Jakub Skoczen
- mod-circulation, mod-configuration: shale
- raml-module-builder: shale, Adam Dickmeiss, Julian Ladisch
- raml: shale, Adam Dickmeiss
- stripes-core: Niels Erik Nielsen, Jason Skomorowski, Mike Taylor, John Coburn
- stripes-components: John Coburn (lead)
- stripes-connect: Jason Skomorowski, Mike Taylor, Niels Erik Nielsen
- stripes-loader: Jason Skomorowski (lead)
- stripes-sample-platform: Jason Skomorowski (lead)
- okapi-stripes: Wolfram Schneider (lead)
- ui-users: Mike Taylor, Niels Erik Nielsen, Jason Skomorowski, John Coburn, Matt Connolly, Jeremy Huff
- ui-items: Mike Taylor
- ui-okapi-console: Mike Taylor, Niels Erik Nielsen
- cql2pgjson-java: Julian Ladisch (lead)
- container-perf-tests: Adam Dickmeiss (lead), Jakub Skoczen
- folio-sample-modules: Heikki Levanto (lead), Niels Erik Nielsen
- folio-ansible: Wayne Schneider (lead), John Malconian
- folio-org.github.io: David Crossley (lead)
There are many ways to contribute to FOLIO development, for example:
- Contributing directly to the software development.
- Engaging with the issue tracker.
- Joining the conversations.
- Participating in Special Interest Groups.
Guidelines for Contributing Code: GitHub Flow, feature branches, pull requests, version numbers, coding style, tests, etc.
Which forum to use for communication: Issue tracker, Slack chat, Discuss discussion, GitHub pull requests. Some guidelines about when to use each, and some usage tips.
Other guides and best practices.