Return-Path: X-Original-To: apmail-incubator-directmemory-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-directmemory-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E28AA985A for ; Tue, 6 Dec 2011 12:32:23 +0000 (UTC) Received: (qmail 17847 invoked by uid 500); 6 Dec 2011 12:32:23 -0000 Delivered-To: apmail-incubator-directmemory-dev-archive@incubator.apache.org Received: (qmail 17796 invoked by uid 500); 6 Dec 2011 12:32:23 -0000 Mailing-List: contact directmemory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: directmemory-dev@incubator.apache.org Delivered-To: mailing list directmemory-dev@incubator.apache.org Received: (qmail 17788 invoked by uid 99); 6 Dec 2011 12:32:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2011 12:32:23 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of williamstw@gmail.com designates 209.85.216.47 as permitted sender) Received: from [209.85.216.47] (HELO mail-qw0-f47.google.com) (209.85.216.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2011 12:32:15 +0000 Received: by qadb17 with SMTP id b17so2526869qad.6 for ; Tue, 06 Dec 2011 04:31:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=2/tvVC/VqgPwkm101+AXzoQW//C83ARczc/tyk0MVNE=; b=dgPm2uy9IXl8ubektxf6A5nnBgD9QuP60M12sBK4TnSHbBKTmSzJ9XYJuHM8uH+nYL uxjZ89TmLoKJ4Fo7usMuxrwCTyAkyYgy+Xlm1ByJsgzsQC89eU/ZLBazrF+vup3YPiXz nXbYB9qtsS1GR4waKIVPrQV+GmBXv6xmitXNg= MIME-Version: 1.0 Received: by 10.182.231.100 with SMTP id tf4mr2638261obc.78.1323174714579; Tue, 06 Dec 2011 04:31:54 -0800 (PST) Received: by 10.182.36.98 with HTTP; Tue, 6 Dec 2011 04:31:54 -0800 (PST) In-Reply-To: References: <20111201010858.0A5109A79@minotaur.apache.org> Date: Tue, 6 Dec 2011 07:31:54 -0500 Message-ID: Subject: Re: Incubator PMC/Board report for Dec 2011 ([ppmc]) From: Tim Williams To: directmemory-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Great, thanks Raffaele. I have some suggestions to offer on the "three most important issues to address in the move towards graduation." I think the issues listed are critical to a 1.0 release, but aren't necessarily on the critical path towards graduation. I think the previous list from November (branding, IP, and guidelines[release/new committers]) are still the top three things needing addressed before graduation. The issues listed are certainly important to the project but probably not so much to the board. Anyway, my thoughts... Thanks, --tim [1] - http://wiki.apache.org/incubator/December2011 On Tue, Dec 6, 2011 at 3:16 AM, Raffaele P. Guidi wrote: > Hi, as Simone seems to be a bit busy at the moment I tried to follow on h= is > last month's report. Could this help? > > Ciao, > =A0 =A0R > * > * > *DirectMemory *(incubating since October 2011) Apache DirectMemory is a > multi layered cache implementation featuring off-heap memory management > (a-la BigMemory) to enable efficient handling of a large number of java > objects without affecting jvm garbage collection performance > > *A list of the three most important issues to address in the move towards > graduation.* > 1. APIs finalization - the team decided to keep the singleton API but > rebuilding it on top of a more flexible classic interface-implementation > service layer > 2. The tutorial on how to build apps on top of DirectMemory is still > lacking as most of the documentation > > *Any issues that the Incubator PMC or ASF Board might wish/need to be awa= re > of* > - We lost one mentor (still not too bad, we have others but we will miss > Christian) > *How has the community developed since the last report* > - Two more people have asked for inclusion in the team as committers up o= n > the mailing lists > - Tasks and proposals contributed by non-committers > *How has the project developed since the last report.* > - Healthy activity on 3rd parties integrations such as Apache Karaf > (complete with an ad-hoc module) and Apache Commons JCS (still in progres= s > with help from the JCS team) > > On Mon, Dec 5, 2011 at 2:45 PM, Tim Williams wrote= : > >> Simone? >> >> --tim >> >> On Fri, Dec 2, 2011 at 8:43 AM, Tim Williams wrot= e: >> > Simone, are you picking this up again? =A05 days out... >> > >> > --tim >> > >> > On Wed, Nov 30, 2011 at 8:08 PM, Marvin wrote: >> >> >> >> >> >> Dear podling, >> >> >> >> This email was sent by an automated system on behalf of the Apache >> Incubator PMC. >> >> It is an initial reminder to give you plenty of time to prepare your >> quarterly >> >> board report. >> >> >> >> The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PS= T. >> The report >> >> for your podling will form a part of the Incubator PMC report. The >> Incubator PMC >> >> requires your report to be submitted 2 weeks before the board meeting= , >> to allow >> >> sufficient time for review and submission (Wed, Dec 7th). >> >> >> >> Please submit your report with sufficient time to allow the incubator >> PMC, and >> >> subsequently board members to review and digest. Again, the very late= st >> you >> >> should submit your report is 2 weeks prior to the board meeting. >> >> >> >> Thanks, >> >> >> >> The Apache Incubator PMC >> >> >> >> Submitting your Report >> >> ---------------------- >> >> >> >> Your report should contain the following: >> >> >> >> =A0* Your project name >> >> =A0* A brief description of your project, which assumes no knowledge = of >> the project >> >> =A0 or necessarily of its field >> >> =A0* A list of the three most important issues to address in the move >> towards >> >> =A0 graduation. >> >> =A0* Any issues that the Incubator PMC or ASF Board might wish/need t= o be >> aware of >> >> =A0* How has the community developed since the last report >> >> =A0* How has the project developed since the last report. >> >> >> >> This should be appended to the Incubator Wiki page at: >> >> >> >> =A0http://wiki.apache.org/incubator/2011 >> >> >> >> Note: This manually populated. You may need to wait a little before >> this page is >> >> =A0 =A0 =A0created from a template. >> >> >> >> Mentors >> >> ------- >> >> Mentors should review reports for their project(s) and sign them off = on >> the >> >> Incubator wiki page. Signing off reports shows that you are following >> the >> >> project - projects that are not signed may raise alarms for the >> Incubator PMC. >> >> >> >> Incubator PMC >> >> >>