bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <>
Subject [jira] [Commented] (BIGTOP-718) Update wiki for component requirements
Date Sat, 29 Sep 2012 04:11:08 GMT


Roman Shaposhnik commented on BIGTOP-718:

Now that we've graduated, I believe that having a clearly spelled out set of bylaws as part
of our permanent web site is a must for the project. As Tom pointed out, our ASF Board resolution
is an obvious kernel for this document, but obviously we have to drill down into more details
to arrive at something similar to:

Eli has offered a nice list of additional things that require further clarification and I
see that Cos and others chimed in with really good questions. It seems like we need a way
to coalesce all of this input and follow up with a PMC vote to make it official.

If this sounds like a reasonable way forward we can start a wiki as a tool for coalescing
all these ideas.

The timing is right -- I'm in the process of post-graduation infrastructure move and this
feels like exactly the right thing to get nailed down now.
> Update wiki for component requirements
> --------------------------------------
>                 Key: BIGTOP-718
>                 URL:
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
> I think some updates are in order for this Wiki page in order to more accurately reflect
the goals of the project:
> For starters, it should have a more prominent link on the Wiki and a summary on the project
home page. Not only is it going to be an increasingly common question, but it's an important
part of defining what "Bigtop" is really all about. I know when I first started on the project
it was the first thing I looked for.
> Second, we say projects have to be "Big Data"-related. Judging by other documents* and
existing discussions regarding new components, it seems like we really mean to say "Hadoop"-related,
and I think the extra focus would be good (having said that, I do think of Spark as Hadoop-related).
> *

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message