Skip to end of banner
Go to start of banner

Tech Council Election May/June 2021

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

The FOLIO Technical Council's charter is to maintain the community’s technical policies, best practices, infrastructure, and monitor the operational health of the FOLIO project. It will also track and report Technical Debt and facilitate architectural decisions as needed by the community. It operates with close collaboration with the Community and Product Councils. 

Seats on the Technical Council are available to Members of the FOLIO community, in accordance with the FOLIO Governance Model. Member is defined as an individual who is an employee or a sponsored contractor of a Member Organization. Individuals will be elected to seats for two year terms. Shorter terms may be required for the initial transition period or to fill seats that become vacant between elections.

There will be up to 11 members selected for the Technical Council.

The Technical Council will be seeking nominees who have deep experience with one or more of:

  • Strong collaboration skills, able to drive decisions that champion the interests of the community and project
  • Deep understanding of software development processes and technologies required for a modern services oriented application
  • Agile software development methodologies, including Epic, Feature and Story creation
  • Knowledge of DevOps and Quality tools and processes
  • Experience with FOLIO’s code-base, technologies and development processes
  • Frequent contributor to FOLIO’s code-base
  • Experience managing technology, technical debt, and competing priorities 
  • Participating in and/or managing open community governance
  • Library management systems and library workflows
  • Leadership of development or other technical teams

Dates

Nominations will be collected from May 18, 2021 through June 4, 2021 

Voting will be open from June 7, 2021 through June 25, 2021

Council becomes active the week of July 12, 2021

Nominees

We are collecting nominees using this form: https://forms.gle/rojfBgzh2ZXCVa6q7

The following people have been nominated:

NameOrganizationStatement
Aaron NeslinFive Colleges

I am nominating Aaron Neslin, 5 Colleges FOLIO implementation/maintenance coordinator. Aaron is collaborative, conscientious, and technically skilled. He has a great deal of experience brining up new library systems.

Phil RobinsonCornell University

IT leader with 20+ years’ experience in these roles: Director of Library Systems (current), Assistant Director of Integration, Technical Architect, Manager of Custom Applications, and Sr Developer. I champion cloud-first and DevOps methodologies. In FOLIO I participate in these SIGs: SysOps, User Management, and Support. I attended the last WOLFCon and ran tests in the last two FOLIO Bug Fests.
At Cornell I lead FOLIO systems integration efforts including identity management, user import, Caiasoft, accounting, bursar export (PO of fee/fine exports), BorrowDirect (OCLC Relais), and others. On the Technical Council I would focus on: systems integrations, technical debt, DevOps and IT security best practices, and enhancing community outreach.

Mark DeutschDuke University

I'd like to continue being a member of the Technical Council so that I can continue to be a voice that pushes to prioritise the needs of all kinds of users at all kinds of institutions. Whether those users are interacting with the UI, developing integrations, or customising their installation, we shouldn't lose focus of them when debating technical questions.

While working for Duke University, I've spent time as a member of the Stripes Core and ERM teams. More recently, I've been working on more varied projects including the Courses front-end and edge modules, and integrating Folio into Duke's systems.

Craig McNallyEBSCO Information Services

* Developer on FOLIO for 4+ years with contributions in many domains, e.g. acquisitions, finance, permissions, OKAPI, Spring/RMB, authn/authz, edge APIs, etc.
* Ongoing participation and leadership in several FOLIO groups: Tech Council, Tech Leads, Security Group.
* Extensive experience with FOLIO DevOps/SysOps - Almost 5 years on the EBSCO FSE (FOLIO Hosting) team.
* Strong interpersonal and organizational skills with a track record of getting things done. At various times have worked with many of the different SIGs and other groups within the community.
* Not afraid to have an opinion and make decisions.
* Excellent communicator - This is necessary to be an effective leader on a project with the size/scope that FOLIO has.

Jakub SkoczenIndex Data

Jakub is Index Data's Lead Software Architect and has been a member of the original FOLIO team behind the design and development of Okapi, RMB and Stripes. Currently Jakub is primarily the Product Owner for Core Platform team where he oversees the development of core FOLIO modules and frameworks. He is also the lead of the community DevOps team that maintains FOLIO's development environments, CI/CD tools and performs release management.

Jeremy HuffTexas A&M University

I am happy to put my name forward as a nominee to serve on the folio Technical Council. I have been a member on the council for the past six months, and have been a contributing member to the folio community for the past five years.

I am a Software Application III for Texas A&M University Libraries, and in that capacity I have had the opportunity to work on many open source projects, including FOLIO. Through my role as a developer for the libraries I have gained experience in all the areas which pertain to this appointment.

It would be my pleasure to continue to serve the FOLIO project on this council.

Sha JiangJIANGSU JIATU NETWORK TECHONOLOGY CO.,LTD.

