Re: MADLib "contributors"

2016-06-02 Thread Chris Mattmann
BTW, Roman, when discussing Spark’s move to Apache, and becoming
Apache Spark, this same question was asked. The things I’ve purported
in these situations is that it is fine to credit pre-Apache work as
simply the project name. Universities by their very nature don’t 
compete with companies, nor do they compete technologically with 501c3
charities and other foundations. I’m not saying they are prohibited
with competing. I’m saying, that there isn’t a competition. Companies can 
put 100-1000 people on a single feature. Universities don’t have the bandwidth
to do that at a University, and they are a different beast, than say,
company X, company Y and Z that have agreed to bring prior project A
now renamed Apache A. We should assume good faith in these situations
dealing with prior use. Clarifications are always welcomed, but we’re 
not going to go back and update 1000+ research papers and change all
references of Spark to Apache Spark it’s not feasible, nor is it desired
because it was Spark first, to start out with, and academic research use
is not competing with its use or name as an Apache project.



On 6/2/16, 5:22 PM, "shaposh...@gmail.com on behalf of Roman Shaposhnik" 
 wrote:

>Please stop putting a public mailing list on the same To: line as a
>private one. This is a pretty dangerous habit.
>
>I'll replace private@madlib with dev@madlib. Please reply to that part
>of the thread.
>
>Thanks,
>Roman.
>
>On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:
>> Looking at:
>>
>> http://madlib.incubator.apache.org/community.html
>>
>> I am not sure I like the statement that:
>>
>> "including both individuals and institutions. Amongst our current 
>> contributors:"
>>
>> and then a list of entities.
>>
>> There are only individuals who contribute. Not institutions. In other
>> words, Pivotal is not a "contributor"... nor is ANY institution.
>>
>> Please fix this. Thx!
>>
>> PS: I am not on the private@madlib list
>> -
>> 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: MADLib "contributors"

2016-06-02 Thread Roman Shaposhnik
Please stop putting a public mailing list on the same To: line as a
private one. This is a pretty dangerous habit.

I'll replace private@madlib with dev@madlib. Please reply to that part
of the thread.

Thanks,
Roman.

On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:
> Looking at:
>
> http://madlib.incubator.apache.org/community.html
>
> I am not sure I like the statement that:
>
> "including both individuals and institutions. Amongst our current 
> contributors:"
>
> and then a list of entities.
>
> There are only individuals who contribute. Not institutions. In other
> words, Pivotal is not a "contributor"... nor is ANY institution.
>
> Please fix this. Thx!
>
> PS: I am not on the private@madlib list
> -
> 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: MADLib "contributors"

2016-06-02 Thread Roman Shaposhnik
Changing private -> dev.

Correct. But credit needs to be given where credit is due. I'm actually
in the middle of a very similar discussion here at AMPlab with Spark
folks. Now that they acknowledged that all ongoing contributions should
be credited according to the Apache Way, they are asking a fair question:
how can they cite work that happened in Spark prior to entering ASF.

It is easier for projects like Gemfire, where all prior history remained with
the old name. It is more difficult for MADlib and Spark and a host of others.

In short, I agree with Jim observations that the page needs to be clarified,
but it needs to be clarified in a much more thoughtful way so that we
acknowledge past history of the project.

Thanks,
Roman.

On Thu, Jun 2, 2016 at 1:00 PM, Jim Jagielski  wrote:
> Part of the incubation process is to fully embrace the tenets of the
> Apache Way; considering that MADlib started in Sept 2015 and it is
> now June 2016, I would have expected that the page would have been
> changed awhile ago. It does beg the question on whether or not
> MADlib itself fully groks how important this issue is, allowing the
> page to continue as-is for so long...
>
>
>> On Jun 2, 2016, at 3:52 PM, Gregory Chase  wrote:
>>
>> In MADlib's history, contribution was enabled by institutions prior to
>> coming to Apache.  However, I agree that this needs to be "historical" not
>> "current.
>>
>> -Greg
>>
>> On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:
>>
>>> Looking at:
>>>
>>>http://madlib.incubator.apache.org/community.html
>>>
>>> I am not sure I like the statement that:
>>>
>>>"including both individuals and institutions. Amongst our current
>>> contributors:"
>>>
>>> and then a list of entities.
>>>
>>> There are only individuals who contribute. Not institutions. In other
>>> words, Pivotal is not a "contributor"... nor is ANY institution.
>>>
>>> Please fix this. Thx!
>>>
>>> PS: I am not on the private@madlib list
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>>
>> --
>> Greg Chase
>>
>> Global Head, Big Data Communities
>> http://www.pivotal.io/big-data
>>
>> Pivotal Software
>> http://www.pivotal.io/
>>
>> 650-215-0477
>> @GregChase
>> Blog: http://geekmarketing.biz/
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Request to add project proposal to Incubator Wiki.

2016-06-02 Thread John D. Ament
Yes, it would.

When I said mentor I meant champion.  So if you're in need of one, and no
one else steps up, I'd be happy to help.

sleep-- lately. :-)

John

On Thu, Jun 2, 2016 at 3:10 PM James Bognar 
wrote:

> Thanks John!
>
> I've added a new page...
>
> https://wiki.apache.org/incubator/JuneauProposal
>
> I guess my next step is to find a Champion?
>
>
> > James,
> >
> > I've added you, please edit away.
> >
> > If you're in need of a mentor, I'd be happy to help.
> >
> > John
>
>
> --
> James Bognar
>


Re: [VOTE] Graduate Apache Twill as Top Level Project

2016-06-02 Thread John D. Ament
Henry,

Just wondering if you can give me an answer on
https://lists.apache.org/thread.html/Zmz8ynxuks2ynai ?

I'm -1 until then, due to lack of community growth in the past 10 months.

John

On Thu, Jun 2, 2016 at 6:06 PM Henry Saputra 
wrote:

> Hi All,
>
> Following the DISCUSS thread about Apache Twill graduating as TLP, I would
> like to send VOTE request thread.
>
> All the +1 binding votes sent in the DISCUSS will be counted in the final
> tally unless the individual request otherwise.
>
> Here is the link to the VOTE in dev@ list:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
>
>
> Here is link to the VOTE result summary in the dev@list :
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
>
>
> The VOTE will run until June 6, 2016 4pm PST
>
> +1 [  ]
> 0 [  ]
> -1 [  ]
>
>
>
> Thanks,
>
> - Henry
> On behalf of Apache Twill PPMC
>
>
> PS:
>
> Here is my vote:
>
> +1 (binding)
>
>
>
>
> ## Resolution to create a TLP from graduating Incubator podling
>
>
> X. Establish the Apache Twill Project
>
>
>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, related to providing a set of libraries as
> abstraction to develop
>
>distributed applications, with a programming model that is similar
> to
>
>running threads, inside compute cluster such as Apache Hadoop YARN
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>
>Committee (PMC), to be known as the "Apache Twill Project",
>
>be and hereby is established pursuant to Bylaws of the
>
>Foundation; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby is
>
>responsible for the creation and maintenance of software
>
>related to providing a set of libraries as abstraction to develop
>
>distributed applications, with a programming model that is similar
> to
>
>running threads, inside compute cluster such as Apache Hadoop YARN
>
>and be it further
>
>
>RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
>
>for management of the projects within the scope of
>
>responsibility of the Apache Twill 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 Twill Project:
>
>
>  * Terence Yim 
>
>  * Andreas Neumann 
>
>  * Gary Helmling 
>
>  * Albert Shau 
>
>  * Poorna Chandra 
>
>  * Henry Saputra 
>
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
>
>be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby
>
>is tasked with the migration and rationalization of the Apache
>
>Incubator Twill podling; and be it further
>
>
>RESOLVED, that all responsibilities pertaining to the Apache
>
>Incubator Twill podling encumbered upon the Apache Incubator
>
>Project are hereafter discharged.
>


Re: [VOTE] Graduate Apache Twill as Top Level Project

2016-06-02 Thread Amol Kekre
+1 (non-binding)

Thks
Amol

On Thu, Jun 2, 2016 at 3:27 PM, James Taylor  wrote:

> +1 (binding)
>
> On Thursday, June 2, 2016, Andrew Purtell  wrote:
>
> > +1 (binding)
> >
> > On Thu, Jun 2, 2016 at 3:06 PM, Henry Saputra  > >
> > wrote:
> >
> > > Hi All,
> > >
> > > Following the DISCUSS thread about Apache Twill graduating as TLP, I
> > would
> > > like to send VOTE request thread.
> > >
> > > All the +1 binding votes sent in the DISCUSS will be counted in the
> final
> > > tally unless the individual request otherwise.
> > >
> > > Here is the link to the VOTE in dev@ list:
> > >
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
> > >
> > >
> > > Here is link to the VOTE result summary in the dev@list :
> > >
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
> > >
> > >
> > > The VOTE will run until June 6, 2016 4pm PST
> > >
> > > +1 [  ]
> > > 0 [  ]
> > > -1 [  ]
> > >
> > >
> > >
> > > Thanks,
> > >
> > > - Henry
> > > On behalf of Apache Twill PPMC
> > >
> > >
> > > PS:
> > >
> > > Here is my vote:
> > >
> > > +1 (binding)
> > >
> > >
> > >
> > >
> > > ## Resolution to create a TLP from graduating Incubator podling
> > >
> > >
> > > X. Establish the Apache Twill Project
> > >
> > >
> > >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, related to providing a set of libraries as
> > > abstraction to develop
> > >
> > >distributed applications, with a programming model that is
> similar
> > > to
> > >
> > >running threads, inside compute cluster such as Apache Hadoop
> YARN
> > >
> > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >
> > >Committee (PMC), to be known as the "Apache Twill Project",
> > >
> > >be and hereby is established pursuant to Bylaws of the
> > >
> > >Foundation; and be it further
> > >
> > >
> > >RESOLVED, that the Apache Twill Project be and hereby is
> > >
> > >responsible for the creation and maintenance of software
> > >
> > >related to providing a set of libraries as abstraction to
> develop
> > >
> > >distributed applications, with a programming model that is
> similar
> > > to
> > >
> > >running threads, inside compute cluster such as Apache Hadoop
> YARN
> > >
> > >and be it further
> > >
> > >
> > >RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
> > >
> > >for management of the projects within the scope of
> > >
> > >responsibility of the Apache Twill 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 Twill Project:
> > >
> > >
> > >  * Terence Yim >
> > >
> > >  * Andreas Neumann >
> > >
> > >  * Gary Helmling >
> > >
> > >  * Albert Shau >
> > >
> > >  * Poorna Chandra >
> > >
> > >  * Henry Saputra >
> > >
> > >
> > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
> > >
> > >be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further
> > >
> > >
> > >RESOLVED, that the Apache Twill Project be and hereby
> > >
> > >is tasked with the migration and rationalization of the Apache
> > >
> > >Incubator Twill podling; and be it further
> > >
> > >
> > >RESOLVED, that all responsibilities pertaining to the Apache
> > >
> > >Incubator Twill podling encumbered upon the Apache Incubator
> > >
> > >Project are hereafter discharged.
> > >
> >
> >
> >

Re: [VOTE] Graduate Apache Twill as Top Level Project

2016-06-02 Thread James Taylor
+1 (binding)

On Thursday, June 2, 2016, Andrew Purtell  wrote:

> +1 (binding)
>
> On Thu, Jun 2, 2016 at 3:06 PM, Henry Saputra  >
> wrote:
>
> > Hi All,
> >
> > Following the DISCUSS thread about Apache Twill graduating as TLP, I
> would
> > like to send VOTE request thread.
> >
> > All the +1 binding votes sent in the DISCUSS will be counted in the final
> > tally unless the individual request otherwise.
> >
> > Here is the link to the VOTE in dev@ list:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
> >
> >
> > Here is link to the VOTE result summary in the dev@list :
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
> >
> >
> > The VOTE will run until June 6, 2016 4pm PST
> >
> > +1 [  ]
> > 0 [  ]
> > -1 [  ]
> >
> >
> >
> > Thanks,
> >
> > - Henry
> > On behalf of Apache Twill PPMC
> >
> >
> > PS:
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
> >
> >
> >
> > ## Resolution to create a TLP from graduating Incubator podling
> >
> >
> > X. Establish the Apache Twill Project
> >
> >
> >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, related to providing a set of libraries as
> > abstraction to develop
> >
> >distributed applications, with a programming model that is similar
> > to
> >
> >running threads, inside compute cluster such as Apache Hadoop YARN
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >
> >Committee (PMC), to be known as the "Apache Twill Project",
> >
> >be and hereby is established pursuant to Bylaws of the
> >
> >Foundation; and be it further
> >
> >
> >RESOLVED, that the Apache Twill Project be and hereby is
> >
> >responsible for the creation and maintenance of software
> >
> >related to providing a set of libraries as abstraction to develop
> >
> >distributed applications, with a programming model that is similar
> > to
> >
> >running threads, inside compute cluster such as Apache Hadoop YARN
> >
> >and be it further
> >
> >
> >RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
> >
> >for management of the projects within the scope of
> >
> >responsibility of the Apache Twill 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 Twill Project:
> >
> >
> >  * Terence Yim >
> >
> >  * Andreas Neumann >
> >
> >  * Gary Helmling >
> >
> >  * Albert Shau >
> >
> >  * Poorna Chandra >
> >
> >  * Henry Saputra >
> >
> >
> >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
> >
> >be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further
> >
> >
> >RESOLVED, that the Apache Twill Project be and hereby
> >
> >is tasked with the migration and rationalization of the Apache
> >
> >Incubator Twill podling; and be it further
> >
> >
> >RESOLVED, that all responsibilities pertaining to the Apache
> >
> >Incubator Twill podling encumbered upon the Apache Incubator
> >
> >Project are hereafter discharged.
> >
>
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>


Re: [VOTE] Graduate Apache Twill as Top Level Project

2016-06-02 Thread Andrew Purtell
+1 (binding)

On Thu, Jun 2, 2016 at 3:06 PM, Henry Saputra 
wrote:

> Hi All,
>
> Following the DISCUSS thread about Apache Twill graduating as TLP, I would
> like to send VOTE request thread.
>
> All the +1 binding votes sent in the DISCUSS will be counted in the final
> tally unless the individual request otherwise.
>
> Here is the link to the VOTE in dev@ list:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
>
>
> Here is link to the VOTE result summary in the dev@list :
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
>
>
> The VOTE will run until June 6, 2016 4pm PST
>
> +1 [  ]
> 0 [  ]
> -1 [  ]
>
>
>
> Thanks,
>
> - Henry
> On behalf of Apache Twill PPMC
>
>
> PS:
>
> Here is my vote:
>
> +1 (binding)
>
>
>
>
> ## Resolution to create a TLP from graduating Incubator podling
>
>
> X. Establish the Apache Twill Project
>
>
>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, related to providing a set of libraries as
> abstraction to develop
>
>distributed applications, with a programming model that is similar
> to
>
>running threads, inside compute cluster such as Apache Hadoop YARN
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>
>Committee (PMC), to be known as the "Apache Twill Project",
>
>be and hereby is established pursuant to Bylaws of the
>
>Foundation; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby is
>
>responsible for the creation and maintenance of software
>
>related to providing a set of libraries as abstraction to develop
>
>distributed applications, with a programming model that is similar
> to
>
>running threads, inside compute cluster such as Apache Hadoop YARN
>
>and be it further
>
>
>RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
>
>for management of the projects within the scope of
>
>responsibility of the Apache Twill 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 Twill Project:
>
>
>  * Terence Yim 
>
>  * Andreas Neumann 
>
>  * Gary Helmling 
>
>  * Albert Shau 
>
>  * Poorna Chandra 
>
>  * Henry Saputra 
>
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
>
>be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby
>
>is tasked with the migration and rationalization of the Apache
>
>Incubator Twill podling; and be it further
>
>
>RESOLVED, that all responsibilities pertaining to the Apache
>
>Incubator Twill podling encumbered upon the Apache Incubator
>
>Project are hereafter discharged.
>



