text
🥳 New license for datasets: Apache 2.0!
🥳 New license for datasets: Apache 2.0!
new_line
new_line
text
I have been struggling mentally for many months now with the OpenAI terms of use that indicate that their model outputs cannot be used to build "competing models". This leads to many questions:
I have been struggling mentally for many months now with the OpenAI terms of use that indicate that their model outputs cannot be used to build "competing models". This leads to many questions:
new_line
new_line
text
- what is the definition of competing? Is it the same as "commercial"?
- what is the definition of competing? Is it the same as "commercial"?
new_line
text
- since this is part of the terms of use between OpenAI and the API user, can a third party still use the generated dataset to build competing models?
- since this is part of the terms of use between OpenAI and the API user, can a third party still use the generated dataset to build competing models?
new_line
text
- are such restrictions even legal in the first place?
- are such restrictions even legal in the first place?
new_line
new_line
text
Trying to "follow the rules" as much as possible despite wanting to be as open as possible, I kept releasing my datasets under non-commercial licenses (which are too restrictive anyhow - nothing should prevent you from using the data in non-LM commercial settings), just like models trained on these datasets. This has put me at a competitive disadvantage compared to creators who do not follow the same approach and release their data/models on apache 2.0 despite the OpenAI "restrictions". Moreover, I fear (
Trying to "follow the rules" as much as possible despite wanting to be as open as possible, I kept releasing my datasets under non-commercial licenses (which are too restrictive anyhow - nothing should prevent you from using the data in non-LM commercial settings), just like models trained on these datasets. This has put me at a competitive disadvantage compared to creators who do not follow the same approach and release their data/models on apache 2.0 despite the OpenAI "restrictions". Moreover, I fear (
link
https://twitter.com/BramVanroy/status/1780220420316164246
https://twitter.com/BramVanroy/status/1780220420316164246
text
) that my approach blocks adaptation of my data/models for (commercial) applications/integrations.
) that my approach blocks adaptation of my data/models for (commercial) applications/integrations.
new_line
new_line
text
Thankfully 
Thankfully 
mention
@Rijgersberg
Rijgersberg
text
  noted that these OpenAI terms of use are NOT explicit in the Azure OpenAI API (
  noted that these OpenAI terms of use are NOT explicit in the Azure OpenAI API (
link
https://twitter.com/E_Rijgersberg/status/1780308971762450725
https://twitter.com/E_Rijgersberg/status/1780308971762450725
text
). Since my latest datasets were created via Azure, this comes as a relief. As far as I can tell after digging through Azure docs, this allows me to change all recent GPT4-generated datasets to apache 2.0! 🥳 
). Since my latest datasets were created via Azure, this comes as a relief. As far as I can tell after digging through Azure docs, this allows me to change all recent GPT4-generated datasets to apache 2.0! 🥳 
new_line
new_line
text
- 
- 
resource
https://huggingface.co/datasets/BramVanroy/ultrachat_200k_dutch
dataset
BramVanroy/ultrachat_200k_dutch
https://huggingface.co/datasets/BramVanroy/ultrachat_200k_dutch
new_line
text
- 
- 
resource
https://huggingface.co/datasets/BramVanroy/orca_dpo_pairs_dutch
dataset
BramVanroy/orca_dpo_pairs_dutch
https://huggingface.co/datasets/BramVanroy/orca_dpo_pairs_dutch
new_line
text
- 
- 
resource
https://huggingface.co/datasets/BramVanroy/ultra_feedback_dutch
dataset
BramVanroy/ultra_feedback_dutch
https://huggingface.co/datasets/BramVanroy/ultra_feedback_dutch
new_line
text
- 
- 
resource
https://huggingface.co/datasets/BramVanroy/ultra_feedback_dutch_cleaned
dataset
BramVanroy/ultra_feedback_dutch_cleaned
https://huggingface.co/datasets/BramVanroy/ultra_feedback_dutch_cleaned
new_line
text
- 
- 
resource
https://huggingface.co/datasets/BramVanroy/no_robots_dutch
dataset
BramVanroy/no_robots_dutch
https://huggingface.co/datasets/BramVanroy/no_robots_dutch
new_line
new_line
text
I will have to mull over what I'll do for the older GPT3.5 datasets. What do you think that I should do?
I will have to mull over what I'll do for the older GPT3.5 datasets. What do you think that I should do?
🥳 New license for datasets: Apache 2.0!

I have been struggling mentally for many months now with the OpenAI terms of use that indicate that their model outputs cannot be used to build "competing models". This leads to many questions:

- what is the definition of competing? Is it the same as "commercial"?
- since this is part of the terms of use between OpenAI and the API user, can a third party still use the generated dataset to build competing models?
- are such restrictions even legal in the first place?

Trying to "follow the rules" as much as possible despite wanting to be as open as possible, I kept releasing my datasets under non-commercial licenses (which are too restrictive anyhow - nothing should prevent you from using the data in non-LM commercial settings), just like models trained on these datasets. This has put me at a competitive disadvantage compared to creators who do not follow the same approach and release their data/models on apache 2.0 despite the OpenAI "restrictions". Moreover, I fear (https://twitter.com/BramVanroy/status/1780220420316164246) that my approach blocks adaptation of my data/models for (commercial) applications/integrations.

Thankfully @Rijgersberg  noted that these OpenAI terms of use are NOT explicit in the Azure OpenAI API (https://twitter.com/E_Rijgersberg/status/1780308971762450725). Since my latest datasets were created via Azure, this comes as a relief. As far as I can tell after digging through Azure docs, this allows me to change all recent GPT4-generated datasets to apache 2.0! 🥳 

- https://huggingface.co/datasets/BramVanroy/ultrachat_200k_dutch
- https://huggingface.co/datasets/BramVanroy/orca_dpo_pairs_dutch
- https://huggingface.co/datasets/BramVanroy/ultra_feedback_dutch
- https://huggingface.co/datasets/BramVanroy/ultra_feedback_dutch_cleaned
- https://huggingface.co/datasets/BramVanroy/no_robots_dutch

I will have to mull over what I'll do for the older GPT3.5 datasets. What do you think that I should do?
🔥
stefan-it JorgeDeC adamo1139 alielfilali01 martineden
🚀
Rijgersberg martineden
🤗
wvangils
https://cdn-avatars.huggingface.co/v1/production/uploads/625579238e2cfccdb434c5e1/WIZtyNNzeSMo3F5Xsr161.jpeg
Jorge De Corte
JorgeDeC
user
https://cdn-avatars.huggingface.co/v1/production/uploads/1594192845975-5e1e17b6fcf41d740b6996a8.jpeg
Bram Vanroy
BramVanroy
user
https://cdn-avatars.huggingface.co/v1/production/uploads/6319b164bc8f3b313f7a1db0/Hh0kuwsAnD2AOKdL6PpRs.png
Edwin Rijgersberg
Rijgersberg
user
https://cdn-avatars.huggingface.co/v1/production/uploads/62d1218684bfbee86b6ee521/BpXX_XUP80IfdGAvbs_VI.png
MD
markding
user