Re: [VOTE] Apache Gobblin 0.12.0 release RC2

[Matthew Hayes]

Abhishek, what about using a bootstrap gradle task to download the jar and
gradlew?  DataFu does this [1], which was based on Samza's solution.  You
just need to have some version of gradle installed and can run `gradle -b
bootstrap.gradle`.  Then you don't need the jar or gradlew checked in.

-Matt

[1]https://github.com/apache/datafu/blob/master/bootstrap.gradle

On Tue, Mar 27, 2018 at 10:30 AM, Abhishek Tiwari  wrote:

> Yes, I understand that gradle-wrapper.jar is a convenience jar that helps
> get the gradle.
> However, we could not include it in the distribution because it is not
> acceptable to include binaries and instead we went with the proposed
> resolution in this thread:
> https://issues.apache.org/jira/browse/LEGAL-288?focusedCommentId=15980830;
> page=com.atlassian.jira.plugin.system.issuetabpanels%
> 3Acomment-tabpanel#comment-15980830
>
>
> This is (almost) exactly the same as what Apache Fineract does to address
> the same:
> - https://github.com/apache/fineract/blob/develop/README.md
> -
> https://www.mail-archive.com/dev@gobblin.incubator.apache.
> org/msg01727.html
> I like the Fineract model, especially because it requires only one extra
> step than what would be required otherwise to build the distribution.
> However, we will continue to improve upon the build process in future.
>
> We have not moved to newer versions of gradle yet, and we specify the
> gradle version requirement in README.md.
>
> Abhishek
>
> On Tue, Mar 27, 2018 at 10:06 AM, Matt Sicker  wrote:
>
> > I'd suggest not including gradlew and gradlew.bat in your source
> > distribution then. You are aware that gradle-wrapper.jar is itself a
> > bootstrap jar to get gradle itself, right? It's tiny and generally
> bundled
> > with source code for convenience. As an aside, in order to regenerate the
> > gradle wrapper the normal way (gradle wrapper --gradle-version 2.13), I
> had
> > to run it outside the project since the latest version of gradle is
> > incompatible, too. :/
> >
> > On 27 March 2018 at 11:46, Abhishek Tiwari  wrote:
> >
> > > Hi Matt,
> > >
> > > Thanks for checking. We intentionally do not bundle gradle-wrapper.jar,
> > and
> > > instead document the steps to obtain it and build.
> > > Please check the included README.md file.
> > >
> > > Regards,
> > > Abhishek
> > >
> > > On Tue, Mar 27, 2018 at 8:18 AM, Matt Sicker  wrote:
> > >
> > > > The bundled gradle wrapper in the source tgz doesn't work. It appears
> > to
> > > be
> > > > missing gradle/wrapper/gradle-wrapper.jar
> > > >
> > > > On 26 March 2018 at 19:01, Abhishek Tiwari  wrote:
> > > >
> > > > > The Apache Gobblin community has voted on and approved the release
> of
> > > > > Apache Gobblin 0.12.0 (incubating):
> > > > >
> > > > > https://www.mail-archive.com/dev@gobblin.incubator.apache.
> > > > > org/msg01772.html
> > > > >
> > > > > Results:
> > > > > 5 binding +1 votes
> > > > > No 0 votes
> > > > > No -1 votes
> > > > >
> > > > > The feedback from previous release candidates has been addressed:
> > > > > RC0 thread: https://www.mail-archive.com/general@incubator.
> > > > > apache.org/msg62151.html
> > > > > RC0 resolution: LICENSE and NOTICE files have been updated (tracked
> > by
> > > > > GOBBLIN-431 )
> > > > > RC1 thread: https://www.mail-archive.com/dev@gobblin.
> > > > > incubator.apache.org/msg01733.html
> > > > > RC1 resolution: gradlew scripts have been included in the source
> > > > > distribution, and the steps for building the distribution has been
> > > added
> > > > to
> > > > > README (including the way to obtain gradlew jar)
> > > > >
> > > > > I'd like to call a vote in general to approve the release.
> > > > >
> > > > > The source release candidate RC2 can be downloaded here:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/incubator/gobblin/
> > > > > apache-gobblin-incubating-0.12.0-rc2/
> > > > >
> > > > > The artifacts (i.e. JARs) corresponding to this release candidate
> can
> > > be
> > > > > found here:
> > > > >
> > > > > https://repository.apache.org/content/repositories/
> > > orgapachegobblin-1002
> > > > >
> > > > > This has been signed with PGP key 234E3FE3, corresponding to
> > > > > a...@apache.org, which is included in the repository's KEYS file (
> > > > > https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS
> ).
> > > > This
> > > > > key can be found on keyservers, such as:
> > > > >
> > > > > *http://pgp.mit.edu/pks/lookup?op=get=0x234E3FE3
> > > > > *
> > > > >
> > > > > It is also listed here:
> > > > >
> > > > > https://people.apache.org/keys/committer/abti.asc
> > > > >
> > > > > The release candidate has been tagged with release-0.12.0-rc2.
> > > > > I've also created a branch 0.12.0.
> > > > >
> > > > > For reference, here is a list of all closed JIRAs tagged with
> 0.12.0:
> > > > >
> > 

Re: [VOTE] Apache DataFu podling graduation

[Matthew Hayes]

The vote has passed with three +1 binding votes and no -1 or 0 votes.

+1 (binding):
Jakob Homan
Roman Shaposhnik
Ted Dunning

Thanks for taking the time to vote!  I will follow up on next steps.

-Matt

On Sat, Feb 17, 2018 at 11:20 PM, Ted Dunning <ted.dunn...@gmail.com> wrote:

> +1 (binding)
>
> On Feb 17, 2018 9:33 PM, "Roman Shaposhnik" <ro...@shaposhnik.org> wrote:
>
> > On Wed, Feb 14, 2018 at 9:36 AM, Matthew Hayes <mha...@apache.org>
> wrote:
> > > Hi all,
> > >
> > > I would like to open a vote for Apache DataFu's graduation from
> > incubator.  The
> > > DataFu community previously voted on this back in July, 2017 and the
> vote
> > >  passed
> > > <http://mail-archives.apache.org/mod_mbox/incubator-datafu-
> > dev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%
> > 3DaP5-Q8kstgY%2B0xM48kNuJMFWw%40mail.gmail.com%3E>.
> > > Following this there was a discussion
> > > <https://mail-archives.apache.org/mod_mbox/incubator-
> > general/201710.mbox/%3CCAA4Vo8DuQH2KkQ82bOm4Aj8GyoH
> > s8hoauywco2mutibwgwx...@mail.gmail.com%3E>
> > > on
> > > this list about graduation.  There were several pieces of feedback.  To
> > > summarize, there were:
> > >
> > > * Comments about the number of committers vs. proposed PMC size (here
> > > <https://mail-archives.apache.org/mod_mbox/incubator-
> > general/201710.mbox/%3Cop.y7jw80af4ntv07@desktop-v42f38k%3E>
> > >  and here
> > > <https://mail-archives.apache.org/mod_mbox/incubator-
> > general/201710.mbox/%3CCAOqetn_tXYM0MgZ_QUJg9xDiWUr2_
> > vg5msde96fmvbubqri...@mail.gmail.com%3E>
> > > )
> > > * Comments about the process for removing committers (here
> > > <https://mail-archives.apache.org/mod_mbox/incubator-
> > general/201710.mbox/%3CCAFAMeYLxX5VD-t7Z4MQkKQ6y_
> > m8bedu975tjsubay7b5qvu...@mail.gmail.com%3E>
> > >  and here
> > > <https://mail-archives.apache.org/mod_mbox/incubator-
> > general/201710.mbox/%3CCAFAMeY+nwEV7evK12dsjVMXt5o3OFGen9PAnf
> > UhRvQ=4vre...@mail.gmail.com%3E>
> > > )
> > > * Comments about the website, sha-512 extension, etc. (here
> > > <https://mail-archives.apache.org/mod_mbox/incubator-
> > general/201710.mbox/%3CCAOGo0VZN4mLw-eS-Oz8W1hVhS70Y_
> > bwwikjjri9sx3n0s8s...@mail.gmail.com%3E>
> > > ).  DATAFU-131 <https://issues.apache.org/jira/browse/DATAFU-131> was
> > filed
> > > to address these.
> > >
> > > All of that feedback should now be addressed (see the bottom of this
> > email
> > > for a more detailed summary than what follows).  The list of proposed
> PMC
> > > members has been updated in the graduation resolution to include 11
> > > individuals, which includes 10 of the current 14 committers.  The
> > remaining
> > > committers declined to remain committers and join the PMC and upon
> > > graduation these individuals will no longer be committers.  However
> given
> > > their past contributions they would be welcomed back if they wished to
> > > become committers again in the future and contribute.  Following these
> > > updates another community vote was held in February 2018 to reaffirm
> > > graduation and this vote passed as well
> > > <http://mail-archives.apache.org/mod_mbox/incubator-datafu-
> > dev/201802.mbox/%3CCAA4Vo8Cft9p-2uHF8NdNN%3D-
> v3Hn1Zzsc3N_1NOdOT8dNR4kZaA%
> > 40mail.gmail.com%3E>
> > > .
> > >
> > > Given this, I would like to open a vote for Apache DataFu's graduation
> > from
> > > incubator and becoming a top-level project.  The proposed graduation
> > > resolution can be found at https://cwiki.apache.org/
> confluence/display/
> > > DATAFU/Graduation+Resolution as well as at the bottom of this email.
> > >
> > > The vote will be open for 72 hours.
> > >
> > > [ ] +1 graduate DataFu to a TLP
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> >
> > +1 (binding)
> >
> > Thanks,
> > Roman.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

[VOTE] Apache DataFu podling graduation

[Matthew Hayes]

 with the

Foundation's purpose to establish a Project Management

Committee charged with the creation and maintenance of

open-source software, for distribution at no charge to the

public, consisting of well-tested libraries that help developers

solve common data problems in Hadoop and similar distributed

systems.



NOW, THEREFORE, BE IT RESOLVED, that a Project Management

Committee (PMC), to be known as the "Apache DataFu Project",

be and hereby is established pursuant to Bylaws of the

Foundation; and be it further



RESOLVED, that the Apache DataFu Project be and hereby is

responsible for the creation and maintenance of libraries that

 help solve common data problems and work with large-scale data

in Hadoop and similar distributed systems; and be it further RESOLVED,

that the office of Vice President, Apache DataFu" be and hereby

is created, the person holding such office to serve at the direction

of the Board of Directors as the chair of the Apache DataFu Project,

and to have primary responsibility for management of the projects

within the scope of responsibility of the Apache DataFu Project; and be

it further



RESOLVED, that the persons listed immediately below be and

