History

Grape was created by Michael Bleigh at Intridea and made its debut at RubyConf 2010 in New Orleans. Jerry Cheung had later joined development. Grape left the Intridea home on August 3rd, 2015 and became an independent project that belongs to the Ruby community. Today Grape is maintained by Daniel Doubrovkine and consists of numerous projects, each individually maintained by a growing group that is defined by rough concensus and running code. Grape is used by many thousands of developers and numerous commercial and non-commercial applications. Grape itself had 6,462 stars and 726 forks on Github as of August 3rd, 2015.

Organization Maintainers

• Daniel Doubrovkine, @dblock, CTO at Artsy.net, New York, USA.
• Michael Bleigh, @mbleigh: CEO at DivShot, Los Angeles, USA.

Individual Project Maintainers

grape

• Dmitry Dedov, @dm1try: Minsk, Belarus.
• Adam Gotterer, @adamgotterer: New York, USA.
• Vladimir Kochnev, @marshall-lee: Saint Petersburg, Russia.
• Kunpei Sakai, @namusyaka: Tokyo, Japan.

grape-entity

• Vladimir Kochnev, @marshall-lee: Saint Petersburg, Russia.
• Mark Madsen, @idyll: The Great White North.

grape-swagger

• Tim Vandecasteele, @tim-vandecasteele: Gent, Belgium.
• Craig S. Cottingham, @CraigCottingham: Olathe, Kansas, USA.
• Peter Scholz, @le_fnord: Leipzig, Germany.
• Kirill Zaitsev, @Bugagazavr: Moscow, Russia.

grape-swagger-rails

• Alexander Logunov, @unloved: Cheboksary, Russia.
• Andrew Schuster, @aschuster3: Atlanta, Georgia, USA.

grape-rabl

• Piotr Niełacny, @LTe: Wrocław, Poland.

grape-active_model_serializers

• Jonathan Evans, @jrhe: London, UK.
• Teng Siong Ong, @siong1987: San Francisco, USA.
• Darren Cheng, @drn: San Francisco, USA.

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.