Until it becomes untenable to manage/maintain, I'd be in favor of keeping a page somewhere on the Accumulo site that we can allow people to request listing on.

Happy to keep these links up to date and process any requests.

On 2/28/14, 8:13 PM, Arshak Navruzyan wrote:
I like the single ecosystem page approach.

If I am new to Accumulo and visit this page, I would expect to see a list
like this under the heading "What are Accumulo related projects I should
care about?"

- Non-Java client libraries (C++, Python, Scala ...)
- Event processing interfaces (Storm ...)
- Querying (Hive, Pig ...)
- Data pipelines (Cascading/Scalding, Flume)
- Serialization (Avro, Protobuf, Thrift)

I am sure that there are many more however as a new user something like
this seems like "table stakes".


On Fri, Feb 28, 2014 at 8:39 PM, Christopher <[email protected]> wrote:

I agree with both points.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Fri, Feb 28, 2014 at 2:34 PM, Sean Busbey <[email protected]>
wrote:
On Fri, Feb 28, 2014 at 2:16 PM, Arshak Navruzyan <[email protected]>
wrote:

Sean,

I was just using the Cascading code as an example.  Not suggesting we
hijack Anagha's project :)

I think there is a benefit to having a "standard" set of contribs that
have
been reviewed / tested.  Something similar to this:
http://docs.mongodb.org/ecosystem/

I'm concerned that letting new users go hunting for contribs on their
own
gives (which may or may not work, may or may not be documented) gives
the
Accumulo project a little bit of an incomplete feeling.  Obviously it's
not
possible to take on the responsibility to moderate every possible
contribution but some basic/obvious ones would be helpful.

Arshak



I definitely agree on the importance of a curated set of related outside
projects. I'd much rather we not have links that answer the question "How
do I search github for Accumulo projects?" since that doesn't really
answer
the question of "What are Accumulo related projects I should care about?"

Maybe we shouldn't continue to separate "contrib projects" in Accumulo
and
"ecosystem projects" that are hosted and run elsewhere to the extent we
currently do. If I'm looking for examples of things that leverage
Accumulo
I probably don't want to look at two different places on our website.
Maybe
we could list the Accumulo hosted contribs and the external projects on
an
ecosystem page? "Powered by Accumulo" maybe?


Reply via email to