<div dir="ltr"><div><div><div><div><div>> 1. i would never pull a pre-built binary from a 3rd party into one of my<br>
> projects. lol security?<br>
> 2. that this project doesn't address rebar3/relx/hex at all means it is at<br>
> odds with the direction the community has been pushing toward for several<br>>
years now, and makes it relatively useless<br></div>1. You can't push any built package to the server. You can only ask server to go to github, pull the sources and build the package. Security is the same as you will clone and build github repository.<br></div>To gain better security - you can fork repo (that is why I use namespace/name in packages).<br></div>To gain even better security - you can start your own build server and mention it as repository in the client's config. Server is started with one command `docker-compose up -d` - quite simple.<br></div>2. As you can see - my client uses rebar/<a href="http://erlang.mk">erlang.mk</a> and can resolve links from hex. I can't say it is 100% compatible, but it even can build package from rebar project. <br>But the main reason of using python is - it has lots of plugins and modules. For now I use only Jinja2 templating in erlang configs, but theoretically we can use any plugin available in ansible.<br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-02-12 18:49 GMT+01:00 <span dir="ltr"><<a href="mailto:erlang-questions-request@erlang.org" target="_blank">erlang-questions-request@erlang.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send erlang-questions mailing list submissions to<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:erlang-questions-request@erlang.org">erlang-questions-request@<wbr>erlang.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:erlang-questions-owner@erlang.org">erlang-questions-owner@erlang.<wbr>org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of erlang-questions digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Coon - new tool for building Erlang packages, dependency<br>
management and deploying Erlang services (Valery Tikhonov)<br>
2. Re: Coon - new tool for building Erlang packages, dependency<br>
management and deploying Erlang services (Jordan Chaitin)<br>
3. Re: Coon - new tool for building Erlang packages, dependency<br>
management and deploying Erlang services (Tom Santero)<br>
4. Re: erlang-questions Digest, Vol 360, Issue 5 (Onorio Catenacci)<br>
5. Re: Coon - new tool for building Erlang packages, dependency<br>
management and deploying Erlang services (<a href="mailto:zxq9@zxq9.com">zxq9@zxq9.com</a>)<br>
6. Re: erlang-questions Digest, Vol 360, Issue 5 (Roman Galeev)<br>
7. Re: erlang-questions Digest, Vol 360, Issue 5<br>
(Karolis Petrauskas)<br>
8. Re: Coon - new tool for building Erlang packages, dependency<br>
management and deploying Erlang services (Rick Pettit)<br>
9. Re: erlang-questions Digest, Vol 360, Issue 5 (Alin Popa)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Mon, 12 Feb 2018 16:59:50 +0100<br>
From: Valery Tikhonov <<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@gmail.com</a>><br>
To: Roman Galeev <<a href="mailto:jamhedd@gmail.com">jamhedd@gmail.com</a>><br>
Cc: Erlang <<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] Coon - new tool for building Erlang<br>
packages, dependency management and deploying Erlang services<br>
Message-ID:<br>
<<a href="mailto:CAFH5SaUfe0acXZEGxL2_bmyewDv9u9uK34Qqm_eD4L_ZoEkhig@mail.gmail.com">CAFH5SaUfe0acXZEGxL2_<wbr>bmyewDv9u9uK34Qqm_eD4L_<wbr>ZoEkhig@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Frankly speaking, I've expected another type of questions, when writing<br>
announcement.<br>
Again - I selected name `coon` because `raccoon` was occupied. That's all.<br>
<br>
Also I've always beleived that programmers are beyond the politics, sexism<br>
and all kind of discriminations. So not using library, that can potentially<br>
be useful is a little bit surprising for me.<br>
<br>
It's a pity, that today I can't fully use language to express what I would<br>
like to. But to make everyone happy, I will create a wrapper around coon<br>
for those who don't like coon name itself.<br>
<br>
P.S.: Just think - prohibiting words in the language will finally leave you<br>
with empty vocabulary.<br>
<br>
<br>
<br>
2018-02-12 16:25 GMT+01:00 Roman Galeev <<a href="mailto:jamhedd@gmail.com">jamhedd@gmail.com</a>>:<br>
<br>
> > denigrate protected groups<br>
><br>
> I'm quite sure you can use any given word for that.<br>
><br>
> On Mon, Feb 12, 2018 at 4:22 PM, Lo?c Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>> wrote:<br>
><br>
>> That's the thing about identity politics, it's not all offensive words<br>
>> that are bad, it's only those that can be used to denigrate protected<br>
>> groups (regardless of intent or how old or local the meaning is).<br>
>><br>
>> On 02/12/2018 04:18 PM, Roman Galeev wrote:<br>
>><br>
>>> Well, we have git already and nobody seems to be offended.<br>
>>><br>
>>> On Mon, Feb 12, 2018 at 4:11 PM, Chris Waymire <<a href="mailto:chris@waymire.net">chris@waymire.net</a><br>
>>> <mailto:<a href="mailto:chris@waymire.net">chris@waymire.net</a>>> wrote:<br>
>>><br>
>>> The idea that a software library that happens to share name with a<br>
>>> racial slur that is over 180 years old and has not been part of<br>
>>> common social use for several decades would make people angry is<br>
>>> ridiculous. Especially when the word as meanings that pre-date the<br>
>>> slur. If that upsets you to the point where you are unable to get<br>
>>> past it then it is time to unplug your tv, your radio and your<br>
>>> internet and live a life of peaceful solitude.<br>
>>><br>
>>> On Mon, Feb 12, 2018 at 7:03 AM, Lo?c Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a><br>
>>> <mailto:<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>>> wrote:<br>
>>><br>
>>> This idea that white supremacists need a reason to call others<br>
>>> using racial slurs is ridiculous at best. At this rate you will<br>
>>> call me a Nazi by the next reply. Fingers crossed.<br>
>>><br>
>>> Again Valery does not apply this term to black people or make<br>
>>> any reference about them or the US History, so there's no intent<br>
>>> here. He's using the other meaning.<br>
>>><br>
>>> Soon you will argue that hunters are racists because they call<br>
>>> racoons "coons".<br>
>>><br>
>>><br>
>>> On 02/12/2018 03:53 PM, Josh Barney wrote:<br>
>>><br>
>>> Intent IS important and the intent of the people who applied<br>
>>> this term to black people was a very bad intent.<br>
>>><br>
>>> ?People are getting offended much too easily these days? ?<br>
>>> this argument has been plastered all over American news for<br>
>>> years, always coming from a privileged group claiming hurt.<br>
>>> This is the white supremesist position.<br>
>>><br>
>>><br>
>>> On Mon, Feb 12, 2018 at 9:34 AM Lo?c Hoguin<br>
>>> <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a> <mailto:<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>>> wrote:<br>
>>><br>
>>> This reminds me of people who were calling some coffee<br>
>>> brand racist not<br>
>>> realizing that the Spanish or Portuguese translation<br>
>>> for "black"<br>
>>> looks a<br>
>>> lot like a racist slur.<br>
>>><br>
>>> People are getting offended much too easily these days.<br>
>>> Intent is<br>
>>> important and there's no intent to slur here.<br>
>>><br>
>>> On 02/12/2018 03:15 PM, Josh Barney wrote:<br>
>>> > One would presume that all the black persons who<br>
>>> have been called<br>
>>> in an<br>
>>> > effort to reduce them to rabid animals hunted for<br>
>>> sport by white men<br>
>>> > with dogs would be aware. That?s the import thing<br>
>>> about racial<br>
>>> slurs,<br>
>>> > not that you are unhurt, but that someone else is<br>
>>> hurt.<br>
>>> ><br>
>>> > On Mon, Feb 12, 2018 at 9:04 AM Lo?c Hoguin<br>
>>> <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a> <mailto:<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>>><br>
>>> wrote:<br>
>>> ><br>
>>> > More importantly, who is aware of them? I doubt too<br>
>>> many people<br>
>>> outside<br>
>>> > of North America know about it.<br>
>>> ><br>
>>> > And secondly, should you censor a word that's<br>
>>> otherwise perfectly<br>
>>> fine<br>
>>> > because of its use in slang? It'll get some radical<br>
>>> activists<br>
>>> angry for<br>
>>> > sure so it depends on whether you see this as a good<br>
>>> or a bad thing.<br>
>>> > Nowadays that tends to be a good thing.<br>
>>> ><br>
>>> > Most people will not think twice about it.<br>
>>> ><br>
>>> > On 02/12/2018 02:17 PM, Fred Hebert wrote:<br>
>>> > > Are you aware of the connotations coming with that<br>
>>> name?<br>
>>> > ><br>
>>> > > On Sun, Feb 11, 2018 at 4:05 PM, Valery Tikhonov<br>
>>> > > <<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@gmail.com</a><br>
>>> <mailto:<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@<wbr>gmail.com</a>><br>
>>> <mailto:<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@<wbr>gmail.com</a><br>
>>><br>
>>> <mailto:<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@<wbr>gmail.com</a>>>><br>
>>> > wrote:<br>
>>> > ><br>
>>> > > Hi,<br>
>>> > > I would like to introduce ?oon<br>
>>> <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a><br>
>>> <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a>>> -<br>
>>> > > build and dependency management system and tool<br>
>>> for easy<br>
>>> deployment<br>
>>> > > Erlang packages.<br>
>>> > > In short:<br>
>>> > ><br>
>>> > > * coon uses prebuilt packages from CoonHub<br>
>>> > > <<a href="https://coon.justtech.blog" rel="noreferrer" target="_blank">https://coon.justtech.blog</a>>, what reduces build<br>
>>> time<br>
>>> > > * thanks to github integration it allows to<br>
>>> trigger new builds for<br>
>>> > > Erlang packages when commiting new tag in repo<br>
>>> > > * you can set installation steps to deploy and run<br>
>>> Erlang service<br>
>>> > > from prebuilt package on system without otp/Erlang<br>
>>> installed<br>
>>> > > with `coon install namespace/name`<br>
>>> > ><br>
>>> > > Documentation, articles and links:<br>
>>> > ><br>
>>> > > coon (client) - <a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a><br>
>>> <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a>><br>
>>> > > <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a><br>
>>> <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a>>> see Readme.md and doc<br>
>>> folder<br>
>>> > ><br>
>>> > > coon_auto_builder (server) -<br>
>>> > > <a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a><br>
>>> <<a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a>><br>
>>> > > <<a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a><br>
>>> <<a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a>>><br>
>>> > ><br>
>>> > > how to create and build Erlang service from scratch<br>
>>> > ><br>
>>> <a href="https://justtech.blog/2018/01/07/create-erlang-service-with-" rel="noreferrer" target="_blank">https://justtech.blog/2018/01/<wbr>07/create-erlang-service-with-</a><br>
>>> coon/<br>
>>> <<a href="https://justtech.blog/2018/01/07/create-erlang-service-with" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>01/07/create-erlang-service-<wbr>with</a><br>
>>> -coon/><br>
>>> > ><br>
>>> <<a href="https://justtech.blog/2018/01" rel="noreferrer" target="_blank">https://justtech.blog/2018/01</a><br>
>>> /07/create-erlang-service-<wbr>with-coon/<br>
>>> <<a href="https://justtech.blog/2018/01/07/create-erlang-service-with" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>01/07/create-erlang-service-<wbr>with</a><br>
>>> -coon/>><br>
>>> > ><br>
>>> > > how to prepare Erlang service for deploy<br>
>>> > ><br>
>>> ><br>
>>> <a href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy-" rel="noreferrer" target="_blank">https://justtech.blog/2018/02/<wbr>11/erlang-service-easy-deploy-</a><br>
>>> with-coon/<br>
>>> <<a href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>02/11/erlang-service-easy-<wbr>deploy</a><br>
>>> -with-coon/><br>
>>> > ><br>
>>> ><br>
>>> <<a href="https://justtech.blog/2018/02" rel="noreferrer" target="_blank">https://justtech.blog/2018/02</a><br>
>>> /11/erlang-service-easy-<wbr>deploy-with-coon/<br>
>>> <<a href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>02/11/erlang-service-easy-<wbr>deploy</a><br>
>>> -with-coon/>><br>
>>><br>
>>> > ><br>
>>> > > example service which uses coon<br>
>>> > > <a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a><br>
>>> <<a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a>><br>
>>> > > <<a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a><br>
>>> <<a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a>>><br>
>>> > ><br>
>>> > > example library which uses coon<br>
>>> > > <a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a><br>
>>> <<a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a>><br>
>>> > > <<a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a><br>
>>> <<a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a>>><br>
>>> > ><br>
>>> > > Hope you find this tool useful :)<br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > > ______________________________<wbr>_________________<br>
>>> > > erlang-questions mailing list<br>
>>> > > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>>> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>><br>
>>> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a><br>
>>> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>>><br>
>>> > ><br>
>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>><br>
>>> > ><br>
>>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>>><br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > ><br>
>>> > > ______________________________<wbr>_________________<br>
>>> > > erlang-questions mailing list<br>
>>> > > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>>> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>><br>
>>> > ><br>
>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>><br>
>>> > ><br>
>>> ><br>
>>> > --<br>
>>> > Lo?c Hoguin<br>
>>> > <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
>>> > ______________________________<wbr>_________________<br>
>>> > erlang-questions mailing list<br>
>>> > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>>> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>><br>
>>> > <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>><br>
>>> ><br>
>>><br>
>>> -- Lo?c Hoguin<br>
>>> <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
>>><br>
>>><br>
>>> -- Lo?c Hoguin<br>
>>><br>
>>> <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
>>> ______________________________<wbr>_________________<br>
>>> erlang-questions mailing list<br>
>>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>><br>
>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>><br>
>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> erlang-questions mailing list<br>
>>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>><br>
>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> With best regards,<br>
>>> Roman Galeev,<br>
>>> <a href="tel:%2B420%20702%20817%20968" value="+420702817968">+420 702 817 968</a><br>
>>><br>
>><br>
>> --<br>
>> Lo?c Hoguin<br>
>> <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> With best regards,<br>
> Roman Galeev,<br>
> <a href="tel:%2B420%20702%20817%20968" value="+420702817968">+420 702 817 968</a> <+420%20702%20817%20968><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://erlang.org/pipermail/erlang-questions/attachments/20180212/3537f748/attachment-0001.html" rel="noreferrer" target="_blank">http://erlang.org/pipermail/<wbr>erlang-questions/attachments/<wbr>20180212/3537f748/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 12 Feb 2018 22:28:19 +0530<br>
From: Jordan Chaitin <<a href="mailto:jordanchaitin@gmail.com">jordanchaitin@gmail.com</a>><br>
To: Chris Waymire <<a href="mailto:chris@waymire.net">chris@waymire.net</a>><br>
Cc: Valery Tikhonov <<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@gmail.com</a>>, Erlang<br>
<<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] Coon - new tool for building Erlang<br>
packages, dependency management and deploying Erlang services<br>
Message-ID: <<a href="mailto:42CDDAD6-3CF6-4143-B108-F66F7B4723BB@gmail.com">42CDDAD6-3CF6-4143-B108-<wbr>F66F7B4723BB@gmail.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Not being from North America, I am (was) unaware of the connotations surrounding coon.<br>
<br>
But I?d like to share something related: while living in Europe, a friend wanted to set up a food stall and call it the SS Amsterdam. SS being the abbreviation for Sweets and Snacks, which is what the proposed stall would be selling. The name got shot down (on account of it reminding people of the Nazi SS) by everyone he presented to, including friends, colleagues, acquaintances, and investors. Ultimately he had to change the name. I won?t divulge whether or not he went ahead with a new name or dropped the whole thing. I thought the whole criticism was hypocritical and funny, because nobody seemed to have a problem with the SS Rotterdam, which is a popular former cruise ship and current hotel ship. Maybe it has to do with the fact that SS, as a naval abbreviation (for Steam Ship, or technically Steam Screw) predates the use by the Nazis, whereas the Nazis predate the hypothetical SS Amsterdam proposed by my friend. Going by that line of reasoning, Coon as a slur predates coon<br>
as a package manager, and hence takes precedence. Not that I agree with it. But it does seem to rile people up.<br>
<br>
Cheers<br>
<br>
<br>
<br>
> On Feb 12, 2018, at 20:41, Chris Waymire <<a href="mailto:chris@waymire.net">chris@waymire.net</a>> wrote:<br>
><br>
> The idea that a software library that happens to share name with a racial slur that is over 180 years old and has not been part of common social use for several decades would make people angry is ridiculous. Especially when the word as meanings that pre-date the slur. If that upsets you to the point where you are unable to get past it then it is time to unplug your tv, your radio and your internet and live a life of peaceful solitude.<br>
><br>
> On Mon, Feb 12, 2018 at 7:03 AM, Lo?c Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>> wrote:<br>
> This idea that white supremacists need a reason to call others using racial slurs is ridiculous at best. At this rate you will call me a Nazi by the next reply. Fingers crossed.<br>
><br>
> Again Valery does not apply this term to black people or make any reference about them or the US History, so there's no intent here. He's using the other meaning.<br>
><br>
> Soon you will argue that hunters are racists because they call racoons "coons".<br>
><br>
><br>
> On 02/12/2018 03:53 PM, Josh Barney wrote:<br>
> Intent IS important and the intent of the people who applied this term to black people was a very bad intent.<br>
><br>
> ?People are getting offended much too easily these days? ? this argument has been plastered all over American news for years, always coming from a privileged group claiming hurt. This is the white supremesist position.<br>
><br>
><br>
> On Mon, Feb 12, 2018 at 9:34 AM Lo?c Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>> wrote:<br>
><br>
> This reminds me of people who were calling some coffee brand racist not<br>
> realizing that the Spanish or Portuguese translation for "black"<br>
> looks a<br>
> lot like a racist slur.<br>
><br>
> People are getting offended much too easily these days. Intent is<br>
> important and there's no intent to slur here.<br>
><br>
> On 02/12/2018 03:15 PM, Josh Barney wrote:<br>
> > One would presume that all the black persons who have been called<br>
> in an<br>
> > effort to reduce them to rabid animals hunted for sport by white men<br>
> > with dogs would be aware. That?s the import thing about racial<br>
> slurs,<br>
> > not that you are unhurt, but that someone else is hurt.<br>
> ><br>
> > On Mon, Feb 12, 2018 at 9:04 AM Lo?c Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>><br>
> wrote:<br>
> ><br>
> > More importantly, who is aware of them? I doubt too many people<br>
> outside<br>
> > of North America know about it.<br>
> ><br>
> > And secondly, should you censor a word that's otherwise perfectly<br>
> fine<br>
> > because of its use in slang? It'll get some radical activists<br>
> angry for<br>
> > sure so it depends on whether you see this as a good or a bad thing.<br>
> > Nowadays that tends to be a good thing.<br>
> ><br>
> > Most people will not think twice about it.<br>
> ><br>
> > On 02/12/2018 02:17 PM, Fred Hebert wrote:<br>
> > > Are you aware of the connotations coming with that name?<br>
> > ><br>
> > > On Sun, Feb 11, 2018 at 4:05 PM, Valery Tikhonov<br>
> > > <<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@gmail.com</a> <mailto:<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@<wbr>gmail.com</a>>><br>
> > wrote:<br>
> > ><br>
> > > Hi,<br>
> > > I would like to introduce ?oon<br>
> <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a>> -<br>
> > > build and dependency management system and tool for easy<br>
> deployment<br>
> > > Erlang packages.<br>
> > > In short:<br>
> > ><br>
> > > * coon uses prebuilt packages from CoonHub<br>
> > > <<a href="https://coon.justtech.blog" rel="noreferrer" target="_blank">https://coon.justtech.blog</a>>, what reduces build time<br>
> > > * thanks to github integration it allows to trigger new builds for<br>
> > > Erlang packages when commiting new tag in repo<br>
> > > * you can set installation steps to deploy and run Erlang service<br>
> > > from prebuilt package on system without otp/Erlang installed<br>
> > > with `coon install namespace/name`<br>
> > ><br>
> > > Documentation, articles and links:<br>
> > ><br>
> > > coon (client) - <a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a><br>
> > > <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a>> see Readme.md and doc folder<br>
> > ><br>
> > > coon_auto_builder (server) -<br>
> > > <a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a><br>
> > > <<a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a>><br>
> > ><br>
> > > how to create and build Erlang service from scratch<br>
> > > <a href="https://justtech.blog/2018/01/07/create-erlang-service-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/01/<wbr>07/create-erlang-service-with-<wbr>coon/</a><br>
> > ><br>
> <<a href="https://justtech.blog/2018/01/07/create-erlang-service-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>01/07/create-erlang-service-<wbr>with-coon/</a>><br>
> > ><br>
> > > how to prepare Erlang service for deploy<br>
> > ><br>
> ><br>
> <a href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/02/<wbr>11/erlang-service-easy-deploy-<wbr>with-coon/</a><br>
> > ><br>
> ><br>
> <<a href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>02/11/erlang-service-easy-<wbr>deploy-with-coon/</a>><br>
><br>
> > ><br>
> > > example service which uses coon<br>
> > > <a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a><br>
> > > <<a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a>><br>
> > ><br>
> > > example library which uses coon<br>
> > > <a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a><br>
> > > <<a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a>><br>
> > ><br>
> > > Hope you find this tool useful :)<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > ______________________________<wbr>_________________<br>
> > > erlang-questions mailing list<br>
> > > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>><br>
> > > <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
> > > <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > ______________________________<wbr>_________________<br>
> > > erlang-questions mailing list<br>
> > > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> > > <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
> > ><br>
> ><br>
> > --<br>
> > Lo?c Hoguin<br>
> > <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
> > ______________________________<wbr>_________________<br>
> > erlang-questions mailing list<br>
> > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> > <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
> ><br>
><br>
> -- Lo?c Hoguin<br>
> <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
><br>
><br>
> --<br>
> Lo?c Hoguin<br>
><br>
> <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 12 Feb 2018 12:10:20 -0500<br>
From: Tom Santero <<a href="mailto:tsantero@gmail.com">tsantero@gmail.com</a>><br>
To: Jesper Louis Andersen <<a href="mailto:jesper.louis.andersen@gmail.com">jesper.louis.andersen@gmail.<wbr>com</a>><br>
Cc: Erlang <<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] Coon - new tool for building Erlang<br>
packages, dependency management and deploying Erlang services<br>
Message-ID:<br>
<<a href="mailto:CAAOU%2BetQc4KEOnqmiEtRHeBx1qr3yzdfHtO0VE8FOZwY-pGp0w@mail.gmail.com">CAAOU+<wbr>etQc4KEOnqmiEtRHeBx1qr3yzdfHtO<wbr>0VE8FOZwY-pGp0w@mail.gmail.com</a><wbr>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Putting the project's name aside for a moment, there are two things I'd<br>
like to point about:<br>
<br>
1. i would never pull a pre-built binary from a 3rd party into one of my<br>
projects. lol security?<br>
2. that this project doesn't address rebar3/relx/hex at all means it is at<br>
odds with the direction the community has been pushing toward for several<br>
years now, and makes it relatively useless<br>
<br>
That said, the name: anyone in North America who reads this immediately<br>
thinks of the racist slur, despite intent or cultural differences. if<br>
you're an adult in 2018 and can't comprehend that being offended by<br>
something and that thing being objectively offensive aren't mutually<br>
exclusive then...well I'd suggest you take a good long time to reevaluate<br>
everything you've done with your life up until today.<br>
<br>
On Mon, Feb 12, 2018 at 12:01 PM, Jesper Louis Andersen <<br>
<a href="mailto:jesper.louis.andersen@gmail.com">jesper.louis.andersen@gmail.<wbr>com</a>> wrote:<br>
<br>
> There is also "Maine Coon", which is a cat breed.<br>
><br>
> Personally, I'd do two things:<br>
><br>
> 1. I'm interested in the etymology of the word in<br>
> Russian/Ukrainian/Belarussian etc and why that name was chosen in the first<br>
> place.<br>
> 2. I'd probably change the name. There is a well known proof assistant<br>
> named "Coq" (french for "Rooster"). Apart from snickers and giggles, one<br>
> has to make the case that a certain amount of internationality is to be<br>
> expected of library names. It simply creates more trouble than it solves.<br>
><br>
> Of course, the balance is that an innocent western name might really upset<br>
> the asian population in a major asian country (China, India, Japan, ...),<br>
> and few people care about this. It is just that Americans tend to<br>
> self-immolate as soon as you mention their past.<br>
><br>
><br>
><br>
> On Mon, Feb 12, 2018 at 5:52 PM Chris Duesing <<a href="mailto:chris.duesing@gmail.com">chris.duesing@gmail.com</a>><br>
> wrote:<br>
><br>
>> I can't believe this "discussion" is happening. Coon is a racial slur,<br>
>> there is no other use of the word. The fact that a bunch of white Europeans<br>
>> are pointing out that the dozen people involved in this thread aren't<br>
>> offended simply shows the lack of diversity in the mailing list. The "oh<br>
>> I'm butthurt because other people get offended by things" is fucking<br>
>> ridiculous. It is a racial slur, period. If this isn't a library only<br>
>> intended to be used by racist fucks then rename it.<br>
>><br>
>> On Mon, Feb 12, 2018 at 10:28 AM, nx <<a href="mailto:nx@nu-ex.com">nx@nu-ex.com</a>> wrote:<br>
>><br>
>>> For what it's worth, the first thing I thought of when I saw the title<br>
>>> of this thread was "that is a racist slur". I've also never heard anyone<br>
>>> call a raccoon a coon.<br>
>>><br>
>>> The news that cowboy was named for "cowboys kill apaches" is<br>
>>> disappointing.<br>
>>><br>
>>> On Mon, Feb 12, 2018 at 11:22 AM Fred Hebert <<a href="mailto:mononcqc@ferd.ca">mononcqc@ferd.ca</a>> wrote:<br>
>>><br>
>>>> What I'm saying is that it does not matter how I interpret things. I<br>
>>>> asked and the author said publicly it was a raccoon. I'm okay with that<br>
>>>> explanation and I'm ready to believe it.<br>
>>>><br>
>>>> My point is that other people won't ask the author, won't know who he<br>
>>>> is, and will pick an interpretation and stick with it. They won't need the<br>
>>>> context, they won't need anything. They'll just do it. The name can be<br>
>>>> interpreted in a racist way, and so it's pretty much guaranteed that it<br>
>>>> will be eventually interpreted that way. The author is free to go ahead and<br>
>>>> keep the name, and the users and onlookers will be free to read whatever<br>
>>>> they want in that name.<br>
>>>><br>
>>>> That is 100% my point.<br>
>>>><br>
>>>> On Mon, Feb 12, 2018 at 11:17 AM, Krzysztof Jurewicz <<br>
>>>> <a href="mailto:krzysztof.jurewicz@gmail.com">krzysztof.jurewicz@gmail.com</a>> wrote:<br>
>>>><br>
>>>>> Fred Hebert writes:<br>
>>>>><br>
>>>>> > Anyone is of course free to name their software whatever they want.<br>
>>>>> Picking<br>
>>>>> > a racist name is however never going to be consequences-free as this<br>
>>>>> e-mail<br>
>>>>> > thread first shows on the first day of release, and adoption figures<br>
>>>>> may<br>
>>>>> > also reflect it.<br>
>>>>><br>
>>>>> Merriam-Webster online dictionary (naming itself as ?America?s<br>
>>>>> most-trusted online dictionary?) says that there two meanings of ?coon?:<br>
>>>>><br>
>>>>> ? raccoon;<br>
>>>>> ? offensive ? used as an insulting and contemptuous term for a black<br>
>>>>> person.<br>
>>>>><br>
>>>>> I presume that context matters. What makes you think that in this<br>
>>>>> context this word means ?? Wikipedia in the article about raccoon says that<br>
>>>>> is also known coloquially as ?coon?, so I guess this is not a very uncommon<br>
>>>>> usage.<br>
>>>>><br>
>>>>> Or are you saying that non-racist usages of words that have also<br>
>>>>> racist meanings should be eventually abandoned?<br>
>>>>><br>
>>>>> (I?m not a native speaker, so bear with my eventual ignorance).<br>
>>>>><br>
>>>><br>
>>>> ______________________________<wbr>_________________<br>
>>>> erlang-questions mailing list<br>
>>>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> erlang-questions mailing list<br>
>>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>><br>
>>><br>
>> ______________________________<wbr>_________________<br>
>> erlang-questions mailing list<br>
>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>><br>
><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://erlang.org/pipermail/erlang-questions/attachments/20180212/27178887/attachment-0001.html" rel="noreferrer" target="_blank">http://erlang.org/pipermail/<wbr>erlang-questions/attachments/<wbr>20180212/27178887/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 12 Feb 2018 12:22:46 -0500<br>
From: Onorio Catenacci <<a href="mailto:Catenacci@ieee.org">Catenacci@ieee.org</a>><br>
To: erlang-questions <<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] erlang-questions Digest, Vol 360,<br>
Issue 5<br>
Message-ID:<br>
<CAP=<a href="mailto:vNq_4NNaZt_O0W2n6cbYbGJw4XQwweJQNEuq9a_p-wOvpaQ@mail.gmail.com">vNq_4NNaZt_<wbr>O0W2n6cbYbGJw4XQwweJQNEuq9a_p-<wbr>wOvpaQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
A few thoughts:<br>
<br>
1.) As a native speaker of American English, trust me the word "coon" is<br>
extremely offensive. I'm not trying to be hyperbolic but it's my<br>
impression that to African-Americans this word is almost as offensive as<br>
the N word is. I'm not a SJW and I'm not politically correct. I simply<br>
don't have any good reason to likely offend people when a less offensive<br>
term (like "Racoon") is easily available to use. If you don't speak<br>
American English natively, trust me this is not a case of someone being<br>
hypersensitive. It's a very offensive word.<br>
<br>
2.) It looks like Valery simply decide to build Rebar3/Hex/Mix etc. with<br>
Python. That's perfectly fine. I'm not seeing anything much on there<br>
other than "we decided to rebuild rebar3 with python" and "we're going to<br>
build packages to work with our new build system" but it doesn't look as if<br>
they have yet.<br>
<br>
3.) I also agree with Fred and others who say that all this discussion on<br>
the subtleties of political correctness and freedom of expression will get<br>
lost outside of this mailing list. All this would do is give a black eye<br>
to the Erlang community and convince people who don't know any better than<br>
some segment of developers who use Erlang are racists. Fair or not that's<br>
what will happen. Of course who ever said life is fair?<br>
<br>
I wish I had a better grasp of the native language of some folks on this<br>
list so I could express how offensive this particular word is to people who<br>
speak American English. Maybe if I said to Valery I were going to build a<br>
library named " ???" that might give some idea of how loaded with negative<br>
meaning the word "Coon" is in English. The fact that lots of Russian folks<br>
might find that particular phrase offensive--well they need to stop being<br>
so sensitive right?<br>
<br>
If you want to continue with this library, please simply change the name to<br>
"Racoon." This is not about offending or not offending anyone. Its about<br>
giving people the wrong impression by picking a name with a negative<br>
meaning in American English. Or if you insist on using "Coon" then use the<br>
word in whatever your native language is for "Racoon".<br>
<br>
I'll put it this way: I wouldn't name a library "Bitch". Yes, it refers to<br>
a female dog. But it's more commonly used as an offensive way to describe<br>
a female that one doesn't like.<br>
<br>
I also wouldn't name a library "Ass". That word can refer to a donkey but<br>
it's so overwhelmingly identified with a pejorative slang term that native<br>
speakers wouldn't think "donkey"--they'd think the other thing.<br>
<br>
--<br>
Onorio Catenacci<br>
<br>
<a href="http://onor.io" rel="noreferrer" target="_blank">http://onor.io</a><br>
<a href="http://www.google.com/+OnorioCatenacci" rel="noreferrer" target="_blank">http://www.google.com/+<wbr>OnorioCatenacci</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://erlang.org/pipermail/erlang-questions/attachments/20180212/4e893b05/attachment-0001.html" rel="noreferrer" target="_blank">http://erlang.org/pipermail/<wbr>erlang-questions/attachments/<wbr>20180212/4e893b05/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 13 Feb 2018 02:28:47 +0900<br>
From: <a href="mailto:zxq9@zxq9.com">zxq9@zxq9.com</a><br>
To: <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
Subject: Re: [erlang-questions] Coon - new tool for building Erlang<br>
packages, dependency management and deploying Erlang services<br>
Message-ID: <2713817.h8SfDXM89s@takoyaki><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On 2018?2?12???? 12?10?20? JST Tom Santero wrote:<br>
> Putting the project's name aside for a moment, there are two things I'd<br>
> like to point about:<br>
<br>
THANK YOU<br>
<br>
> 1. i would never pull a pre-built binary from a 3rd party into one of my<br>
> projects. lol security?<br>
<br>
I disagree, in that we are right back in "trusting trust" territory. I prefer building from source (for a number of reasons) but source or not, for nearly everyone (perhaps actually everyone) who builds a project that involves external dependencies, the security is only as strong as the signature on the code received (and implicitly, the trust of the signature scheme employed) and the trust of the review process which granted the signature.<br>
<br>
Both are greviously lacking in using direct-from-github packages (whether source or pre-built) as repository inputs.<br>
<br>
> 2. that this project doesn't address rebar3/relx/hex at all means it is at<br>
> odds with the direction the community has been pushing toward for several<br>
> years now, and makes it relatively useless<br>
<br>
I disagree again. In this era we have full-blown systems to drive; the common case today is NOT to deploy to a resource-strapped or custom-built piece of hardware that can never be accessed by system administrators. The common environment today is more like a (to use an awful term) "devops" environment where people want things to rebuild in the lightest possible way and "just go". Which is to say, people desperately wish that Erlang (not to mention Elixir) code could be more commonly built and run the way Python projects that use virtualenv can be.<br>
<br>
I think the to-date direction of the Erlang community de facto practices is a bit dated, being built around the ancient and original assumption "everything has to be an Erlang distribution".<br>
<br>
-Craig<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Mon, 12 Feb 2018 18:39:14 +0100<br>
From: Roman Galeev <<a href="mailto:jamhedd@gmail.com">jamhedd@gmail.com</a>><br>
To: Onorio Catenacci <<a href="mailto:Catenacci@ieee.org">Catenacci@ieee.org</a>><br>
Cc: erlang-questions <<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] erlang-questions Digest, Vol 360,<br>
Issue 5<br>
Message-ID:<br>
<CANJ6ymbe=<a href="mailto:kAtc%2BdLb7dhubdB7fBPikHKoEBkm9de39O4griJ5g@mail.gmail.com">kAtc+<wbr>dLb7dhubdB7fBPikHKoEBkm9de39O4<wbr>griJ5g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
> how offensive this particular word is to people who speak American<br>
English.<br>
<br>
There are offensive words in Russian, and they even form a sublanguage<br>
named 'mat'. But you can't find something like this <a href="http://coonlabs.com/" rel="noreferrer" target="_blank">http://coonlabs.com/</a><br>
<<a href="https://mltrk.io/link/http%3A%2F%2Fcoonlabs.com%2F/GEcpm9pL4x4ePNgwJw0H" rel="noreferrer" target="_blank">https://mltrk.io/link/http%<wbr>3A%2F%2Fcoonlabs.com%2F/<wbr>GEcpm9pL4x4ePNgwJw0H</a>><br>
with any of such words, this is simply not possible.<br>
<br>
On Mon, Feb 12, 2018 at 6:22 PM, Onorio Catenacci <<a href="mailto:Catenacci@ieee.org">Catenacci@ieee.org</a>><br>
wrote:<br>
<br>
> A few thoughts:<br>
><br>
> 1.) As a native speaker of American English, trust me the word "coon" is<br>
> extremely offensive. I'm not trying to be hyperbolic but it's my<br>
> impression that to African-Americans this word is almost as offensive as<br>
> the N word is. I'm not a SJW and I'm not politically correct. I simply<br>
> don't have any good reason to likely offend people when a less offensive<br>
> term (like "Racoon") is easily available to use. If you don't speak<br>
> American English natively, trust me this is not a case of someone being<br>
> hypersensitive. It's a very offensive word.<br>
><br>
> 2.) It looks like Valery simply decide to build Rebar3/Hex/Mix etc. with<br>
> Python. That's perfectly fine. I'm not seeing anything much on there<br>
> other than "we decided to rebuild rebar3 with python" and "we're going to<br>
> build packages to work with our new build system" but it doesn't look as if<br>
> they have yet.<br>
><br>
> 3.) I also agree with Fred and others who say that all this discussion on<br>
> the subtleties of political correctness and freedom of expression will get<br>
> lost outside of this mailing list. All this would do is give a black eye<br>
> to the Erlang community and convince people who don't know any better than<br>
> some segment of developers who use Erlang are racists. Fair or not that's<br>
> what will happen. Of course who ever said life is fair?<br>
><br>
> I wish I had a better grasp of the native language of some folks on this<br>
> list so I could express how offensive this particular word is to people who<br>
> speak American English. Maybe if I said to Valery I were going to build a<br>
> library named " ???" that might give some idea of how loaded with<br>
> negative meaning the word "Coon" is in English. The fact that lots of<br>
> Russian folks might find that particular phrase offensive--well they need<br>
> to stop being so sensitive right?<br>
><br>
> If you want to continue with this library, please simply change the name<br>
> to "Racoon." This is not about offending or not offending anyone. Its<br>
> about giving people the wrong impression by picking a name with a negative<br>
> meaning in American English. Or if you insist on using "Coon" then use the<br>
> word in whatever your native language is for "Racoon".<br>
><br>
> I'll put it this way: I wouldn't name a library "Bitch". Yes, it refers<br>
> to a female dog. But it's more commonly used as an offensive way to<br>
> describe a female that one doesn't like.<br>
><br>
> I also wouldn't name a library "Ass". That word can refer to a donkey but<br>
> it's so overwhelmingly identified with a pejorative slang term that native<br>
> speakers wouldn't think "donkey"--they'd think the other thing.<br>
><br>
> --<br>
> Onorio Catenacci<br>
><br>
> <a href="http://onor.io" rel="noreferrer" target="_blank">http://onor.io</a><br>
> <a href="http://www.google.com/+OnorioCatenacci" rel="noreferrer" target="_blank">http://www.google.com/+<wbr>OnorioCatenacci</a><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
><br>
<br>
<br>
--<br>
With best regards,<br>
Roman Galeev,<br>
+420 702 817 968<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://erlang.org/pipermail/erlang-questions/attachments/20180212/f19af5f1/attachment-0001.html" rel="noreferrer" target="_blank">http://erlang.org/pipermail/<wbr>erlang-questions/attachments/<wbr>20180212/f19af5f1/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Mon, 12 Feb 2018 19:47:05 +0200<br>
From: Karolis Petrauskas <<a href="mailto:k.petrauskas@gmail.com">k.petrauskas@gmail.com</a>><br>
To: Roman Galeev <<a href="mailto:jamhedd@gmail.com">jamhedd@gmail.com</a>><br>
Cc: Onorio Catenacci <<a href="mailto:Catenacci@ieee.org">Catenacci@ieee.org</a>>, erlang-questions<br>
<<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] erlang-questions Digest, Vol 360,<br>
Issue 5<br>
Message-ID:<br>
<CAFteovL6bJc6x=<a href="mailto:KJCbS%2BorBYVMxD7juzAHTgZooi-8ajoGOgqA@mail.gmail.com">KJCbS+<wbr>orBYVMxD7juzAHTgZooi-<wbr>8ajoGOgqA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Here you go: <a href="https://kurvasoft.com/" rel="noreferrer" target="_blank">https://kurvasoft.com/</a><br>
<br>
Karolis<br>
<br>
On Mon, Feb 12, 2018 at 7:39 PM, Roman Galeev <<a href="mailto:jamhedd@gmail.com">jamhedd@gmail.com</a>> wrote:<br>
<br>
> > how offensive this particular word is to people who speak American<br>
> English.<br>
><br>
> There are offensive words in Russian, and they even form a sublanguage<br>
> named 'mat'. But you can't find something like this <a href="http://coonlabs.com/" rel="noreferrer" target="_blank">http://coonlabs.com/</a><br>
> <<a href="https://mltrk.io/link/http%3A%2F%2Fcoonlabs.com%2F/GEcpm9pL4x4ePNgwJw0H" rel="noreferrer" target="_blank">https://mltrk.io/link/http%<wbr>3A%2F%2Fcoonlabs.com%2F/<wbr>GEcpm9pL4x4ePNgwJw0H</a>><br>
> with any of such words, this is simply not possible.<br>
><br>
> On Mon, Feb 12, 2018 at 6:22 PM, Onorio Catenacci <<a href="mailto:Catenacci@ieee.org">Catenacci@ieee.org</a>><br>
> wrote:<br>
><br>
>> A few thoughts:<br>
>><br>
>> 1.) As a native speaker of American English, trust me the word "coon" is<br>
>> extremely offensive. I'm not trying to be hyperbolic but it's my<br>
>> impression that to African-Americans this word is almost as offensive as<br>
>> the N word is. I'm not a SJW and I'm not politically correct. I simply<br>
>> don't have any good reason to likely offend people when a less offensive<br>
>> term (like "Racoon") is easily available to use. If you don't speak<br>
>> American English natively, trust me this is not a case of someone being<br>
>> hypersensitive. It's a very offensive word.<br>
>><br>
>> 2.) It looks like Valery simply decide to build Rebar3/Hex/Mix etc. with<br>
>> Python. That's perfectly fine. I'm not seeing anything much on there<br>
>> other than "we decided to rebuild rebar3 with python" and "we're going to<br>
>> build packages to work with our new build system" but it doesn't look as if<br>
>> they have yet.<br>
>><br>
>> 3.) I also agree with Fred and others who say that all this discussion on<br>
>> the subtleties of political correctness and freedom of expression will get<br>
>> lost outside of this mailing list. All this would do is give a black eye<br>
>> to the Erlang community and convince people who don't know any better than<br>
>> some segment of developers who use Erlang are racists. Fair or not that's<br>
>> what will happen. Of course who ever said life is fair?<br>
>><br>
>> I wish I had a better grasp of the native language of some folks on this<br>
>> list so I could express how offensive this particular word is to people who<br>
>> speak American English. Maybe if I said to Valery I were going to build a<br>
>> library named " ???" that might give some idea of how loaded with<br>
>> negative meaning the word "Coon" is in English. The fact that lots of<br>
>> Russian folks might find that particular phrase offensive--well they need<br>
>> to stop being so sensitive right?<br>
>><br>
>> If you want to continue with this library, please simply change the name<br>
>> to "Racoon." This is not about offending or not offending anyone. Its<br>
>> about giving people the wrong impression by picking a name with a negative<br>
>> meaning in American English. Or if you insist on using "Coon" then use the<br>
>> word in whatever your native language is for "Racoon".<br>
>><br>
>> I'll put it this way: I wouldn't name a library "Bitch". Yes, it refers<br>
>> to a female dog. But it's more commonly used as an offensive way to<br>
>> describe a female that one doesn't like.<br>
>><br>
>> I also wouldn't name a library "Ass". That word can refer to a donkey but<br>
>> it's so overwhelmingly identified with a pejorative slang term that native<br>
>> speakers wouldn't think "donkey"--they'd think the other thing.<br>
>><br>
>> --<br>
>> Onorio Catenacci<br>
>><br>
>> <a href="http://onor.io" rel="noreferrer" target="_blank">http://onor.io</a><br>
>> <a href="http://www.google.com/+OnorioCatenacci" rel="noreferrer" target="_blank">http://www.google.com/+<wbr>OnorioCatenacci</a><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> erlang-questions mailing list<br>
>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>><br>
>><br>
><br>
><br>
> --<br>
> With best regards,<br>
> Roman Galeev,<br>
> +420 702 817 968 <+420%20702%20817%20968><br>
><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://erlang.org/pipermail/erlang-questions/attachments/20180212/ec3651bd/attachment-0001.html" rel="noreferrer" target="_blank">http://erlang.org/pipermail/<wbr>erlang-questions/attachments/<wbr>20180212/ec3651bd/attachment-<wbr>0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Mon, 12 Feb 2018 11:47:26 -0600<br>
From: Rick Pettit <<a href="mailto:rpettit@vailsys.com">rpettit@vailsys.com</a>><br>
To: Lo?c Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>><br>
Cc: Valery Tikhonov <<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@gmail.com</a>>, Vance Shipley<br>
<<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] Coon - new tool for building Erlang<br>
packages, dependency management and deploying Erlang services<br>
Message-ID: <<a href="mailto:391EF6A8-F1FC-45C8-B6C0-E90BF37EC2E1@vailsys.com">391EF6A8-F1FC-45C8-B6C0-<wbr>E90BF37EC2E1@vailsys.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
As someone who lives in North America, I wouldn?t be terribly excited about the idea of advocating for a piece of software with such a controversial name, to put it mildly.<br>
<br>
I have no doubt it would take more work defending the software and explaining the name than it would be to write my own package manager.<br>
<br>
I also cannot imagine what a ?hero? some of my coworkers (many of which I consider to be close friends) would consider me to be, enabling folks to casually throw out what many know to be a racial slur around the office without fear of consequences.<br>
<br>
Of course I could always throw the ?intent? argument out there, which would no doubt immediately clear up the optics and melt away all the negative feelings...<br>
<br>
Boy this better be one hell of a package manager to be worth all that trouble.<br>
<br>
-Rick<br>
<br>
> On Feb 12, 2018, at 8:04 AM, Lo?c Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>> wrote:<br>
><br>
> More importantly, who is aware of them? I doubt too many people outside of North America know about it.<br>
><br>
> And secondly, should you censor a word that's otherwise perfectly fine because of its use in slang? It'll get some radical activists angry for sure so it depends on whether you see this as a good or a bad thing. Nowadays that tends to be a good thing.<br>
><br>
> Most people will not think twice about it.<br>
><br>
> On 02/12/2018 02:17 PM, Fred Hebert wrote:<br>
>> Are you aware of the connotations coming with that name?<br>
>> On Sun, Feb 11, 2018 at 4:05 PM, Valery Tikhonov <<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@gmail.com</a> <mailto:<a href="mailto:valerii.tikhonov@gmail.com">valerii.tikhonov@<wbr>gmail.com</a>>> wrote:<br>
>> Hi,<br>
>> I would like to introduce ?oon <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a>> -<br>
>> build and dependency management system and tool for easy deployment<br>
>> Erlang packages.<br>
>> In short:<br>
>> * coon uses prebuilt packages from CoonHub<br>
>> <<a href="https://coon.justtech.blog" rel="noreferrer" target="_blank">https://coon.justtech.blog</a>>, what reduces build time<br>
>> * thanks to github integration it allows to trigger new builds for<br>
>> Erlang packages when commiting new tag in repo<br>
>> * you can set installation steps to deploy and run Erlang service<br>
>> from prebuilt package on system without otp/Erlang installed<br>
>> with `coon install namespace/name`<br>
>> Documentation, articles and links:<br>
>> coon (client) - <a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a><br>
>> <<a href="https://github.com/comtihon/coon" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon</a>> see Readme.md and doc folder<br>
>> coon_auto_builder (server) -<br>
>> <a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a><br>
>> <<a href="https://github.com/comtihon/coon_auto_builder" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>coon_auto_builder</a>><br>
>> how to create and build Erlang service from scratch<br>
>> <a href="https://justtech.blog/2018/01/07/create-erlang-service-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/01/<wbr>07/create-erlang-service-with-<wbr>coon/</a><br>
>> <<a href="https://justtech.blog/2018/01/07/create-erlang-service-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>01/07/create-erlang-service-<wbr>with-coon/</a>><br>
>> how to prepare Erlang service for deploy<br>
>> <a href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/02/<wbr>11/erlang-service-easy-deploy-<wbr>with-coon/</a><br>
>> <<a href="https://justtech.blog/2018/02/11/erlang-service-easy-deploy-with-coon/" rel="noreferrer" target="_blank">https://justtech.blog/2018/<wbr>02/11/erlang-service-easy-<wbr>deploy-with-coon/</a>><br>
>> example service which uses coon<br>
>> <a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a><br>
>> <<a href="https://github.com/comtihon/example_service" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>example_service</a>><br>
>> example library which uses coon<br>
>> <a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a><br>
>> <<a href="https://github.com/comtihon/mongodb-erlang" rel="noreferrer" target="_blank">https://github.com/comtihon/<wbr>mongodb-erlang</a>><br>
>> Hope you find this tool useful :)<br>
>> ______________________________<wbr>_________________<br>
>> erlang-questions mailing list<br>
>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org">erlang-questions@<wbr>erlang.org</a>><br>
>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>> <<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a>><br>
>> ______________________________<wbr>_________________<br>
>> erlang-questions mailing list<br>
>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
> --<br>
> Lo?c Hoguin<br>
> <a href="https://ninenines.eu" rel="noreferrer" target="_blank">https://ninenines.eu</a><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
><br>
> ----------<br>
><br>
> This email has been scanned for spam and viruses by Proofpoint Essentials. Visit the following link to report this email as spam:<br>
> <a href="https://us4.proofpointessentials.com/index01.php?mod_id=11&mod_option=logitem&mail_id=1518444255-EGmkz3btmH1c&r_address=rpettit%40vailsys.com&report=" rel="noreferrer" target="_blank">https://us4.<wbr>proofpointessentials.com/<wbr>index01.php?mod_id=11&mod_<wbr>option=logitem&mail_id=<wbr>1518444255-EGmkz3btmH1c&r_<wbr>address=rpettit%40vailsys.com&<wbr>report=</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Mon, 12 Feb 2018 17:49:03 +0000<br>
From: Alin Popa <<a href="mailto:alin.popa@gmail.com">alin.popa@gmail.com</a>><br>
To: Karolis Petrauskas <<a href="mailto:k.petrauskas@gmail.com">k.petrauskas@gmail.com</a>><br>
Cc: Onorio Catenacci <<a href="mailto:Catenacci@ieee.org">Catenacci@ieee.org</a>>, erlang-questions<br>
<<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
Subject: Re: [erlang-questions] erlang-questions Digest, Vol 360,<br>
Issue 5<br>
Message-ID:<br>
<<a href="mailto:CAEu176eNTYxehwtLXV-TZPPek5x9eN5BpZkaGp3epdQqErGwGA@mail.gmail.com">CAEu176eNTYxehwtLXV-<wbr>TZPPek5x9eN5BpZkaGp3epdQqErGwG<wbr>A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I guess that this guy needs to change his name to Josh Racoon now:<br>
<a href="http://coonlabs.com/about/team/josh-coon/" rel="noreferrer" target="_blank">http://coonlabs.com/about/<wbr>team/josh-coon/</a><br>
<br>
On Mon, Feb 12, 2018 at 5:47 PM, Karolis Petrauskas <<a href="mailto:k.petrauskas@gmail.com">k.petrauskas@gmail.com</a>><br>
wrote:<br>
<br>
> Here you go: <a href="https://kurvasoft.com/" rel="noreferrer" target="_blank">https://kurvasoft.com/</a><br>
><br>
> Karolis<br>
><br>
> On Mon, Feb 12, 2018 at 7:39 PM, Roman Galeev <<a href="mailto:jamhedd@gmail.com">jamhedd@gmail.com</a>> wrote:<br>
><br>
>> > how offensive this particular word is to people who speak American<br>
>> English.<br>
>><br>
>> There are offensive words in Russian, and they even form a sublanguage<br>
>> named 'mat'. But you can't find something like this <a href="http://coonlabs.com/" rel="noreferrer" target="_blank">http://coonlabs.com/</a><br>
>> <<a href="https://mltrk.io/link/http%3A%2F%2Fcoonlabs.com%2F/GEcpm9pL4x4ePNgwJw0H" rel="noreferrer" target="_blank">https://mltrk.io/link/http%<wbr>3A%2F%2Fcoonlabs.com%2F/<wbr>GEcpm9pL4x4ePNgwJw0H</a>><br>
>> with any of such words, this is simply not possible.<br>
>><br>
>> On Mon, Feb 12, 2018 at 6:22 PM, Onorio Catenacci <<a href="mailto:Catenacci@ieee.org">Catenacci@ieee.org</a>><br>
>> wrote:<br>
>><br>
>>> A few thoughts:<br>
>>><br>
>>> 1.) As a native speaker of American English, trust me the word "coon" is<br>
>>> extremely offensive. I'm not trying to be hyperbolic but it's my<br>
>>> impression that to African-Americans this word is almost as offensive as<br>
>>> the N word is. I'm not a SJW and I'm not politically correct. I simply<br>
>>> don't have any good reason to likely offend people when a less offensive<br>
>>> term (like "Racoon") is easily available to use. If you don't speak<br>
>>> American English natively, trust me this is not a case of someone being<br>
>>> hypersensitive. It's a very offensive word.<br>
>>><br>
>>> 2.) It looks like Valery simply decide to build Rebar3/Hex/Mix etc. with<br>
>>> Python. That's perfectly fine. I'm not seeing anything much on there<br>
>>> other than "we decided to rebuild rebar3 with python" and "we're going to<br>
>>> build packages to work with our new build system" but it doesn't look as if<br>
>>> they have yet.<br>
>>><br>
>>> 3.) I also agree with Fred and others who say that all this discussion<br>
>>> on the subtleties of political correctness and freedom of expression will<br>
>>> get lost outside of this mailing list. All this would do is give a black<br>
>>> eye to the Erlang community and convince people who don't know any better<br>
>>> than some segment of developers who use Erlang are racists. Fair or not<br>
>>> that's what will happen. Of course who ever said life is fair?<br>
>>><br>
>>> I wish I had a better grasp of the native language of some folks on this<br>
>>> list so I could express how offensive this particular word is to people who<br>
>>> speak American English. Maybe if I said to Valery I were going to build a<br>
>>> library named " ???" that might give some idea of how loaded with<br>
>>> negative meaning the word "Coon" is in English. The fact that lots of<br>
>>> Russian folks might find that particular phrase offensive--well they need<br>
>>> to stop being so sensitive right?<br>
>>><br>
>>> If you want to continue with this library, please simply change the name<br>
>>> to "Racoon." This is not about offending or not offending anyone. Its<br>
>>> about giving people the wrong impression by picking a name with a negative<br>
>>> meaning in American English. Or if you insist on using "Coon" then use the<br>
>>> word in whatever your native language is for "Racoon".<br>
>>><br>
>>> I'll put it this way: I wouldn't name a library "Bitch". Yes, it refers<br>
>>> to a female dog. But it's more commonly used as an offensive way to<br>
>>> describe a female that one doesn't like.<br>
>>><br>
>>> I also wouldn't name a library "Ass". That word can refer to a donkey<br>
>>> but it's so overwhelmingly identified with a pejorative slang term that<br>
>>> native speakers wouldn't think "donkey"--they'd think the other thing.<br>
>>><br>
>>> --<br>
>>> Onorio Catenacci<br>
>>><br>
>>> <a href="http://onor.io" rel="noreferrer" target="_blank">http://onor.io</a><br>
>>> <a href="http://www.google.com/+OnorioCatenacci" rel="noreferrer" target="_blank">http://www.google.com/+<wbr>OnorioCatenacci</a><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> erlang-questions mailing list<br>
>>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>>><br>
>>><br>
>><br>
>><br>
>> --<br>
>> With best regards,<br>
>> Roman Galeev,<br>
>> +420 702 817 968 <+420%20702%20817%20968><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> erlang-questions mailing list<br>
>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
>><br>
>><br>
><br>
> ______________________________<wbr>_________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://erlang.org/pipermail/erlang-questions/attachments/20180212/1976adf6/attachment.html" rel="noreferrer" target="_blank">http://erlang.org/pipermail/<wbr>erlang-questions/attachments/<wbr>20180212/1976adf6/attachment.<wbr>html</a>><br>
<br>
------------------------------<br>
<br>
______________________________<wbr>_________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
<br>
<br>
End of erlang-questions Digest, Vol 360, Issue 7<br>
******************************<wbr>******************<br>
</blockquote></div><br></div>