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

Recommended license on pub publish page links to wrong version of the BSD license #10815

Closed
DartBot opened this issue May 23, 2013 · 4 comments
Closed

Comments

@DartBot
Copy link

DartBot commented May 23, 2013

This issue was originally filed by Robert...@dartvoid.com


What steps will reproduce the problem?

  1. Check out the licenses at:
       https://github.com/dart-lang/bleeding_edge/blob/master/LICENSE
       http://pub.dartlang.org/packages/args
       http://pub.dartlang.org/packages/oauth2
       
  2. Notice the BSD 3-Clause License
       http://opensource.org/licenses/BSD-3-Clause
  3. Go to pub page about publishing:
       http://pub.dartlang.org/doc/pub-lish.html
  4. Notice how it recommends the BSD 2-Clause License by linking to it:
       http://opensource.org/licenses/BSD-2-Clause

Not sure if the project have changes from 2-Clause to 3-Clause BSD license, but it seems like the link on the pub page should to to the 3-Clause license.

If the project in fact wants to recommend the 2-Clause license over the 3-Clause license, the text needs to be changed anyway to reflect that since it now says, indirectly, that the Dart project uses the 2-Clause license.

@sethladd
Copy link
Contributor

Added Area-Pub, Triaged labels.

@munificent
Copy link
Member

Removed Area-Pub label.
Added Area-PubSite label.

@nicolasgarnier
Copy link
Contributor

This issue has been moved to Github as part of a migration. Please use the Issue on Github going forward: https://github.com/dart-lang/pub-dartlang/issues


Added MovedToGithub label.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

This issue has been moved to dart-archive/pub-dartlang#327.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants