These two seem to be covered pretty well in the below text.
Community
Code / Plans.
-----Original Message-----
From: DeBardeleben, Ruth L
Sent: Tuesday, May 08, 2007 9:29 AM
To: [email protected]
Subject: RE: [Fwd: WARNING - 2 days to deadline for May reports]
Ah good. Thanks Filip. Excellent point.
So:
--- begin board report text ---
One of the Lokahi committers (Steve Toback) attended ApacheCon, along
with other community members from Merck. Initial draft of Lokahi's data
model for the proposed switch to a Jackrabbit back-end was worked out
with input from Jackrabbit community (Jukka Zitting). Steve presented at
FastFeather track (15-min sessions) & gave an short overview of what
Lokahi does and what it currently supports. Discussed possibilities for
using Lokahi to manage Geronimo servers as well. An initial roadmap of
features has been planned, and development will be moving in the
direction of the new roadmap.
The conversion to JCR takes first priority because it will mitigate
existing difficulties that hinder community-growing, namely:
(a) Oracle as db requirement, which reduces the potential user "market";
(b) inability to run Lokahi on a standalone machine, due to (a);
(c) complicated build process, partially due to (a);
And JCR will provide the following benefits:
(a) database independence (run Lokahi with a file system backend to try
it out, or use a more robust storage platform for production) + embedded
Derby db
(b) lower barrier to contribution, see (a)
(c) versioned objects -- the basis for storing versioned configuration
files & foundation for a future "undo" feature requested by users.
Great for real-world use in regulated environments which require
detailed audit trails of who-changed-what-and-when.
--- end board report text ---
anything else?
Ruth
-----Original Message-----
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 9:11 AM
To: [email protected]
Subject: Re: [Fwd: WARNING - 2 days to deadline for May reports]
It would be good to add in that an "initial" roadmap of features has
been planned, and that development will be moving in the direction of
the new roadmap
and maybe mention some of the stuff on the road map
Filip
DeBardeleben, Ruth L wrote:
Here's my take on it:
One of the Lokahi committers (Steve Toback) attended ApacheCon, along
with other community members from Merck. Initial draft of Lokahi's
data
model for the proposed switch to a Jackrabbit back-end was worked out
with input from Jackrabbit community (Jukka Zitting). Steve presented
at
FastFeather track (15-min sessions) & gave an short overview of what
Lokahi does and what it currently supports. Discussed possibilities
for
using Lokahi to manage Geronimo servers as well.
any edits, folks?
-----Original Message-----
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 11:05 PM
To: [email protected]
Subject: [Fwd: WARNING - 2 days to deadline for May reports]
Drat - forward of the belated reminder.
------------------------------------------------------------------------
------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and
then
delete it from your system.
------------------------------------------------------------------------
------
------------------------------------------------------------------------
------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------
------
------------------------------------------------------------------------
------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------
------
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
------------------------------------------------------------------------------