hereby are appointed to serve as the initial members of the

Apache DataFu Project:

   - Casey Stella cestella at apache dot org
   - Evion Kim evion at apache dot org
   - Eyal Allweil eyal at apache dot org
   - Jarek Jarcec Cecho jarcec at apache dot org
   - Josh Wills jwills at apache dot org
   - Matthew Hayes mhayes at apache dot org
   - Mitul Tiwari mitultiwari at apache dot org
   - Roman Shaposhnik rvs at apache dot org
   - Russell Jurney rjurney at apache dot org
   - Sam Shah samshah at apache dot org
   - William Vaughan wvaughan at apache dot org


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Hayes

be appointed to the office of Vice President, Apache DataFu, to

serve in accordance with and subject to the direction of the

Board of Directors and the Bylaws of the Foundation until

death, resignation, retirement, removal or disqualification,

or until a successor is appointed; and be it further



RESOLVED, that the initial Apache DataFu PMC be and hereby is

tasked with the creation of a set of bylaws intended to

encourage open development and increased participation in the

Apache DataFu Project; and be it further



RESOLVED, that the Apache DataFu Project be and hereby

is tasked with the migration and rationalization of the Apache

Incubator DataFu podling; and be it further



RESOLVED, that all responsibilities pertaining to the Apache

Incubator DataFu podling encumbered upon the Apache Incubator

Project are hereafter discharged.

Re: [DISCUSSION] Apache DataFu podling graduation

[Matthew Hayes]

Hi John,

Regarding the events you listed:

- Podling discusses graduation.


 Done.  See here
<http://mail-archives.apache.org/mod_mbox/datafu-dev/201707.mbox/%3CCAA4Vo8BYw7Qw6uo44f07QTuha9UJr_WgtA0Fsq4qW7pGdUBOuA%40mail.gmail.com%3E>
.

- Podling drafts a charter (whimsy more or less generates this for you
> these days)


The charter is in the graduation resolution right?  DataFu's graduation
resolution is here
<https://cwiki.apache.org/confluence/display/DATAFU/Graduation+Resolution>.

- Podling calls for a vote & at the same time podling notifies IPMC about
> that vote


Vote started yesterday.  See here
<http://mail-archives.apache.org/mod_mbox/datafu-dev/201802.mbox/%3CCAA4Vo8BQc%2BrPCPpvo%3DucarwhYkJESwevZOT%2BVBQPG_iNu4OVqQ%40mail.gmail.com%3E>
.

- Podling members start a discussion on general@incu about the graduation.


Done, as this is the current discussion thread about graduation.  I opened
the discussion before voting because DataFu had already voted once before
<http://mail-archives.apache.org/mod_mbox/datafu-dev/201707.mbox/%3CCAA4Vo8Bt%3D57kKUY_ba5zQbv_xP2j4hEZ2LsheqotaHiPAghC9w%40mail.gmail.com%3E>
the
most recent vote and there was feedback in the discussion that followed. I
wanted to collect all feedback from the general list before starting
another vote so those issues could be addressed first.  Hopefully this was
okay.

- Calls for a vote (usually, the discussions go 72 hrs - 1 week, depending
> on how lively they are)


Waiting for current vote.

I see a few disconnects between your status page and whimsy roster.  Can
> you double check that everything lines up?  If people are not going to be
> included in the new TLP, I would recommend removing them from whimsy; this
> will save some work.  Any reason you are losing members when graduating?


I've updated the Whimsy roster to match the proposed PMC members in the
graduation proposal.  Most people are continuing on to PMC.  We are only
losing a few, for different reasons.

I see a few disconnects between your status page and whimsy roster.  Can
> you double check that everything lines up?


Can you specify what disconnects you see?  Under Mentors on the roster page
<https://whimsy.apache.org/roster/ppmc/datafu> I see Jakob is not listed
but he is listed on the status page
<http://incubator.apache.org/projects/datafu.html>.  The Licensing section
on the roster page lists that there have been no software grant and IP
clearance and no releases, which isn't true.  How does the roster get
updated?  Otherwise I'm not sure what disconnects there are.

-Matt

On Thu, Feb 1, 2018 at 7:12 PM, John D. Ament <johndam...@apache.org> wrote:

> On Thu, Feb 1, 2018 at 6:23 PM Matthew Hayes <
> matthew.terence.ha...@gmail.com> wrote:
>
> > Given that it has been a few days and I've only seen positive feedback so
> > far, I have opened a new vote for graduation in the datafu dev
> > <http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/> list.
> I
> > will open a new vote here when this vote passes.
> >
> >
> Matt,
>
> The typical order of events is:
>
> - Podling discusses graduation.
> - Podling drafts a charter (whimsy more or less generates this for you
> these days)
> - Podling calls for a vote & at the same time podling notifies IPMC about
> that vote
> - Podling members start a discussion on general@incu about the graduation.
> - Calls for a vote (usually, the discussions go 72 hrs - 1 week, depending
> on how lively they are)
>
> I see a few disconnects between your status page and whimsy roster.  Can
> you double check that everything lines up?  If people are not going to be
> included in the new TLP, I would recommend removing them from whimsy; this
> will save some work.  Any reason you are losing members when graduating?
>
> The IPMC (specifically, the graduating podlings) have received consistent
> feedback from the board regarding ASF members being present on newly formed
> TLPs.  I believe you will not have that issue with both Roman & Jarek on
> the proposed PMC.
>
> John
>
>
> > -Matt
> >
> > On Mon, Jan 29, 2018 at 3:57 PM, Jakob Homan <jgho...@gmail.com> wrote:
> >
> > > +1
> > >
> > > On 29 January 2018 at 15:49, Matthew Hayes <mha...@apache.org> wrote:
> > > > Hi,
> > > >
> > > > I would like to reopen the discussion regarding Apache DataFu's
> > > graduation
> > > > from incubator.  In the community vote
> > > > <http://mail-archives.apache.org/mod_mbox/incubator-datafu-
> > > dev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%
> > > 3DaP5-Q8kstgY%2B0xM48kNuJMFWw%40mail.gmail.com%3E>
> > > >  there was consensus to graduate to TLP 

Re: [DISCUSSION] Apache DataFu podling graduation

[Matthew Hayes]

Given that it has been a few days and I've only seen positive feedback so
far, I have opened a new vote for graduation in the datafu dev
<http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/> list.  I
will open a new vote here when this vote passes.

-Matt

On Mon, Jan 29, 2018 at 3:57 PM, Jakob Homan <jgho...@gmail.com> wrote:

> +1
>
> On 29 January 2018 at 15:49, Matthew Hayes <mha...@apache.org> wrote:
> > Hi,
> >
> > I would like to reopen the discussion regarding Apache DataFu's
> graduation
> > from incubator.  In the community vote
> > <http://mail-archives.apache.org/mod_mbox/incubator-datafu-
> dev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%
> 3DaP5-Q8kstgY%2B0xM48kNuJMFWw%40mail.gmail.com%3E>
> >  there was consensus to graduate to TLP status.  Here is my email that
> > kicked off the previous discussion:
> >
> > https://mail-archives.apache.org/mod_mbox/incubator-
> general/201710.mbox/%3CCAA4Vo8DuQH2KkQ82bOm4Aj8GyoH
> s8hoauywco2mutibwgwx...@mail.gmail.com%3E
> >
> > There were several pieces of feedback from that discussion that should
> all
> > be addressed as of now.
> >
> > * Comments about number of committers vs. proposed PMC size (here
> > <https://mail-archives.apache.org/mod_mbox/incubator-
> general/201710.mbox/%3Cop.y7jw80af4ntv07@desktop-v42f38k%3E>
> > and
> > here
> > <https://mail-archives.apache.org/mod_mbox/incubator-
> general/201710.mbox/%3CCAOqetn_tXYM0MgZ_QUJg9xDiWUr2_
> vg5msde96fmvbubqri...@mail.gmail.com%3E>
> > )
> > * Comments about process for removing committers (here
> > <https://mail-archives.apache.org/mod_mbox/incubator-
> general/201710.mbox/%3CCAFAMeYLxX5VD-t7Z4MQkKQ6y_
> m8bedu975tjsubay7b5qvu...@mail.gmail.com%3E>
> > and
> > here
> > <https://mail-archives.apache.org/mod_mbox/incubator-
> general/201710.mbox/%3CCAFAMeY+nwEV7evK12dsjVMXt5o3OFGen9PAnf
> UhRvQ=4vre...@mail.gmail.com%3E>
> > )
> > * Comments about the website, sha-512 extension, etc. (here
> > <https://mail-archives.apache.org/mod_mbox/incubator-
> general/201710.mbox/%3CCAOGo0VZN4mLw-eS-Oz8W1hVhS70Y_
> bwwikjjri9sx3n0s8s...@mail.gmail.com%3E>
> > ).  DATAFU-131 <https://issues.apache.org/jira/browse/DATAFU-131> was
> filed
> > to address these.
> >
> > To summarize what has happened since the last discussion:
> >
> > * Each committer was reached out to and asked whether they were willing
> to
> > join the PMC and fulfill the responsibilities that come with it.  The
> > graduation
> > resolution
> > <https://cwiki.apache.org/confluence/display/DATAFU/
> Graduation+Resolution> has
> > been updated to reflect those who were willing to join the PMC.  The
> > remainder declined to remain committers.  The proposed PMC size is now 11
> > out of 14 current committers.
> > * The Becoming a Committer
> > <https://cwiki.apache.org/confluence/display/DATAFU/Becoming+a+Committer>
> page
> > no longer has a section about removing committers.
> > * All the issues that were raised and led to DATAFU-131 being filed have
> > been addressed.  A summary:
> > - The Quick Start page has been replaced with a Download page
> > <http://datafu.incubator.apache.org/docs/download.html>.  The list of
> > source releases is prominent at the top and there is a section describing
> > how to validate releases.
> > - Links to ASF website, license, thanks, apache feather, etc. were
> added
> > - Links have been updated to reflect recent 1.3.3 release.
> > - Old releases have been cleaned up from
> >
> > https://dist.apache.org/repos/dist/dev/incubator/datafu and
> > https://dist.apache.org/repos/dist/release/incubator/datafu.
> >
> > - DataFu Whimsy <https://whimsy.apache.org/pods/project/datafu>
> page is
> > now mostly passing aside from Image and Events (not clear if these are
> > expected to pass).
> >
> > - SHA-512 checksum file now ends in .sha512
> >
> > Below is the original discussion email with updated stats and updated
> > graduation resolution.
> >
> > Apache DataFu began incubating Jan 5th, 2014.  Since then we have made 4
> > releases and added 4 committers.  The Apache DataFu website
> > <http://datafu.incubator.apache.org/> includes documentation such as a
> > getting started page and guides for various methods.
> >
> > Project status:
> > http://incubator.apache.org/projects/datafu.html
> >
> > Project website:
> > http://datafu.incubator.apache.org/
> &g

