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 d
+1 for Gerrit. I have experience with it so let me know if you need my help.
On Fri, Mar 28, 2014 at 9:39 AM, Keith Turner wrote:
> On Fri, Mar 28, 2014 at 12:23 AM, Sean Busbey >wrote:
>
> > Aside from the occasional stability problem, I really like the idea of
> > using ReviewBoard. It has t
On 3/28/14, 9:39 AM, Keith Turner wrote:
On Fri, Mar 28, 2014 at 12:23 AM, Sean Busbeywrote:
>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.
>
Another plus is tha
Why not have the design doc in markdown only? I assume its not expressive
enough?
For the ACCUMULO-1000 design doc I used asciidoc to try that out.The
asciidoc source was readable like markdown and maybe more expressive than
markdown
On Fri, Apr 4, 2014 at 12:45 PM, Josh Elser wrote:
> On
On Fri, Apr 4, 2014 at 12:45 PM, Josh Elser wrote:
>
> The localized commenting on reviewboard is nice, but making updates to the
> document is definitely not fun.
>
Why not use GitHub? it provides most of what you're using RB for now, but:
- Markdown is easily edited/previewed on GitHub
- pull
On Fri, Apr 4, 2014 at 1:40 PM, Alex Moundalexis wrote:
> On Fri, Apr 4, 2014 at 12:45 PM, Josh Elser wrote:
> >
> > The localized commenting on reviewboard is nice, but making updates to
> the
> > document is definitely not fun.
> >
>
> Why not use GitHub? it provides most of what you're using R
Granted, the syntax is probably expressive enough to read, but viewing
it in plaintext isn't the same as having it "rendered".
The lack of varying font size is probably the most noticeable problem.
Trying to read a table in raw markdown is also a good example. Code
snippets also are difficult
On Fri, Apr 4, 2014 at 12:49 PM, Keith Turner wrote:
> On Fri, Apr 4, 2014 at 1:40 PM, Alex Moundalexis >wrote:
>
> > On Fri, Apr 4, 2014 at 12:45 PM, Josh Elser
> wrote:
> > >
> > > The localized commenting on reviewboard is nice, but making updates to
> > the
> > > document is definitely not
On Fri, Apr 4, 2014 at 1:49 PM, Josh Elser wrote:
> Granted, the syntax is probably expressive enough to read, but viewing it
> in plaintext isn't the same as having it "rendered".
>
> The lack of varying font size is probably the most noticeable problem.
> Trying to read a table in raw markdown
On 4/4/14, 2:09 PM, Keith Turner wrote:
On Fri, Apr 4, 2014 at 1:49 PM, Josh Elser wrote:
>Granted, the syntax is probably expressive enough to read, but viewing it
>in plaintext isn't the same as having it "rendered".
>
>The lack of varying font size is probably the most noticeable problem.
>
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 wrote:
> I would really like to review the design doc posted on
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 wrote:
> I've seen other projects upload a file to the appropriate JIRA and that
> seemed to work well. I don't have specific experien
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
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 p
On Fri, Mar 28, 2014 at 12:23 AM, Sean Busbey wrote:
> 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.
>
Another plus is that the inline discussion threads go w/ a
Could this be a good test case for Gerrit?
On Fri, Mar 28, 2014 at 12:23 AM, Sean Busbey wrote:
> 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 f
16 matches
Mail list logo
