creativecommons / .github Goto Github PK

See:
https://docs.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
https://github.com/sponsors/creativecommons/

⚠️ NOTE

This issue is [Meta] and contains instructions for engaging with repositories. Please be sure to appropriately separate comments and other interactions between this [Meta] issue and repository issues (almost always the latter is more appropriate).

This issue is labeled 🏁 status: ready for work so people can find it and NOT because any work on this [Meta] issue itself is expected

Problem

Since we established our norms (GitHub Repo Guidelines — Creative Commons Open Source), GitHub has expanded the files that are supported as organizational defaults (Creating a default community health file - GitHub Docs).

Many of our repositories have the following files that duplicate the organizational defaults:

• CODE_OF_CONDUCT.md
• CONTRIBUTING.md

Description

1. Identify repositories that need work: Code search results
2. For each repository:
   1. Verify identical files via checksum
   2. Create issue in repository
   3. Create PR for repository
      • Remove duplicate files
      • Ensure the organization defaults are mentioned in the README.md so they are visible in default repository view (the organization default files are displayed in the auxiliary column of issues and pull requests)
        • For an example, see the README.md in creativecommons/index-dev-env

Additional context

• creativecommons/.github: Default templates and guidelines for Creative Commons GitHub repositories.
• GitHub Repo Guidelines — Creative Commons Open Source
• Creating a default community health file - GitHub Docs

Problem

Python Style Guide should be supported by code, where possible, so that computers are offloading as much work as possible.

Description

Add pre-commit hooks and GitHub Action workflows to support Python Style Guide

🚧 Currently blocked pending publication of Python Style Guide

Alternatives

Additional context

Implementation

• I would be interested in implementing this feature.

Problem Description

Problem described in creativecommons/ccos-scripts#17

Solution Description

Add the awaiting triage label to default issue template.

I saw an interesting feature on another repository that allows for displaying custom links on the issue creation page by creating a ISSUE_TEMPLATE/config.yaml file like so:

blank_issues_enabled: true
contact_links:
  - name: GitHub Community Support
    url: https://github.community/
    about: Please ask and answer questions here.
  - name: GitHub Security Bug Bounty
    url: https://bounty.github.com/
    about: Please report security vulnerabilities here.

A single contact_link renders like this:

Could be a nice way to direct users to wikis, community resources, or any other more specific channels for their issues.

Description

Update the Pull Request template (.github/PULL_REQUEST_TEMPLATE.md) to support main as a default branch name.

For background/context, see [Meta] Support "main" as a default branch name · Issue #1125 · creativecommons/creativecommons.org.

Reproduction

Checklist currently includes:

- [ ] My pull request targets the `master` branch of the repository.

Expectation

Checklist should include something like:

- [ ] My pull request targets the *default* branch of the repository (`main` or `master`).

Description

Many repositories have outdated versions of CODE_OF_CONDUCT.md and CONTRIBUTING.md

Reproduction

• Search · org:creativecommons creativecommons.github.io/community/
• Search · org:creativecommons master/content/community

Expectation

• Copied files should be kept up-to-date

Additional context

• GitHub Repo Guidelines — Creative Commons Open Source

Description

The Developer Certificate of Origin requires pull requests to be submitted under an “open source license”. At least one of Creative Commons’s repos is available under CC0. CC0 is a public domain dedication, not a license. Even if it was, it's not clear whether or not it would be an open source one since CC0 tries to waive copyright. See:

• https://opensource.org/faq#public-domain
• https://opensource.org/faq#cc-zero

Reproduction

1. Try submitting a pull request to the cc-licenses-data repo.
2. Carefully read through the Developer Certificate of Origin at the bottom of the PR template.

Expectation

I would expect that part (a), (b) or (c) would have me certify that my contribution is dedicated to the public domain using CC0 because that repo is dedicated to the public domain under CC0. I would also expect part (d) to have me certify “that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or ” CC0.

Additional context

I originally submitted a fix for this problem in creativecommons/cc-legal-tools-data#47, but I was told that it would be better to have the issue fixed here. The DCO itself doesn’t allow modifications, so my proposed solution was to add the following sentence above the DCO:

For the purposes of this DCO, the CC0 1.0 Universal (CC0 1.0) Public Domain Dedication counts as being an "open source license."

Resolution

• I would be interested in resolving this bug.