-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)


[VOTE] Graduate Apache Twill as Top Level Project

2016-06-02 Thread Henry Saputra
Hi All,

Following the DISCUSS thread about Apache Twill graduating as TLP, I would
like to send VOTE request thread.

All the +1 binding votes sent in the DISCUSS will be counted in the final
tally unless the individual request otherwise.

Here is the link to the VOTE in dev@ list:

http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e


Here is link to the VOTE result summary in the dev@list :

http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e


The VOTE will run until June 6, 2016 4pm PST

+1 [  ]
0 [  ]
-1 [  ]



Thanks,

- Henry
On behalf of Apache Twill PPMC


PS:

Here is my vote:

+1 (binding)




## Resolution to create a TLP from graduating Incubator podling


X. Establish the Apache Twill Project


   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, related to providing a set of libraries as
abstraction to develop

   distributed applications, with a programming model that is similar to

   running threads, inside compute cluster such as Apache Hadoop YARN

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

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

   be and hereby is established pursuant to Bylaws of the

   Foundation; and be it further


   RESOLVED, that the Apache Twill Project be and hereby is

   responsible for the creation and maintenance of software

   related to providing a set of libraries as abstraction to develop

   distributed applications, with a programming model that is similar
to

   running threads, inside compute cluster such as Apache Hadoop YARN

   and be it further


   RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility

   for management of the projects within the scope of

   responsibility of the Apache Twill 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 Twill Project:


 * Terence Yim 

 * Andreas Neumann 

 * Gary Helmling 

 * Albert Shau 

 * Poorna Chandra 

 * Henry Saputra 


   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim

   be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further


   RESOLVED, that the Apache Twill Project be and hereby

   is tasked with the migration and rationalization of the Apache

   Incubator Twill podling; and be it further


   RESOLVED, that all responsibilities pertaining to the Apache

   Incubator Twill podling encumbered upon the Apache Incubator

   Project are hereafter discharged.


Re: [DICSUSS] Graduation of Apache Twill as Top Level Project

2016-06-02 Thread Henry Saputra
Thanks for all the inputs. Seemed like we have positive response word Twill
to graduate I will kick off official VOTE thread.

Will count all +1 in this thread unless you change your mind.

Thanks,

Henry

On Wed, Jun 1, 2016 at 10:24 AM, Henry Saputra 
wrote:

> Hi All,
>
> The Apache Twill PPMCs and the community had discussed and voted to
> graduate to become Apache TLP.
>
> It is a small but welcoming community, and the mentors and rest of PPMCs
> believe that we have satisfied the learning phase during our incubation
> period.
>
> The community has made several good releases and added new PPMC during its
> time in incubator [1]
>
> It also has been used by external project such as Cask Data CDAP [2] and
> Apache Fluo [3]
>
> The PPMCs also have made some presentations in conferences and meetups to
> be open and inclusive [4] [5]
>
>
> Here is the link to the VOTE:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
>
>
> Here is link to the VOTE result summary:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
>
> Thanks,
>
> - Henry
> On behalf of Apache Twill PPMC
>
>
> [1] http://incubator.apache.org/projects/twill.html
> [2] http://cdap.io
> [3] https://wiki.apache.org/incubator/FluoProposal
> [4]
> http://apacheconnorthamerica2014.sched.org/event/1fhOZ6T/harnessing-the-power-of-yarn-with-apache-twill
> [5]
> http://apachebigdata2016.sched.org/event/6Lzt/building-large-scale-applications-in-apache-hadoop-yarn-with-apache-twill-henry-saputra-terence-yim-apache-software-foundation?iframe=no&w=&sidebar=yes&bg=no
>
> ## Resolution to create a TLP from graduating Incubator podling
>
>
> X. Establish the Apache Twill Project
>
>
>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, related to providing a set of libraries to provide 
> abstraction
>
>to develop distributed applications such as with Apache Hadoop YARN.
>
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>
>Committee (PMC), to be known as the "Apache Twill Project",
>
>be and hereby is established pursuant to Bylaws of the
>
>Foundation; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby is
>
>responsible for the creation and maintenance of software
>
>related to providing a set of libraries to provide abstraction to 
> develop
>
>distributed applications such as with Apache Hadoop YARN
>
>and be it further
>
>
>RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
>
>for management of the projects within the scope of
>
>responsibility of the Apache Twill 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 Twill Project:
>
>
>  * Terence Yim 
>
>  * Andreas Neumann 
>
>  * Gary Helmling 
>
>  * Albert Shau 
>
>  * Poorna Chandra 
>
>  * Henry Saputra 
>
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
>
>be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby
>
>is tasked with the migration and rationalization of the Apache
>
>Incubator Twill podling; and be it further
>
>
>RESOLVED, that all responsibilities pertaining to the Apache
>
>Incubator Twill podling encumbered upon the Apache Incubator
>
>Project are hereafter discharged.
>
>


[VOTE] Release Apache Mynewt 0.9.0-incubating-rc3

2016-06-02 Thread Christopher Collins
Hello all,

I am pleased to be calling this vote for the source release of Apache
Mynewt 0.9.0. Given that it is version 0.x, it is still a bit of a beta.
This is the third release candidate for Mynewt 0.9.0 (rc3).  A summary
of what changed between the prior release candidates can be found in the
respective [CANCEL][VOTE] emails:
* rc1: https://lists.apache.org/thread.html/Zunmlysgs7hcywt
* rc2: https://lists.apache.org/thread.html/Zkeq5fu5s6r05tu

Apache Mynewt is a community-driven, permissively licensed open source
initiative for constrained, embedded applications. Mynewt provides a
real-time operating system, flash file system, network stacks, and
support utilities for real-world embedded systems.

For full release notes, please visit the Apache Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes.

[VOTE] thread:
https://lists.apache.org/thread.html/b01d7ebb991bfc8a3913cb623743ba68297694faf8fc15508d064ff9@1464633264@%3Cdev.mynewt.apache.org%3E

[RESULT][VOTE] thread:
https://lists.apache.org/thread.html/0ff6875703299d1f9b2e22fb43b3271ab102d8e6441e71575736fdde@%3Cdev.mynewt.apache.org%3E

[DISCUSS] thread:
https://lists.apache.org/thread.html/fbd7acb28c25bdb4e4d7c4bb7cb6ffa4236cc3e1cdc3999b5f07aced@1464633342@%3Cdev.mynewt.apache.org%3E


This release candidate was tested as follows:
1. Manual execution of the Mynewt test plan
   
(https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan).
2. The full unit test suite for this release was executed via "newt
   test all" with no failures. This testing was performed on the
   following platforms:
 * OS X 10.10.5
 * Linux 3.19.0 (Ubuntu 14.04)

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-0.9.0-incubating/rc3/

