Re: [RESULT] [VOTE] Apache Fineract podling graduation

[Ed Cable]

Thank you to all of our mentors and the entire Apache community throughout
this journey!

Special props to Myrle for spearheading the process to shepherd our
community through.

Ed

On Mon, Mar 27, 2017 at 3:33 AM, Myrle Krantz  wrote:

> Hello Incubator,
>
> The vote to graduate Apache Fineract from the incubator passes with 8
> binding votes,  2 non-binding votes, and no down-votes
>
> +1 binding: John D. Ament, Daniel Gruno, Bertrand Delacretaz, Roman
> Shaposhnik, Niclas Hedhman, Jim Jagielski, Justin Mclean, Tom Barber
> +1 non-binding: Pierre Smits, Markus Geiß
>
> (+1 binding votes not carried over from the pre-proposal-correction
> vote thread: Jean-Baptiste Onofré, Ross Gardler)
>
> We at Apache Fineract deeply appreciate the expressions of good will
> that came together with your votes.
>
> Thank you,
> Myrle
>
>
> On Wed, Mar 22, 2017 at 3:11 PM, Myrle Krantz  wrote:
> > Greetings Incubator,
> >
> > I propose that we graduate Apache Fineract from the Incubator.  The
> > full text of the proposal is below.
> >
> > This is a restarted VOTE thread to correct an error in the resolution
> > from the original thread. Here's the previous VOTE thread:
> >
> > [https://lists.apache.org/thread.html/1cbc738bbb4083e50b7772d5226b88
> d3fe321b91451303a69dbc4fa8@%3Cgeneral.incubator.apache.org%3E]
> >
> > And here's the DISCUSS thread:
> >
> > [https://lists.apache.org/thread.html/630d3ec22b4f72f827cd817a0a4da5
> c3c52dee4f96f47a1369f5dc50@%3Cgeneral.incubator.apache.org%3E]
> >
> >
> > Thank you,
> > Myrle Krantz
> >
> >
> > Resolution:
> >
> > Establish the Apache Fineract 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 a core banking platform that provides a reliable,
> > robust, and affordable solution for entrepreneurs, financial
> > institutions, and service providers to offer financial
> > services to the world's underbanked and unbanked.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Fineract Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Fineract Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a core banking platform that provides a reliable,
> > robust, and affordable solution for entrepreneurs, financial
> > institutions, and service providers to offer financial
> > services to the world's underbanked and unbanked.
> >
> > RESOLVED, that the office of "Vice President, Apache Fineract" 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 Fineract Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Fineract 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 Fineract Project:
> >
> > * Vishwas Babu AJ 
> > * Edward Cable 
> > * Markus Geiss 
> > * Sander van der Heijden 
> > * Ishan Khanna 
> > * Myrle Krantz 
> > * Terence Monteiro 
> > * Adi Nayaran Raju 
> > * Gaurav Saini 
> > * Nazeer Hussain Shaik 
> > * Jim Jagielski 
> > * Michael Vorburger 
> >
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Myrle Krantz
> > be appointed to the office of Vice President, Apache Fineract, 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 Fineract 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 Fineract Project; and be it further
> >
> > RESOLVED, that the Apache Fineract Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator Fineract podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator Fineract podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
>
> -
> To unsubscribe, e-mail: 

Re: Slack

[Wade Chandler]

The 90 member thing is really odd to me. I think you should write Slack help to 
ask for details about your issue. The agreement does mention invites where 
people don’t accept, and too many of those, could reduce your ability to add 
more members, but this has been really rare in my experience, and we have way 
more for NetBeans, and other than perhaps 10 people, our over 300+ members were 
self invited using https://netbeans.signup.team/ 
 Too, before I set all this up, one of the 
questions I specifically asked Slack was related to limitations, members, etc 
as it was a worry for us, and they said there is no real limit on the number of 
members, but did mention the message limits on logging etc, and directed us to 
setup a log bot while taking our request for some other OSS subscription models.

Hope it helps,

Wade



> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré  wrote:
> 
> Yes, but they will be member anyway, so it won't change the limit we have 
> today (90), right ?
> 
> Regards
> JB
> 
> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
>> Hi JB,
>> 
>> A common practice/hack is to create a small web app that allows people to
>> send themselves invitations using the Slack API.
>> For example:
>> http://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1
>> 
>> Cheers,
>> Yaniv
>> 
>> 
>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré 
>> wrote:
>> 
>>> Hi Wade,
>>> 
>>> You are right: invite people on Slack means adding them as member.
>>> 
>>> However, how can we accept Slack participants without inviting them ? Is it
>>> possible ?
>>> 
>>> Thanks !
>>> Regards
>>> JB
>>> 
>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
 My understanding is there isn’t a max limit on Slack for users for free,
>>> and I have confirmed this with Slack there is not supposed to be a
>>> limitation on numbers of members. NetBeans for instance has 320 members.
>>> Did someone tell you this or did you run into some issue? If so, you might
>>> write them to ask what is the deal.. It could be the difference in setup;
>>> we use a registration page which sends invitations
>>> https://netbeans.signup.team/  and is
>>> using bots from https://stacktodo.com/  Or, it
>>> could be something about when it was setup and differences in plans over
>>> time.
 
 It doesn’t change the limits on the log and file storage, but we explain
>>> to folks it is for ephemeral real time communication and never to be
>>> considered historic, but we are looking into setting up a log bot which
>>> Slack personnel told us could also be helpful for OSS use. Slack said they
>>> don’t have plans for more features for OSS specific projects at the moment
>>> as one request from us was they make some new individual/personal low pay
>>> option which could help communities with dedicated membership to pay for
>>> their own personal use, but they said no plans at this time, but would take
>>> it into consideration as an idea.
 
 Thanks,
 
 Wade
 
 
> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré 
>>> wrote:
> 
> Hi,
> 
> Slack is very convenient for quick communication, but clearly, it
>>> doesn't change that the mailing list is the first communication channel. If
>>> discussions happen on Slack, minute notes/discussion has to be forwarded on
>>> the mailing list.
> 
> I wonder if we plan to ask for some "pro" Slack account for Apache
>>> projects (as we have license for IntelliJ for example). Now, at Apache
>>> Beam, we reached the max capacity of the Slack free version (90 Slack users
>>> on Beam channel and limited history). We already received new member
>>> request that we can't accept for now.
> 
> Thoughts ?
> 
> Regards
> JB
> 
> On 03/22/2017 10:37 PM, Craig Russell wrote:
>> Hi James,
>> 
>> There was a pretty extensive discussion on the netbeans dev list. I’d
>>> encourage you to review this thread https://lists.apache.org/thread.html/
>>> 2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%
>>> 3Cdev.netbeans.apache.org%3E
>> 
>> You can get all of the messages in the thread by doing a quick search
>>> for “slack” on the d...@netbeans.apache.org list in lists.apache.org.
>> 
>> My takeaway is that Slack not a substitute for email. But it is useful
>>> for ping-pong communication when people are in the heat of development.
>> 
>> But no decisions are made on Slack, and any discussion there (aside
>>> from “add a semicolon there” and “let’s get lunch") needs to be brought
>>> back to the dev list.
>> 
>> The underlying principle is that “if it didn’t happen on dev, then it
>>> didn’t happen”. We strive for open, inclusive communications at Apache and
>>> that means attempting to encourage participation by everyone who 

Re: Slack

[Phillip Rhodes]

I don't understand the desire to use a closed-source, proprietary,
locked-down walled-garden application like Slack to begin with.   Why
not use one of the several open-source look-a-like versions that are
available?  Or use Gitter, which is about to go Open Source[1].

[1]: 
https://venturebeat.com/2017/03/15/gitlab-acquires-software-chat-startup-gitter-will-open-source-the-code/


Phil
This message optimized for indexing by NSA PRISM


On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler  wrote:
> The 90 member thing is really odd to me. I think you should write Slack help 
> to ask for details about your issue. The agreement does mention invites where 
> people don’t accept, and too many of those, could reduce your ability to add 
> more members, but this has been really rare in my experience, and we have way 
> more for NetBeans, and other than perhaps 10 people, our over 300+ members 
> were self invited using https://netbeans.signup.team/ 
>  Too, before I set all this up, one of the 
> questions I specifically asked Slack was related to limitations, members, etc 
> as it was a worry for us, and they said there is no real limit on the number 
> of members, but did mention the message limits on logging etc, and directed 
> us to setup a log bot while taking our request for some other OSS 
> subscription models.
>
> Hope it helps,
>
> Wade
>
>
>
>> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré  wrote:
>>
>> Yes, but they will be member anyway, so it won't change the limit we have 
>> today (90), right ?
>>
>> Regards
>> JB
>>
>> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
>>> Hi JB,
>>>
>>> A common practice/hack is to create a small web app that allows people to
>>> send themselves invitations using the Slack API.
>>> For example:
>>> http://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1
>>>
>>> Cheers,
>>> Yaniv
>>>
>>>
>>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré 
>>> wrote:
>>>
 Hi Wade,

 You are right: invite people on Slack means adding them as member.

 However, how can we accept Slack participants without inviting them ? Is it
 possible ?

 Thanks !
 Regards
 JB

 On 03/26/2017 07:05 PM, Wade Chandler wrote:
> My understanding is there isn’t a max limit on Slack for users for free,
 and I have confirmed this with Slack there is not supposed to be a
 limitation on numbers of members. NetBeans for instance has 320 members.
 Did someone tell you this or did you run into some issue? If so, you might
 write them to ask what is the deal.. It could be the difference in setup;
 we use a registration page which sends invitations
 https://netbeans.signup.team/  and is
 using bots from https://stacktodo.com/  Or, it
 could be something about when it was setup and differences in plans over
 time.
>
> It doesn’t change the limits on the log and file storage, but we explain
 to folks it is for ephemeral real time communication and never to be
 considered historic, but we are looking into setting up a log bot which
 Slack personnel told us could also be helpful for OSS use. Slack said they
 don’t have plans for more features for OSS specific projects at the moment
 as one request from us was they make some new individual/personal low pay
 option which could help communities with dedicated membership to pay for
 their own personal use, but they said no plans at this time, but would take
 it into consideration as an idea.
>
> Thanks,
>
> Wade
>
>
>> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré 
 wrote:
>>
>> Hi,
>>
>> Slack is very convenient for quick communication, but clearly, it
 doesn't change that the mailing list is the first communication channel. If
 discussions happen on Slack, minute notes/discussion has to be forwarded on
 the mailing list.
>>
>> I wonder if we plan to ask for some "pro" Slack account for Apache
 projects (as we have license for IntelliJ for example). Now, at Apache
 Beam, we reached the max capacity of the Slack free version (90 Slack users
 on Beam channel and limited history). We already received new member
 request that we can't accept for now.
>>
>> Thoughts ?
>>
>> Regards
>> JB
>>
>> On 03/22/2017 10:37 PM, Craig Russell wrote:
>>> Hi James,
>>>
>>> There was a pretty extensive discussion on the netbeans dev list. I’d
 encourage you to review this thread https://lists.apache.org/thread.html/
 2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%
 3Cdev.netbeans.apache.org%3E
>>>
>>> You can get all of the messages in the thread by doing a quick search
 for “slack” on the 

Re: [RESULT] [VOTE] Apache Fineract podling graduation

[Roman Shaposhnik]

Congrats and best of luck!

Thanks,
Roman.

On Mon, Mar 27, 2017 at 3:33 AM, Myrle Krantz  wrote:
> Hello Incubator,
>
> The vote to graduate Apache Fineract from the incubator passes with 8
> binding votes,  2 non-binding votes, and no down-votes
>
> +1 binding: John D. Ament, Daniel Gruno, Bertrand Delacretaz, Roman
> Shaposhnik, Niclas Hedhman, Jim Jagielski, Justin Mclean, Tom Barber
> +1 non-binding: Pierre Smits, Markus Geiß
>
> (+1 binding votes not carried over from the pre-proposal-correction
> vote thread: Jean-Baptiste Onofré, Ross Gardler)
>
> We at Apache Fineract deeply appreciate the expressions of good will
> that came together with your votes.
>
> Thank you,
> Myrle
>
>
> On Wed, Mar 22, 2017 at 3:11 PM, Myrle Krantz  wrote:
>> Greetings Incubator,
>>
>> I propose that we graduate Apache Fineract from the Incubator.  The
>> full text of the proposal is below.
>>
>> This is a restarted VOTE thread to correct an error in the resolution
>> from the original thread. Here's the previous VOTE thread:
>>
>> [https://lists.apache.org/thread.html/1cbc738bbb4083e50b7772d5226b88d3fe321b91451303a69dbc4fa8@%3Cgeneral.incubator.apache.org%3E]
>>
>> And here's the DISCUSS thread:
>>
>> [https://lists.apache.org/thread.html/630d3ec22b4f72f827cd817a0a4da5c3c52dee4f96f47a1369f5dc50@%3Cgeneral.incubator.apache.org%3E]
>>
>>
>> Thank you,
>> Myrle Krantz
>>
>>
>> Resolution:
>>
>> Establish the Apache Fineract 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 a core banking platform that provides a reliable,
>> robust, and affordable solution for entrepreneurs, financial
>> institutions, and service providers to offer financial
>> services to the world's underbanked and unbanked.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Fineract Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>>
>> RESOLVED, that the Apache Fineract Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to a core banking platform that provides a reliable,
>> robust, and affordable solution for entrepreneurs, financial
>> institutions, and service providers to offer financial
>> services to the world's underbanked and unbanked.
>>
>> RESOLVED, that the office of "Vice President, Apache Fineract" 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 Fineract Project, and to have primary responsibility
>> for management of the projects within the scope of
>> responsibility of the Apache Fineract 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 Fineract Project:
>>
>> * Vishwas Babu AJ 
>> * Edward Cable 
>> * Markus Geiss 
>> * Sander van der Heijden 
>> * Ishan Khanna 
>> * Myrle Krantz 
>> * Terence Monteiro 
>> * Adi Nayaran Raju 
>> * Gaurav Saini 
>> * Nazeer Hussain Shaik 
>> * Jim Jagielski 
>> * Michael Vorburger 
>>
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Myrle Krantz
>> be appointed to the office of Vice President, Apache Fineract, 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 Fineract 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 Fineract Project; and be it further
>>
>> RESOLVED, that the Apache Fineract Project be and hereby
>> is tasked with the migration and rationalization of the Apache
>> Incubator Fineract podling; and be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache
>> Incubator Fineract podling encumbered upon the Apache Incubator
>> Project are hereafter discharged.

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

Re: [DISCUSS] Apache Metron podling Graduation

[Casey Stella]

Hi Dave,

To clarify, we have 24 PPMC members, of which 12 are Hortonworks-affiliated
and 12 are not. We have 6 additional committers who are not PPMC members.
Some of them are affiliated and some of them are not. For the purpose of
this, we only captured the affiliations of the PPMC members.

I did some quick analysis of the git log and found the following:

% Commits by Hortonworkers: 79%

% Contributors affiliated to Hortonworks: 42%

In associating affiliation, I am being as generous as possible and
including people who I know to work at Hortonworks who may or may not be in
the engineering organization.  I know that some of these people are
contributing to Metron in their spare time as independent open source
contributions.


Best,

Casey

On Sun, Mar 26, 2017 at 2:59 PM, Dave Fisher  wrote:

>
>
> Sent from my iPhone
>
> > On Mar 24, 2017, at 9:03 PM, John D. Ament 
> wrote:
> >
> >> On Fri, Mar 24, 2017 at 11:52 PM P. Taylor Goetz 
> wrote:
> >>
> >> To be honest, I don't know, but I don't see it as a problem.
> >>
> >> I will admit upfront that I am a Hortonworks employee, so there is
> >> potential for bias. But I always try to wear the right hat, even when my
> >> position may not please my employer.
> >>
> >> As a mentor (to this and other podlings), I try to instill that ethic
> >> during incubation and thereafter.
> >>
> >> In the Metron community I see some that share that ethic. They selected
> a
> >> PMC Chair that gets it and I trust will serve the project well in that
> role.
> >>
> >> Yes, the project is Hortonworks-heavy. But I think they are doing things
> >> right in terms of the Apache Way. I also intend to participate in the
> PMC
> >> to help ensure it remains that way.
> >>
> >>
> > Agreed - from what I have seen, Hortonworks as a company understands the
> > Apache Way and is able to ensure that it is held in open source projects.
> > I see no concerns with Metron graduating.
>
> Sure, but the question is not about whether or not HortonWorks understands
> the Apache Way. It is what happens to Metron if HortonWorks is no longer
> interested in the project?
>
> Given the experience with OpenOffice I think we need to always ask this.
>
> Regards,
> Dave
>
> >
> >
> >> -Taylor
> >>
> >>
> >>> On Mar 24, 2017, at 8:15 PM, Dave Fisher 
> wrote:
> >>>
> >>> This is a list of 24 of which 12 are Hortonworks.
> >>>
> >>> Can we assume that the other 12 of which 6 are PPMC are unaffiliated?
> >>>
> >>> What percentage of the commits are coming from Hortonworks affiliated
> >> contributors?
> >>>
> >>> Thanks,
> >>> Dave
> >>>
>  On Mar 23, 2017, at 8:39 PM, Casey Stella  wrote:
> 
>  Of course, very fair question.  Also, yes, the we have 36 committers
> as
> >> all
>  PPMC members are committers.
> 
>  The affiliations are as follows:
> 
>  Hortonworks:
>  * Sheetal Dolas (sheetal_dolas)
>  * Larry McCay (lmccay)
>  * P. Taylor Goetz (ptgoetz)
>  * Ryan Merriman (rmerriman)
>  * James Sirota (jsirota)
>  * Casey Stella (cstella)
>  * David Lyle (lyle)
>  * Nick Allen (nickallen)
>  * George Vetticaden (gvetticaden)
>  * Vinod Kumar Vavilapalli (vinodkv)
>  * Kiran Komaravolu (kirankom)
>  * Michael Perez (mperez)
> 
>  Cisco:
>  * Debo Dutta (ddutta)
>  * Discovery Gerdes (discovery)
> 
>  Rackspace:
>  * Oskar Zabik (smogg)
>  * Andrew Hartnett (dev_warlord)
>  * Paul Kehrer (reaperhulk)
>  * Sean Schulte (sirsean)
> 
>  B23:
>  * Mark Bittmann (mbittmann)
>  * Dave Hirko (dbhirko)
>  * Brad Kolarov (bjkolly)
> 
>  Mantech:
>  * Charles Porter (cporter)
>  * Ray Urciuoli (rurcioli)
> 
>  Fogbeam Labs:
>  * Phillip Rhodes (prhodes)
> 
> 
> 
> 
> 
> > On Thu, Mar 23, 2017 at 9:34 PM, P. Taylor Goetz 
> >> wrote:
> >
> >
> >
> >> On Mar 23, 2017, at 7:38 PM, John D. Ament 
> > wrote:
> >>
> >>> On Thu, Mar 23, 2017 at 3:10 PM P. Taylor Goetz  >
> > wrote:
> >>>
> >>> As a mentor, I fully support Metron's graduation. The community has
> > come a
> >>> long way, learned to make solid releases, build a sustainable
> >> community,
> >>> and follow the Apache Way.
> >>>
> >>> One minor nit: The paddling status page is missing a few Apache
> IDs,
> > but I
> >>> see them in the resolution, so it's an easy fix.
> >>>
> >>>
> >> Paddlings are always out of sync :-P
> >>
> >> One other nit - I'm not sure why you only have 6 committers.  I
> think
> >> you
> >> mean 30 committers (all PMC members are committers).  Can you
> provide
> >> the
> >> associations of PMC members and employers?
> >
> > Metron PPMC,
> >
> > Can you respond? I 

Re: [DISCUSS] Apache Metron podling Graduation

[Dave Fisher]

Hi,

Thank you for the answers.

I am all for graduation if Metron.

Regards,
Dave

Sent from my iPhone

> On Mar 27, 2017, at 10:25 AM, Casey Stella  wrote:
> 
> Hi Dave,
> 
> To clarify, we have 24 PPMC members, of which 12 are Hortonworks-affiliated
> and 12 are not. We have 6 additional committers who are not PPMC members.
> Some of them are affiliated and some of them are not. For the purpose of
> this, we only captured the affiliations of the PPMC members.
> 
> I did some quick analysis of the git log and found the following:
> 
> % Commits by Hortonworkers: 79%
> 
> % Contributors affiliated to Hortonworks: 42%
> 
> In associating affiliation, I am being as generous as possible and
> including people who I know to work at Hortonworks who may or may not be in
> the engineering organization.  I know that some of these people are
> contributing to Metron in their spare time as independent open source
> contributions.
> 
> 
> Best,
> 
> Casey
> 
>> On Sun, Mar 26, 2017 at 2:59 PM, Dave Fisher  wrote:
>> 
>> 
>> 
>> Sent from my iPhone
>> 
>>> On Mar 24, 2017, at 9:03 PM, John D. Ament 
>> wrote:
>>> 
 On Fri, Mar 24, 2017 at 11:52 PM P. Taylor Goetz 
>> wrote:
 
 To be honest, I don't know, but I don't see it as a problem.
 
 I will admit upfront that I am a Hortonworks employee, so there is
 potential for bias. But I always try to wear the right hat, even when my
 position may not please my employer.
 
 As a mentor (to this and other podlings), I try to instill that ethic
 during incubation and thereafter.
 
 In the Metron community I see some that share that ethic. They selected
>> a
 PMC Chair that gets it and I trust will serve the project well in that
>> role.
 
 Yes, the project is Hortonworks-heavy. But I think they are doing things
 right in terms of the Apache Way. I also intend to participate in the
>> PMC
 to help ensure it remains that way.
 
 
>>> Agreed - from what I have seen, Hortonworks as a company understands the
>>> Apache Way and is able to ensure that it is held in open source projects.
>>> I see no concerns with Metron graduating.
>> 
>> Sure, but the question is not about whether or not HortonWorks understands
>> the Apache Way. It is what happens to Metron if HortonWorks is no longer
>> interested in the project?
>> 
>> Given the experience with OpenOffice I think we need to always ask this.
>> 
>> Regards,
>> Dave
>> 
>>> 
>>> 
 -Taylor
 
 
> On Mar 24, 2017, at 8:15 PM, Dave Fisher 
>> wrote:
> 
> This is a list of 24 of which 12 are Hortonworks.
> 
> Can we assume that the other 12 of which 6 are PPMC are unaffiliated?
> 
> What percentage of the commits are coming from Hortonworks affiliated
 contributors?
> 
> Thanks,
> Dave
> 
>> On Mar 23, 2017, at 8:39 PM, Casey Stella  wrote:
>> 
>> Of course, very fair question.  Also, yes, the we have 36 committers
>> as
 all
>> PPMC members are committers.
>> 
>> The affiliations are as follows:
>> 
>> Hortonworks:
>> * Sheetal Dolas (sheetal_dolas)
>> * Larry McCay (lmccay)
>> * P. Taylor Goetz (ptgoetz)
>> * Ryan Merriman (rmerriman)
>> * James Sirota (jsirota)
>> * Casey Stella (cstella)
>> * David Lyle (lyle)
>> * Nick Allen (nickallen)
>> * George Vetticaden (gvetticaden)
>> * Vinod Kumar Vavilapalli (vinodkv)
>> * Kiran Komaravolu (kirankom)
>> * Michael Perez (mperez)
>> 
>> Cisco:
>> * Debo Dutta (ddutta)
>> * Discovery Gerdes (discovery)
>> 
>> Rackspace:
>> * Oskar Zabik (smogg)
>> * Andrew Hartnett (dev_warlord)
>> * Paul Kehrer (reaperhulk)
>> * Sean Schulte (sirsean)
>> 
>> B23:
>> * Mark Bittmann (mbittmann)
>> * Dave Hirko (dbhirko)
>> * Brad Kolarov (bjkolly)
>> 
>> Mantech:
>> * Charles Porter (cporter)
>> * Ray Urciuoli (rurcioli)
>> 
>> Fogbeam Labs:
>> * Phillip Rhodes (prhodes)
>> 
>> 
>> 
>> 
>> 
>>> On Thu, Mar 23, 2017 at 9:34 PM, P. Taylor Goetz 
 wrote:
>>> 
>>> 
>>> 
 On Mar 23, 2017, at 7:38 PM, John D. Ament 
>>> wrote:
 
> On Thu, Mar 23, 2017 at 3:10 PM P. Taylor Goetz >> 
>>> wrote:
> 
> As a mentor, I fully support Metron's graduation. The community has
>>> come a
> long way, learned to make solid releases, build a sustainable
 community,
> and follow the Apache Way.
> 
> One minor nit: The paddling status page is missing a few Apache
>> IDs,
>>> but I
> see them in the resolution, so it's an easy fix.
> 
> 
 Paddlings are always out of sync :-P

Re: [DISCUSS] Apache Metron podling Graduation

[Casey Stella]

Thanks Dave;  I think that we all appreciate the concerns around insulating
the project from a single sponsor.   The fact that we do take the ASF
processes seriously is one of the things that makes the community
comforted, I think.  I appreciate the diligence in ensuring that we have
our ducks in a row from that perspective.

Best,

Casey

On Mon, Mar 27, 2017 at 1:36 PM, Dave Fisher  wrote:

> Hi,
>
> Thank you for the answers.
>
> I am all for graduation if Metron.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Mar 27, 2017, at 10:25 AM, Casey Stella  wrote:
> >
> > Hi Dave,
> >
> > To clarify, we have 24 PPMC members, of which 12 are
> Hortonworks-affiliated
> > and 12 are not. We have 6 additional committers who are not PPMC members.
> > Some of them are affiliated and some of them are not. For the purpose of
> > this, we only captured the affiliations of the PPMC members.
> >
> > I did some quick analysis of the git log and found the following:
> >
> > % Commits by Hortonworkers: 79%
> >
> > % Contributors affiliated to Hortonworks: 42%
> >
> > In associating affiliation, I am being as generous as possible and
> > including people who I know to work at Hortonworks who may or may not be
> in
> > the engineering organization.  I know that some of these people are
> > contributing to Metron in their spare time as independent open source
> > contributions.
> >
> >
> > Best,
> >
> > Casey
> >
> >> On Sun, Mar 26, 2017 at 2:59 PM, Dave Fisher 
> wrote:
> >>
> >>
> >>
> >> Sent from my iPhone
> >>
> >>> On Mar 24, 2017, at 9:03 PM, John D. Ament 
> >> wrote:
> >>>
>  On Fri, Mar 24, 2017 at 11:52 PM P. Taylor Goetz 
> >> wrote:
> 
>  To be honest, I don't know, but I don't see it as a problem.
> 
>  I will admit upfront that I am a Hortonworks employee, so there is
>  potential for bias. But I always try to wear the right hat, even when
> my
>  position may not please my employer.
> 
>  As a mentor (to this and other podlings), I try to instill that ethic
>  during incubation and thereafter.
> 
>  In the Metron community I see some that share that ethic. They
> selected
> >> a
>  PMC Chair that gets it and I trust will serve the project well in that
> >> role.
> 
>  Yes, the project is Hortonworks-heavy. But I think they are doing
> things
>  right in terms of the Apache Way. I also intend to participate in the
> >> PMC
>  to help ensure it remains that way.
> 
> 
> >>> Agreed - from what I have seen, Hortonworks as a company understands
> the
> >>> Apache Way and is able to ensure that it is held in open source
> projects.
> >>> I see no concerns with Metron graduating.
> >>
> >> Sure, but the question is not about whether or not HortonWorks
> understands
> >> the Apache Way. It is what happens to Metron if HortonWorks is no longer
> >> interested in the project?
> >>
> >> Given the experience with OpenOffice I think we need to always ask this.
> >>
> >> Regards,
> >> Dave
> >>
> >>>
> >>>
>  -Taylor
> 
> 
> > On Mar 24, 2017, at 8:15 PM, Dave Fisher 
> >> wrote:
> >
> > This is a list of 24 of which 12 are Hortonworks.
> >
> > Can we assume that the other 12 of which 6 are PPMC are unaffiliated?
> >
> > What percentage of the commits are coming from Hortonworks affiliated
>  contributors?
> >
> > Thanks,
> > Dave
> >
> >> On Mar 23, 2017, at 8:39 PM, Casey Stella 
> wrote:
> >>
> >> Of course, very fair question.  Also, yes, the we have 36 committers
> >> as
>  all
> >> PPMC members are committers.
> >>
> >> The affiliations are as follows:
> >>
> >> Hortonworks:
> >> * Sheetal Dolas (sheetal_dolas)
> >> * Larry McCay (lmccay)
> >> * P. Taylor Goetz (ptgoetz)
> >> * Ryan Merriman (rmerriman)
> >> * James Sirota (jsirota)
> >> * Casey Stella (cstella)
> >> * David Lyle (lyle)
> >> * Nick Allen (nickallen)
> >> * George Vetticaden (gvetticaden)
> >> * Vinod Kumar Vavilapalli (vinodkv)
> >> * Kiran Komaravolu (kirankom)
> >> * Michael Perez (mperez)
> >>
> >> Cisco:
> >> * Debo Dutta (ddutta)
> >> * Discovery Gerdes (discovery)
> >>
> >> Rackspace:
> >> * Oskar Zabik (smogg)
> >> * Andrew Hartnett (dev_warlord)
> >> * Paul Kehrer (reaperhulk)
> >> * Sean Schulte (sirsean)
> >>
> >> B23:
> >> * Mark Bittmann (mbittmann)
> >> * Dave Hirko (dbhirko)
> >> * Brad Kolarov (bjkolly)
> >>
> >> Mantech:
> >> * Charles Porter (cporter)
> >> * Ray Urciuoli (rurcioli)
> >>
> >> Fogbeam Labs:
> >> * Phillip Rhodes (prhodes)
> >>
> >>
> >>
> >>
> >>
> >>> On Thu, Mar 23, 2017 at 9:34 PM, P. Taylor Goetz <
> ptgo...@gmail.com>
>  wrote:
> 

Re: Slack

[Wade Chandler]

I have used Gitter; not a good product honestly; not really comparable. IRC
has limitations in the editing and group experience. The others require
keeping up infrastructure. Slack just works, and works well for what it
does. Some of us in the NB community discussed these points while setting
it up and choosing. Too, they have been letting communities use it for free
a long time. We use Atlassian products too, but don't get me going on
hipchat differences; one of which is the sed like comment editing oddness.

Thanks

Wade

On Mar 27, 2017 12:57 PM, "Phillip Rhodes" 
wrote:

> I don't understand the desire to use a closed-source, proprietary,
> locked-down walled-garden application like Slack to begin with.   Why
> not use one of the several open-source look-a-like versions that are
> available?  Or use Gitter, which is about to go Open Source[1].
>
> [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
> software-chat-startup-gitter-will-open-source-the-code/
>
>
> Phil
> This message optimized for indexing by NSA PRISM
>
>
> On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler 
> wrote:
> > The 90 member thing is really odd to me. I think you should write Slack
> help to ask for details about your issue. The agreement does mention
> invites where people don’t accept, and too many of those, could reduce your
> ability to add more members, but this has been really rare in my
> experience, and we have way more for NetBeans, and other than perhaps 10
> people, our over 300+ members were self invited using
> https://netbeans.signup.team/  Too, before
> I set all this up, one of the questions I specifically asked Slack was
> related to limitations, members, etc as it was a worry for us, and they
> said there is no real limit on the number of members, but did mention the
> message limits on logging etc, and directed us to setup a log bot while
> taking our request for some other OSS subscription models.
> >
> > Hope it helps,
> >
> > Wade
> >
> >
> >
> >> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré 
> wrote:
> >>
> >> Yes, but they will be member anyway, so it won't change the limit we
> have today (90), right ?
> >>
> >> Regards
> >> JB
> >>
> >> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> >>> Hi JB,
> >>>
> >>> A common practice/hack is to create a small web app that allows people
> to
> >>> send themselves invitations using the Slack API.
> >>> For example:
> >>> http://www.skill-space.com/blog/2015/11/16/create-an-
> auto-invite-channel-using-slack-heroku1
> >>>
> >>> Cheers,
> >>> Yaniv
> >>>
> >>>
> >>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré 
> >>> wrote:
> >>>
>  Hi Wade,
> 
>  You are right: invite people on Slack means adding them as member.
> 
>  However, how can we accept Slack participants without inviting them ?
> Is it
>  possible ?
> 
>  Thanks !
>  Regards
>  JB
> 
>  On 03/26/2017 07:05 PM, Wade Chandler wrote:
> > My understanding is there isn’t a max limit on Slack for users for
> free,
>  and I have confirmed this with Slack there is not supposed to be a
>  limitation on numbers of members. NetBeans for instance has 320
> members.
>  Did someone tell you this or did you run into some issue? If so, you
> might
>  write them to ask what is the deal.. It could be the difference in
> setup;
>  we use a registration page which sends invitations
>  https://netbeans.signup.team/  and is
>  using bots from https://stacktodo.com/  Or,
> it
>  could be something about when it was setup and differences in plans
> over
>  time.
> >
> > It doesn’t change the limits on the log and file storage, but we
> explain
>  to folks it is for ephemeral real time communication and never to be
>  considered historic, but we are looking into setting up a log bot
> which
>  Slack personnel told us could also be helpful for OSS use. Slack said
> they
>  don’t have plans for more features for OSS specific projects at the
> moment
>  as one request from us was they make some new individual/personal low
> pay
>  option which could help communities with dedicated membership to pay
> for
>  their own personal use, but they said no plans at this time, but
> would take
>  it into consideration as an idea.
> >
> > Thanks,
> >
> > Wade
> >
> >
> >> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré 
>  wrote:
> >>
> >> Hi,
> >>
> >> Slack is very convenient for quick communication, but clearly, it
>  doesn't change that the mailing list is the first communication
> channel. If
>  discussions happen on Slack, minute notes/discussion has to be
> forwarded on
>  the mailing list.
> >>
> >> I wonder if we plan to ask for some 

RE: [DISCUSS] Apache Amaterasu Incubator Proposal

[Ross Gardler]

Exciting stuff, it may have already been said but the name is pretty bad. To my 
(native) English ear it sounds like "Amateur".

Ross

-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] 
Sent: Monday, March 20, 2017 11:39 PM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Apache Amaterasu Incubator Proposal

Hi all,

gently reminder about this thread.

I would like to start a formal vote pretty soon.

Thanks,
Regards
JB

On 03/07/2017 09:49 PM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I would like to submit a new proposal to bring Amaterasu to the Apache 
> Software Foundation incubator.
>
> The proposal is included below and available on the wiki:
>
> https://wiki.apache.org/incubator/AmaterasuProposal
>
> We are eager to get your comments and questions.
>
> Thanks !
> JB (on behalf of the Amaterasu community)
>
> = Apache Amaterasu =
>
> == Abstract ==
>
> Apache Amaterasu is a framework providing continuous deployment for 
> Big Data pipelines.
>
> It provides the following capabilities:
>
>  * '''Continuous integration''' tools to '''package pipelines and run 
> tests'''.
>  * A repository to store those packaged applications: the 
> '''applications repository'''.
>  * A repository to store the pipelines, and engine configuration (for 
> instance, location of the Spark master, etc.): per environment - the 
> '''configuration repository'''.
>  * A '''dashboard''' to monitor the pipelines.
>  * A '''DSL and integration hooks''' allowing third parties to easily 
> integrate.
>
> == Proposal ==
>
> Amaterasu is a simple and powerful framework to build and dispense pipelines.
> It aims to help data engineers and data scientists to compose, 
> configure, test, package, deploy and execute data pipelines written 
> using multiple tools, languages and frameworks. Amaterasu provides a 
> standard repo structure to package big data pipelines, a YAML based 
> Domain Specific Languages (DSL) for data engineers, data scientists 
> and operations engineers to manage complex pipelines throughout their entire 
> lifecycle (Dev, UAT, Prod, etc.).
>
> == Background ==
>
> Amaterasu is a relatively new project that was created to deal with 
> some of the issues that as Consultants, we have seen recurring at different 
> client sites.
> Mainly the need to continuously deploy complex pipelines built in 
> multiple tools and languages.
> Amaterasu started as a pet project and is currently being evaluated by 
> a couple of organizations, supported by the contributors, on a 
> personal time and voluntary bases.
>
> == Rational ==
>
> As software engineers working on big data projects we have straggled 
> for a long time to apply the same CI/CD practices that have become the 
> standard in the software industry for the last few years. While some 
> of them are possible, for example Apache Spark is easy to unit test. 
> However large scale pipelines are more complex and often use data, 
> which might be un-structured as integration point, which requires heavy 
> integration tests.
>
> To automate such tests and complex deployments, we have found the need 
> to often handcraft scripts and use a mixture tools, so we have decided 
> to finally build a tool we can apply in a general way and not on a project by 
> project basis.
>
> Another issue Amaterasu is trying to tackle is the Integrating between 
> the work of software engineers, data scientists, and sometimes 
> operations engineers. The approach Amaterasu takes to integrate 
> between those three schools of thought it to provide a simple YAML 
> based DSL that provides a simple way to integrate different pipeline 
> written in the native tools for each task (R, Spark in different languages, 
> etc.).
>
> == Initial Goals ==
>
> Our initial goals are to bring Amaterasu into the ASF, transition 
> internal engineering processes into the open, and foster a 
> collaborative development model according to the "Apache Way".
>
> In addition, we intend to continue the development of Amaterasu, add 
> new features as well as  integrate better with other frameworks, including:
>
>  * Apache Arrow
>  * Apache Hive
>  * Apache Drill
>  * Apache Beam
>  * Apache YARN
>  * Farther and more complete integration with Apache Spark
>
> Other frameworks will be evaluated after those initial goals are reached.
>
> == Current Status ==
>
> Amaterasu is preview state but provide a large set of features. We 
> plan to stabilize and head to a first production ready release during 
> the incubation process. The current license is already Apache 2.0.
>
> === Meritocracy ===
>
> We intend to radically expand the initial developer and user community 
> by running the project in accordance with the "Apache Way". Users and 
> new contributors will be treated with respect and welcomed. By 
> participating in the community and providing quality patches/support 
> that move the project forward, they will earn merit. They also will be 
> encouraged to provide non-code 

Re: [DISCUSS] Apache Metron podling Graduation

[Pierre Smits]

I can't agree more. Though I am just one from the peanut gallery I
primarily look at the CoC (community over code) aspects applied in
podlings.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Mon, Mar 27, 2017 at 9:32 AM, Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Sun, Mar 26, 2017 at 8:59 PM, Dave Fisher 
> wrote:
> > ...the question is not about whether or not HortonWorks understands the
> Apache Way. It is what happens
> > to Metron if HortonWorks is no longer interested in the project?...
>
> Which boils down to whether the project is governed in an open way
> that allows volunteers to jump in if needed.
> I had a look at [1] and the pages that it links to and it looks like
> this is the case for Metron.
>
> -Bertrand
>
> [1] https://cwiki.apache.org/confluence/display/METRON/
> Apache+Project+Maturity+Model
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache Metron podling Graduation

[Bertrand Delacretaz]

On Sun, Mar 26, 2017 at 8:59 PM, Dave Fisher  wrote:
> ...the question is not about whether or not HortonWorks understands the 
> Apache Way. It is what happens
> to Metron if HortonWorks is no longer interested in the project?...

Which boils down to whether the project is governed in an open way
that allows volunteers to jump in if needed.
I had a look at [1] and the pages that it links to and it looks like
this is the case for Metron.

-Bertrand

[1] 
https://cwiki.apache.org/confluence/display/METRON/Apache+Project+Maturity+Model

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

[RESULT] [VOTE] Apache Fineract podling graduation

[Myrle Krantz]

Hello Incubator,

The vote to graduate Apache Fineract from the incubator passes with 8
binding votes,  2 non-binding votes, and no down-votes

+1 binding: John D. Ament, Daniel Gruno, Bertrand Delacretaz, Roman
Shaposhnik, Niclas Hedhman, Jim Jagielski, Justin Mclean, Tom Barber
+1 non-binding: Pierre Smits, Markus Geiß

(+1 binding votes not carried over from the pre-proposal-correction
vote thread: Jean-Baptiste Onofré, Ross Gardler)

We at Apache Fineract deeply appreciate the expressions of good will
that came together with your votes.

Thank you,
Myrle


On Wed, Mar 22, 2017 at 3:11 PM, Myrle Krantz  wrote:
> Greetings Incubator,
>
> I propose that we graduate Apache Fineract from the Incubator.  The
> full text of the proposal is below.
>
> This is a restarted VOTE thread to correct an error in the resolution
> from the original thread. Here's the previous VOTE thread:
>
> [https://lists.apache.org/thread.html/1cbc738bbb4083e50b7772d5226b88d3fe321b91451303a69dbc4fa8@%3Cgeneral.incubator.apache.org%3E]
>
> And here's the DISCUSS thread:
>
> [https://lists.apache.org/thread.html/630d3ec22b4f72f827cd817a0a4da5c3c52dee4f96f47a1369f5dc50@%3Cgeneral.incubator.apache.org%3E]
>
>
> Thank you,
> Myrle Krantz
>
>
> Resolution:
>
> Establish the Apache Fineract 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 a core banking platform that provides a reliable,
> robust, and affordable solution for entrepreneurs, financial
> institutions, and service providers to offer financial
> services to the world's underbanked and unbanked.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Fineract Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Fineract Project be and hereby is
> responsible for the creation and maintenance of software
> related to a core banking platform that provides a reliable,
> robust, and affordable solution for entrepreneurs, financial
> institutions, and service providers to offer financial
> services to the world's underbanked and unbanked.
>
> RESOLVED, that the office of "Vice President, Apache Fineract" 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 Fineract Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Fineract 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 Fineract Project:
>
> * Vishwas Babu AJ 
> * Edward Cable 
> * Markus Geiss 
> * Sander van der Heijden 
> * Ishan Khanna 
> * Myrle Krantz 
> * Terence Monteiro 
> * Adi Nayaran Raju 
> * Gaurav Saini 
> * Nazeer Hussain Shaik 
> * Jim Jagielski 
> * Michael Vorburger 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Myrle Krantz
> be appointed to the office of Vice President, Apache Fineract, 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 Fineract 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 Fineract Project; and be it further
>
> RESOLVED, that the Apache Fineract Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Fineract podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Fineract podling encumbered upon the Apache Incubator
> Project are hereafter discharged.

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

Incubator PMC April 2017 Report Timeline

[John D. Ament]

I'll be unavailable Wednesday, so wanted to make sure this made its way out

April 2017 Incubator report timeline:

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

Wed April 05 -- Podling reports due by end of day
Sun April 09 -- Shepherd reviews due by end of day
Sun April 09 -- Summary due by end of day
Tue April 11 -- Mentor signoff due by end of day
Wed April 12 -- Report submitted to Board
Wed April 19 -- Board meeting

John

Re: Request to be added to the ContributorsGroup

[Marvin Humphrey]

On Mon, Mar 27, 2017 at 3:52 PM, Ashutosh Chauhan  wrote:

 Wiki username: JeffFeng

I added JeffFeng.  Happy Wikifying!

Marvin Humphrey

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

Re: Slack

[Ted Dunning]

Slack works incredibly well is the basic reason. Some of the aspect that
work well include:

- very effective UI

- great integration with email so that i hear about messages that I didn't
seem to see

- great notification. An alert appears on the platform I am using. That is,
I hear clicks on my laptop or a tone on my phone depending on which I am
using, but I don't hear notifications from every platform I *might* be
using. That means that when a notification happens I tend to actually hear
it rather than tuning it out.

- great sonic UI. The sounds are distinctive and penetrate cluttered
soundscapes well without being painful.

It may be that any given person doesn't care, but this sort of UI driven
discussion often comes up an not uncommonly comes out in favor of non open
alternatives. I try gimp again every few years, but every time I have done
it, I go back to photoshop due to quality of results and productivity. I
occasionally check out alternatives to IntelliJ, but they keep making it
better and more multi-lingual and more useful.

Where commercial products really are better, using them is a fine choice.
But I really do think that commercial vendors have to keep jumping the bar
set by OSS and they (we, actually) have to clear that bar and more.


(obligatory note: I work for a company that makes software that we sell.
The revenues from that pay for my groceries)



On Mon, Mar 27, 2017 at 4:07 PM, Edward Capriolo 
wrote:

> On Mon, Mar 27, 2017 at 3:08 PM, Wade Chandler 
> wrote:
>
> > I have used Gitter; not a good product honestly; not really comparable.
> IRC
> > has limitations in the editing and group experience. The others require
> > keeping up infrastructure. Slack just works, and works well for what it
> > does. Some of us in the NB community discussed these points while setting
> > it up and choosing. Too, they have been letting communities use it for
> free
> > a long time. We use Atlassian products too, but don't get me going on
> > hipchat differences; one of which is the sed like comment editing
> oddness.
> >
> > Thanks
> >
> > Wade
> >
> > On Mar 27, 2017 12:57 PM, "Phillip Rhodes" 
> > wrote:
> >
> > > I don't understand the desire to use a closed-source, proprietary,
> > > locked-down walled-garden application like Slack to begin with.   Why
> > > not use one of the several open-source look-a-like versions that are
> > > available?  Or use Gitter, which is about to go Open Source[1].
> > >
> > > [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
> > > software-chat-startup-gitter-will-open-source-the-code/
> > >
> > >
> > > Phil
> > > This message optimized for indexing by NSA PRISM
> > >
> > >
> > > On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <
> wadechand...@apache.org
> > >
> > > wrote:
> > > > The 90 member thing is really odd to me. I think you should write
> Slack
> > > help to ask for details about your issue. The agreement does mention
> > > invites where people don’t accept, and too many of those, could reduce
> > your
> > > ability to add more members, but this has been really rare in my
> > > experience, and we have way more for NetBeans, and other than perhaps
> 10
> > > people, our over 300+ members were self invited using
> > > https://netbeans.signup.team/  Too,
> > before
> > > I set all this up, one of the questions I specifically asked Slack was
> > > related to limitations, members, etc as it was a worry for us, and they
> > > said there is no real limit on the number of members, but did mention
> the
> > > message limits on logging etc, and directed us to setup a log bot while
> > > taking our request for some other OSS subscription models.
> > > >
> > > > Hope it helps,
> > > >
> > > > Wade
> > > >
> > > >
> > > >
> > > >> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré 
> > > wrote:
> > > >>
> > > >> Yes, but they will be member anyway, so it won't change the limit we
> > > have today (90), right ?
> > > >>
> > > >> Regards
> > > >> JB
> > > >>
> > > >> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> > > >>> Hi JB,
> > > >>>
> > > >>> A common practice/hack is to create a small web app that allows
> > people
> > > to
> > > >>> send themselves invitations using the Slack API.
> > > >>> For example:
> > > >>> http://www.skill-space.com/blog/2015/11/16/create-an-
> > > auto-invite-channel-using-slack-heroku1
> > > >>>
> > > >>> Cheers,
> > > >>> Yaniv
> > > >>>
> > > >>>
> > > >>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <
> > j...@nanthrax.net>
> > > >>> wrote:
> > > >>>
> > >  Hi Wade,
> > > 
> > >  You are right: invite people on Slack means adding them as member.
> > > 
> > >  However, how can we accept Slack participants without inviting
> them
> > ?
> > > Is it
> > >  possible ?
> > > 
> > >  Thanks !
> > >  Regards
> > >  JB
> > > 
> > >  On 03/26/2017 07:05 PM, 

Re: Slack

[Edward Capriolo]

On Mon, Mar 27, 2017 at 3:08 PM, Wade Chandler 
wrote:

> I have used Gitter; not a good product honestly; not really comparable. IRC
> has limitations in the editing and group experience. The others require
> keeping up infrastructure. Slack just works, and works well for what it
> does. Some of us in the NB community discussed these points while setting
> it up and choosing. Too, they have been letting communities use it for free
> a long time. We use Atlassian products too, but don't get me going on
> hipchat differences; one of which is the sed like comment editing oddness.
>
> Thanks
>
> Wade
>
> On Mar 27, 2017 12:57 PM, "Phillip Rhodes" 
> wrote:
>
> > I don't understand the desire to use a closed-source, proprietary,
> > locked-down walled-garden application like Slack to begin with.   Why
> > not use one of the several open-source look-a-like versions that are
> > available?  Or use Gitter, which is about to go Open Source[1].
> >
> > [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
> > software-chat-startup-gitter-will-open-source-the-code/
> >
> >
> > Phil
> > This message optimized for indexing by NSA PRISM
> >
> >
> > On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler  >
> > wrote:
> > > The 90 member thing is really odd to me. I think you should write Slack
> > help to ask for details about your issue. The agreement does mention
> > invites where people don’t accept, and too many of those, could reduce
> your
> > ability to add more members, but this has been really rare in my
> > experience, and we have way more for NetBeans, and other than perhaps 10
> > people, our over 300+ members were self invited using
> > https://netbeans.signup.team/  Too,
> before
> > I set all this up, one of the questions I specifically asked Slack was
> > related to limitations, members, etc as it was a worry for us, and they
> > said there is no real limit on the number of members, but did mention the
> > message limits on logging etc, and directed us to setup a log bot while
> > taking our request for some other OSS subscription models.
> > >
> > > Hope it helps,
> > >
> > > Wade
> > >
> > >
> > >
> > >> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré 
> > wrote:
> > >>
> > >> Yes, but they will be member anyway, so it won't change the limit we
> > have today (90), right ?
> > >>
> > >> Regards
> > >> JB
> > >>
> > >> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> > >>> Hi JB,
> > >>>
> > >>> A common practice/hack is to create a small web app that allows
> people
> > to
> > >>> send themselves invitations using the Slack API.
> > >>> For example:
> > >>> http://www.skill-space.com/blog/2015/11/16/create-an-
> > auto-invite-channel-using-slack-heroku1
> > >>>
> > >>> Cheers,
> > >>> Yaniv
> > >>>
> > >>>
> > >>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > >>> wrote:
> > >>>
> >  Hi Wade,
> > 
> >  You are right: invite people on Slack means adding them as member.
> > 
> >  However, how can we accept Slack participants without inviting them
> ?
> > Is it
> >  possible ?
> > 
> >  Thanks !
> >  Regards
> >  JB
> > 
> >  On 03/26/2017 07:05 PM, Wade Chandler wrote:
> > > My understanding is there isn’t a max limit on Slack for users for
> > free,
> >  and I have confirmed this with Slack there is not supposed to be a
> >  limitation on numbers of members. NetBeans for instance has 320
> > members.
> >  Did someone tell you this or did you run into some issue? If so, you
> > might
> >  write them to ask what is the deal.. It could be the difference in
> > setup;
> >  we use a registration page which sends invitations
> >  https://netbeans.signup.team/  and
> is
> >  using bots from https://stacktodo.com/  Or,
> > it
> >  could be something about when it was setup and differences in plans
> > over
> >  time.
> > >
> > > It doesn’t change the limits on the log and file storage, but we
> > explain
> >  to folks it is for ephemeral real time communication and never to be
> >  considered historic, but we are looking into setting up a log bot
> > which
> >  Slack personnel told us could also be helpful for OSS use. Slack
> said
> > they
> >  don’t have plans for more features for OSS specific projects at the
> > moment
> >  as one request from us was they make some new individual/personal
> low
> > pay
> >  option which could help communities with dedicated membership to pay
> > for
> >  their own personal use, but they said no plans at this time, but
> > would take
> >  it into consideration as an idea.
> > >
> > > Thanks,
> > >
> > > Wade
> > >
> > >
> > >> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré 
> >  wrote:
> > 

Re: Slack

[Carlos Santana]

I use Slack everyday internally for my work. 
I like Slack and the fact that I can use one tool for open source and internal 
company things. 

Apache Cordova (1400 members)and Apache Incubating OpenWhisk (175 members) both 
use Slack there is no limit on number of users and there is an open invite from 
the website from both projects. 

PS: I also use Slack for Ionic open source project with 3000 members also free 
tier. 

- Carlos Santana
@csantanapr

> On Mar 27, 2017, at 3:08 PM, Wade Chandler  wrote:
> 
> I have used Gitter; not a good product honestly; not really comparable. IRC
> has limitations in the editing and group experience. The others require
> keeping up infrastructure. Slack just works, and works well for what it
> does. Some of us in the NB community discussed these points while setting
> it up and choosing. Too, they have been letting communities use it for free
> a long time. We use Atlassian products too, but don't get me going on
> hipchat differences; one of which is the sed like comment editing oddness.
> 
> Thanks
> 
> Wade
> 
> On Mar 27, 2017 12:57 PM, "Phillip Rhodes" 
> wrote:
> 
>> I don't understand the desire to use a closed-source, proprietary,
>> locked-down walled-garden application like Slack to begin with.   Why
>> not use one of the several open-source look-a-like versions that are
>> available?  Or use Gitter, which is about to go Open Source[1].
>> 
>> [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
>> software-chat-startup-gitter-will-open-source-the-code/
>> 
>> 
>> Phil
>> This message optimized for indexing by NSA PRISM
>> 
>> 
>> On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler 
>> wrote:
>>> The 90 member thing is really odd to me. I think you should write Slack
>> help to ask for details about your issue. The agreement does mention
>> invites where people don’t accept, and too many of those, could reduce your
>> ability to add more members, but this has been really rare in my
>> experience, and we have way more for NetBeans, and other than perhaps 10
>> people, our over 300+ members were self invited using
>> https://netbeans.signup.team/  Too, before
>> I set all this up, one of the questions I specifically asked Slack was
>> related to limitations, members, etc as it was a worry for us, and they
>> said there is no real limit on the number of members, but did mention the
>> message limits on logging etc, and directed us to setup a log bot while
>> taking our request for some other OSS subscription models.
>>> 
>>> Hope it helps,
>>> 
>>> Wade
>>> 
>>> 
>>> 
 On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré 
>> wrote:
 
 Yes, but they will be member anyway, so it won't change the limit we
>> have today (90), right ?
 
 Regards
 JB
 
> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> Hi JB,
> 
> A common practice/hack is to create a small web app that allows people
>> to
> send themselves invitations using the Slack API.
> For example:
> http://www.skill-space.com/blog/2015/11/16/create-an-
>> auto-invite-channel-using-slack-heroku1
> 
> Cheers,
> Yaniv
> 
> 
> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré 
> wrote:
> 
>> Hi Wade,
>> 
>> You are right: invite people on Slack means adding them as member.
>> 
>> However, how can we accept Slack participants without inviting them ?
>> Is it
>> possible ?
>> 
>> Thanks !
>> Regards
>> JB
>> 
>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
>>> My understanding is there isn’t a max limit on Slack for users for
>> free,
>> and I have confirmed this with Slack there is not supposed to be a
>> limitation on numbers of members. NetBeans for instance has 320
>> members.
>> Did someone tell you this or did you run into some issue? If so, you
>> might
>> write them to ask what is the deal.. It could be the difference in
>> setup;
>> we use a registration page which sends invitations
>> https://netbeans.signup.team/  and is
>> using bots from https://stacktodo.com/  Or,
>> it
>> could be something about when it was setup and differences in plans
>> over
>> time.
>>> 
>>> It doesn’t change the limits on the log and file storage, but we
>> explain
>> to folks it is for ephemeral real time communication and never to be
>> considered historic, but we are looking into setting up a log bot
>> which
>> Slack personnel told us could also be helpful for OSS use. Slack said
>> they
>> don’t have plans for more features for OSS specific projects at the
>> moment
>> as one request from us was they make some new individual/personal low
>> pay
>> option which could help communities with dedicated membership to pay
>> for

Re: Request to be added to the ContributorsGroup

[Ashutosh Chauhan]

Ping.

On Fri, Mar 24, 2017 at 8:49 AM, Jeff Feng  wrote:

> + apa...@apache.org
>
> On Fri, Mar 24, 2017 at 7:59 AM, Jeff Feng  wrote:
>
>> +Daniel & Ashutosh
>>
>> Hello, just sending a friendly bump on my request to get wiki contributor
>> access.
>>
>> Thanks,
>> Jeff
>>
>> On Tue, Mar 21, 2017 at 3:55 AM, Jeff Feng  wrote:
>>
>>> Hi!
>>>
>>> I'm a Product Manager from Airbnb and I'd like to be added to the
>>> ContributorsGroup so that I can create a wiki and share about Superset as
>>> an Apache Incubation project.  Could you add me to the group so that I have
>>> write access.
>>>
>>> Wiki username: JeffFeng
>>>
>>> Thanks!
>>> Jeff
>>>
>>> --
>>>
>>> *Jeff Feng*
>>> Product Manager
>>> m: (949)-610-5108 <(949)%20610-5108>
>>> twitter: @jtfeng
>>>
>>>
>>
>>
>> --
>>
>> *Jeff Feng*
>> Product Manager
>> m: (949)-610-5108 <(949)%20610-5108>
>> twitter: @jtfeng
>>
>>
>
>
> --
>
> *Jeff Feng*
> Product Manager
> m: (949)-610-5108 <(949)%20610-5108>
> twitter: @jtfeng
>
>