Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Use of the term "open source" to describe qwen when the training data is not open #1055

Closed
4 tasks done
phly95 opened this issue Nov 6, 2024 · 4 comments
Closed
4 tasks done
Labels

Comments

@phly95
Copy link

phly95 commented Nov 6, 2024

Model Series

Qwen2.5

What are the models used?

qwen 2.5

What is the scenario where the problem happened?

all

Is this a known issue?

  • I have followed the GitHub README.
  • I have checked the Qwen documentation and cannot find an answer there.
  • I have checked the documentation of the related framework and cannot find useful information.
  • I have searched the issues and there is not a similar one.

Information about environment

All

Log output

N/A

Description

Use of the term "open source" to describe qwen when the training data is not open is incorrect usage of the term. For something to be open source, it requires that all components required to "compile" the application are available. If you consider the trained model a "binary" then the training data is the "source code". If you do not have that data, it is not "open source", but rather "open weights". Please correct all documentation to use the correct term.

@jklj077
Copy link
Collaborator

jklj077 commented Nov 6, 2024

we mostly use the term open-weight. please open a PR for the ones you found.

@phly95
Copy link
Author

phly95 commented Nov 6, 2024

https://qwenlm.github.io/blog/qwen2.5/ uses the term for example.

@jklj077
Copy link
Collaborator

jklj077 commented Nov 7, 2024

different repo: https://github.com/QwenLM/qwenlm.github.io

Copy link

github-actions bot commented Dec 8, 2024

This issue has been automatically marked as inactive due to lack of recent activity. Should you believe it remains unresolved and warrants attention, kindly leave a comment on this thread.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants