I really appreciate your sharing this—thank you very much.
We will update the white paper to include a reference to opensource.org/osd
May I ask follow up questions:
1-What term/ terms do you use to describe code that requires permission from the repository creator to gain access to that code to in a version control system?
2-What term/ terms do you use to describe code that does not requires permission from the repository creator to gain access to that code to in a version control system?
3- What term/ terms do you use to describe code that does not requires permission from the repository creator to gain access to that code to in a version control system, but does require paying for use?
We would describe #1 as “Private”, #2 as “Open Source,” and #3 as “Open Source- Commercial.” Full disclosure, our team has to explain these definitions to very non-technical audiences on occasion, so I’m sure there’s nuance missing in our summaries. Keen to hear your terminology.
Your questions are about the access to a version control system, rather than the code.
As I've already said, code becomes Open Source when an Open Source license is embedded in the code text. It retains that license as it travels. This idea, and its leverage of copyright laws predates and is independent of code versioning.
To paraphrase a little: your question is like asking whether a haiku, as a type of poem should have a different name depending on when it is written in pen or pencil. Which is that you are mistaking the tool for the content.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really appreciate your sharing this—thank you very much.
We will update the white paper to include a reference to opensource.org/osd
May I ask follow up questions:
1-What term/ terms do you use to describe code that requires permission from the repository creator to gain access to that code to in a version control system?
2-What term/ terms do you use to describe code that does not requires permission from the repository creator to gain access to that code to in a version control system?
3- What term/ terms do you use to describe code that does not requires permission from the repository creator to gain access to that code to in a version control system, but does require paying for use?
We would describe #1 as “Private”, #2 as “Open Source,” and #3 as “Open Source- Commercial.” Full disclosure, our team has to explain these definitions to very non-technical audiences on occasion, so I’m sure there’s nuance missing in our summaries. Keen to hear your terminology.
Grateful for your careful read.
Stefan
Your questions are about the access to a version control system, rather than the code.
As I've already said, code becomes Open Source when an Open Source license is embedded in the code text. It retains that license as it travels. This idea, and its leverage of copyright laws predates and is independent of code versioning.
To paraphrase a little: your question is like asking whether a haiku, as a type of poem should have a different name depending on when it is written in pen or pencil. Which is that you are mistaking the tool for the content.