[DISCUSSION] Apache DataFu podling graduation

[Matthew Hayes]

Hi,

I would like to reopen the discussion regarding Apache DataFu's graduation
from incubator.  In the community vote
<http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%3DaP5-Q8kstgY%2B0xM48kNuJMFWw%40mail.gmail.com%3E>
 there was consensus to graduate to TLP status.  Here is my email that
kicked off the previous discussion:

https://mail-archives.apache.org/mod_mbox/incubator-general/201710.mbox/%3ccaa4vo8duqh2kkq82bom4aj8gyohs8hoauywco2mutibwgwx...@mail.gmail.com%3E

There were several pieces of feedback from that discussion that should all
be addressed as of now.

* Comments about number of committers vs. proposed PMC size (here
<https://mail-archives.apache.org/mod_mbox/incubator-general/201710.mbox/%3Cop.y7jw80af4ntv07@desktop-v42f38k%3E>
and
here
<https://mail-archives.apache.org/mod_mbox/incubator-general/201710.mbox/%3ccaoqetn_txym0mgz_qujg9xdiwur2_vg5msde96fmvbubqri...@mail.gmail.com%3E>
)
* Comments about process for removing committers (here
<https://mail-archives.apache.org/mod_mbox/incubator-general/201710.mbox/%3ccafameylxx5vd-t7z4mqkkq6y_m8bedu975tjsubay7b5qvu...@mail.gmail.com%3E>
and
here
<https://mail-archives.apache.org/mod_mbox/incubator-general/201710.mbox/%3CCAFAMeY+nwEV7evK12dsjVMXt5o3OFGen9PAnfUhRvQ=4vre...@mail.gmail.com%3E>
)
* Comments about the website, sha-512 extension, etc. (here
<https://mail-archives.apache.org/mod_mbox/incubator-general/201710.mbox/%3ccaogo0vzn4mlw-es-oz8w1hvhs70y_bwwikjjri9sx3n0s8s...@mail.gmail.com%3E>
).  DATAFU-131 <https://issues.apache.org/jira/browse/DATAFU-131> was filed
to address these.

To summarize what has happened since the last discussion:

* Each committer was reached out to and asked whether they were willing to
join the PMC and fulfill the responsibilities that come with it.  The
graduation
resolution
<https://cwiki.apache.org/confluence/display/DATAFU/Graduation+Resolution> has
been updated to reflect those who were willing to join the PMC.  The
remainder declined to remain committers.  The proposed PMC size is now 11
out of 14 current committers.
* The Becoming a Committer
<https://cwiki.apache.org/confluence/display/DATAFU/Becoming+a+Committer> page
no longer has a section about removing committers.
* All the issues that were raised and led to DATAFU-131 being filed have
been addressed.  A summary:
- The Quick Start page has been replaced with a Download page
<http://datafu.incubator.apache.org/docs/download.html>.  The list of
source releases is prominent at the top and there is a section describing
how to validate releases.
- Links to ASF website, license, thanks, apache feather, etc. were added
- Links have been updated to reflect recent 1.3.3 release.
- Old releases have been cleaned up from

https://dist.apache.org/repos/dist/dev/incubator/datafu and
https://dist.apache.org/repos/dist/release/incubator/datafu.

- DataFu Whimsy <https://whimsy.apache.org/pods/project/datafu> page is
now mostly passing aside from Image and Events (not clear if these are
expected to pass).

- SHA-512 checksum file now ends in .sha512

Below is the original discussion email with updated stats and updated
graduation resolution.

Apache DataFu began incubating Jan 5th, 2014.  Since then we have made 4
releases and added 4 committers.  The Apache DataFu website
<http://datafu.incubator.apache.org/> includes documentation such as a
getting started page and guides for various methods.

Project status:
http://incubator.apache.org/projects/datafu.html

Project website:
http://datafu.incubator.apache.org/

JIRA:
https://issues.apache.org/jira/projects/DATAFU

Maturity Evaluation:
https://cwiki.apache.org/confluence/display/DATAFU/Maturity+Evaluation

A draft of the board resolution can be found at the bottom of this email.

Proposed PMC size: 11
Current number of committers: 14
Proposed number of committers: 11

PMC affiliation (* indicates chair):

Data Syndrome:
  - Russell Jurney

Hortonworks:
  - Casey Stella

LinkedIn:
  - William Vaughan

Passage AI:
  - Mitul Tiwari

Paypal:
  - Eyal Allweil

SkipFlag:
  - (*) Matthew Hayes
- Sam Shah

Slack:
  - Josh Wills

StreamSets Inc.
  - Jarek Jarcec Cecho

Uber:
  - Evion Kim

Other:
  - Roman Shaposhnik

Here are some project statistics since entering graduation on Jan 5th, 2014:

- 151 commits
- 4 releases
- 21 unique contributors
- 4 committers added
- 136 issues created
- 100 issues closed

Resolution:

WHEREAS, the Board of Directors deems it to be in the best

interests of the Foundation and consistent with the

Foundation's purpose to establish a Project Management

Committee charged with the creation and maintenance of

open-source software, for distribution at no charge to the

public, consisting of well-tested libraries that help developers

solve common data problems in Hadoop and similar distributed

systems.



NOW, THEREFORE,

[RESULT] [VOTE] Apache DataFu 1.3.3 release RC1

[Matthew Hayes]

The vote has passed with three +1 binding votes, and no -1s or 0s.

Binding +1s: Justin Mclean (binding), Jakob Homan (binding), Roman
Shaposhnik (binding)

Thanks for taking the time to look at the release!

-Matt

On Fri, Jan 26, 2018 at 3:38 PM, Matthew Hayes <
matthew.terence.ha...@gmail.com> wrote:

> Thanks for taking a look Roman.  I have filed the following JIRA about the
> gradle.properties issue you raised:
>
> https://issues.apache.org/jira/browse/DATAFU-136
>
>
>
> On Fri, Jan 26, 2018 at 2:53 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
>> +1 (binding)
>>
>> - checked sigs
>> - LICENSES/NOTICE/DISCLAIMER look good
>> - Headers look good
>> - checked for the release tag in Git
>> - offending (cat X) material got removed, but otherwise git tag
>> matches release tarball
>>
>> Thanks,
>> Roman.
>>
>> P.S. Weirdly gradle.properties is set to non-release on tag -- you may
>> want to look
>> into that for future releases
>>
>>
>> On Thu, Jan 25, 2018 at 10:59 AM, Jakob Homan <jgho...@gmail.com> wrote:
>> > +1 (binding)
>> > - Sigs/asc look good
>> > - NOTICE/LICENSE/DISCLAIMER look good
>> > - Licenses look good
>> > - Tests succeed
>> > - Gradle binaries not included
>> >
>> > Good work.
>> > -Jakob
>> >
>> > On 24 January 2018 at 13:01, Justin Mclean <justinmcl...@me.com> wrote:
>> >> Hi,
>> >>
>> >>> Hi, it's been almost 72 hours since the vote was opened.  How many
>> votes do
>> >>> we need for this to pass?  Can other folks take a look if necessary?
>> >>
>> >> I suggest asking your mentor who are IPMC member to vote.
>> >>
>> >> Thanks,
>> >> Justin
>> >>
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

Re: [VOTE] Apache DataFu 1.3.3 release RC1

[Matthew Hayes]

Thanks for taking a look Roman.  I have filed the following JIRA about the
gradle.properties issue you raised:

https://issues.apache.org/jira/browse/DATAFU-136



On Fri, Jan 26, 2018 at 2:53 PM, Roman Shaposhnik 
wrote:

> +1 (binding)
>
> - checked sigs
> - LICENSES/NOTICE/DISCLAIMER look good
> - Headers look good
> - checked for the release tag in Git
> - offending (cat X) material got removed, but otherwise git tag
> matches release tarball
>
> Thanks,
> Roman.
>
> P.S. Weirdly gradle.properties is set to non-release on tag -- you may
> want to look
> into that for future releases
>
>
> On Thu, Jan 25, 2018 at 10:59 AM, Jakob Homan  wrote:
> > +1 (binding)
> > - Sigs/asc look good
> > - NOTICE/LICENSE/DISCLAIMER look good
> > - Licenses look good
> > - Tests succeed
> > - Gradle binaries not included
> >
> > Good work.
> > -Jakob
> >
> > On 24 January 2018 at 13:01, Justin Mclean  wrote:
> >> Hi,
> >>
> >>> Hi, it's been almost 72 hours since the vote was opened.  How many
> votes do
> >>> we need for this to pass?  Can other folks take a look if necessary?
> >>
> >> I suggest asking your mentor who are IPMC member to vote.
> >>
> >> Thanks,
> >> Justin
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache DataFu 1.3.3 release RC1

[Matthew Hayes]

Hi, it's been almost 72 hours since the vote was opened.  How many votes do
we need for this to pass?  Can other folks take a look if necessary?

Thanks,
Matt

On Sun, Jan 21, 2018 at 9:13 PM, Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signature and hashes good
> - disclaimer exists
> - LICENSE and NOTICE good
> - no unexpected binary files
> - can compile from source
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Apache DataFu 1.3.3 release RC1

[Matthew Hayes]

The Apache DataFu community has voted on and approved the release of Apache
DataFu 1.3.3 RC1 (incubating):

http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201801.mbox/%3CCAA4Vo8C_WCsDTU0MYPVGCXB9EeMZFzYrr-b-gWYuQKW-KmWKXA%40mail.gmail.com%3E

Results:
3 binding +1 votes
No 0 votes
No -1 votes

I'd like to call a vote in general to approve the release.

The source release candidate RC1 can be downloaded here:

https://dist.apache.org/repos/dist/dev/incubator/datafu/apache-datafu-incubating-1.3.3-rc1/

The artifacts (i.e. JARs) built from 1.3.3 RC1 can be found here:

https://repository.apache.org/content/repositories/orgapachedatafu-1006/

These have been signed with PGP key 7BA4C7DF, corresponding to
mha...@apache.org, which is included in the repository's KEYS file.  This
key can be found on keyservers, such as:

*http://pgp.mit.edu/pks/lookup?op=get=0x7BA4C7DF
*

The key is also listed here:

https://people.apache.org/keys/group/datafu.asc

The release candidate has been tagged in git with release-1.3.3-rc1, which
has been signed with the same key.  There is also a branch named 1.3.3.

For reference, here is a list of all closed JIRAs tagged with 1.3.3:

https://issues.apache.org/jira/browse/DATAFU-126?jql=project
%20%3D%20DATAFU%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%201.3
.3%20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%20status%
20DESC%2C%20priority%20DESC

