History

Grape was created by Michael Bleigh at Intridea and made its debut at RubyConf 2010 in New Orleans. Jerry Cheung later joined development. Grape left Intridea on August 3, 2015 and became an independent project belonging to the Ruby community.

Today, the ruby-grape organization maintains the framework and ecosystem projects through individual project teams, rough consensus, and running code.

Maintainers and Contributors

See the organization’s public members, Grape contributors, and each project’s README and contribution guide for its maintainers and collaboration process. These live resources avoid treating an old roster or employer affiliation as current.

Participating in the Grape Community

We welcome all contributors to the Grape ecosystem, built upon rough consensus and running code, a principle described in the Tao of IETF. We are highly inclusive, try to be nice and helpful to both experienced and new developers. We encourage you to participate and to be pragmatic. To quote David Clark, “We reject kings, presidents and voting”, and Jon Postel, “Be conservative in what you send and liberal in what you accept.”

We also have a contributor code of conduct.

Becoming a Project Maintainer

Team members from organizational maintainers down to individual project nominate individuals who have significantly contributed to the project to join the team. We recommend requiring a simple majority and no significant objections (also known as rough consensus) as a sufficient criteria for acceptance. A great first step in becoming a maintainer of any project could be making a release.