Mostly what you've just done: given explicit permission for Apache to
incorporate your code.
On top of that it would be great if you could help figure out how to
integrate this into the source tree and build process. Please file a Jira
issue if you're able to help. We can iterate on patch files there.
On Nov 9, 2012 2:13 PM, "Martin Kleppmann" <[EMAIL PROTECTED]> wrote:
> Thanks, I'd love to have it part of Apache! What would that involve in
> (Purely selfishly, I quite like working with git and Github rather
> than svn and JIRA, but I'm happy to fit in with Apache's processes.)
> On 9 November 2012 17:57, Doug Cutting <[EMAIL PROTECTED]> wrote:
> > That's awesome!
> > Would you be interested in contributing this to Apache?
> > Doug
> > On Fri, Nov 9, 2012 at 7:05 AM, Martin Kleppmann <[EMAIL PROTECTED]>
> >> Hello Avro world,
> >> A while ago I had some frustration trying to understand a complex Avro
> >> schema, a JSON file thousands of lines long, with many nested record
> >> types. I ended up using regexes in vim to manually transform it into
> >> something readable. I wondered: why isn't there something like
> >> Javadoc, but for Avro schemas?
> >> So I built the tool that I wanted: https://github.com/ept/avrodoc
> >> Avrodoc is still at an early stage, but it already does the job of
> >> giving you Javadoc-like browsable documentation for Avro schemata.
> >> Check the demo on the website, try it yourself, and I'd love to hear
> >> any feedback!
> >> Martin