For a summary of the changes in this release, see:

https://github.com/apache/incubator-datafu/blob/1.3.3/changes.md

RC0 addressed feedback from an earlier discussion in general regarding the
SHA-512 file extension being incorrect according to release distribution
guidelines.  RC1 additionally addresses feedback from the RC0 vote in
incubator general regarding the json dependency:

http://mail-archives.apache.org/mod_mbox/incubator-general/201801.mbox/%3CD15D6493-7375-4384-AAD3-6C956E4A67B9%40classsoftware.com%3E

Other changes in RC1 compared to RC0:

* Website source code removed from source release and LICENSE updated
accordingly.
* Now builds on Windows.

Please download the release candidate, check the hashes, check the
signatures, test it, and vote.  The vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Matt, on behalf of the Apache DataFu PPMC

Re: question about including website source in release

[Matthew Hayes]

Got it, thanks Mark and Julian.

On Thu, Jan 18, 2018 at 1:12 PM, Julian Hyde <jh...@apache.org> wrote:

> I agree that standard practice is to not include the site. However, in
> Calcite we do include the web site (or rather, the markdown files from
> which the site is generated) since the web site is also our documentation.
> So, your choice.
>
> Our site includes Jekyll template code under MIT license and some fonts
> under Open Font License, so we had to add a few lines to our LICENSE file.
>
> Julian
>
>
> > On Jan 18, 2018, at 12:47 PM, Mark Thomas <ma...@apache.org> wrote:
> >
> > On 18/01/18 20:43, Matthew Hayes wrote:
> >> Hi,
> >>
> >> Sorry if this is already answered somewhere but I couldn't find the
> >> information.  The source code that generates the Apache DataFu website
> >> content [1] is currently included in the source code release.  However
> the
> >> source code for the website is independent from the source code and
> build
> >> files that produce the project artifacts (i.e. JAR files).  If the
> website
> >> source was removed from the release it would have no impact on building
> >> these artifacts.  Should Apache DataFu continue to bundle the website
> >> source in this way or remove it from the release?  What is standard
> >> practice for other projects?
> >
> > Standard practice would be not to include it.
> >
> > Mark
> >
> >>
> >> Thanks,
> >> Matt
> >>
> >> 1. http://datafu.incubator.apache.org/
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

question about including website source in release

[Matthew Hayes]

Hi,

Sorry if this is already answered somewhere but I couldn't find the
information.  The source code that generates the Apache DataFu website
content [1] is currently included in the source code release.  However the
source code for the website is independent from the source code and build
files that produce the project artifacts (i.e. JAR files).  If the website
source was removed from the release it would have no impact on building
these artifacts.  Should Apache DataFu continue to bundle the website
source in this way or remove it from the release?  What is standard
practice for other projects?

Thanks,
Matt

1. http://datafu.incubator.apache.org/

Re: [VOTE] Apache DataFu 1.3.3 release RC0

[Matthew Hayes]

Justin, regrading the bootstrap and glyphicons licensing points you raised,
there was a github discussion in 2012 [1] [3] that led to the licensing
text in [2] about bootstrap's usage of glyphicons.  This discussion
predates the release of 3.0.3, which we are using.  So you're right that
glyphicons should be considered apache-2.0 licensed because we are using it
from the bootstrap distribution.  I will be updating [4] our LICENSE to
reflect that both bootstrap and glyphicons are apache-2.0 licensed.

[1] https://github.com/twbs/bootstrap/issues/3942#issuecomment-6869818
[2] http://glyphicons.com/license/
[3] https://github.com/twbs/bootstrap/issues/3942#issuecomment-12559146
[4] https://issues.apache.org/jira/projects/DATAFU/issues/DATAFU-134

On Thu, Jan 18, 2018 at 10:00 AM, Matthew Hayes <
matthew.terence.ha...@gmail.com> wrote:

> Thanks Justin for clarifying.
>
> On Wed, Jan 17, 2018 at 11:20 PM, Justin Mclean <jus...@classsoftware.com>
> wrote:
>
>> Hi,
>>
>> > Thanks for pointing out the json license issue.  I searched the code and
>> > found only a small piece of code that uses it so it shouldn't be hard to
>> > replace with an alternative.  For my understanding, when [1] states "CAN
>> > APACHE PRODUCTS INCLUDE WORKS LICENSED UNDER THE JSON LICENSE?", does
>> > either having the source code in the source release or having a build or
>> > runtime dependency count as "including" the licensed work?  In our case
>> we
>> > have a build+runtime dependency but do not include the source code.
>>
>> Sorry to say but you can’t have a build or runtime dependancy and you
>> can’t distribute it [1] unless it’s optional [2].
>>
>> Thanks,
>> Justin
>>
>> 1. https://www.apache.org/legal/resolved.html#prohibited
>> 2. https://www.apache.org/legal/resolved.html#optional
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

Re: [VOTE] Apache DataFu 1.3.3 release RC0

[Matthew Hayes]

Thanks Justin for clarifying.

On Wed, Jan 17, 2018 at 11:20 PM, Justin Mclean 
wrote:

> Hi,
>
> > Thanks for pointing out the json license issue.  I searched the code and
> > found only a small piece of code that uses it so it shouldn't be hard to
> > replace with an alternative.  For my understanding, when [1] states "CAN
> > APACHE PRODUCTS INCLUDE WORKS LICENSED UNDER THE JSON LICENSE?", does
> > either having the source code in the source release or having a build or
> > runtime dependency count as "including" the licensed work?  In our case
> we
> > have a build+runtime dependency but do not include the source code.
>
> Sorry to say but you can’t have a build or runtime dependancy and you
> can’t distribute it [1] unless it’s optional [2].
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/legal/resolved.html#prohibited
> 2. https://www.apache.org/legal/resolved.html#optional
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache DataFu 1.3.3 release RC0

[Matthew Hayes]

Hi Justin,

Thanks for pointing out the json license issue.  I searched the code and
found only a small piece of code that uses it so it shouldn't be hard to
replace with an alternative.  For my understanding, when [1] states "CAN
APACHE PRODUCTS INCLUDE WORKS LICENSED UNDER THE JSON LICENSE?", does
either having the source code in the source release or having a build or
runtime dependency count as "including" the licensed work?  In our case we
have a build+runtime dependency but do not include the source code.

I'll take a look at your bootstrap license suggestion too.

Regarding Java 8, there is a JIRA filed for this [2] with a patch submitted
so it'll probably be taken care of for the next release.

1. https://www.apache.org/legal/resolved.html#json
2. https://issues.apache.org/jira/projects/DATAFU/issues/DATAFU-132


On Wed, Jan 17, 2018 at 8:36 PM, Justin Mclean 
wrote:

> Hi,
>
> Sorry but it’s -1 (binding) from me due to Category X license. Everything
> else looks good however.
>
> The LICENSE mentions the he JSON license which is now category X and
> cannot be included or a dependancy of an Apache project. [1] This changed a
> year ago and, there was a grace period that has since expired. [4]
>
> I checked:
> - incubating in name
> - signatures and hashes
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - All file have ASF header
> - No unexpected binary files
> - Can compile from source
>
> The year in NOTICE needs to be updated.
>
> You may (but it’s not required) want to add bootstrap to your LICENSE file
> [2] even though it’s Apache licensed, some version are MIT licensed, so it
> can be a source of confusion. That may also mean that the glyphicons font
> is also under apache license not MIT as stated in LICENSE. See the very
> bottom of three [3] although what that page said when bootstrap v3.0.3 come
> up I’m not 100% sure.
>
> I also note it only compiles on Java 1.7, might be time to try and getting
> to to work on 1.8?
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/legal/resolved.html#json
> 2. apache-datafu-incubating-sources-1.3.3/site/source/
> stylesheets/bootstrap.css
> 3. http://glyphicons.com/license/
> 4. http://mail-archives.apache.org/mod_mbox/www-legal-
> discuss/201705.mbox/%3c63d25f99-c5d1-4115-816b-477943ff4...@apache.org%3E
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Apache DataFu 1.3.3 release RC0

[Matthew Hayes]

The Apache DataFu community has voted on and approved the release of Apache
DataFu 1.3.3 (incubating):

http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201801.mbox/%3CCAA4Vo8DpgMgAzbbgAbdKTTqQ0m%3DyK5OLsACLEc8MeK1pwyv1NA%40mail.gmail.com%3E

Results:
3 binding +1 votes
No 0 votes
No -1 votes

I'd like to call a vote in general to approve the release.

The source release candidate RC0 can be downloaded here:

https://dist.apache.org/repos/dist/dev/incubator/datafu/apache-datafu-incubating-1.3.3-rc0/

The artifacts (i.e. JARs) built from 1.3.3 RC0 can be found here:

https://repository.apache.org/content/repositories/orgapachedatafu-1005/

These have been signed with PGP key 7BA4C7DF, corresponding to
mha...@apache.org, which is included in the repository's KEYS file.  This
key can be found on keyservers, such as:

*http://pgp.mit.edu/pks/lookup?op=get=0x7BA4C7DF
*

The key is also listed here:

https://people.apache.org/keys/group/datafu.asc

The release candidate has been tagged in git with release-1.3.3-rc0, which
has been signed with the same key.  I've also created a branch 1.3.3.

For reference, here is a list of all closed JIRAs tagged with 1.3.3:

https://issues.apache.org/jira/browse/DATAFU-126?jql=
project%20%3D%20DATAFU%20AND%20status%20%3D%20Closed%20AND%
20fixVersion%20%3D%201.3.3%20ORDER%20BY%20updated%20DESC%
2C%20created%20DESC%2C%20status%20DESC%2C%20priority%20DESC

For a summary of the changes in this release, see:

https://github.com/apache/incubator-datafu/blob/1.3.3/changes.md

This release also addresses feedback from an earlier discussion in general
regarding the SHA-512 file extension being incorrect according to release
distribution guidelines.

Please download the release candidate, check the hashes, check the
signatures, test it, and vote.  The vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Matt, on behalf of the Apache DataFu PPMC

Re: [DISCUSSION] Apache DataFu podling graduation

[Matthew Hayes]

Regarding Raphael's comment:

You have 14 Committers, but only 4 for the proposed PMC?


The project began incubation with 10 committers.  If I recall correctly,
the proposed list of committers was drawn largely from contributors in the
git commit history in order to be inclusive and give them a chance to
continue contributing as committers.  Some of these people are not actively
involved at this time.  The list of committers has so far not been reduced
in size.  4 additional committers were later added, bringing the total to
14.  The 4 proposed PMC members were committers who volunteered when asked
who was willing to commit time to be on PMC.

Regarding Mike's comment:

