# Afterthoughts around about Kernel code and custom operators complaints

**URL:** <https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558>\
**Category:** Request Feedback\
**Created:** [April 16, 2020, 8:40am UTC](https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558 "2020-04-16T08:40:44Z")\
**Posts on this page:** 1\
**Showing post:** 63

<div class="post-metadata">

**Author:** ![turboMaCk](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/turbomack/32/355_2.png) [@turboMaCk](https://discourse.elm-lang.org/u/turboMaCk)\
**Post date:** [April 22, 2020, 9:24am UTC](https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558/63 "2020-04-22T09:24:46Z")

</div>

Just one note. I don’t think any fork should include `elm` in a name. I’m kind of fan of interpreting this Clause in BSD3 quite strictly:

```auto
3. Neither the name of the <organization> nor the
   names of its contributors may be used to endorse or promote products
   derived from this software without specific prior written permission.

```

I think it protects original authors from being tight to stuff they don’t approve of, what ever it might be. I would suggest picking up some name of the tree for name of fork will it happen. That way it would be still related but less obviously. It can be `ash` or `oak` for instance. Also if you want to be super creative there seems to be thing called [Camperdownii](https://en.wikipedia.org/wiki/Ulmus_glabra_%27Camperdownii%27) (which would be arguably hard to type though).

Disclaimer: I personally not dissatisfied enough to switch to fork so take it as just personal opinion / suggestion.

---

_[View the full topic](https://discourse.elm-lang.org/t/afterthoughts-around-about-kernel-code-and-custom-operators-complaints/5558)._