Master of software engineering management, Peking University. Head of JIATU FOLIO team. 15 years of software development experience. 8 years management experience in software development team. 3 years experience in FOLIO localization & deployment.

Raman AuramauEPAM

I am an engineer with strong technical background in Java development and micro-service design, and with main professional focus in solution architecture. Having ~15 years of experience in software engineering I can now present myself as a skilled Solution Architect and Team Leader with proven success stories in different domains.
I've been working with EBSCO for 4 years, and ~0.5y of them with FOLIO, so I've already got domain knowledge, understanding of terminology and processes.
Since currently EPAM contributes a lot into FOLIO success (together with other Member Organizations of course), I strongly believe all my experience and skills should be useful for the community, and I can act as a bridge between Tech Council and EPAM teams.

Fred SchumacherUniversity of Colorado, Boulder

As the Program Manager for library technologies, I have been directly involved in assessing FOLIO as a viable next-gen LSP. In January 2021, CU Boulder launched our own FOLIO@CU initiative with a projected go-live date of mid 2022. I am the designated project owner and tech lead.

I have 30+ years in engineering/IT and have performed senior roles in a variety of sectors. My experience has been mainly with large enterprise systems. I am also an experienced leader with significant experience in strategy development, and building and leading high performance teams.

To that end, I would welcome an opportunity to contribute to the FOLIO open source project as a member of the Technical Council.

Zak BurkeCornell University/FOLIO Community

A front-end developer for FOLIO since 2017, I am a current member of the Tech Council and Support SIG, UI team lead for several core UI apps and modules, and unofficial convener of weekly UI developer meetings. The modules I regularly commit to rely on more than 50 different Okapi interfaces, providing me with broad insight both into FOLIO's features and its technical underpinnings and challenges. I recognize the need to balance individual teams' desires to operate nimbly and independently within their domains with the need to establish common, project-wide expectations, services, and guidelines. I am particularly concerned with a11y and i18n, making sure FOLIO is usable by the widest possible audience.

Tod OlsonUniversity of Chicago

I am a Systems Librarian and manage our ILS group. I have worked in library systems for three decades in various technical and analytic roles. I have a broad understanding of library data, data lifecycle, applications, integrations, and how they support a library’s operations and mission. I often act as a bridge between technical staff, non-technical staff, operations and administration.
I currently serve on the TC, have been active in the Reporting and SysOps SIGs, working groups, provided analysis, and presented issues to one group on behalf of another. I advocate taking a longer view of our technical decisions and investments. I believe I bring value to the TC and would like to continue to serve.

Dennis BenndorfGBV (Goettingen)

I am Head of Department System Engineering at VZG/GBV (non-profit) and as such responsible for the technical implementation and maintenance of the GBV Folio plattform (based on Kubernetes) and other hosting services. I studied Economics with a focus on IT. I have 3 years experience in running Folio and about 12 years in running conventional library management systems in a hosted environment for over 200 libraries. My technical focus is on providing services in a bigger scope with the use of scalable systems and automation (e.g. Kubernetes, Ceph, Puppet). I am a member of our internal CBS2Folio project which aims to connect Folio to our central catalog for title data retrieval and a member of the German SysOps SIG.

Chulin MengLehigh University

I have been leading the library systems department for more than 15 years. I have experience with both commercial ILS (Voyager, SirsiDynix) and Open Source Library Management Platform (OLE, FOLIO). I led Lehigh University’s FOLIO implementation effort to bring FOLIO in production in August 2020. I have been actively participating in the FOLIO Implementers Group.

As a member of the Technical Council, I would like to advocate for addressing critical technical challenges we are seeing as a FOLIO production library, such as Data Integrity, Data Import/Export, and Performance issues.

Marc JohnsonKnowledge Integration (K-Int)

I would very much like to help the community make cohesive decisions and reflect upon the impact, and improve the collaboration between the developers and the users of system

I am the Prokopovych Technical Lead and regular participant in the Technical Council meetings, having worked on FOLIO for more than 5 years

I’ve worked as a developer and technical lead for more than 15 years using a variety of tools and architectures across different domains. I've worked with Agile practices (and been involved in the Agile community) for most of that time

I’ve participated in the whole development lifecycle ranging from requirements gathering and support to architecture and operations. I am a keen advocate for Continuous Delivery, DevOps and TDD

Steffen KöhlerLeipzig University Library

I am a business informatics specialist and have been working in the library environment since 2013. As a developer, mostly Java, I have been involved in several projects in the context of library needs and I am equally experienced in bringing together different stakeholder interests. These projects were mainly based on open source software stacks and included participation in development.

Regarding FOLIO I have two years of experience with on-premises operation on Kubernetes at Leipzig University Library, with two tenants being productive for some time now. Therefore, I would like to bring these experiences to the TC and at the same time actively participate in open questions.

  • No labels