>
> I have concern about the DataFu process of removing committers due to
> inactivity, as outlined on this wiki page -
> https://cwiki.apache.org/confluence/display/DATAFU/Becoming+a+Committer

How often has this process been used?


This process hasn't been used so far.  This page was created earlier this
year as we were going through the maturity evaluation.  This was largely
based on Fineract's wiki page
<https://cwiki.apache.org/confluence/display/FINERACT/Becoming+a+Committer>
on the same subject, which seemed well written.  For the Apache DataFu page
we increased the time frame from 6 months to 1 year actually.  For myself
at least and probably others on the project the concept of "merit is
considered to never expire" is shared.  Do you think we should add a bullet
point to the page that if someone were removed from the committer list that
their past contributions would be considered if they expressed interest in
joining again?  If so I can propose that we update the page with this
language.

-Matt



On Tue, Oct 3, 2017 at 2:21 PM, Mike Drob <md...@apache.org> wrote:

> I have concern about the DataFu process of removing committers due to
> inactivity, as outlined on this wiki page -
> https://cwiki.apache.org/confluence/display/DATAFU/Becoming+a+Committer
>
> How often has this process been used?
>
> At many Apache projects, merit is considered to never expire. Circumstances
> can pull people away from projects for a period of time, I would hope that
> if somebody is able to return they are warmly welcomed back.
>
>
> Mike
>
> On Tue, Oct 3, 2017 at 4:13 PM, Raphael Bircher <rbircherapa...@gmail.com>
> wrote:
>
> > Hi Matthew
> >
> > You have 14 Committers, but only 4 for the proposed PMC?
> >
> > Regards Raphael
> >
> >
> > Am .10.2017, 22:45 Uhr, schrieb Matthew Hayes <mha...@apache.org>:
> >
> > Hi,
> >>
> >> I would like to kick off a discussion regarding Apache DataFu's
> graduation
> >> from incubator.  In the community vote
> >> <http://mail-archives.apache.org/mod_mbox/incubator-datafu-d
> >> ev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%3DaP5-Q8kstgY%
> >> 2B0xM48kNuJMFWw%40mail.gmail.com%3E>
> >> there was consensus to graduate to TLP status.
> >>
> >> Apache DataFu began incubating Jan 5th, 2014.  Since then we have made 3
> >> releases and added 4 committers.  The Apache DataFu website
> >> <http://datafu.incubator.apache.org/> includes documentation such as a
> >> getting started page and guides for various methods.
> >>
> >> Project status:
> >> http://incubator.apache.org/projects/datafu.html
> >>
> >> Project website:
> >> http://datafu.incubator.apache.org/
> >>
> >> JIRA:
> >> https://issues.apache.org/jira/projects/DATAFU
> >>
> >> Maturity Evaluation:
> >> https://cwiki.apache.org/confluence/display/DATAFU/Maturity+
> >> Evaluation
> >>
> >> A draft of the board resolution can be found at the bottom of this
> email.
> >>
> >> Proposed PMC size: 4
> >> Total number of committers: 14
> >>
> >> PMC affiliation (* indicates chair):
> >>
> >> Paypal:
> >>   - Eyal Allweil
> >>
> >> Pivotal:
> >> - Roman Shaposhnik
> >>
> >> SkipFlag:
> >>   - (*) Matthew Hayes
> >> - Sam Shah
> >>
> >> Here are some project statistics since entering graduation on Jan 5th,
> >> 2014:
> >>
> >> - 131 commits
> >> - 3 releases
> >> - 21 unique contributors
> >> - 4 committers added
> >> - 130 issues created
> >> - 82 issues closed
> >>
> >> Resolution:
> >>
> >> WHEREAS, the Board of Directors deems it to be in the best
> >>
> >> interests of the Foundation and consistent with the
> >>
> >> Foundation's purpose to esta

[DISCUSSION] Apache DataFu podling graduation

[Matthew Hayes]

Hi,

I would like to kick off a discussion regarding Apache DataFu's graduation
from incubator.  In the community vote
<http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%3DaP5-Q8kstgY%2B0xM48kNuJMFWw%40mail.gmail.com%3E>
there was consensus to graduate to TLP status.

Apache DataFu began incubating Jan 5th, 2014.  Since then we have made 3
releases and added 4 committers.  The Apache DataFu website
<http://datafu.incubator.apache.org/> includes documentation such as a
getting started page and guides for various methods.

Project status:
http://incubator.apache.org/projects/datafu.html

Project website:
http://datafu.incubator.apache.org/

JIRA:
https://issues.apache.org/jira/projects/DATAFU

Maturity Evaluation:
https://cwiki.apache.org/confluence/display/DATAFU/Maturity+Evaluation

A draft of the board resolution can be found at the bottom of this email.

Proposed PMC size: 4
Total number of committers: 14

PMC affiliation (* indicates chair):

Paypal:
  - Eyal Allweil

Pivotal:
- Roman Shaposhnik

SkipFlag:
  - (*) Matthew Hayes
- Sam Shah

Here are some project statistics since entering graduation on Jan 5th, 2014:

- 131 commits
- 3 releases
- 21 unique contributors
- 4 committers added
- 130 issues created
- 82 issues closed

Resolution:

WHEREAS, the Board of Directors deems it to be in the best

interests of the Foundation and consistent with the

Foundation's purpose to establish a Project Management

Committee charged with the creation and maintenance of

open-source software, for distribution at no charge to the

public, consisting of well-tested libraries that help developers

solve common data problems in Hadoop and similar distributed

systems.



NOW, THEREFORE, BE IT RESOLVED, that a Project Management

Committee (PMC), to be known as the "Apache DataFu Project",

be and hereby is established pursuant to Bylaws of the

Foundation; and be it further



RESOLVED, that the Apache DataFu Project be and hereby is

responsible for the creation and maintenance of libraries that

 help solve common data problems and work with large-scale data

in Hadoop and similar distributed systems; and be it further RESOLVED,

that the office of Vice President, Apache DataFu" be and hereby

is created, the person holding such office to serve at the direction

of the Board of Directors as the chair of the Apache DataFu Project,

and to have primary responsibility for management of the projects

within the scope of responsibility of the Apache DataFu Project; and be

it further


RESOLVED, that the persons listed immediately below be and

hereby are appointed to serve as the initial members of the

Apache DataFu Project:

   - Eyal Allweil eyal at apache dot org
   - Matthew Hayes mhayes at apache dot org
   - Roman Shaposhnik rvs at apache dot org
   - Sam Shah samshah at apache dot org


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Hayes

be appointed to the office of Vice President, Apache DataFu, to

serve in accordance with and subject to the direction of the

Board of Directors and the Bylaws of the Foundation until

death, resignation, retirement, removal or disqualification,

or until a successor is appointed; and be it further



RESOLVED, that the initial Apache DataFu PMC be and hereby is

tasked with the creation of a set of bylaws intended to

encourage open development and increased participation in the

Apache DataFu Project; and be it further



RESOLVED, that the Apache DataFu Project be and hereby

is tasked with the migration and rationalization of the Apache

Incubator DataFu podling; and be it further



RESOLVED, that all responsibilities pertaining to the Apache

Incubator DataFu podling encumbered upon the Apache Incubator

Project are hereafter discharged.

Fwd: [VOTE] Apache DataFu graduation proposal

[Matthew Hayes]

FYI, the community vote is starting.

Thanks,
Matt

-- Forwarded message --
From: Matthew Hayes <matthew.terence.ha...@gmail.com>
Date: Fri, Jul 28, 2017 at 5:49 PM
Subject: [VOTE] Apache DataFu graduation proposal
To: DataFu <d...@datafu.incubator.apache.org>


Hi all,

Given the positive discussion about Apache DataFu graduating from
Incubator, I would like to open a vote.  Referring to the checklist at
https://incubator.apache.org/guides/graduation.html#graduation_check_list,

   - Status file at http://incubator.apache.org/projects/datafu.html is up
   to date
   - Podling name search for DataFu was completed https://issues.apach
   e.org/jira/browse/PODLINGNAMESEARCH-48
   <https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-48>
   - Demonstrated Apache releases through releasing 1.3.0, 1.3.1, and 1.3.2
   - Community seems ready to graduate according to
   https://cwiki.apache.org/confluence/display/DATAFU/Maturity+Evaluation
   <https://cwiki.apache.org/confluence/display/DATAFU/Maturity+Evaluation>
   - I don't know of any remaining issues from mentors or IPMC

I propose that Apache DataFu graduate from incubator and become a top-level
project.  The proposed graduation resolution can be found at
https://cwiki.apache.org/confluence/display/DATAFU/Graduation+Resolution.

The vote will be open for 72 hours (ends on July 31st 6 pm PST).

[ ] +1 approve of graduation
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

My vote: +1

If this vote passes then the next step is an Incubator PMC vote.  I will
forward this email to the Incubator general list as an FYI that the vote is
taking place.

-Matt

Re: [VOTE] Apache DataFu 1.3.2 release RC0

[Matthew Hayes]

The vote has passed with three +1 binding votes, and no -1s or 0s.

Binding +1s: Roman Shaposhnik, Jakob Homan, Suneel Marthi

Thanks for checking out the release candidate for us!  I will proceed with
the release.

-Matt

On Mon, Mar 6, 2017 at 5:46 PM, Suneel Marthi <smar...@apache.org> wrote:

