Aside from the occasional stability problem, I really like the idea of using ReviewBoard. It has the best option for in-context commenting amongst our options at Apache AFAICT.
I think the finished doc (preferably in markdown) could just be attached to the jira that's relevant. I'd like to see a pipeline for incorporating information from the design doc into our user facing documentation or javadocs, but I wouldn't want to just push them over as-is since the audience is different. -Sean On Thu, Mar 27, 2014 at 7:37 PM, Josh Elser <[email protected]> wrote: > There's also the confluence wiki that we could get space on, I think. > > A wiki isn't very well suited to making inline comments though (unless we > break up the design doc into individual wiki pages... hmm). > > > On 3/27/14, 5:06 PM, Bill Havanki wrote: > >> Another idea: Use a wiki? We could establish an area beneath the Hadoop >> wiki [1]. >> >> [1] http://wiki.apache.org/hadoop/ >> >> >> On Thu, Mar 27, 2014 at 7:02 PM, Mike Drob <[email protected]> wrote: >> >> I've seen other projects upload a file to the appropriate JIRA and that >>> seemed to work well. I don't have specific experience with that, though, >>> so >>> I cannot warn you about any pitfalls. >>> >>> >>> On Thu, Mar 27, 2014 at 6:05 PM, Keith Turner <[email protected]> wrote: >>> >>> I would really like to review the design doc posted on ACCUMULO-378, but >>>> >>> I >>> >>>> would rather not do that on Google docs. I would like to use Apache >>>> infrastructure and have the discussion around the design doc archived in >>>> the mailing list. >>>> >>>> One option is to use Markdown + RB and never check the design documents >>>> >>> in >>> >>>> anywhere. Basically we generate a patch that posed to RB, but never >>>> checked in. Or maybe we could check the design docs in somewhere. >>>> >>>> Does anyone have any suggestions? >>>> >>>> >>> >> >> >>