The commits under consideration are as follows:

blinky:
repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky
commit: b9a65d46d21c370f56ee934d4f24267ec62722ec

core:
repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core
commit: 054efdb9d9bb14b01f30d3184c9129e3cfd275c9

newt:
repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
commit: f0a27b6294c25b85c2a7a1e465c5d36ef467054d

In addition, the following newt convenience binaries are available:
linux: 
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-0.9.0-incubating/rc3/apache-mynewt-newt-bin-linux-0.9.0-incubating.tgz
osx: 
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-0.9.0-incubating/rc3/apache-mynewt-newt-bin-osx-0.9.0-incubating.tgz


The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS

The vote is open for at least 72 hours.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...

Thanks,
Chris

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: MADLib "contributors"

2016-06-02 Thread Frank McQuillan
Thanks for pointing this out, Jim.  I will update the page.

The MADlib project has endeavored to follow the Apache way in all we do,
under the fine mentorship of Roman Shaposhnik.  We take that charter
seriously.  We did detailed review of the web site
 and the wiki

when
we moved to ASF, but may not have caught everything.  If you have any other
suggestions on content, kindly let us know.

Regards,
Frank

On Thu, Jun 2, 2016 at 1:07 PM, Gregory Chase  wrote:

> I would agree that MADlib can use more contributors to help make these
> changes.  Would you like to join?
>
> -Greg
>
> On Thu, Jun 2, 2016 at 1:00 PM, Jim Jagielski  wrote:
>
> > Part of the incubation process is to fully embrace the tenets of the
> > Apache Way; considering that MADlib started in Sept 2015 and it is
> > now June 2016, I would have expected that the page would have been
> > changed awhile ago. It does beg the question on whether or not
> > MADlib itself fully groks how important this issue is, allowing the
> > page to continue as-is for so long...
> >
> >
> > > On Jun 2, 2016, at 3:52 PM, Gregory Chase  wrote:
> > >
> > > In MADlib's history, contribution was enabled by institutions prior to
> > > coming to Apache.  However, I agree that this needs to be "historical"
> > not
> > > "current.
> > >
> > > -Greg
> > >
> > > On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski 
> wrote:
> > >
> > >> Looking at:
> > >>
> > >>http://madlib.incubator.apache.org/community.html
> > >>
> > >> I am not sure I like the statement that:
> > >>
> > >>"including both individuals and institutions. Amongst our current
> > >> contributors:"
> > >>
> > >> and then a list of entities.
> > >>
> > >> There are only individuals who contribute. Not institutions. In other
> > >> words, Pivotal is not a "contributor"... nor is ANY institution.
> > >>
> > >> Please fix this. Thx!
> > >>
> > >> PS: I am not on the private@madlib list
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Greg Chase
> > >
> > > Global Head, Big Data Communities
> > > http://www.pivotal.io/big-data
> > >
> > > Pivotal Software
> > > http://www.pivotal.io/
> > >
> > > 650-215-0477
> > > @GregChase
> > > Blog: http://geekmarketing.biz/
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Greg Chase
>
> Global Head, Big Data Communities
> http://www.pivotal.io/big-data
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/
>


Re: MADLib "contributors"

2016-06-02 Thread Gregory Chase
I would agree that MADlib can use more contributors to help make these
changes.  Would you like to join?

-Greg

On Thu, Jun 2, 2016 at 1:00 PM, Jim Jagielski  wrote:

> Part of the incubation process is to fully embrace the tenets of the
> Apache Way; considering that MADlib started in Sept 2015 and it is
> now June 2016, I would have expected that the page would have been
> changed awhile ago. It does beg the question on whether or not
> MADlib itself fully groks how important this issue is, allowing the
> page to continue as-is for so long...
>
>
> > On Jun 2, 2016, at 3:52 PM, Gregory Chase  wrote:
> >
> > In MADlib's history, contribution was enabled by institutions prior to
> > coming to Apache.  However, I agree that this needs to be "historical"
> not
> > "current.
> >
> > -Greg
> >
> > On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:
> >
> >> Looking at:
> >>
> >>http://madlib.incubator.apache.org/community.html
> >>
> >> I am not sure I like the statement that:
> >>
> >>"including both individuals and institutions. Amongst our current
> >> contributors:"
> >>
> >> and then a list of entities.
> >>
> >> There are only individuals who contribute. Not institutions. In other
> >> words, Pivotal is not a "contributor"... nor is ANY institution.
> >>
> >> Please fix this. Thx!
> >>
> >> PS: I am not on the private@madlib list
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
> >
> > --
> > Greg Chase
> >
> > Global Head, Big Data Communities
> > http://www.pivotal.io/big-data
> >
> > Pivotal Software
> > http://www.pivotal.io/
> >
> > 650-215-0477
> > @GregChase
> > Blog: http://geekmarketing.biz/
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/


Re: MADLib "contributors"

2016-06-02 Thread Jim Jagielski
Part of the incubation process is to fully embrace the tenets of the
Apache Way; considering that MADlib started in Sept 2015 and it is
now June 2016, I would have expected that the page would have been
changed awhile ago. It does beg the question on whether or not
MADlib itself fully groks how important this issue is, allowing the
page to continue as-is for so long...


> On Jun 2, 2016, at 3:52 PM, Gregory Chase  wrote:
> 
> In MADlib's history, contribution was enabled by institutions prior to
> coming to Apache.  However, I agree that this needs to be "historical" not
> "current.
> 
> -Greg
> 
> On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:
> 
>> Looking at:
>> 
>>http://madlib.incubator.apache.org/community.html
>> 
>> I am not sure I like the statement that:
>> 
>>"including both individuals and institutions. Amongst our current
>> contributors:"
>> 
>> and then a list of entities.
>> 
>> There are only individuals who contribute. Not institutions. In other
>> words, Pivotal is not a "contributor"... nor is ANY institution.
>> 
>> Please fix this. Thx!
>> 
>> PS: I am not on the private@madlib list
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> 
> -- 
> Greg Chase
> 
> Global Head, Big Data Communities
> http://www.pivotal.io/big-data
> 
> Pivotal Software
> http://www.pivotal.io/
> 
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: MADLib "contributors"

2016-06-02 Thread Gregory Chase
In MADlib's history, contribution was enabled by institutions prior to
coming to Apache.  However, I agree that this needs to be "historical" not
"current.

-Greg

On Thu, Jun 2, 2016 at 12:43 PM, Jim Jagielski  wrote:

> Looking at:
>
> http://madlib.incubator.apache.org/community.html
>
> I am not sure I like the statement that:
>
> "including both individuals and institutions. Amongst our current
> contributors:"
>
> and then a list of entities.
>
> There are only individuals who contribute. Not institutions. In other
> words, Pivotal is not a "contributor"... nor is ANY institution.
>
> Please fix this. Thx!
>
> PS: I am not on the private@madlib list
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/


MADLib "contributors"

2016-06-02 Thread Jim Jagielski
Looking at:

http://madlib.incubator.apache.org/community.html

I am not sure I like the statement that:

"including both individuals and institutions. Amongst our current 
contributors:"

and then a list of entities.

There are only individuals who contribute. Not institutions. In other
words, Pivotal is not a "contributor"... nor is ANY institution.

Please fix this. Thx!

PS: I am not on the private@madlib list
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[RESULT][VOTE] Accept CarbonData into the Apache Incubator

2016-06-02 Thread Jean-Baptiste Onofré

Hi,

I close this vote with only +1: welcome to Apache CarbonData in the 
Incubator !


I will request the resources creation.

