Call for contributors: Dredd Hooks for Java #875
Description
The mission of Dredd was always to let people do design-first approach with APIs. People can generate their API design documents from their code, but we wanted them to think first, to have the API description upfront to any coding. Why? Because we believe that produces much better designs and usability of the interface in question. This wouldn't be possible without Dredd, which closes the loop - during and after the implementation phase, one can use it to check they actually implemented what they designed.
The world of Java is one big area still waiting to be evangelized in this regard. With Apiary (the company behind Dredd) being recently acquired by Oracle, we have now much larger contact with the Java world then ever before. This is an opportunity for us to go and preach design-first approach there, with significant impact. But to do that, we first need to find a hero who contributes and maintains Java hooks for Dredd (we can do JavaScript, C++, Python, Ruby, you name it... but we're short of any Java people).
I'll be personally looking for someone inside or outside the company, but I wanted to file this issue to bring visibility to this demand, so anyone who walks by the Dredd issues knows this would be wanted and appreciated ✨