> +1 binding
>
> 1. Checked License Notice Disclaimer in Source Tar ball
> 2. Ran RAT check
> 3. Checked the hashes and signatures
> 4. Ran complete build and unit tests
>
>
> > -- Forwarded message --
> > From: Jakob Homan <jgho...@gmail.com>
> > Date: Mon, Mar 6, 2017 at 2:23 PM
> > Subject: Re: [VOTE] Apache DataFu 1.3.2 release RC0
> > To: DataFu <d...@datafu.incubator.apache.org>
> > Cc: "general@incubator.apache.org" <general@incubator.apache.org>
> >
> >
> > +1 (binding)
> >
> > * Built jar, ran tests, checked MD5, checked N/L/D files, spot checked
> > for headers
> >
> > -Jakob
> >
> >
> > On 5 March 2017 at 19:57, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> > > On Thu, Mar 2, 2017 at 12:31 PM, Matthew Hayes <mha...@apache.org>
> > wrote:
> > >> The Apache DataFu community has voted on and approved the release of
> > Apache
> > >> DataFu 1.3.2 (incubating):
> > >>
> > >> http://mail-archives.apache.org/mod_mbox/incubator-datafu-de
> > v/201703.mbox/browser
> > >>
> > >> Results:
> > >> 3 binding +1 votes
> > >> No 0 votes
> > >> No -1 votes
> > >>
> > >> I'd like to call a vote in general to approve the release.
> > >>
> > >> The source release candidate RC0 can be downloaded here:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/incubator/datafu/apache-datafu
> > >> -incubating-1.3.2-rc0/
> > >>
> > >> The artifacts (i.e. JARs) built from 1.3.2 RC0 can be found here:
> > >>
> > >> https://repository.apache.org/content/repositories/orgapache
> > datafu-1004/
> > >>
> > >> These have been signed with PGP key 7BA4C7DF, corresponding to
> > >> mha...@apache.org, which is included in the repository's KEYS file.
> > This
> > >> key can be found on keyservers, such as:
> > >>
> > >> *http://pgp.mit.edu/pks/lookup?op=get=0x7BA4C7DF
> > >> <http://pgp.mit.edu/pks/lookup?op=get=0x7BA4C7DF>*
> > >>
> > >> The key is also listed here:
> > >>
> > >> https://people.apache.org/keys/group/datafu.asc
> > >>
> > >> The release candidate has been tagged in git with release-1.3.2-rc0,
> > which
> > >> has been signed with the same key.  I've also created a branch 1.3.2.
> > >>
> > >> For reference, here is a list of all closed JIRAs tagged with 1.3.2:
> > >>
> > >> https://issues.apache.org/jira/issues/?jql=project%20%
> > >> 3D%20DATAFU%20AND%20status%20%3D%20Closed%20AND%20fixVersion
> > %20%3D%201.3.2%
> > >> 20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%
> > >> 20status%20DESC%2C%20priority%20DESC
> > >>
> > >> For a summary of the changes in this release, see:
> > >>
> > >> https://github.com/apache/incubator-datafu/blob/1.3.2/changes.md
> > >>
> > >> Note that starting with this release, LICENSE, NOTICE, and DISCLAIMER
> > files
> > >> are included in the META-INF of the JARs.  These differ from the
> source
> > >> release versions as they reflect what is bundled in the JARs.
> > >>
> > >> Please download the release candidate, check the hashes, check the
> > >> signatures, test it, and vote.  The vote will be open for 72 hours.
> > >>
> > >> [ ] +1 approve
> > >> [ ] +0 no opinion
> > >> [ ] -1 disapprove (and reason why)
> > >
> > > +1 (binding)
> > >
> > > * Checked Maven artifacts (jars) to have the right LICENSE, NOTICE and
> > > DISCLAIMER
> > > * Checked source tarball for LICENSE, NOTICE and DISCLAIMER
> > > * Checked the keyfile
> > > * Checked the hashes and signatures
> > > * Compared content of the tarball to the tag
> > > * Run RAT check
> > > * Built the project
> > >
> > > Thanks,
> > > Roman.
> >
>

[VOTE] Apache DataFu 1.3.2 release RC0

[Matthew Hayes]

The Apache DataFu community has voted on and approved the release of Apache
DataFu 1.3.2 (incubating):

http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201703.mbox/browser

Results:
3 binding +1 votes
No 0 votes
No -1 votes

I'd like to call a vote in general to approve the release.

The source release candidate RC0 can be downloaded here:

https://dist.apache.org/repos/dist/dev/incubator/datafu/apache-datafu
-incubating-1.3.2-rc0/

The artifacts (i.e. JARs) built from 1.3.2 RC0 can be found here:

https://repository.apache.org/content/repositories/orgapachedatafu-1004/

These have been signed with PGP key 7BA4C7DF, corresponding to
mha...@apache.org, which is included in the repository's KEYS file.  This
key can be found on keyservers, such as:

*http://pgp.mit.edu/pks/lookup?op=get=0x7BA4C7DF
*

The key is also listed here:

https://people.apache.org/keys/group/datafu.asc

The release candidate has been tagged in git with release-1.3.2-rc0, which
has been signed with the same key.  I've also created a branch 1.3.2.

For reference, here is a list of all closed JIRAs tagged with 1.3.2:

https://issues.apache.org/jira/issues/?jql=project%20%
3D%20DATAFU%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%201.3.2%
20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%
20status%20DESC%2C%20priority%20DESC

For a summary of the changes in this release, see:

https://github.com/apache/incubator-datafu/blob/1.3.2/changes.md

Note that starting with this release, LICENSE, NOTICE, and DISCLAIMER files
are included in the META-INF of the JARs.  These differ from the source
release versions as they reflect what is bundled in the JARs.

Please download the release candidate, check the hashes, check the
signatures, test it, and vote.  The vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Matt, on behalf of the Apache DataFu PPMC

Re: [VOTE] Apache DataFu 1.3.1 release RC1

[Matthew Hayes]

The vote has passed with three +1 binding votes, and no -1s or 0s.

Binding +1s: Jakob Homan, Justin Mclean, John D. Ament

Thanks for taking the time to look at the release!

Justin, I've updated the NOTICE file in the master branch and updated the
footer template in the site source code.  I'll update the website along
with this release.  The _footer.erb page has the header but it was missing
a # sign on one line (now fixed) so it may have messed up the detection.
The script.js file is generated by javadocs and should be excluded I
think.  I actually plan to remove the multiple versions of javadocs from
the git repo since they are also stored in the SVN repo for the website.

-Matt

On Mon, Jul 25, 2016 at 5:55 PM, John D. Ament 
wrote:

> +1 as well, no additional comments beyond what Justin pointed out.
>
> On Thu, Jul 21, 2016 at 6:10 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > +1 (binding)
> >
> > I checked:
> > - release contains incubating
> > - signatures and hashes good
> > - DISCLAIMER exists
> > - LICENSE and NOTICE OK
> > - Most files has ASF headers
> > - No unexpected binaries in release
> > - Can compile from source
> >
> > Minor issues:
> > - year is wrong in NOTICE file
> > - year range in site footed doesn’t match that in NOTICE [1]
> > - a few files missing ASF headers e.g. [2]
> >
> > Thanks,
> > Justin
> >
> > 1. ./site/source/layouts/_footer.erb
> > 2. ./site/source/docs/datafu/1.3.0/script.js
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

[VOTE] Apache DataFu 1.3.1 release RC1

[Matthew Hayes]

Hi all,

The Apache DataFu community has voted on and approved the release of Apache
DataFu 1.3.1 (incubating):

http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201607.mbox/%3CCAA4Vo8AQ_gbDvvVN49LcU%3DgdneSnjyc%2Bd%2BrfNd2u5imJUxBJUQ%40mail.gmail.com%3E

Results:
4 binding +1 votes
No 0 votes
No -1 votes

I'd like to call a vote in general to approve the release.

The source release candidate RC1 can be downloaded here:

https://dist.apache.org/repos/dist/dev/incubator/datafu/apache-datafu
-incubating-1.3.1-rc1/

The artifacts (i.e. JARs) corresponding to this release candidate can be
found here:

https://repository.apache.org/content/repositories/orgapachedatafu-1003/

This has been signed with PGP key 7BA4C7DF, corresponding to
mha...@apache.org, which is included in the repository's KEYS file.  This
key can be found on keyservers, such as:

*http://pgp.mit.edu/pks/lookup?op=get=0x7BA4C7DF
*

It is also listed here:

https://people.apache.org/keys/group/datafu.asc

The release candidate has been tagged with release-1.3.1-rc1, which has
been signed with the same key.  I've also created a branch 1.3.1.

For reference, here is a list of all closed JIRAs tagged with 1.3.1:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20DATAFU%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%201.3.1%20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%20status%20DESC%2C%20priority%20DESC

For a summary of the changes in this release, see:

https://github.com/apache/incubator-datafu/blob/1.3.1/changes.md

This release also addresses feedback from the last release process, namely:

* Using an ASF-related email for code signing
* Storing the source release in the right place
* Using a hash other than MD5
* Releasing artifacts at the same time as the source release
* Updated release documentation based on above

The vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Matt, on behalf of the Apache DataFu PPMC

Re: [VOTE] Apache DataFu 1.3.0 (incubating) release to maven

[Matthew Hayes]

That's a good suggestion Justin.  I've updated the release instructions
patch I've been working on (https://issues.apache.org/jira/browse/DATAFU-111
if you'd like to review) to include that.

What's the best way to have the 1.3.0 artifacts be reviewed?  Should we do
a small release 1.3.1 with source + binary to have them reviewed together?
By the way, Justin, I released the 1.3.0 repository in Nexus before you
last email went out.

-Matt

On Mon, Dec 7, 2015 at 1:17 PM, Justin Mclean 
wrote:

> Hi,
>
> > Okay got it, thanks Marvin, I hadn't seen that.  It sounds like we are
> okay
> > to release then given that the DataFu community already voted on and
> > approved the JARs to be released.  The vote is cancelled.
>
> It may still be useful to check that the connivance binary follows Apache
> policy. For instance the NOTICE and LICENSE may need to be different from
> the source release. It’s best to offer but the source and binary for review
> at the same time.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache DataFu 1.3.0 (incubating) release to maven

[Matthew Hayes]

Okay got it, thanks Marvin, I hadn't seen that.  It sounds like we are okay
to release then given that the DataFu community already voted on and
approved the JARs to be released.  The vote is cancelled.

Thanks,
Matt

On Mon, Dec 7, 2015 at 11:21 AM, Marvin Humphrey <mar...@rectangular.com>
wrote:

> Hello, Matthew,
>
> On Mon, Dec 7, 2015 at 10:33 AM, Matthew Hayes <mha...@apache.org>
>
> > Note that the source release vote passed on November 15th:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/201511.mbox/%3CCAA4Vo8AdnsvZtEeWKEDUt72HzCEVhaNqbX4jnXDf0_joTx5V%3Dg%40mail.gmail.com%3E
> >
> > I am now calling for a vote in Incubator general to approve the release
> of
> > the artifacts to maven.
>
> Only the source release is an official Apache release requiring a VOTE:
>
>   http://www.apache.org/legal/release-policy#compiled-packages
>
>   The Apache Software Foundation produces open source software. All
> releases
>   are in the form of the source materials needed to make changes to the
>   software being released.
>
>   As a convenience to users that might not have the appropriate tools to
> build
>   a compiled version of the source, binary/bytecode packages MAY be
>   distributed alongside official Apache releases. In all such cases, the
>   binary/bytecode package MUST have the same version number as the source
>   release and MUST only add binary/bytecode files that are the result of
>   compiling that version of the source code release and its dependencies.
>
> This VOTE is not necessary and should not be completed.  Assuming that the
> binary package adheres to the requirements spelled out at the link above,
> you
> should already have what you need to distribute it in accordance with
> Release
> Distribution Policy:
>
>   http://www.apache.org/dev/release-distribution
>
> Hope this helps,
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Apache DataFu 1.3.0 (incubating) release to maven

[Matthew Hayes]

Hi all,

