nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Payne <>
Subject Re: Developer Guide
Date Sun, 01 Feb 2015 14:59:05 GMT

Awesome. I appreciate the feedback! I’ll definitely create those links - good call. Will
review / commit your pull requests (this one and the other one) tomorrow morning.

Thanks again!


From: Daniel Bress
Sent: ‎Sunday‎, ‎February‎ ‎1‎, ‎2015 ‎9‎:‎52‎ ‎AM

   I just looked at the documentation.  I think its really detailed and helpful to new developers.
 Nice work.

   I made two tiny tweaks(fixed some broken markup, and changed a "." to a ":"), and updated
the processor documentation section to reflect the new generated documentation feature.  You'll
see a pull request for that shortly.

   I'd also suggest linking the Processor annotations in the upper sections, to the description
of those annotations in the lower section.  You reference that processors should be using
them above, without describing why.  Having a link to their meaning would clear that up. 
I did not make this change, just suggesting it.

   FYI, one of the markup problems was with: `ProvenanceEventRecord`s
   It doesn't seem to like the `s at the end, so I put a space in between and now it formats
a little better, meaning the monospace shows up, but there is an ugly space between the d
and the s.  Not sure how to fix this 100%.  Any asciidoc gurus out there?

Dan Bress
Software Engineer
ONYX Consulting Services

From: Mark Payne <>
Sent: Friday, January 30, 2015 2:06 PM
Subject: Re: Developer Guide

As suggested by Ryan here, I went ahead and pushed the developer guide to the website, with
a link in the Documentation menu and the Developer menu.

Hopefully it is useful for people - feel free to let me know if anything you read isn’t
clear, and I’ll try to address.



From: Ryan Blue
Sent: ‎Thursday‎, ‎January‎ ‎29‎, ‎2015 ‎4‎:‎13‎ ‎PM

On 01/29/2015 12:54 PM, Mark Payne wrote:
> I’ve put together a first draft version of the developer guide. I uploaded the .html
file to the website, but there’s nothing linking to it. Does it make more sense to add a
link to the “Documentation” menu or the “Development” menu? I would think Development,
but I’m curious which menu others would look at first to try to find a developer guide?

What about both? However the developer gets to the link, it should be
clear enough that it is for developers, so I think it's safe to put in
both places.


Ryan Blue
Software Engineer
Cloudera, Inc.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message