Skip to content

Use BSD0 license for code in docs #84064

Description

@toddrjen
mannequin
BPO 39883
Nosy @gvanrossum, @terryjreedy, @ned-deily, @bbayles, @miss-islington, @toddrjen
PRs
  • bpo-39883: Use BSD0 license for code in docs #17635
  • [3.9] bpo-39883: Use BSD0 license for code in docs (GH-17635) #22073
  • [3.8] bpo-39883: Use BSD0 license for code in docs (GH-17635) #22074
  • bpo-39883: Update macOS installer copy of LICENSE. #22235
  • [3.9] bpo-39883: Update macOS installer copy of LICENSE. (GH-22235) #22236
  • [3.8] bpo-39883: Update macOS installer copy of LICENSE. (GH-22235) #22237
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2020-09-14.17:58:40.131>
    created_at = <Date 2020-03-07.03:50:57.242>
    labels = ['type-feature', '3.8', '3.9', '3.10', 'docs']
    title = 'Use BSD0 license for code in docs'
    updated_at = <Date 2020-09-14.17:58:40.130>
    user = 'https://github.com/toddrjen'

    bugs.python.org fields:

    activity = <Date 2020-09-14.17:58:40.130>
    actor = 'gvanrossum'
    assignee = 'docs@python'
    closed = True
    closed_date = <Date 2020-09-14.17:58:40.131>
    closer = 'gvanrossum'
    components = ['Documentation']
    creation = <Date 2020-03-07.03:50:57.242>
    creator = 'toddrjen'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 39883
    keywords = ['patch']
    message_count = 14.0
    messages = ['363573', '364139', '364276', '364286', '376276', '376287', '376305', '376306', '376307', '376423', '376865', '376866', '376867', '376890']
    nosy_count = 7.0
    nosy_names = ['gvanrossum', 'terry.reedy', 'ned.deily', 'docs@python', 'bbayles', 'miss-islington', 'toddrjen']
    pr_nums = ['17635', '22073', '22074', '22235', '22236', '22237']
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue39883'
    versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

    Activity

    1. toddrjen commented on Mar 7, 2020

      toddrjenmannequin
      MannequinAuthor

      Currently using code examples and recipes from the documentation is complicated by the fact that they are all under the Python 2.0 license. Putting them under a more permissive license, particular the BSD0 license, would make them much easier to use in other projects.

    2. added
      docsDocumentation in the Doc dir
      type-featureA feature request or enhancement
      on Mar 7, 2020
    3. added
      docsDocumentation in the Doc dir
      type-featureA feature request or enhancement
      on Mar 7, 2020
    4. terryjreedy commented on Mar 14, 2020

      @terryjreedy
      Member

      What is the complication? The Python license is already rather permissive. Anyway, there is a name@mail.python.org address for trademark issues, listed on the site, and it might be appropriate for license legal questions also. Or this might be a question for discuss.python.org.

    5. toddrjen commented on Mar 16, 2020

      toddrjenmannequin
      MannequinAuthor

      Hi Terry,

      Please take a look at the linked PR. This was already discussed on the python-ideas mailing list and Guido agreed this is a good idea. It is currently waiting on a PSF board decision. Guido requested I create a blurb, and that required a corresponding issue number, so I created this issue.

      But to answer your question, the problem is incorporating code into an existing project. The whole point of examples and recipes is that they be used in other projects. But keeping them under the Python 2.0 license makes this hard, since it requires all the documentation keep that same license. So you can't use, say, an itertools recipe without keeping a separate license for that code, and some way to identify which code falls under that license.

    6. terryjreedy commented on Mar 16, 2020

      @terryjreedy
      Member

      OK. I looked at the PR. Normally, issue comes first, with justification and approval status.

    7. gvanrossum commented on Sep 3, 2020

      @gvanrossum
      Member

      FWIW the PSF board approved the change.

    8. gvanrossum commented on Sep 3, 2020

      @gvanrossum
      Member

      New changeset e223d06 by Todd in branch 'master':
      bpo-39883: Use BSD0 license for code in docs (GH-17635)
      e223d06

    9. gvanrossum commented on Sep 3, 2020

      @gvanrossum
      Member

      New changeset a5d0232 by Miss Islington (bot) in branch '3.9':
      bpo-39883: Use BSD0 license for code in docs (GH-17635) (GH-22073)
      a5d0232

    10. gvanrossum commented on Sep 3, 2020

      @gvanrossum
      Member

      New changeset 9fef7c5 by Miss Islington (bot) in branch '3.8':
      bpo-39883: Use BSD0 license for code in docs (GH-17635) (GH-22074)
      9fef7c5

    11. gvanrossum commented on Sep 3, 2020

      @gvanrossum
      Member

      Todd, you have a PR for the pydotorg repo as well, right? Can you link it here?

    12. toddrjen commented on Sep 5, 2020

      toddrjenmannequin
      MannequinAuthor

      The pull request is

      python/python-docs-theme#36

      It doesn't seem to went let me add it to linked pull requests.

    13. ned-deily commented on Sep 14, 2020

      @ned-deily
      Member

      New changeset 7dbbea7 by Ned Deily in branch 'master':
      bpo-39883: Update macOS installer copy of LICENSE. (GH-22235)
      7dbbea7

    14. miss-islington commented on Sep 14, 2020

      @miss-islington
      Contributor

      New changeset 3c618d0 by Miss Islington (bot) in branch '3.8':
      bpo-39883: Update macOS installer copy of LICENSE. (GH-22235)
      3c618d0

    15. ned-deily commented on Sep 14, 2020

      @ned-deily
      Member

      New changeset bf7d4d0 by Miss Islington (bot) in branch '3.9':
      bpo-39883: Update macOS installer copy of LICENSE. (GH-22235) (GH-22236)
      bf7d4d0

    16. gvanrossum commented on Sep 14, 2020

      @gvanrossum
      Member

      This looks fully resolved. Thanks again Todd!

    17. transferred this issue fromon Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      3.10 (EOL)end of life3.8 (EOL)end of life3.9 (EOL)end of lifedocsDocumentation in the Doc dirtype-featureA feature request or enhancement

      Projects

      No projects

        Milestone

        No milestone

        Relationships

        None yet

        Development

        No branches or pull requests

        Issue actions