O G wrote:
> Hello,
>
> I just heard LucidEra is shutting down. Since LucidEra was a LucidDB
> sponsor, I wonder what this means for the future of this project?
>
> Thank you and sorry for the possibly touchy question.
Hi Otis and everyone,
Coincidentally, I was about to send out a message on this topic, so I'm
glad you asked. LucidDB is the only open source DBMS built from the
ground up specifically for data warehousing, and it is important to many
people for an option like that to remain available.
From its inception, LucidDB has had dual sponsorship from both LucidEra
(a startup) and The Eigenbase Project, a non-profit. Sponsorship from
Eigenbase continues unchanged, and the project as a whole has certainly
grown beyond the seeding from those sponsors into a community which
includes all of you. So although the LucidEra news is certainly a loss
for the project, I'm confident that the tree is already healthy and
thriving on its own and will continue to flourish without the aid of one
of the original gardeners, if you'll pardon the cliche.
In fact, I actually left LucidEra last October, but have continued to
put most of my time into LucidDB feature development, release, and
promotion; and I intend to keep that up. So from a project leadership
perspective, LucidDB has already been independent of LucidEra for quite
some time. Other developers previously at LucidEra remain involved as
well. In addition, a sister project for parallelization and clustering
is being incubated at firewater.sourceforge.net; this will take the
technology underlying LucidDB to the next level of scalability.
Because LucidDB is built on the Eigenbase platform, it automatically
inherits improvements contributed by other participants in that
ecosystem (such as SQLstream, which has quite a few developers working
on it--this includes Julian Hyde, who is also the Mondrian project
founder, and who has been helping to promote LucidDB as an ideal DB for
OLAP). Julian has actually contributed directly to the optimizer used
by LucidDB in a number of cases.
We are also working on growing the Eigenbase ecosystem in the wake of
the Oracle acquisition of Sun/MySQL--storage engine vendors are looking
for new integration options in order to maintain their independence, and
Eigenbase could be a good fit, so some of them have approached us
already, and we're prototyping potential solutions.
This transition time actually opens wide a great opportunity for
community members to step up and dig deeper into LucidDB development and
promotion. We already have a few community-initiated investigations
underway into areas such as named sequence support, Hibernate dialect,
and C++ client connectivity, and I'd be very encouraged to see more of
those in areas such as packaging and usability improvements.
So...let me flip the question around and ask you, how would you like to
be involved in the future of LucidDB to ensure that it continues to
thrive? Do you have ideas and resources you can contribute? What
changes would you like to see? A developer mailing list? Source code
replicated from Perforce to Subversion/git for easier access (I'm
working on this one)? Let's hear it...
Thanks for your support,
JVS
p.s. We'll be updating some of the web pages to reflect the impact of
the news.
------------------------------------------------------------------------------
_______________________________________________
luciddb-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/luciddb-users
