+1. Signed off. Good job. -Jakob
On 6 July 2016 at 08:54, Chris Nauroth <[email protected]> wrote: > This looks good. I have entered my mentor sign-off. Thank you, Gurer and > Chris. > > --Chris Nauroth > > > > > On 7/5/16, 8:42 PM, "Chris Riccomini" <[email protected]> wrote: > >>Hey all, >> >>I've updated the report. I've used Gurer's summary, but tweaked a couple >>of >>things based on feedback. Please have a look: >> >> https://wiki.apache.org/incubator/July2016 >> >>@Gurer, thanks so much for doing the leg work on this! Makes things much >>easier. :) >> >>Cheers, >>Chris >> >>On Tue, Jul 5, 2016 at 11:37 AM, Jakob Homan <[email protected]> wrote: >> >>> Yeah, I'm not sure we should have much about the non-ASF release in >>> the report. We ran a question by IPMC about the release, so doing the >>> release itself was kosher, but having it dominate the report may not >>> be good. If we do include any reference to the non-ASF release, we >>> should have a link to the Incubator discussion okaying it, to avoid >>> any 'was-this-approved' questions (since a non-ASF release in >>> incubation is not typical)" http://bit.ly/AirflowInFlightRelease. >>> >>> -Jakob >>> >>> On 5 July 2016 at 10:23, Chris Nauroth <[email protected]> wrote: >>> > Hello Gurer, >>> > >>> > Thank you for putting together the report. This looks good to me >>> overall, >>> > after completing it by filling in each [placeholder]. >>> > >>> > I have a question regarding "we had a release on...". IIUC, this was >>>not >>> > an Apache release, but rather a release that followed the pre-Apache >>> > process. Am I right? If so, then would you please clarify that in >>>the >>> > report? If there has been progress on anything related to Apache >>>release >>> > process (e.g. license headers in source, writing a NOTICE file to >>> > acknowledge licenses of dependencies, etc.) then that would be good to >>> > mention too. >>> > >>> > --Chris Nauroth >>> > >>> > >>> > >>> > >>> > On 7/5/16, 6:16 AM, "Gurer Kiratli" <[email protected]> >>> > wrote: >>> > >>> >>Hi folks, >>> >> >>> >>As promised, please see a draft for the July 2016 Podling report. >>>Please >>> >>provide your feedback as soon as possible as this is due by the end of >>> day >>> >>Wednesday July 6th. >>> >> >>> >>Cheers, >>> >> >>> >>Gurer >>> >> >>> >>>>> >>> >> >>> >> - *Project Name:* Airflow >>> >> - *Project Description:* Airflow is a workflow automation and >>> >>scheduling >>> >> system that can be used to author and manage data pipelines. >>>Airflow >>> >>has >>> >> been incubating since 2016-03-31. >>> >> - *3 Issues to address before graduation:* >>> >> - An end to end testing framework for the whole community. >>> >> - The last and the only released was mostly managed by >>>committers >>> >> from Airbnb, we need to have a joint release. >>> >> - Improve and extend documentation. >>> >> - *Issues that Incubator PMC or ASF Board need to know:* >>> >> - We had to revert the latest release couple times due to some >>> buggy >>> >> code. This created a concern about lack of testing, review and >>> >> coordination. We are working on addressing these via cooperation >>> >>guidelines >>> >> and principles. >>> >> - *How has the community developed since the last report?:* >>> >> - Since our last podling report 1 month ago, we grew our >>> >>contributors >>> >> from 148 to 160. >>> >> - In June 2016 we had 56 commits. >>> >> - We organized a meet up at WePay. We also had one before at >>> Airbnb. >>> >> - We had several[how many??] committers meetings. >>> >> - 1 new committer. 2 offers were given but 1 was declined. >>> >> - *How has the project developed since the last report.* >>> >> - We had a release on [exact date]! >>> > >>> >