The Apache DataFu community has voted on and approved a proposal to release
Apache DataFu 1.3.0 (incubating) archives to Maven:


http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201512.mbox/%3CCAA4Vo8Bg-2hj98azHnhhYRbaah5dTq%3Dhx3jxs8thWUYmR4k9kQ%40mail.gmail.com%3E

Note that the source release vote passed on November 15th:


http://mail-archives.apache.org/mod_mbox/incubator-general/201511.mbox/%3CCAA4Vo8AdnsvZtEeWKEDUt72HzCEVhaNqbX4jnXDf0_joTx5V%3Dg%40mail.gmail.com%3E

I am now calling for a vote in Incubator general to approve the release of
the artifacts to maven.  I've created a staging repository from the 1.3.0
source release in Apache's Nexus Repository, which you can access at:

https://repository.apache.org/content/repositories/orgapachedatafu-1001

Instructions on obtaining the source release and building can be found at:
http://datafu.incubator.apache.org/docs/quick-start.html

The vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Matt, on behalf of the Apache DataFu PPMC

Re: [VOTE] Apache DataFu 1.3.0 (incubating)

[Matthew Hayes]

Thanks Jakob, Roman, and Ashutosh.  I've filed JIRAs for the issues you've
raised.  We can address them in the next minor source release.

-Matt

On Sat, Nov 14, 2015 at 9:06 AM, Ashutosh Chauhan <hashut...@apache.org>
wrote:

> +1 (binding)
>
> Signatures & md5 matches. LICENSE & NOTICE looks good except for what Roman
> & Jakob noted.
>
> Thanks,
> Ashutosh
>
> On Sat, Nov 14, 2015 at 8:46 AM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > On Wed, Nov 11, 2015 at 5:33 PM, Matthew Hayes
> > <matthew.terence.ha...@gmail.com> wrote:
> > > Hi all,
> > >
> > > The Apache DataFu community has voted on and approved a proposal to
> > release
> > > Apache DataFu 1.3.0 (incubating).  This is the first release since the
> > > project began incubating!
> > >
> > > Proposal:
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201511.mbox/%3CCAA4Vo8BR_-8whhNYr6jUdXTrE2ZYZWwJEx2XvgHDt22SRyr55w%40mail.gmail.com%3E
> > >
> > > Results:
> > >
> > > 3 binding +1 votes
> > > No 0 votes
> > > No -1 votes
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201511.mbox/%3CCAA4Vo8ARiFsxZnRbZ-QPp9y_%2B_2SDhA%3DT4UChH24kaqtLG-PMA%40mail.gmail.com%3E
> > >
> > > You can download the release candidate RC1 here:
> > >
> > > http://people.apache.org/~mhayes/incubator-datafu-1.3.0-rc1/
> > >
> > > This has been signed with PGP key 01D3DE61, which is included in the
> > > repository's KEYS file.  This key can be found on keyservers, such as:
> > >
> > > http://pgp.mit.edu/pks/lookup?op=get=0x01D3DE61
> > >
> > > The release candidate has been tagged with release-1.3.0-rc1, which has
> > > been signed with the same key.  You can also checkout branch 1.3.0.
> For
> > > repo checkout instructions, please see:
> > >
> > > http://datafu.incubator.apache.org/community/contributing.html
> > >
> > > For reference, here is a list of all closed JIRAs tagged with 1.3.0:
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20DATAFU%20AND%20fixVersion%20%3D%201.3.0%20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%20status%20DESC%2C%20priority%20DESC
> > >
> > > For a summary of the changes, see:
> > >
> > > https://github.com/apache/incubator-datafu/blob/master/changes.md
> > >
> > > The vote will be open for 72 hours.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> >
> > +1 (binding)
> >
> > Nits:
> >1. I'd like to see a code signing key associated with an ASF email
> >in addition to gmail.com address.
> >2. I'd like to see see bottom of LICENSE move to NOTICE
> >
> > * checked sigs and hashes
> > * checked that the release corresponds to an repo tag
> > * LICENSE file looks OK, but I don't think other LICENSE notices
> >   belong there. They typically belong to... NOTICE ;-)
> > * the build works fine
> > * headers look fine (sans Jakob's comment)
> >
> > Thanks,
> > Roman.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

[RESULT] [VOTE] Apache DataFu 1.3.0 (incubating)

[Matthew Hayes]

The vote has passed with four +1 binding votes, and no -1s or 0s.

Jakob Homan  +1 (binding)
Roman Shaposhnik  +1 (binding)
Ashutosh Chauhan  +1 (binding)
Justin Mclean  +1 (binding)

Thanks to all who voted and took the time to look over the release!

Also, thanks Justin for your comments and clarifications.  I will
file/update JIRAs accordingly for the next release.

-Matt


On Sat, Nov 14, 2015 at 3:30 PM, Justin Mclean  wrote:

> Hi,
>
> > * I don't see bootstrap (./site/source/javascripts/bootstrap.js,
> > ./site/source/javascripts/bootstrap.min.js) in the LICENSE file.
>
> As this versions of bootstrap is Apache licensed there is no need to add
> it to LICENSE. [1] As there is no NOTICE file nothing need to be added to
> NOTICE [1][2]
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/dev/licensing-howto.html#alv2-dep <
> http://www.apache.org/dev/licensing-howto.html#alv2-dep>
> 2. https://github.com/twbs/bootstrap/tree/v2.0.3 <
> https://github.com/twbs/bootstrap/tree/v2.0.3>

[VOTE] Apache DataFu 1.3.0 (incubating)

[Matthew Hayes]

Hi all,

The Apache DataFu community has voted on and approved a proposal to release
Apache DataFu 1.3.0 (incubating).  This is the first release since the
project began incubating!

Proposal:

http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201511.mbox/%3CCAA4Vo8BR_-8whhNYr6jUdXTrE2ZYZWwJEx2XvgHDt22SRyr55w%40mail.gmail.com%3E

Results:

3 binding +1 votes
No 0 votes
No -1 votes

http://mail-archives.apache.org/mod_mbox/incubator-datafu-dev/201511.mbox/%3CCAA4Vo8ARiFsxZnRbZ-QPp9y_%2B_2SDhA%3DT4UChH24kaqtLG-PMA%40mail.gmail.com%3E

You can download the release candidate RC1 here:

http://people.apache.org/~mhayes/incubator-datafu-1.3.0-rc1/

This has been signed with PGP key 01D3DE61, which is included in the
repository's KEYS file.  This key can be found on keyservers, such as:

http://pgp.mit.edu/pks/lookup?op=get=0x01D3DE61

The release candidate has been tagged with release-1.3.0-rc1, which has
been signed with the same key.  You can also checkout branch 1.3.0.  For
repo checkout instructions, please see:

http://datafu.incubator.apache.org/community/contributing.html

For reference, here is a list of all closed JIRAs tagged with 1.3.0:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20DATAFU%20AND%20fixVersion%20%3D%201.3.0%20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%20status%20DESC%2C%20priority%20DESC

For a summary of the changes, see:

https://github.com/apache/incubator-datafu/blob/master/changes.md

The vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
Matt, on behalf of the Apache DataFu PPMC

Re: apache package naming convention

[Matthew Hayes]

Thanks everyone for the feedback!

-Matt

On Mon, Aug 10, 2015 at 9:55 AM, Chris Nauroth cnaur...@hortonworks.com
wrote:

 Consideration of end user impact is a great point, and perhaps the most
 important consideration.  In the case of DataFu, others have brought up
 that the rename would be a backwards-incompatible change that breaks all
 existing client scripts that use DataFu, and going forward such a change
 would cause extra low-value typing in a scripting language that's targeted
 to serving non-programmers.  I think this makes a compelling argument for
 preserving the existing names in DataFu.  For another project where the
 package names are entirely an implementation detail and not user-facing,
 doing the rename is not likely to cause impact.

 Thanks for bringing up the topic, Matt.

 --Chris Nauroth




 On 8/10/15, 2:22 AM, Stian Soiland-Reyes st...@apache.org wrote:

 I think you should consider the impact and potential gain on a
 per-project basis, and agree this within the podling. I don't think we
 can prescribe one way or the other for every project.
 
 
 Changing the package name can for Java developers be a bit of an
 identity thing and help to level the playing field if a strong
 commercial actor is still involved. Removing
 com.proprietarycompany.projectname can be more important than removing
 a neutral org.projectname.
 
 
 A more user-fronting project (e.g. a GUI or self-contained server)
 face less impact on renaming than a project with many compile-bindings
 outside the project (e.g. Hadoop).
 
 
 For the Taverna incubator (which can't be reliably placed on such an
 axis with a GUI+server and many external plugins), we decided that as
 we were moving to Apache at the same time as we were getting ready for
 3.0 with a different plugin system anyway, then this was a good time
 (and perhaps the only time) to do package rename.
 
 But for our project, which had numerous git repositories, Maven
 modules and OSGi configurations (and was due some refactoring), a Java
 package rename and restructuring was a bit more work than a quick sed
 and folder move, and left the codebase in non-compilable flux for
 several months and took away focus from community building.
 
 On the other hand, this was a good exercise for engaging the whole of
 the PPMC in taking responsibility for all of the code base - for our
 project we had a history of divide-and-conquer responsibilities, but
 once we had agreed on the new structure, then several committers could
 help in getting the code back in shape. Deciding on the code base
 structure by committee in the open rather than through a visionary
 dictatorship is quite a bit of overhead, but also helps build a
 common understanding and buy-in of how the project should be.
 
 For an early project like the Commons RDF incubator, package rename
 was done in a day and had minimal impact. Here we didn't do any
 structural changes except splitting out a new module. I think keeping
 the change lightweight is the best option if possible.
 
 As Andy pointed out, for a mature project like Jena (with third-party
 bindings) you might consider to hold off package rename until the next
 major release, which could be years down the line. You can still use
 the org.apache.* packages for new stuff, and if you have a clear
 api/impl split, also gradually move impl modules under org.apache.
 
 
 
 
 On 10 August 2015 at 02:28, Roman Shaposhnik ro...@shaposhnik.org
 wrote:
  Thank you all for the feedback. This is super helpful!
 
  One question that I still have is this: do we have a bias
  for suggesting package rename or any package name
  can remain in place?
 
  Thanks,
  Roman.
 
  On Sat, Aug 8, 2015 at 2:25 AM, Andy Seaborne a...@apache.org wrote:
  Hi,
 
  Jena graduated 2012 with old namespaces under com.hp.hpl.jena, and some
  under org.openjena, with an intention to change at the first major
 release
  update.  As new packages came along, they went into org.apache.jena
 but the
  user facing packages remained where they were.
 
  We released Jena 3.0.0 last month, so 3 years. That major release was
  coupled to another incompatible change (RDF 1.1 semantics) so 3.x
  wasn't just to do the packages, package renaming waited until a
 convenient
  point.
 
  Our users have data with (RDF) namespaces under old names - we are not
  planning on changing that at all.  (A general issue for all linked
 data.)
 
  I don't see it as an issue for graduation if the project has
 considered the
  matter.
 
  Andy
 
 
  On 07/08/15 23:16, Matthew Hayes wrote:
 
  Hi all,
 
  Roman Shaposhnik suggested I open a discussion on the following topic:
 
  For Apache DataFu, all of the Java classes are declared in a datafu.*
  namespace.  This has been the naming convention since the DataFu
 project
  started in 2010.  Since DataFu became part of the Apache incubation
  process, the topic has come up of moving all of the classes into a
  org.apache.datafu.* namespace

