+1

On Tue, Dec 4, 2018 at 5:14 PM Ryan Blue <rb...@netflix.com.invalid> wrote:

> Done. Thanks for working on the first draft.
>
> rb
>
> On Tue, Dec 4, 2018 at 4:47 PM Owen O'Malley <owen.omal...@gmail.com>
> wrote:
>
> > Go ahead and edit the wiki
> >
> > https://wiki.apache.org/incubator/December2018
> >
> > I'd suggest that we do a source-only release and after the release
> passes,
> > push the binaries into Maven central.
> >
> > On Tue, Dec 4, 2018 at 4:43 PM Ryan Blue <rb...@netflix.com.invalid>
> > wrote:
> >
> >> Looks good to me!
> >>
> >> We might want to note that the codebase has been updated with Apache
> >> license headers and now complies with ASF guidelines for a source
> release.
> >>
> >> We still need to cut over to org.apache package names instead of
> >> com.netflix, which I think we should do before the first release. We
> >> should
> >> also decide whether to do a source-only first release or to go through
> the
> >> pain of publishing convenience binaries with their own LICENSE and
> NOTICE
> >> content.
> >>
> >> rb
> >>
> >> On Tue, Dec 4, 2018 at 3:37 PM Owen O'Malley <owen.omal...@gmail.com>
> >> wrote:
> >>
> >> > I wrote a first pass of the report for the Apache board.
> >> >
> >> > Iceberg
> >> > >
> >> > > Iceberg is a table format for large, slow-moving tabular data.
> >> > >
> >> > > Iceberg has been incubating since 2018-11-16.
> >> > >
> >> > > Three most important issues to address in the move towards
> graduation:
> >> > >
> >> > >   1. Get the SGA accepted.
> >> > >   2. Finish the name clearance.
> >> > >   3. Make the first Apache release.
> >> > >
> >> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> be
> >> > > aware of?
> >> > >
> >> > >   * Gitbox integration has helped a lot, although it is frustrating
> >> that
> >> > >     the team members are not allowed to configure the project and
> >> must go
> >> > >     through infra for every change.
> >> > >   * The traffic on the dev list from Github pull requests and issues
> >> is
> >> > >     pretty heavy. It would be nice to have emails from creation go
> to
> >> > dev@
> >> > > ,
> >> > >     while updates and resolutions would go the issues@.
> >> > >
> >> > > How has the community developed since the last report?
> >> > >
> >> > >   This is the first report.
> >> > >
> >> > > How has the project developed since the last report?
> >> > >
> >> > >   This is the first report.
> >> > >
> >> > > How would you assess the podling's maturity?
> >> > > Please feel free to add your own commentary.
> >> > >
> >> > >   [X] Initial setup
> >> > >   [ ] Working towards first release
> >> > >   [ ] Community building
> >> > >   [ ] Nearing graduation
> >> > >   [ ] Other:
> >> > >
> >> > > Date of last release:
> >> > >
> >> > >   None yet
> >> > >
> >> > > When were the last committers or PPMC members elected?
> >> > >
> >> > >   None yet
> >> > >
> >> > > Have your mentors been helpful and responsive or are things falling
> >> > > through the cracks? In the latter case, please list any open issues
> >> > > that need to be addressed.
> >> > >
> >> > >   We're working through the issues as they come up.
> >> > >
> >> >
> >>
> >>
> >> --
> >> Ryan Blue
> >> Software Engineer
> >> Netflix
> >>
> >
>
> --
> Ryan Blue
> Software Engineer
> Netflix
>

Reply via email to