Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread chatz
Charitha Elvitigala On 21 January 2016 at 16:17, Jean-Baptiste Onofré wrote: > Hi Chatz, > > sure, what name should I use on the proposal, Charitha ? > > Regards > JB > > > On 01/21/2016 11:32 AM, chatz wrote: > >> Hi Jean, >> >> I’d be interested in contributing as well. >>

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Jean-Baptiste Onofré
Hi Chatz, sure, what name should I use on the proposal, Charitha ? Regards JB On 01/21/2016 11:32 AM, chatz wrote: Hi Jean, I’d be interested in contributing as well. Thanks, Chatz On 21 January 2016 at 14:22, Jean-Baptiste Onofré wrote: Sweet: you are on the

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Jean-Baptiste Onofré
Perfect: done, you are on the proposal. Thanks ! Regards JB On 01/21/2016 11:55 AM, chatz wrote: Charitha Elvitigala On 21 January 2016 at 16:17, Jean-Baptiste Onofré wrote: Hi Chatz, sure, what name should I use on the proposal, Charitha ? Regards JB On 01/21/2016

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread chatz
Hi Jean, I’d be interested in contributing as well. Thanks, Chatz On 21 January 2016 at 14:22, Jean-Baptiste Onofré wrote: > Sweet: you are on the proposal ;) > > Thanks ! > Regards > JB > > > On 01/21/2016 08:55 AM, Byung-Gon Chun wrote: > >> This looks very interesting.

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Jean-Baptiste Onofré
Sweet: you are on the proposal ;) Thanks ! Regards JB On 01/21/2016 08:55 AM, Byung-Gon Chun wrote: This looks very interesting. I'm interested in contributing. Thanks. -Gon --- Byung-Gon Chun On Thu, Jan 21, 2016 at 1:32 AM, James Malone < jamesmal...@google.com.invalid> wrote: Hello

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Alexander Bezzubov
Hi, it's great to see DataFlow becoming part to Apache ecosystem, thank you bringing it in. I would be happy to get involved and help. -- Alex On Thu, Jan 21, 2016 at 8:42 PM, Jean-Baptiste Onofré wrote: > Perfect: done, you are on the proposal. > > Thanks ! > Regards > JB

Re: Request for advice on code donation

2016-01-21 Thread Josh Elser
Cool, thanks for weighing in as well, Shane! I learned something new :) Shane Curcuru wrote: Alex has it right, and it's important to remember that the ASF never asks for copyright assignment of code; we only ask for an SGA grant or a voluntary submission from a contributor of ICLA signer. We

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Marvin Humphrey
On Wed, Jan 20, 2016 at 3:30 PM, James Malone wrote: > If we need to rename, we would ideally choose a new name, change the > project name at that time, and start our refactoring with that new name. Is > is acceptable for us to flag a name change as something we

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Jean-Baptiste Onofré
Hey Alex, awesome: I added you on the proposal. Thanks, Regards JB On 01/21/2016 05:03 PM, Alexander Bezzubov wrote: Hi, it's great to see DataFlow becoming part to Apache ecosystem, thank you bringing it in. I would be happy to get involved and help. -- Alex On Thu, Jan 21, 2016 at 8:42

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Supun Kamburugamuve
We are developing parallel machine learning algorithms for a research project and are very interested in DataFlow. I would like to contribute to this project as well. It will be great if you can add me. Thanks, Supun... On Thu, Jan 21, 2016 at 6:29 PM, Mayank Bansal wrote:

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Mayank Bansal
Hi Jean, Nice Proposal. I wanted to contribute to this project. Can you please add me too? Thanks a lot for the help Thanks, Mayank On Thu, Jan 21, 2016 at 8:07 AM, Jean-Baptiste Onofré wrote: > Hey Alex, > > awesome: I added you on the proposal. > > Thanks, > Regards >

Re: [VOTE] Release Apache FreeMarker 2.3.24-rc01 (incubating)

2016-01-21 Thread Justin Mclean
Hi, > Yes, they could be generated as part of the build, but > that wasn't done yet, and frankly that would just complicate the test > suite without practical benefits. Is there a JIRA to fix this for the next release? If may be (but unlikely IMO) that this applies [1]. Best to ask on legal

RE: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread Tsuyoshi Ozawa
Hi, I'm a core developer of Apache Hadoop and a contributor of Apache Tez. I'd be also interested in working on Apache Dataflow as an individual. Regards, - Tsuyoshi -Original Message- From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] Sent: Thursday, January 21, 2016 2:38 PM To:

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

2016-01-21 Thread Henri Yandell
On Wed, Jan 20, 2016 at 10:37 AM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > All of this can be worked during Incubation and I think we have > the right folks here who can help to get it set up. > Yup - my question was well answered; thanks all :) Hen

Re: [DISCUSS] Apache Dataflow Incubator Proposal

2016-01-21 Thread James Malone
Thank you for such a detailed response Marvin! Everything you mention makes a lot of sense. Needless to say, we don't want to squander cycles, break any rules, or throw velocity into disarray all due to a name. To that end, I am going to work with JB to amend the proposal with respect to

Re: [VOTE] Release Apache Twill-0.7.0-incubating

2016-01-21 Thread Henry Saputra
Hi IPMCs, Please help Twill community to VOTE on release. Thank you. - Henry On Sat, Jan 16, 2016 at 8:42 PM, Justin Mclean wrote: > Hi, > > +1 binding > > I checked: > - incubating in name > - signatures and hashes correct > - disclaimer exists > - LICENSE and NOTICE

Re: [VOTE] Release Apache FreeMarker 2.3.24-rc01 (incubating)

2016-01-21 Thread Daniel Dekany
Friday, January 22, 2016, 1:08:36 AM, Justin Mclean wrote: > Hi, > >> Yes, they could be generated as part of the build, but >> that wasn't done yet, and frankly that would just complicate the test >> suite without practical benefits. > > Is there a JIRA to fix this for the next release? Now