Thanks all for your vote.

Regards
JB

On 05/25/2016 10:24 PM, Jean-Baptiste Onofré wrote:

Hi all,

following the discussion thread, I'm now calling a vote to accept
CarbonData into the Incubator.

​[ ] +1 Accept CarbonData into the Apache Incubator
[ ] +0 Abstain
[ ] -1 Do not accept CarbonData into the Apache Incubator, because ...

This vote is open for 72 hours.

The proposal follows, you can also access the wiki page:
https://wiki.apache.org/incubator/CarbonDataProposal

Thanks !
Regards
JB

= Apache CarbonData =

== Abstract ==

Apache CarbonData is a new Apache Hadoop native file format for faster
interactive
query using advanced columnar storage, index, compression and encoding
techniques
to improve computing efficiency, in turn it will help speedup queries an
order of
magnitude faster over PetaBytes of data.

CarbonData github address: https://github.com/HuaweiBigData/carbondata

== Background ==

Huawei is an ICT solution provider, we are committed to enhancing
customer experiences for telecom carriers, enterprises, and consumers on
big data, In order to satisfy the following customer requirements, we
created a new Hadoop native file format:

  * Support interactive OLAP-style query over big data in seconds.
  * Support fast query on individual record which require touching all
fields.
  * Fast data loading speed and support incremental load in period of
minutes.
  * Support HDFS so that customer can leverage existing Hadoop cluster.
  * Support time based data retention.

Based on these requirements, we investigated existing file formats in
the Hadoop eco-system, but we could not find a suitable solution that
satisfying requirements all at the same time, so we start designing
CarbonData.

== Rationale ==

CarbonData contains multiple modules, which are classified into two
categories:

  1. CarbonData File Format: which contains core implementation for file
format such as columnar,index,dictionary,encoding+compression,API for
reading/writing etc.
  2. CarbonData integration with big data processing framework such as
Apache Spark, Apache Hive etc. Apache Beam is also planned to abstract
the execution runtime.

=== CarbonData File Format ===

CarbonData file format is a columnar store in HDFS, it has many features
that a modern columnar format has, such as splittable, compression
schema ,complex data type etc. And CarbonData has following unique
features:

 Indexing 

In order to support fast interactive query, CarbonData leverage indexing
technology to reduce I/O scans. CarbonData files stores data along with
index, the index is not stored separately but the CarbonData file itself
contains the index. In current implementation, CarbonData supports 3
types of indexing:

1. Multi-dimensional Key (B+ Tree index)
  The Data block are written in sequence to the disk and within each
data blocks each column block is written in sequence. Finally, the
metadata block for the file is written with information about byte
positions of each block in the file, Min-Max statistics index and the
start and end MDK of each data block. Since, the entire data in the file
is in sorted order, the start and end MDK of each data block can be used
to construct a B+Tree and the file can be logically  represented as a
B+Tree with the data blocks as leaf nodes (on disk) and the remaining
non-leaf nodes in memory.
2. Inverted index
  Inverted index is widely used in search engine. By using this index,
it helps processing/query engine to do filtering inside one HDFS block.
Furthermore, query acceleration for count distinct like operation is
made possible when combining bitmap and inverted index in query time.
3. MinMax index
  For all columns, minmax index is created so that processing/query
engine can skip scan that is not required.

 Global Dictionary 

Besides I/O reduction, CarbonData accelerates computation by using
global dictionary, which enables processing/query engines to perform all
processing on encoded data without having to convert the data (Late
Materialization). We have observed dramatic performance improvement for
OLAP analytic scenario where table contains many columns in string data
type. The data is converted back to the user readable form just before
processing/query engine returning results to user.

 Column Group 

Sometimes users want to perform processing/query on multi-columns in one
table, for example, performing scan for individual record in
troubleshooting scenario. In this case, row format is more efficient
than columnar format since all columns will be touched by the workload.
To accelerate this, CarbonData supports storing a group of column in row
format, so data in column group is stored together and enable fast
retrieval.

 Optimized for multiple use cases 

CarbonData indices and dictionary is highly configurable. To make
storage optimize

Re: Fwd: Podling Report Reminder - June 2016

2016-06-02 Thread Gary Gregory
On Thu, Jun 2, 2016 at 1:51 AM, Sergio Fernández  wrote:

> On Thu, Jun 2, 2016 at 10:25 AM, Nick Burch  wrote:
>
>> On Thu, 2 Jun 2016, Sergio Fernández wrote:
>>
>>> Can anybody give karma to GaryGregory for editing the incubator wiki?
>>> Thanks.
>>>
>>
>> Karma granted, happy editing!
>
>
> Thanks, Nick!
>

Thank you all.

I signed off on the CommonsRDF report.

Gary

>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory


Re: Request to add project proposal to Incubator Wiki.

2016-06-02 Thread James Bognar
Thanks John!

I've added a new page...

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

I guess my next step is to find a Champion?


> James,
>
> I've added you, please edit away.
>
> If you're in need of a mentor, I'd be happy to help.
>
> John


-- 
James Bognar


RE: Request to add project proposal to Incubator Wiki

2016-06-02 Thread Benjamin Young
Awesome. Thanks, James!

-Original Message-
From: James Bognar [mailto:james.bog...@salesforce.com] 
Sent: Thursday, June 2, 2016 2:26 PM
To: general@incubator.apache.org
Subject: Re: Request to add project proposal to Incubator Wiki

Thanks Benjamin!  I was curious about that and expected someone to chime in 
right away :-)

I've update the website.


> Hey James,
>
> One quick note about the temporary web site you have up. It's probably
best to add "(incubating)" after the name and explain the projects status on 
the home page. Until the project makes it through incubation there is 
technically no "Apache Juneau" just "Apache Juneau (incubating)."
>
> /me channels Shane Curcuru for a bit. ;)
>
> That said, all the best as you go through incubation!
> Benjamin


--
James Bognar


Re: Request to add project proposal to Incubator Wiki

2016-06-02 Thread James Bognar
Thanks Benjamin!  I was curious about that and expected someone to chime in
right away :-)

I've update the website.


> Hey James,
>
> One quick note about the temporary web site you have up. It's probably
best to add "(incubating)" after the name and explain the projects status
on the home page. Until the project makes it through incubation there is
technically no "Apache Juneau" just "Apache Juneau (incubating)."
>
> /me channels Shane Curcuru for a bit. ;)
>
> That said, all the best as you go through incubation!
> Benjamin


-- 
James Bognar


Re: Lack of karma to manage LDAP groups as a mentor impediment

2016-06-02 Thread Marvin Humphrey
On Thu, Jun 2, 2016 at 10:04 AM, Josh Elser  wrote:

> I'm a little frustrated as this has just hit me across three different
> podlings in the past two days. Because I'm not a PMC chair, I don't have the
> ability to actually modify LDAP groups to grant the necessary karma to
> podling members to commit, access Jenkins, etc (e.g. modify_appgroups.pl)
>
> I'm not sure where to start with making this better, but I'm happy to engage
> whoever necessary to try to make sure that all mentors have the ability to
> help their podlings.

This typically comes up only for a minority of committers:

*   People who became committers on another Apache TLP before becoming a
committer on an Incubator podling (as opposed to people who join the
Incubator first and are thus already in the `incubator` ldap group after
Secretary processes their ICLA.)
*   People who need to access Jenkins and thus need `modify_appgroups.pl` run.

The stopgap is that we have a number of PMC Chairs on the IPMC, and if you
send a request to private@incubator someone can take care of it for you.  The
volume so far has been manageable.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Lack of karma to manage LDAP groups as a mentor impediment

