Mailing-List: contact dev-help@calcite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@calcite.incubator.apache.org
References: <20150627174434.8663017A14@minotaur.apache.org>
 <5373B9A9-238C-473B-AF7A-107AD968C44F@apache.org>
In-Reply-To: <5373B9A9-238C-473B-AF7A-107AD968C44F@apache.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <AC3A3044-8661-4D23-9CD4-E0C557DA89CD@gmail.com>
Cc: "general@incubator.apache.org" <general@incubator.apache.org>,
 "dev@calcite.incubator.apache.org" <dev@calcite.incubator.apache.org>,
 "P. Taylor Goetz" <ptgoetz@apache.org>
From: "P. Taylor Goetz" <ptgoetz@gmail.com>
Subject: Re: July 2015 Report
Date: Sun, 5 Jul 2015 19:37:06 -0400
To: Julian Hyde <jhyde@apache.org>

Hi Julian,

I'm okay with a late report. =46rom a shepherds standpoint, the podling repo=
rt is only part of what needs to be reviewed.

Also I'm usually late with my shepherd reports since the Sunday deadline is s=
omewhat inconvenient due to family, etc., but I always try to get it in by n=
oon eastern time the following day.

I think a late report (24-48 hrs., give or take) is perfectly tolerable on o=
ccasion, as long as it doesn't become habitual.

-Taylor


> On Jul 5, 2015, at 1:12 AM, Julian Hyde <jhyde@apache.org> wrote:
>=20
> I am the person who usually writes the incubator report, and I have been o=
n vacation for the last 7 days. So, it looks as if Calcite has missed the de=
adline for this month. My apologies to the IPMC and to our shepherd P. Taylo=
r Goetz.
>=20
> If it would be acceptable to file a report early tomorrow (Sun 5th) I can d=
o that; please let me know. Otherwise I presume that Calcite will be reporti=
ng in August, and I will make sure that the report is filed on time.
>=20
> Julian
>=20
>=20
>> On Jun 27, 2015, at 10:44 AM, Marvin Humphrey <marvin@apache.org> wrote:
>>=20
>> Greetings, {podling} developers,
>>=20
>> The "marvin" automated report reminder script didn't fire for whatever
>> reason this week, so I'm sending out a bulk reminder manually for the 15
>> podlings who are expected to submit a July 2015 report.  Boilerplate
>> reminder text below.
>>=20
>> Best,
>>=20
>> Marvin Humphrey
>>=20
>> ---------------
>>=20
>> Dear podling,
>>=20
>> 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.
>>=20
>> The board meeting is scheduled for Wed, 15 July 2015, 10:30 am Pacific.
>> 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, July 1st).
>>=20
>> Please submit your report with sufficient time to allow the incubator
>> PMC, and subsequently board members to review and digest. Again, the
>> very latest you should submit your report is 2 weeks prior to the board
>> meeting.
>>=20
>> Thanks,
>>=20
>> The Apache Incubator PMC
>>=20
>> Submitting your Report
>>=20
>> ----------------------
>>=20
>> Your report should contain the following:
>>=20
>> *   Your project name
>> *   A brief description of your project, which assumes no knowledge of
>>   the project or necessarily of its field
>> *   A list of the three most important issues to address in the move
>>   towards graduation.
>> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>>   aware of
>> *   How has the community developed since the last report
>> *   How has the project developed since the last report.
>>=20
>> This should be appended to the Incubator Wiki page at:
>>=20
>> http://wiki.apache.org/incubator/July2015
>>=20
>> Note: This is manually populated. You may need to wait a little before
>> this page is created from a template.
>>=20
>> Mentors
>> -------
>>=20
>> 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.
>>=20
>> Incubator PMC
>=20