# Open Source vs. open source vs. open-source vs. OpenSource

**URL:** <https://forum.ospo-alliance.org/t/open-source-vs-open-source-vs-open-source-vs-opensource/64>\
**Category:** Good Governance Initiative\
**Tags:** ggi\
**Created:** [March 4, 2024, 4:52pm UTC](https://forum.ospo-alliance.org/t/open-source-vs-open-source-vs-open-source-vs-opensource/64 "2024-03-04T16:52:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nico.toussaint](https://forum.ospo-alliance.org/user_avatar/forum.ospo-alliance.org/nico.toussaint/32/32_2.png) [@nico.toussaint](https://forum.ospo-alliance.org/u/nico.toussaint)\
**Post date:** [March 4, 2024, 4:52pm UTC](https://forum.ospo-alliance.org/t/open-source-vs-open-source-vs-open-source-vs-opensource/64/1 "2024-03-04T16:52:10Z")

</div>

A [new issue on GGI gitlab](https://gitlab.ow2.org/ggi/ggi/-/issues/174) was created to revisit how to write “open source”.

To share my point of view straight away:  
I was in favour of simplicity with “open source”, arguing that open source became so common and popular, the advocacy for capitalised writing (see [Bruce Perens article](https://perens.com/2017/09/26/on-usage-of-the-phrase-open-source/)) was thankfully outdated. I like things smooth and simple and prefer lower case writing (still a C developer in heart I guess)

However, some interesting arguments were raised (@Silona): search engine indexing (which is why: InnerSource), and the need to identify more closely to the OSI [Open Source Definition](https://opensource.org/osd) to help distinguish Open Source licences from new trendy not-Open Source licences such as [SSPL](https://www.mongodb.com/licensing/server-side-public-license) or [BSL](https://mariadb.com/bsl11/)

@flzara also mentioned in the issue [that article](https://dirkriehle.com/2022/10/29/open-source-and-the-hyphen/) on the use of open-source.

What’s your views ?

---

<div class="post-metadata">

**Author:** ![slejeune](https://forum.ospo-alliance.org/user_avatar/forum.ospo-alliance.org/slejeune/32/16_2.png) [@slejeune](https://forum.ospo-alliance.org/u/slejeune)\
**Post date:** [March 5, 2024, 3:18pm UTC](https://forum.ospo-alliance.org/t/open-source-vs-open-source-vs-open-source-vs-opensource/64/2 "2024-03-05T15:18:51Z")

</div>

Hi there, as long as we are all using the same one in our content I am fine 🙂

Usually in my day to day I am using Open Source and Inner Source but I can live with Camel case, SnowCase, HyphenCase, \*.\*Case 😉

cheers

---

<div class="post-metadata">

**Author:** ![pierre-yves.gibello](https://forum.ospo-alliance.org/user_avatar/forum.ospo-alliance.org/pierre-yves.gibello/32/29_2.png) [@pierre-yves.gibello](https://forum.ospo-alliance.org/u/pierre-yves.gibello)\
**Post date:** [March 11, 2024, 2:54pm UTC](https://forum.ospo-alliance.org/t/open-source-vs-open-source-vs-open-source-vs-opensource/64/3 "2024-03-11T14:54:20Z")

</div>

In the 1st version of the Handbook, we decided to use “open source” - then I remember having fixed a lot of other variants, most of them being “open-source”.  
Note I don’t care much about uniformity, and even didn’t notice any issue using both: simply, it was a community choice.

---

<div class="post-metadata">

**Author:** ![flzara](https://forum.ospo-alliance.org/user_avatar/forum.ospo-alliance.org/flzara/32/6_2.png) [@flzara](https://forum.ospo-alliance.org/u/flzara)\
**Post date:** [March 12, 2024, 10:27am UTC](https://forum.ospo-alliance.org/t/open-source-vs-open-source-vs-open-source-vs-opensource/64/4 "2024-03-12T10:27:01Z")

</div>

> [@nico.toussaint](#):
>
> @flzara also mentioned in the issue [that article](https://dirkriehle.com/2022/10/29/open-source-and-the-hyphen/) on the use of open-source.

If I have a strong opinion on having no hyphen (see [the article linked by @nico.toussaint](https://dirkriehle.com/2022/10/29/open-source-and-the-hyphen/)), I have a small preference for caps in “Open Source”, but I can happily live without the caps as long as it is consistent.
