Dear JavaScript
I usually don&#x27;t comment about these type of posts, but I felt I had to speak out here when the author of this article has been an offender of the things he&#x27;s trying to promote. Perhaps he has just &quot;seen the light,&quot; but I have my reservations.<p>Specifically, these lines got to me:<p>&gt;If we focus on solutions, focus on helping others, focus on sharing ideas, we’ll be in a better place. We’re all part of a broader community and we all have an impact on it. We can either have a positive impact or a negative one. It’s entirely up to us.<p>&gt; This is the reality the community faces. We can either work to fix it or we can continue digging a deeper hole for ourselves.<p>At my company, we were using Lerna [1], a library to help manage mono repos. It wasn&#x27;t perfect, but it worked. So I thought I&#x27;d contribute. I spent a good deal of time replying to issues, fixing bugs, and working on new features.<p>This was at a time when the author was mostly absent. Without the amazing help of gigabo [2] and hzoo [3], the project would have grinded to a halt. As new users rushed in to use this relatively new tool, there were many new issues and feature requests.<p>When the author did make his presence known, he was not very helpful [4] [5]. These are just the examples that stood out to me as a contributor. Most people understand that 1 person can&#x27;t be expected to maintain a big project like this, especially when they are busy at Facebook bootcamp. That&#x27;s why it had 2 additional members to help. Unfortunately, as a result of [5] above, the author decided he no longer wanted [2]&#x27;s help and removed him from the project. He removed a huge contributor because he disagreed with him and failed to openly discuss the issue. Ironic. I stopped contributing immediately. As a result, Asini [6] was born.<p>The thing that really pisses me off about this post from the author is that he&#x27;s promoting open communication, sharing, helping others, etc... when it&#x27;s the complete opposite of my experience with him. Maybe he just had a bad day on those days, maybe it was something else. I don&#x27;t know him personally, I can only assume things based my interactions. Regardless, this was some extremely poor handling of an open source project.<p>It looks like he&#x27;s active on the project again, but it doesn&#x27;t look like much has changed. [7] [8] [9]<p>Mr. Kyle, if you&#x27;re reading this, I really hope you&#x27;ll follow your own advice. If I have misunderstood your actions in the past, I&#x27;m open to being wrong.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna</a>
[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;gigabo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;gigabo</a>
[3] <a href="https:&#x2F;&#x2F;github.com&#x2F;hzoo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;hzoo</a>
[4] <a href="https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;pull&#x2F;255#issuecomment-228954543" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;pull&#x2F;255#issuecomment-2289545...</a>
[5] <a href="https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;issues&#x2F;334#issuecomment-246393716" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;issues&#x2F;334#issuecomment-24639...</a>
[6] <a href="https:&#x2F;&#x2F;github.com&#x2F;asini&#x2F;asini" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;asini&#x2F;asini</a>
[7] <a href="https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;pull&#x2F;255#issuecomment-252332281" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;pull&#x2F;255#issuecomment-2523322...</a>
[8] <a href="https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;pull&#x2F;386#issuecomment-264072507" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;pull&#x2F;386#issuecomment-2640725...</a>
[9] <a href="https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;issues&#x2F;408" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lerna&#x2F;lerna&#x2F;issues&#x2F;408</a>