# Beman Standard drafted

**URL:** <https://discourse.bemanproject.org/t/beman-standard-drafted/118>\
**Category:** Beman Website and Docs\
**Created:** [May 22, 2024, 6:24pm UTC](https://discourse.bemanproject.org/t/beman-standard-drafted/118 "2024-05-22T18:24:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dsankel](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/dsankel/32/5_2.png) [@dsankel](https://discourse.bemanproject.org/u/dsankel)\
**Post date:** [May 22, 2024, 6:24pm UTC](https://discourse.bemanproject.org/t/beman-standard-drafted/118/1 "2024-05-22T18:24:46Z")

</div>

I created a draft for the Beman standard which provides requirements and recommendations for Beman projects ([PR](https://github.com/beman-project/beman/pull/18), [Rendered Version](https://github.com/beman-project/beman/blob/2406f914616a82280ec0bdab58b79ea327486e2a/docs/beman-standard.md)). I’m looking for any/all feedback on this initial version.

The draft’s recommended license is Apache-2.0 WITH LLVM-exception. This is a popular license (which eases adoption within organizations) and addresses patent concerns where the others do not.

Some recommendations differ from what’s in the example repository (e.g. LICENSE vs. LICENSE.txt). Anyone interested in creating a PR that puts the example repository in conformance?

---

<div class="post-metadata">

**Author:** ![bretbrownjr](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/bretbrownjr/32/43_2.png) [@bretbrownjr](https://discourse.bemanproject.org/u/bretbrownjr)\
**Post date:** [May 23, 2024, 1:18pm UTC](https://discourse.bemanproject.org/t/beman-standard-drafted/118/2 "2024-05-23T13:18:35Z")

</div>

Dumb question for my benefit because I like knowing everything about project structure guidelines.

What’s better about a LICENSE file compared to a LICENSE.txt file? Are we watching our ASCII budget?

EDIT: For what it’s worth, from what I can tell, being friendly to relevant license scanning tech is the biggest requirement from what I can tell. Making sure the license shows up on GitHub UX to match our expectations is probably a good enough goal along those lines, at least for now.

---

<div class="post-metadata">

**Author:** ![dsankel](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/dsankel/32/5_2.png) [@dsankel](https://discourse.bemanproject.org/u/dsankel)\
**Post date:** [May 23, 2024, 5:30pm UTC](https://discourse.bemanproject.org/t/beman-standard-drafted/118/3 "2024-05-23T17:30:24Z")

</div>

> [@bretbrownjr](#):
>
> Dumb question…

No such thing…

> [@](#):
>
> What’s better about a LICENSE file compared to a LICENSE.txt file?

A quick look into existing repositories showed LICENSE to be much more prevalent than LICENSE.txt. Additionally, creating a new repository using the GitHub interface creates a LICENSE file.

---

<div class="post-metadata">

**Author:** ![Jeff-Garland](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/jeff-garland/32/23_2.png) [@Jeff-Garland](https://discourse.bemanproject.org/u/Jeff-Garland)\
**Post date:** [May 27, 2024, 5:24pm UTC](https://discourse.bemanproject.org/t/beman-standard-drafted/118/4 "2024-05-27T17:24:22Z")

</div>

I’ve put comments in the PR.

---

<div class="post-metadata">

**Author:** ![neatudarius](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/neatudarius/32/70_2.png) [@neatudarius](https://discourse.bemanproject.org/u/neatudarius)\
**Post date:** [May 30, 2024, 2:56pm UTC](https://discourse.bemanproject.org/t/beman-standard-drafted/118/5 "2024-05-30T14:56:22Z")

</div>

2 minor comments / suggestions from my side. Otherwise, LGTM.

---

<div class="post-metadata">

**Author:** ![neatudarius](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/neatudarius/32/70_2.png) [@neatudarius](https://discourse.bemanproject.org/u/neatudarius)\
**Post date:** [July 23, 2025, 11:46pm UTC](https://discourse.bemanproject.org/t/beman-standard-drafted/118/6 "2025-07-23T23:46:01Z")

</div>