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

Added SPDX license identifiers to .vue, .ts, and .py files #1081

Closed

Conversation

Mahendradoak
Copy link
Contributor

Contributor checklist


Description

This pull request adds SPDX license identifiers to all .vue, .ts, and .py files in the project as required by the issue description. The identifiers added are:

  • .vue files: <!-- SPDX-License-Identifier: AGPL-3.0-or-later -->
  • .ts files: // SPDX-License-Identifier: AGPL-3.0-or-later
  • .py files: # SPDX-License-Identifier: AGPL-3.0-or-later

These changes ensure that each file complies with the licensing requirements.

I verified the changes by reviewing each modified file to ensure the correct identifier was added and ran the necessary tests as described in the project's contributing guide to confirm that the project continues to function as expected.

Copy link

netlify bot commented Jan 12, 2025

Deploy Preview for activist-org ready!

Name Link
🔨 Latest commit 99a6242
🔍 Latest deploy log https://app.netlify.com/sites/activist-org/deploys/67841e5cf3afd400084e8dc1
😎 Deploy Preview https://deploy-preview-1081--activist-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

github-actions bot commented Jan 12, 2025

Thank you for the pull request!

The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

  • The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

  • The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

  • The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First PR Commit Check

  • The commit messages for the remote branch of a new contributor should be checked to make sure their email is set up correctly so that they receive credit for their contribution
    • The contributor's name and icon in remote commits should be the same as what appears in the PR
    • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local activist repo (can be set with git config --global user.email "GITHUB_EMAIL")

@andrewtavis
Copy link
Member

Thanks for the commit, @Mahendradoak! Would you be able to add these to all files? And for Python files, if there is a file level documentation string could you put the license notice at the top? So like this:

"""
# SPDX-License-Identifier: AGPL-3.0-or-later
<REST_OF_DOC_STRING>
"""

Let me know if you have any questions!

@andrewtavis andrewtavis self-requested a review January 12, 2025 20:20
@andrewtavis
Copy link
Member

Or never mind, I think it's fine to do the Python ones as you have, but let's always have them above :) So like this:

# SPDX-License-Identifier: AGPL-3.0-or-later
"""
<DOC_STRING>
"""

@Mahendradoak
Copy link
Contributor Author

do i change the position and commit again or should I let it stay the way it is?

@andrewtavis
Copy link
Member

It'd be great if you could change the position for the ones that are beneath the doc strings and add this notice to all files :)

@andrewtavis
Copy link
Member

Just checking: Are you planning on re-opening, @Mahendradoak?

@Mahendradoak
Copy link
Contributor Author

Mahendradoak commented Jan 12, 2025 via email

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

Successfully merging this pull request may close these issues.

2 participants