2016-06-02 Thread Julian Hyde
And I’ll add to that, that while as member, IPMC member and PMC chair I 
probably have karma for most things, I often hesitate to put up my hand and say 
“I’ll do that” because I know there’s a chance that I’ll hit a permissions 
wall, and the 2 minute task becomes something that is at the back of my mind 
for the rest of my work day. In short, confusing permissions schemes slow 
things down.

Julian


> On Jun 2, 2016, at 10:04 AM, Josh Elser  wrote:
> 
> Hi all,
> 
> I'm a little frustrated as this has just hit me across three different 
> podlings in the past two days. Because I'm not a PMC chair, I don't have the 
> ability to actually modify LDAP groups to grant the necessary karma to 
> podling members to commit, access Jenkins, etc (e.g. modify_appgroups.pl)
> 
> I'm not sure where to start with making this better, but I'm happy to engage 
> whoever necessary to try to make sure that all mentors have the ability to 
> help their podlings.
> 
> Thanks in advance :)
> 
> - Josh
> 
> -
> 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] Release Apache Trafodion 2.0.0 (incubating)

2016-06-02 Thread Steve Varnau
Stian,

Thanks for the note. Since it says 5002 "applies to software containing or
designed for use with encryption software", means that we would add our dist
directory even if we do not bundle OpenSSL, but merely have code that links
with it?

--Steve


> -Original Message-
> From: Stian Soiland-Reyes [mailto:st...@apache.org]
> Sent: Thursday, June 2, 2016 7:20 AM
> To: general@incubator.apache.org
> Subject: RE: [VOTE] Release Apache Trafodion 2.0.0 (incubating)
>
> Note distributing OpenSSL mean you need to update the Trafodion entry on
>
> http://www.apache.org/licenses/exports/
>
> to also include your dist folder.
>
> On 1 Jun 2016 6:54 p.m., "Steve Varnau"  wrote:
>
> > Justin,
> >
> > Thanks for clarifying the issues here.  I will write JIRAs to fix the
> > two
> > minor issues in next release (clarify the rescinded BSD-4 clause and
> > remove
> > the GPL part of the dual license).
> >
> > Looking at the openssl issue, I want to figure out why we are statically
> > linking the libraries.  If there is a key reason it needs to be static
> > rather than dynamically linked, then I'll want to go to legal-discuss
> > and
> > ask whether we can distribute it, given license changes in the works.
> >
> > If we can change the build to change to dynamic linking and not include
> > openssl in the binaries, then perhaps the expedient thing is to go ahead
> > with this release, minus the client binary. And re-package it for next
> > release.
> >
> > Thanks!
> >
> > --Steve
> >
> >
> > > -Original Message-
> > > From: Justin Mclean [mailto:jus...@classsoftware.com]
> > > Sent: Tuesday, May 31, 2016 8:15 PM
> > > To: general@incubator.apache.org
> > > Subject: Re: [VOTE] Release Apache Trafodion 2.0.0 (incubating)
> > >
> > > Hi,
> > >
> > > +1 (binding) to release source package, but -1 for the client
> > > connivence
> > > binary
> > > until the 4 clause BSD licensing issue is resolved.
> > >
> > > For the source released I checked:
> > > - all files have incubating
> > > - signatures check out
> > > - disclaimer exists
> > > - LICENSE and NOTICE good
> > > - No unexpected binary in source
> > > - All ASF licensed file have ASF headers
> > >
> > > The source LICENSE has a minor issue. It mentions the 4 clause BSD
> > license
> > > which is not compatible with the Apache license (only the 2 and 3
> > > clause
> > > BSD
> > > licenses are) [1][2]. In this case the extra clause has been recinded
> > > [3]
> > > you
> > > might want to reword/state that in the license.
> > >
> > > But that does mean there is an issue with the client binary release as
> > > that
> > > includes OpenSSL which lists a 6 clause BSD style license (similar to
> > > a 4
> > > clause
> > > BSD license) and SSLeay under a 4 clause BSD license. You may need to
> > > clarify
> > > this on legal discuss. It may be that their intent to move to an
> > > Apache
> > > licence
> > > may mean you can hold off on doing anything but I’m not 100% sure.
> > > [4][5]
> > >
> > > I would also remove the GPL license text from the server’s LICENSE
> > > file
> > to
> > > make
> > > it clear which license it’s included under. If something is dual
> > > licensed
> > > you
> > > select which licence you want to use.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. http://www.apache.org/legal/resolved.html#category-a
> > > 2. https://issues.apache.org/jira/browse/LEGAL-185
> > > 3. https://opensource.org/licenses/BSD-3-Clause
> > > 4. https://www.openssl.org/blog/blog/2015/08/01/cla/
> > > 5. https://wiki.openssl.org/index.php/License
> > >
> > >
> > >
> > > -
> > > 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



Lack of karma to manage LDAP groups as a mentor impediment

2016-06-02 Thread Josh Elser

Hi all,

I'm a little frustrated as this has just hit me across three different 
podlings in the past two days. Because I'm not a PMC chair, I don't have 
the ability to actually modify LDAP groups to grant the necessary karma 
to podling members to commit, access Jenkins, etc (e.g. modify_appgroups.pl)


I'm not sure where to start with making this better, but I'm happy to 
engage whoever necessary to try to make sure that all mentors have the 
ability to help their podlings.


Thanks in advance :)

- Josh

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [DICSUSS] Graduation of Apache Twill as Top Level Project

2016-06-02 Thread Henry Saputra
Hi Niclas,

Thanks for the input. How about adding some clarification like:

"
related to providing a set of libraries to provide abstraction to develop
distributed applications with a programming model that is similar to
running threads inside compute cluster, such as Apache Hadoop YARN,  and
also providing built-in capabilities required by many distributed
applications, such as real-time logs and metrics collection, lifecycle
management, and network service discovery.
"

Thanks,

Henry


On Thu, Jun 2, 2016 at 3:59 AM, Niclas Hedhman  wrote:

> "providing a set of libraries to provide abstraction to develop distributed
> applications" sounds too generic and "nothing" to me. If I was on the
> board, I would push this back to be a bit more specific.
>
> Other than that, great work and good luck...
>
> On Thu, Jun 2, 2016 at 4:41 AM, Andrew Purtell 
> wrote:
>
> > I'd vote +1. Twill has been doing just fine for a while.
> >
> >
> > > On Jun 1, 2016, at 10:24 AM, Henry Saputra 
> > wrote:
> > >
> > > Hi All,
> > >
> > > The Apache Twill PPMCs and the community had discussed and voted to
> > > graduate to become Apache TLP.
> > >
> > > It is a small but welcoming community, and the mentors and rest of
> PPMCs
> > > believe that we have satisfied the learning phase during our incubation
> > > period.
> > >
> > > The community has made several good releases and added new PPMC during
> > its
> > > time in incubator [1]
> > >
> > > It also has been used by external project such as Cask Data CDAP [2]
> and
> > > Apache Fluo [3]
> > >
> > > The PPMCs also have made some presentations in conferences and meetups
> to
> > > be open and inclusive [4] [5]
> > >
> > >
> > > Here is the link to the VOTE:
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
> > >
> > >
> > > Here is link to the VOTE result summary:
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
> > >
> > > Thanks,
> > >
> > > - Henry
> > > On behalf of Apache Twill PPMC
> > >
> > >
> > > [1] http://incubator.apache.org/projects/twill.html
> > > [2] http://cdap.io
> > > [3] https://wiki.apache.org/incubator/FluoProposal
> > > [4]
> > >
> >
> http://apacheconnorthamerica2014.sched.org/event/1fhOZ6T/harnessing-the-power-of-yarn-with-apache-twill
> > > [5]
> > >
> >
> http://apachebigdata2016.sched.org/event/6Lzt/building-large-scale-applications-in-apache-hadoop-yarn-with-apache-twill-henry-saputra-terence-yim-apache-software-foundation?iframe=no&w=&sidebar=yes&bg=no
> > >
> > > ## Resolution to create a TLP from graduating Incubator podling
> > >
> > >
> > >X. Establish the Apache Twill Project
> > >
> > >
> > >   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, related to providing a set of libraries to provide
> > > abstraction
> > >
> > >   to develop distributed applications such as with Apache Hadoop
> > YARN.
> > >
> > >
> > >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >
> > >   Committee (PMC), to be known as the "Apache Twill Project",
> > >
> > >   be and hereby is established pursuant to Bylaws of the
> > >
> > >   Foundation; and be it further
> > >
> > >
> > >   RESOLVED, that the Apache Twill Project be and hereby is
> > >
> > >   responsible for the creation and maintenance of software
> > >
> > >   related to providing a set of libraries to provide abstraction
> > > to develop
> > >
> > >   distributed applications such as with Apache Hadoop YARN
> > >
> > >   and be it further
> > >
> > >
> > >   RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
> > >
> > >   for management of the projects within the scope of
> > >
> > >   responsibility of the Apache Twill 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 Twill Project:
> > >
> > >
> > > * Terence Yim 
> > >
> > > * Andreas Neumann 
> > >
> > > * Gary Helmling 
> > >
> > > * Albert Shau 
> > >
> > > * Poorna Chandra 
> > >
> > > * Henry Saputra 
> > >
> > >
> > >   NOW, THEREFORE, BE IT FURTHER RESOLVED, that

