Since our last Board message that announced the launch of Steering Committees and making an open call for volunteer leadership, we have spent a significant amount of time discussing the future of our organization.

Those conversations covered sustainability, governance, infrastructure stewardship, community participation, membership, sponsorship, and the role Ruby Central should play in supporting the Ruby ecosystem for years to come.

As those discussions evolved, it became clear that our bylaws no longer reflected how Ruby Central operates today, nor how we want it to operate in the future.

Many of the governing documents that served Ruby Central well in the past were written for a smaller organization operating in a very different environment. Over the past 22 years since Chad Fowler, Jim Weirich, David Alan Black, Paul Brannan and Richard Kilmer launched RubyGems at RubyConf , the RubyGems.org service has become critical infrastructure for the global Ruby community, Ruby Central's responsibilities have grown, and the ecosystem itself has evolved considerably.

What started as a conversation about ideas for the future of Ruby Central ultimately led us to an important realization that, before we could build what comes next, we needed to modernize the foundation we were building on.

Today, we're sharing a comprehensive update to Ruby Central's bylaws aimed at modernizing our governance, improving transparency, clarifying responsibilities, and supporting the long-term sustainability of the organization.

You can read the full bylaws here.

Why Now?

Interestingly, we didn't originally set out to rewrite the bylaws.

Our initial goal was to share updates around governance, membership, steering committees, and new ways for the community to participate in shaping Ruby Central's future. As we worked through our ideas, we repeatedly found ourselves running into limitations, ambiguities, or missing structures within our existing framework.

The more we explored new approaches to community participation, committee structures, and organizational sustainability, the clearer it became that our bylaws were no longer providing the framework we needed.

What began as planning for future initiatives became a broader review of how Ruby Central operates and how we want it to evolve in the years ahead. This bylaw update is the result of that work by our Board.

What Changed

While many of the updates are administrative or clarifying in nature, several themes guided the revision. For those interested in the complete document, the updated bylaws are available here.

Clearer Governance

The updated bylaws more clearly define the roles and responsibilities of the Board of Directors, officers, committees, and participants in Ruby Central's governance processes.

We've clarified decision-making authority, delegation of responsibilities, conflict-of-interest expectations, and accountability throughout the organization.

Support for Participatory Governance

One of the most significant additions is the introduction of a formal framework for participatory governance.

Ruby Central remains legally governed by its Board of Directors, which is required to retain full fiduciary responsibility for the organization. At the same time, we believe the broader ecosystem should have meaningful opportunities to help inform decisions that affect Ruby's future.

The updated bylaws establish a structure that will allow contributors, supporting members, sponsors, and other stakeholders to participate in a more organized and sustainable way while preserving the Board's responsibilities.

Stronger Committee Structure

The bylaws now formally recognize both operational steering committees and advisory committees.

These groups will create opportunities for more members of the community to contribute their expertise and help advance Ruby Central's mission while maintaining clear legal boundaries around authority, accountability, and financial oversight. We need your help, and this is the first step we needed to take to more formally accept it.

Committees can support initiatives, provide guidance, and help execute important work, while ultimate responsibility remains with the Board.

Transparency and Financial Stewardship

The revised bylaws place greater emphasis on transparency, financial reporting, governance documentation, and responsible stewardship of community resources. This may result in more work for us, but we believe it will be an improvement for transparency and trust.

As an organization responsible for shared infrastructure relied upon globally, we believe openness and accountability should be reflected not only in our actions but also in our governing documents.

Reducing Concentrated Influence

We also introduced governance safeguards intended to reduce the concentration of influence within the organization.

The updated bylaws include provisions designed to limit excessive representation from any single company or organization and reinforce the principle that Ruby Central exists to serve the broader Ruby ecosystem.

Long-Term Organizational Stability

The revised bylaws introduce staggered board terms, clearer participation expectations, continuity provisions, vacancy procedures, and more clearly defined leadership responsibilities.

We also clarified how organizational assets will be stewarded in the future, helping ensure that Ruby Central's resources remain dedicated to open source and community-focused purposes aligned with our mission.

Together, these changes are intended to help Ruby Central remain stable, resilient, and effective for the long term.

Looking Ahead

We see this bylaw update as a foundation for our work ahead.

While bylaws may not be the most visible part of a nonprofit, modernizing them removed a number of obstacles that were standing in the way of initiatives we're eager to share with the community.

We have published the new bylaws on our page for you to review in your own time.

In the coming weeks, we'll be publishing updates on membership, sponsorships, steering committees, governance participation, and other efforts designed to strengthen both Ruby Central and our broader Ruby ecosystem.

Shout out to Jim Remsik for keeping us honest in taking much longer than the two weeks Jey and I expected to provide another update. We'll do better now that our Board is unblocked.

We'd also like to share an update to Ruby Central's officer roles. To better align responsibilities with individual strengths and availability, the Board has reorganized its officer positions:

  • Ran Craycraft, President
  • Jey Flores, Vice President
  • Freedom Dumlao, Treasurer
  • Brandon Weaver, Secretary
  • David Corson-Knowles, Board Member

Our goal is to build a Ruby Central that is more participatory, more transparent, more nimble, and more sustainable while becoming less dependent on concentrated sources of funding and more reflective of the broader Ruby ecosystem itself.

We're grateful to everyone who has reached out about joining and leading a Steering Committee, contributed feedback, ideas, and perspective throughout this process, and we're looking forward to continuing this work together. With this groundwork in place, we’re excited for the formal launch of all 5 steering committees at RubyConf Tuesday, July 14th – Thursday, July 16th, 2026. Reach out to us to engage.

Read the Ruby Central Bylaws

Ran Craycraft

Ruby Central Board of Directors President

Update (June 5, 2026): Added additional access links to the bylaws throughout the document for easier access.