Re: {VOTE} move to gitbox

+1 We already do the code reviews and PRs almost entirely on Github and probably some of us use the sync'd Github repo for our upstream remote and not Apache so this will cut out some fat. > On Jul 5, 2017, at 5:35 PM, Suneel Marthi wrote: > >> On Wed, Jul 5, 2017 at 4:39

Re: [VOTE] Graduate Streams to TLP

+1 The community has grown and continues to make progress and has a handle on releasing according to Apache guidelines. The ActivityStreams implementation is a significant contribution. And there’s cross-fertilization with the Juneau project which shows it’s acting as part of the ASF in more

Re: GitHub repo

Do we talk to infra about doing this or is this a self-service change? > On May 17, 2017, at 12:18 PM, Joey Frazee <joey.fra...@icloud.com> wrote: > > +10 > >> On May 17, 2017, at 10:39 AM, Trevor Grant <trevor.d.gr...@gmail.com> wrote: >> >>

Re: GitHub repo

+10 > On May 17, 2017, at 10:39 AM, Trevor Grant wrote: > > Just heard that Apache now supports GitHub as primary repo (not mirroring > svn), just wanted to kick a thread off to see if there is any interest. > > Tg

Re: [DISCUSS] Adopt gitbox

How does gitbox fit into this? I’m totally on board with changing the origins so that the PR merges can be done directly from Github, but I don’t know if I understand the gitbox part. > On May 16, 2017, at 2:40 PM, sblackmon wrote: > > Hello, > > I learned this

Re: [VOTE] Release Apache Streams (incubating) 0.5 RC1

+1 (non-binding) - Verified signatures, hashes, and commit id - Successfully ran `mvn -T 4.0C clean install` on streams-project and streams-examples on Oracle JDK 1.8.0_121 and Mac OSX 10.12.3 - Successfully ran ITs with `mvn clean verify -DskipTests=true -DskipITs=false

Re: [VOTE] Streams-incubator 0.4.1 release

+1 (non-binding) - Verified tag/commit hashes, checksums, GPG signatures - Ran `mvn -T 3.0C clean install -Pcontrib-check` on streams-master on OS X 10.11.6 Oracle JDK 1.8.0_112 - Ran `mvn -T 3.0C clean install -DskipITs -Pcontrib-check` on streams-project on OS X 10.11.6 Oracle JDK 1.8.0_112

Re: [DISCUSS] Beam

I'm in favor of this for a few reasons: - There are enough stream processing frameworks out there that it makes it hard for us to offer much on that front. I don't think streams fills a gap for this internally so we have more to contribute in creating something that people can use with Beam.

Re: [DISCUSS] JSON.org license is now category-x

The PR is a year old so I'm not sure whether we can count on it. Can see if we can push it along though. > On Nov 14, 2016, at 11:41 AM, sblackmon wrote: > > Looking into this it’s already on Twitter4J’s radar and there’s an open > pull-request. > >

Re: [DISCUSS] JSON.org license is now category-x

> https://github.com/yusuke/twitter4j/pull/215 >> >> Provided they resolve and release again in the near future, the only >> action we’ll need to take is to upgrade. >> >> Any ideas on ways to scan all of our direct dependencies for usage of >> org.json:j

[DISCUSS] JSON.org license is now category-x

The ASF recently reclassified the JSON license for org.json as category-x because of its "shall be used for Good, not Evil" clause [1]. There does not appear to be any direct usage of it in Streams but there are a number of dependencies in Streams that do depend on org.json, most notably

Re: [VOTE] Release Apache Streams (incubating) 0.4 RC3

+1 (non-binding) Note that the vote announcement references 'Checksums of streams-examples-0.3-incubating-source-release.zip'. Need to change to 0.4 this before sending to incubator-general. - Verified checksums - Verified signatures with ls *.asc | xargs -n1 gpg --verify - Successfully ran

Re: Release Apache Streams (incubating) 0.4 rc2

It looks like these files are both there just as part of the documentation, so if I haven't misunderstood, this will be an easy fix. > On Nov 1, 2016, at 11:06 PM, Suneel Marthi wrote: > > In light of the issues reported by Justin on general@incubator, rolling > back

Re: Release Apache Streams (incubating) 0.4 rc2

Updating this to +1 (binding) > On Nov 1, 2016, at 7:33 AM, Ate Douma wrote: > > I'll try to validate this new rc4 candidate later this afternoon. > > Ate > >> On 2016-10-31 00:30, sblackmon wrote: >> >> >> I've created another combined 0.4-incubating release candidate (rc2),

[DISCUSS] Coding style conventions + auto-formatting

With some new contributors and project members joining, a question came up around coding conventions. Having something official is probably a necessary evil. Here are a few options: - https://google.github.io/styleguide/javaguide.html - 

Re: Submitting and Handling Github PRs

I've seen some use of Github PR comment templates/pre-filled forms to remind the submitter to do all the necessary stuff: - JIRA issue opened - JIRA issue in the title - Run contrib-check - Link to Apache CLA form - Anything else? It's a nice place to put the info since it's not uncommon for

Re: Switch to using Java 8

Oct 21, 2016 at 11:02 AM Suneel Marthi <suneel.mar...@gmail.com> wrote: Seems like we have a consensus here, @Steve would u be taking care of this? On Fri, Oct 21, 2016 at 10:39 AM, Joey Frazee <joey.fra...@icloud.com> wrote: > +1 > > On Oct 21, 2016, at 09:32 AM, sblac

Re: Switch to using Java 8

+1 On Oct 21, 2016, at 09:32 AM, sblackmon wrote: +1.  Impact should be minimal. Steve On October 21, 2016 at 9:29:49 AM, Suneel Marthi (smar...@apache.org) wrote: Proposing that we switch to Java 8 as of the upcoming release this weekend. Java 7 is EOL anyways. +1

Re: [VOTE] Release Apache Streams version 0.3-incubating

+1 (non-binding) - Verified checksums and signatures. - Ran mvn clean install test verify on OS X with Java 1.8.0_71 on streams-project. - Ran mvn clean install test verify -DskipITs on OS X with Java 1.8.0_71 on streams-examples. - Ran mvn clean install test verify on OS X with Java 1.8.0_71

Re: [VOTE] Retire Apache Streams to the attic

The discussion +/- retiring the project is probably the right discussion to be having, but I think in order to make a decision everyone ought to look at what steps could be taken to get it out of a rut, and whether there's reason to believe those would be successful. So far no one has said

Re: [DISCUSS] STREAMS-213 - maven site

Steve, Is the long-term plan here to have a commercial sponsor host these or to publish them on incubator.apache.org? I was going to suggest publishing them with the github repo (github.io), but given that the fork lives under apache’s org account it doesn’t seem like that’d work out. -joey