RE: [VOTE] Release Apache Trafodion 2.0.0 (incubating)

2016-06-02 Thread Stian Soiland-Reyes
Note distributing OpenSSL mean you need to update the Trafodion entry on

http://www.apache.org/licenses/exports/

to also include your dist folder.

On 1 Jun 2016 6:54 p.m., "Steve Varnau"  wrote:

> Justin,
>
> Thanks for clarifying the issues here.  I will write JIRAs to fix the two
> minor issues in next release (clarify the rescinded BSD-4 clause and remove
> the GPL part of the dual license).
>
> Looking at the openssl issue, I want to figure out why we are statically
> linking the libraries.  If there is a key reason it needs to be static
> rather than dynamically linked, then I'll want to go to legal-discuss and
> ask whether we can distribute it, given license changes in the works.
>
> If we can change the build to change to dynamic linking and not include
> openssl in the binaries, then perhaps the expedient thing is to go ahead
> with this release, minus the client binary. And re-package it for next
> release.
>
> Thanks!
>
> --Steve
>
>
> > -Original Message-
> > From: Justin Mclean [mailto:jus...@classsoftware.com]
> > Sent: Tuesday, May 31, 2016 8:15 PM
> > To: general@incubator.apache.org
> > Subject: Re: [VOTE] Release Apache Trafodion 2.0.0 (incubating)
> >
> > Hi,
> >
> > +1 (binding) to release source package, but -1 for the client connivence
> > binary
> > until the 4 clause BSD licensing issue is resolved.
> >
> > For the source released I checked:
> > - all files have incubating
> > - signatures check out
> > - disclaimer exists
> > - LICENSE and NOTICE good
> > - No unexpected binary in source
> > - All ASF licensed file have ASF headers
> >
> > The source LICENSE has a minor issue. It mentions the 4 clause BSD
> license
> > which is not compatible with the Apache license (only the 2 and 3 clause
> > BSD
> > licenses are) [1][2]. In this case the extra clause has been recinded [3]
> > you
> > might want to reword/state that in the license.
> >
> > But that does mean there is an issue with the client binary release as
> > that
> > includes OpenSSL which lists a 6 clause BSD style license (similar to a 4
> > clause
> > BSD license) and SSLeay under a 4 clause BSD license. You may need to
> > clarify
> > this on legal discuss. It may be that their intent to move to an Apache
> > licence
> > may mean you can hold off on doing anything but I’m not 100% sure. [4][5]
> >
> > I would also remove the GPL license text from the server’s LICENSE file
> to
> > make
> > it clear which license it’s included under. If something is dual licensed
> > you
> > select which licence you want to use.
> >
> > Thanks,
> > Justin
> >
> > 1. http://www.apache.org/legal/resolved.html#category-a
> > 2. https://issues.apache.org/jira/browse/LEGAL-185
> > 3. https://opensource.org/licenses/BSD-3-Clause
> > 4. https://www.openssl.org/blog/blog/2015/08/01/cla/
> > 5. https://wiki.openssl.org/index.php/License
> >
> >
> >
> > -
> > 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: What committers need to know about IP hygiene

2016-06-02 Thread Shane Curcuru
Jignesh Patel wrote on 6/1/16 6:42 PM:
> Thanks Julian!
> 
> This is very helpful and I’d like to suggest a perhaps having a good
> “default” policy in place that all incubators inherit on inception.
> They may choose to change the default if needed, but this approach
> installs some rail guards in place right away.

I would love to see the IPMC have an easy-to-understand set of default
project bylaws/procedures that are offered to each new podling to
consider for their use.  Not a requirement, but for some projects it
would really help to both get started and to have a better edited set of
these guidelines (that our projects have probably re-created dozens of
times by now).

> 
> As you and Roman have suggested, the Spark guidelines are crisp and a
> great start. Perhaps we could (with the permission of the Spark PMC)
> generalize that and make that the default for all incubators? I’m
> willing to help on that front as we need a crisp policy for
> Quickstep.

While it's polite to ask, it's not required to get permission -
everything is under the Apache license.  8-)

It's certainly a good idea to ask, because that might spur more folks to
collaborate on a really solid IPMC-suggested version.

> Apologies in advance if this suggestion blows against some well
> established principle. This is all new and a learning opportunity for
> all of us in the recently incubated Quickstep project.

No, this is just a good idea long overdue for coordinated action.
Obviously, not every podling will use all the guidelines, and
occasionally podlings come in from existing communities who might have
their own well-understood rules already.  The ASF requires a certain set
of minimum rules (voting, CLAs, IP provenance, branding, etc.) but
beyond that it's up to each group.

> Cheers,
> Jignesh 
> 
> 
>> On Jun 1, 2016, at 3:03 PM, Julian Hyde  wrote:
>>
>> A couple of projects I am mentoring have raised very similar questions 
>> recently:
>> * Do contributions via github PRs require a CLA?
>> * Do PRs require a JIRA case?
>>
>> I know the answers to these questions, but I was unable to find them clearly 
>> documented. All committers, including those in podlings, need to be very 
>> clear on IP policy. I looked in the Committers’ FAQ[1] and Guide for New 
>> Committers[2] but neither of them explicitly answered the questions. 
>> Searching for answers, I found legal JIRAs [3], [4] but we can’t expect all 
>> committers to find these.

I applaud the care and thoughtfulness you used to bring this issue up,
and completely agree with you.  Nice research too!

- Shane

>>
>> Now, maybe the answer is “Every project must write its own set of committer 
>> guidelines.” But if so, we as the IPMC should be helping podlings do that.
>>
>> Julian
>>
>> [1] http://www.apache.org/dev/committers.html 
>> 
>>
>> [2] http://www.apache.org/dev/new-committers-guide.html 
>> 
>>
>> [3] https://issues.apache.org/jira/browse/LEGAL-156 
>> 
>>
>> [4] https://issues.apache.org/jira/browse/LEGAL-249 
>> 
> 
> 
> -
> 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: [DICSUSS] Graduation of Apache Twill as Top Level Project

