spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cody Koeninger <c...@koeninger.org>
Subject Re: Design docs: consolidation and discoverability
Date Fri, 24 Apr 2015 14:09:02 GMT
My 2 cents - I'd rather see design docs in github pull requests (using
plain text / markdown).  That doesn't require changing access or adding
people, and github PRs already allow for conversation / email notifications.

Conversation is already split between jira and github PRs.  Having a third
stream of conversation in Google Docs just leads to things being ignored.

On Fri, Apr 24, 2015 at 7:21 AM, Sean Owen <sowen@cloudera.com> wrote:

> That would require giving wiki access to everyone or manually adding people
> any time they make a doc.
>
> I don't see how this helps though. They're still docs on the internet and
> they're still linked from the central project JIRA, which is what you
> should follow.
>  On Apr 24, 2015 8:14 AM, "Punyashloka Biswal" <punya.biswal@gmail.com>
> wrote:
>
> > Dear Spark devs,
> >
> > Right now, design docs are stored on Google docs and linked from tickets.
> > For someone new to the project, it's hard to figure out what subjects are
> > being discussed, what organization to follow for new feature proposals,
> > etc.
> >
> > Would it make sense to consolidate future design docs in either a
> > designated area on the Apache Confluence Wiki, or on GitHub's Wiki pages?
> > If people have a strong preference to keep the design docs on Google
> Docs,
> > then could we have a top-level page on the confluence wiki that lists all
> > active and archived design docs?
> >
> > Punya
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message