Voldemort releases, Voldemort Community

[Alex Esterkin]

Hi, all,

I am concerned with the low frequency of Voldemort releases and with
overly modest levels of community participation and contribution.

What can be done to stimulate the Voldemort community and make it more
vibrant, populous, and fast-growing?

Let us pull in ideas, pick the best suggestions, and put them to work.

- Alex Esterkin

[Maarten Koopmans]

To me, as a newbie to voldemort, I am blown away by the simplicity of
the interfaces comoared tonwhat it solves. I just had to spent some
time with Thrift and the apache java http client, and compared to
voldemort.... I'll just be polite and stop here.

But really, the docs have an "insider feel". A set of howtos, when to
use and to avoid, etc. A community needs decent 'hard material' to
bootstrap.

--Maarten

> --
> You received this message because you are subscribed to the Google Groups "project-voldemort" group.
> To post to this group, send email to project-...@googlegroups.com.
> To unsubscribe from this group, send email to project-voldem...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/project-voldemort?hl=en.
>
>

[Alex Feinberg]

Hi Alex,

To address your point re: infrequent releases.

Presently, there's a very significant difference between the master
github version and the last release. As such, it's taking
longer than usual to merge and test the release. Some of the features
e.g., views are also in a separate views and require a merge.

Here is the list of features (most of them merged and already
available in trunk) that will be present in 0.90 release:

http://wiki.github.com/voldemort/voldemort/release-engineering-090

It's an extensive release, so before we cut an "official" release
branch we'd like to test these features extensively. We expect
to do this before the end of September.

More incremental releases (not featuring extensive addition of
functionality) will remain at monthly frequency.

- Alex

[Alex Feinberg]

That's a good point. There's a lot of documentation that's spread
between the Voldemort site and the Voldemort github wiki. Would the
insider feel, in your opinion, be lessened if we moved some of the
documentation from the wiki to the main site?

Thanks,
- Alex

[Geir Magnusson Jr.]

There's an interesting point there, and as a long-time open-source participant and activist (google me) I understand *exactly* where you are coming from.

But let me give you my perspective as a user that has a $400MM+ and growing business (Gilt Groupe) dependent on Voldemort.

It just works.

Voldemort is a critical component used in multiple places in our shopping experience and order processing system - the lifeblood of our business, where the money comes from. I'm responsible for our platform architecture, development and operations, and Voldemort is *literally* the last thing I worry about.

It just works. There are few things in the world - including things with incredible amounts of energy, activity, and hype - that I can say that about.

geir

[Ian Holsman]

personally I think there is an opportunity for a ripatano/cloudera type company here.

They can provide the hand-holding and enterprise add-on's, as well as do a lot more testing, validation, and training required that some companies require.

I've got no issue with the release frequency or the community either.

--
Ian Holsman
I...@Holsman.net
PH: +1-703 879-3128 AOLIM: ianholsman Skype:iholsman

"When did the future switch from being a promise to a threat?" -Chuck Palahniuk

[Maarten Koopmans]

Agreed. It just works, any serious techie can smell that from a
distance. Now if we can get the docs organized slightly better, it
will workfor much more people.

Top-down:
- Getting Started
- Developers
-- client basics
-- version conflicts
-- your important sub scenarios here
- Admins
-- setup
-- tuning

A lot is there already, between the website the wiki and the mail list
archive. I'd say just organize it and fill in the blanks. After next
week (confernce) I am volunteering, but I need somebody to ask
questions.

Best, Maarten