Re: Blacklist/whitelist

Hey Rich, this is pretty awesome. But you're preaching to the choir here. Members@ might reach more projects who just haven't thought about it yet. But given that several projects *are* working on this, maybe we can get a "Success at Apache" blog post going about it? Best, Myrle On Sat, Jun 6,

Re: Blacklist/whitelist

Having an example if several projects doing this - which I now do - will make that message stronger. I'll write something to members@ Rich On Tue, Jun 9, 2020, 04:27 Myrle Krantz wrote: > Hey Rich, this is pretty awesome. But you're preaching to the choir here. > Members@ might reach more pr

Re: Blacklist/whitelist

Mahout is up now too. And thank you for the reminder- its such a simple thing, but totally slipped my mind to do it. On Tue, Jun 9, 2020 at 7:09 AM Rich Bowen wrote: > Having an example if several projects doing this - which I now do - will > make that message stronger. > > I'll write something

Naming branches "master"

I decided to break this thread off from blacklist/whitelist, but someone brought this up on the Streams slack channel as we were discussing that In removing "master/slave" terminology from tech... is anyone doing anything with the 'master' branches which exist in just about every repo...?

Re: Naming branches "master"

Hi, On Tue, Jun 9, 2020 at 6:31 PM Trevor Grant wrote: > I decided to break this thread off from blacklist/whitelist, but someone > brought this up on the Streams slack channel as we were discussing that > > In removing "master/slave" terminology from tech... is anyone doing > anything with

Re: Naming branches "master"

master in "master/slave" (distributed computing) and master in the sense of a "master record" (version control) are two independent senses of the same word (senses 2.d and 10.b in the OED, respectively) cf. https://www.oed.com/view/Entry/114751 I believe

Re: Naming branches "master"

+1 to Naomi's interpretation. -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Tue, Jun 9, 2020 at 1:02 PM Naomi Slater wrote: > master in "master/slave" (distributed computing) and master in

Re: Blacklist/whitelist

Hi Paul, > On Jun 8, 2020, at 1:28 AM, Paul Angus wrote: > > I'm working on blacklist/whitelist in Cloudsstack (nearly there); But > master/slave is a tough one because we're orchestrating components that > themselves use master/slave terminology... It would help me understand better if you

Re: Blacklist/whitelist

FYI :) https://issues.apache.org/jira/plugins/servlet/mobile#issue/COUCHDB-2248 Sent from my iPhone > On 9. Jun 2020, at 10:27, Myrle Krantz wrote: > > Hey Rich, this is pretty awesome. But you're preaching to the choir here. > Members@ might reach more projects who just haven't thought abo

Re: Blacklist/whitelist

We did the same in Apache Airflow https://twitter.com/AshBerlin/status/1269916465563607040 On Tue, Jun 9, 2020 at 12:43 PM Naomi Slater wrote: > FYI :) > > https://issues.apache.org/jira/plugins/servlet/mobile#issue/COUCHDB-2248 > > > Sent from my iPhone > > > On 9. Jun 2020, at 10:27, Myrle Kra

Re: Naming branches "master"

We're discussing it now on Mahout. It's possible that something like `prod_ready` would be more meaningful, if a project wanted to move off that language. On Tue, Jun 9, 2020 at 11:25 AM Kevin A. McGrail wrote: > +1 to Naomi's interpretation. > -- > Kevin A. McGrail > Member, Apache Software Fou

Re: Naming branches "master"

Yea- I think as Rich said on the whitelist/blacklist thread- its more about making it more welcoming for one committer than being technically correct on the etymology of the word "master" as it pertains to the "master branch". On Tue, Jun 9, 2020 at 5:41 PM Andrew Musselman wrote: > We're disc

Re: Naming branches "master"

+1 On Tue, Jun 9, 2020 at 4:09 PM Trevor Grant wrote: > Yea- I think as Rich said on the whitelist/blacklist thread- its more about > making it more welcoming for one committer than being technically correct > on the etymology of the word "master" as it pertains to the "master > branch". > > > >

Re: Naming branches "master"

You can use the word "trunk" like Apache Subversion does. :) On Tue, 9 Jun 2020 at 18:12, Andrew Musselman wrote: > > +1 > > On Tue, Jun 9, 2020 at 4:09 PM Trevor Grant > wrote: > > > Yea- I think as Rich said on the whitelist/blacklist thread- its more about > > making it more welcoming for one

Re: Blacklist/whitelist

Hi, This may be useful to find and track usage over time: https://github.com/search?q=org%3Aapache+blacklist&type=Code https://github.com/search?q=org%3Aapache+whitelist&type=Code Thanks, Justin - To unsubscribe, e-mail: diversi

Re: Naming branches "master"

:) On Tue, Jun 9, 2020 at 20:38 Matt Sicker wrote: > You can use the word "trunk" like Apache Subversion does. :) > > On Tue, 9 Jun 2020 at 18:12, Andrew Musselman > wrote: > > > > +1 > > > > On Tue, Jun 9, 2020 at 4:09 PM Trevor Grant > > wrote: > > > > > Yea- I think as Rich said on the whit