apache package naming convention

[Matthew Hayes]

Hi all,

Roman Shaposhnik suggested I open a discussion on the following topic:

For Apache DataFu, all of the Java classes are declared in a datafu.*
namespace.  This has been the naming convention since the DataFu project
started in 2010.  Since DataFu became part of the Apache incubation
process, the topic has come up of moving all of the classes into a
org.apache.datafu.* namespace.  This was first discussed in January 2014
(see DATAFU-7) and most recently again in the past couple weeks.  The
consensus at the time last year was that it would be a huge pain for users
and not worth the cost.  It would break any script out there currently
using DataFu.  Also Jakob Homan and Russell Journey pointed out that this
is just a convention and not all Apache projects follow it.  Since we would
like DataFu to graduate sometime soon it would be good to clarify what the
requirements are on package naming conventions before we do a release.

Thoughts?

Thanks,
Matt

permission to edit wiki

[Matthew Hayes]

Hi I would like to add something to the wiki, can I please have access?  My 
login name is Matthew Hayes.

Thanks!
Matt

[PROPOSAL] DataFu for Incubation

[Matthew Hayes]

Hi all,

I would like to share our draft ASF incubation proposal for DataFu, a library 
that makes it easier to solve data problems in Hadoop and high level languages 
based on it.

The proposal can be found here:

https://wiki.apache.org/incubator/DataFuProposal

The source code is available on GitHub:

https://github.com/linkedin/datafu.

The text of the proposal is copied below.  Feedback is appreciated!

Thanks,
Matt

== Abstract ==

Data``Fu makes it easier to solve data problems using Hadoop and higher level 
languages based on it.

== Proposal ==

Data``Fu provides a collection of Hadoop Map``Reduce jobs and functions in 
higher level languages based on it to perform data analysis.  It provides 
functions for common statistics tasks (e.g. quantiles, sampling), Page``Rank, 
stream sessionization, and set and bag operations.  Data``Fu also provides 
Hadoop jobs for incremental data processing in Map``Reduce.

== Background ==

Data``Fu began two years ago as set of UDFs developed internally at Linked``In, 
coming from our desire to solve common problems with reusable components.  
Recognizing that the community could benefit from such a library, we added 
documentation, an extensive suite of unit tests, and open sourced the code.  
Since then there have been steady contributions to Data``Fu as we encountered 
common problems not yet solved by it.  Others outside Linked``In have 
contributed as well.  More recently we recognized the challenges with efficient 
incremental processing of data in Hadoop and have contributed a set of Hadoop 
Map``Reduce jobs as a solution.

Data``Fu began as a project at Linked``In, but it has shown itself to be useful 
to other organizations and developers as well as they have faced similar 
problems.  We would like to share Data``Fu with the ASF and begin developing a 
community of developers and users within Apache.

== Rationale ==

There is a strong need for well tested libraries that help developers solve 
common data problems in Hadoop and higher level languages such as Pig, Hive, 
Crunch, Scalding, etc.

== Current Status ==

=== Meritocracy ===

Our intent with this incubator proposal is to start building a diverse 
developer community around Data``Fu following the Apache meritocracy model.  
Since Data``Fu was initially open sourced in 2011, it has received 
contributions from both within and outside Linked``In.  We plan to continue 
support for new contributors and work with those who contribute significantly 
to the project to make them committers.

=== Community ===

Data``Fu has been building a community of developers for two years.  It began 
with contributors from Linked``In and has received contributions from 
developers at Cloudera since very early on.  It has been included included in 
Cloudera’s Hadoop Distribution and Apache Bigtop.  We hope to extend our 
contributor base significantly and invite all those who are interested in 
solving large-scale data processing problems to participate.

=== Core Developers ===

Data``Fu has a strong base of developers at Linked``In.  Matthew Hayes 
initiated the project in 2011, and aside from continued contributions to 
Data``Fu has also contributed the sub-project Hourglass for incremental 
Map``Reduce processing.  Separate from Data``Fu he has also open sourced the 
White Elephant project.  Sam Shah contributed a significant portion of the 
original code and continues to contribute to the project.  William Vaughan has 
been contributing regularly to Data``Fu for the past two years.  Evion Kim has 
been contributing to Data``Fu for the past year.  Xiangrui Meng recently 
contributed implementations of scalable sampling algorithms based on research 
from a paper he published.  Chris Lloyd has provided some important bug fixes 
and unit tests.  Mitul Tiwari has also contributed to Data``Fu.  Mathieu 
Bastian has been developing Map``Reduce jobs that we hope to include in 
Data``Fu.  In addition he also leads the open source Gephi project.

=== Alignment ===

The ASF is the natural choice to host the Data``Fu project as its goal of 
encouraging community-driven open-source projects fits with our vision for 
Data``Fu.  Additionally, other projects Data``Fu integrates with, such as 
Apache Pig and Apache Hadoop, and in the future Apache Hive and Apache Crunch, 
are hosted by the ASF and we will benefit and provide benefit by close 
proximity to them.

== Known Risks ==

=== Orphaned Products ===

The core developers have been contributing to Data``Fu for the past two years.  
There is very little risk of Data``Fu being abandoned given its widespread use 
within Linked``In.

=== Inexperience with Open Source ===

Data``Fu was started as an open source project in 2011 and has remained so for 
two years.  Matt initiated the project, and additionally is the creator of the 
open source White Elephant project.  He has also contributed patches to Apache 
Pig.  Most recently he has released Hourglass as a sub-project of Data

RE: [PROPOSAL] DataFu for Incubation

[Matthew Hayes]

When we came up with the name a couple years ago, it was inspired by kung fu, 
in a playful way as Roman mentioned.  Sort of like saying your Java Fu or 
Python Fu is excellent.

-Matt

From: sebb [seb...@gmail.com]
Sent: Wednesday, December 18, 2013 3:57 PM
To: general@incubator.apache.org
Subject: Re: [PROPOSAL] DataFu for Incubation

On 18 December 2013 22:49, Matthew Hayes mha...@linkedin.com wrote:
 Hi all,

 I would like to share our draft ASF incubation proposal for DataFu, a library 
 that makes it easier to solve data problems in Hadoop and high level 
 languages based on it.

I am the only person to think that the last part of the name has
unfortunate connotations?
c.f. SNAFU which has the same last two characters.

 The proposal can be found here:

 https://wiki.apache.org/incubator/DataFuProposal

 The source code is available on GitHub:

 https://github.com/linkedin/datafu.

 The text of the proposal is copied below.  Feedback is appreciated!

 Thanks,
 Matt

 == Abstract ==

 Data``Fu makes it easier to solve data problems using Hadoop and higher level 
 languages based on it.

 == Proposal ==

 Data``Fu provides a collection of Hadoop Map``Reduce jobs and functions in 
 higher level languages based on it to perform data analysis.  It provides 
 functions for common statistics tasks (e.g. quantiles, sampling), Page``Rank, 
 stream sessionization, and set and bag operations.  Data``Fu also provides 
 Hadoop jobs for incremental data processing in Map``Reduce.

 == Background ==

 Data``Fu began two years ago as set of UDFs developed internally at 
 Linked``In, coming from our desire to solve common problems with reusable 
 components.  Recognizing that the community could benefit from such a 
 library, we added documentation, an extensive suite of unit tests, and open 
 sourced the code.  Since then there have been steady contributions to 
 Data``Fu as we encountered common problems not yet solved by it.  Others 
 outside Linked``In have contributed as well.  More recently we recognized the 
 challenges with efficient incremental processing of data in Hadoop and have 
 contributed a set of Hadoop Map``Reduce jobs as a solution.

 Data``Fu began as a project at Linked``In, but it has shown itself to be 
 useful to other organizations and developers as well as they have faced 
 similar problems.  We would like to share Data``Fu with the ASF and begin 
 developing a community of developers and users within Apache.

 == Rationale ==

 There is a strong need for well tested libraries that help developers solve 
 common data problems in Hadoop and higher level languages such as Pig, Hive, 
 Crunch, Scalding, etc.

 == Current Status ==

 === Meritocracy ===

 Our intent with this incubator proposal is to start building a diverse 
 developer community around Data``Fu following the Apache meritocracy model.  
 Since Data``Fu was initially open sourced in 2011, it has received 
 contributions from both within and outside Linked``In.  We plan to continue 
 support for new contributors and work with those who contribute significantly 
 to the project to make them committers.

 === Community ===

 Data``Fu has been building a community of developers for two years.  It began 
 with contributors from Linked``In and has received contributions from 
 developers at Cloudera since very early on.  It has been included included in 
 Cloudera’s Hadoop Distribution and Apache Bigtop.  We hope to extend our 
 contributor base significantly and invite all those who are interested in 
 solving large-scale data processing problems to participate.

 === Core Developers ===

 Data``Fu has a strong base of developers at Linked``In.  Matthew Hayes 
 initiated the project in 2011, and aside from continued contributions to 
 Data``Fu has also contributed the sub-project Hourglass for incremental 
 Map``Reduce processing.  Separate from Data``Fu he has also open sourced the 
 White Elephant project.  Sam Shah contributed a significant portion of the 
 original code and continues to contribute to the project.  William Vaughan 
 has been contributing regularly to Data``Fu for the past two years.  Evion 
 Kim has been contributing to Data``Fu for the past year.  Xiangrui Meng 
 recently contributed implementations of scalable sampling algorithms based on 
 research from a paper he published.  Chris Lloyd has provided some important 
 bug fixes and unit tests.  Mitul Tiwari has also contributed to Data``Fu.  
 Mathieu Bastian has been developing Map``Reduce jobs that we hope to include 
 in Data``Fu.  In addition he also leads the open source Gephi project.

 === Alignment ===

 The ASF is the natural choice to host the Data``Fu project as its goal of 
 encouraging community-driven open-source projects fits with our vision for 
 Data``Fu.  Additionally, other projects Data``Fu integrates with, such as 
 Apache Pig and Apache Hadoop, and in the future Apache Hive and Apache 
 Crunch