2016-06-02 Thread Jean-Baptiste Onofré

+1 (binding)

Regards
JB

On 06/01/2016 07:24 PM, Henry Saputra wrote:

Hi All,

The Apache Twill PPMCs and the community had discussed and voted to
graduate to become Apache TLP.

It is a small but welcoming community, and the mentors and rest of PPMCs
believe that we have satisfied the learning phase during our incubation
period.

The community has made several good releases and added new PPMC during its
time in incubator [1]

It also has been used by external project such as Cask Data CDAP [2] and
Apache Fluo [3]

The PPMCs also have made some presentations in conferences and meetups to
be open and inclusive [4] [5]


Here is the link to the VOTE:

http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e


Here is link to the VOTE result summary:

http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e

Thanks,

- Henry
On behalf of Apache Twill PPMC


[1] http://incubator.apache.org/projects/twill.html
[2] http://cdap.io
[3] https://wiki.apache.org/incubator/FluoProposal
[4]
http://apacheconnorthamerica2014.sched.org/event/1fhOZ6T/harnessing-the-power-of-yarn-with-apache-twill
[5]
http://apachebigdata2016.sched.org/event/6Lzt/building-large-scale-applications-in-apache-hadoop-yarn-with-apache-twill-henry-saputra-terence-yim-apache-software-foundation?iframe=no&w=&sidebar=yes&bg=no

## Resolution to create a TLP from graduating Incubator podling


 X. Establish the Apache Twill Project


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, related to providing a set of libraries to provide
abstraction

to develop distributed applications such as with Apache Hadoop YARN.


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

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

be and hereby is established pursuant to Bylaws of the

Foundation; and be it further


RESOLVED, that the Apache Twill Project be and hereby is

responsible for the creation and maintenance of software

related to providing a set of libraries to provide abstraction
to develop

distributed applications such as with Apache Hadoop YARN

and be it further


RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility

for management of the projects within the scope of

responsibility of the Apache Twill 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 Twill Project:


  * Terence Yim 

  * Andreas Neumann 

  * Gary Helmling 

  * Albert Shau 

  * Poorna Chandra 

  * Henry Saputra 


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim

be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further


RESOLVED, that the Apache Twill Project be and hereby

is tasked with the migration and rationalization of the Apache

Incubator Twill podling; and be it further


RESOLVED, that all responsibilities pertaining to the Apache

Incubator Twill podling encumbered upon the Apache Incubator

Project are hereafter discharged.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [DICSUSS] Graduation of Apache Twill as Top Level Project

2016-06-02 Thread Niclas Hedhman
"providing a set of libraries to provide abstraction to develop distributed
applications" sounds too generic and "nothing" to me. If I was on the
board, I would push this back to be a bit more specific.

Other than that, great work and good luck...

On Thu, Jun 2, 2016 at 4:41 AM, Andrew Purtell 
wrote:

> I'd vote +1. Twill has been doing just fine for a while.
>
>
> > On Jun 1, 2016, at 10:24 AM, Henry Saputra 
> wrote:
> >
> > Hi All,
> >
> > The Apache Twill PPMCs and the community had discussed and voted to
> > graduate to become Apache TLP.
> >
> > It is a small but welcoming community, and the mentors and rest of PPMCs
> > believe that we have satisfied the learning phase during our incubation
> > period.
> >
> > The community has made several good releases and added new PPMC during
> its
> > time in incubator [1]
> >
> > It also has been used by external project such as Cask Data CDAP [2] and
> > Apache Fluo [3]
> >
> > The PPMCs also have made some presentations in conferences and meetups to
> > be open and inclusive [4] [5]
> >
> >
> > Here is the link to the VOTE:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
> >
> >
> > Here is link to the VOTE result summary:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
> >
> > Thanks,
> >
> > - Henry
> > On behalf of Apache Twill PPMC
> >
> >
> > [1] http://incubator.apache.org/projects/twill.html
> > [2] http://cdap.io
> > [3] https://wiki.apache.org/incubator/FluoProposal
> > [4]
> >
> http://apacheconnorthamerica2014.sched.org/event/1fhOZ6T/harnessing-the-power-of-yarn-with-apache-twill
> > [5]
> >
> http://apachebigdata2016.sched.org/event/6Lzt/building-large-scale-applications-in-apache-hadoop-yarn-with-apache-twill-henry-saputra-terence-yim-apache-software-foundation?iframe=no&w=&sidebar=yes&bg=no
> >
> > ## Resolution to create a TLP from graduating Incubator podling
> >
> >
> >X. Establish the Apache Twill Project
> >
> >
> >   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, related to providing a set of libraries to provide
> > abstraction
> >
> >   to develop distributed applications such as with Apache Hadoop
> YARN.
> >
> >
> >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >
> >   Committee (PMC), to be known as the "Apache Twill Project",
> >
> >   be and hereby is established pursuant to Bylaws of the
> >
> >   Foundation; and be it further
> >
> >
> >   RESOLVED, that the Apache Twill Project be and hereby is
> >
> >   responsible for the creation and maintenance of software
> >
> >   related to providing a set of libraries to provide abstraction
> > to develop
> >
> >   distributed applications such as with Apache Hadoop YARN
> >
> >   and be it further
> >
> >
> >   RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
> >
> >   for management of the projects within the scope of
> >
> >   responsibility of the Apache Twill 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 Twill Project:
> >
> >
> > * Terence Yim 
> >
> > * Andreas Neumann 
> >
> > * Gary Helmling 
> >
> > * Albert Shau 
> >
> > * Poorna Chandra 
> >
> > * Henry Saputra 
> >
> >
> >   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
> >
> >   be appointed to the office of Vice President, Apache Twill, 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 Twill 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 Twill Project; and be it further
> >
> >
> >   RESOLVED, that the Apache Twill Project be and hereby
> >
> >   is tasked with the migration and rationalization of the Apache
> >
> >   Incubator Twill podli

Re: Fwd: Podling Report Reminder - June 2016

2016-06-02 Thread Sergio Fernández
On Thu, Jun 2, 2016 at 10:25 AM, Nick Burch  wrote:

> On Thu, 2 Jun 2016, Sergio Fernández wrote:
>
>> Can anybody give karma to GaryGregory for editing the incubator wiki?
>> Thanks.
>>
>
> Karma granted, happy editing!


Thanks, Nick!


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co


Re: Fwd: Podling Report Reminder - June 2016

2016-06-02 Thread Nick Burch

On Thu, 2 Jun 2016, Sergio Fernández wrote:
Can anybody give karma to GaryGregory for editing the incubator wiki? 
Thanks.


Karma granted, happy editing!

Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Grant write access to the Incubator Wiki for FranciscoPerezSorrosal

2016-06-02 Thread Nick Burch

On Thu, 2 Jun 2016, Francisco Perez-Sorrosal wrote:
Could you please grant write access to https://wiki.apache.org/incubator 
for id FranciscoPerezSorrosal?


Karma granted, enjoy!

Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Fwd: Podling Report Reminder - June 2016

2016-06-02 Thread Sergio Fernández
Can anybody give karma to GaryGregory for editing the incubator wiki?
Thanks.


-- Forwarded message --
From: Gary Gregory 
Date: Thu, Jun 2, 2016 at 9:21 AM
Subject: Re: Podling Report Reminder - June 2016
To: d...@commonsrdf.incubator.apache.org


Crud, I cannot seem to edit the Wiki. I am logged on the wiki as
"GaryGregory" Do I karma?

Gary

On Wed, Jun 1, 2016 at 4:44 PM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 1st).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/June2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>



--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co