Codeberg/Contributing
Codeberg/Contributing
Fork 5
Code Issues 40 Pull requests 2 Releases Activity

make repo REUSE compliant #102

Merged
fnetX merged 1 commit from juliangmp/make-repo-reuse-compliant into main 2025-05-26 21:33:36 +02:00 AGit
Conversation 15 Commits 1 Files changed 5 +20
JulianGmp commented 2025-05-17 04:22:46 +02:00
Member
Copy link

this is very nitpicky, but I thought that it was kinda ironic since the guideline file that tells us we should be reuse compliant isn't compliant itself :p

this is very nitpicky, but I thought that it was kinda ironic since the guideline file that tells us we should be reuse compliant isn't compliant itself :p
JulianGmp added 1 commit 2025-05-17 04:22:46 +02:00
n0toose requested changes 2025-05-17 17:16:15 +02:00
Dismissed
n0toose left a comment
Member
Copy link

@mikolaj @a-j-wood @yoctozepto @pyfisch @caelandb @tranzystorekk Hi there, I am mentioning you all because this change adds a copyright header 2025 Codeberg e.V. to files that you have modified.

Do you consent to this change, or would you rather have your name included? Keep in mind that I have not checked whether there is any content still present from your pull requests. If there is no response, we can check whether there is still such content present (or a derivative of it) and include your name (with the authorship year) by default (if applicable). If there is a problem with that, please let me know.

@mikolaj @a-j-wood @yoctozepto @pyfisch @caelandb @tranzystorekk Hi there, I am mentioning you all because this change adds a copyright header `2025 Codeberg e.V.` to files that you have modified. Do you consent to this change, or would you rather have your name included? Keep in mind that I have not checked whether there is any content still present from your pull requests. If there is no response, we can check whether there is still such content present (or a derivative of it) and include your name (with the authorship year) by default (if applicable). If there is a problem with that, please let me know.
mikolaj commented 2025-05-17 17:18:12 +02:00
Member
Copy link

Do you consent to this change, or would you rather have your name included?

I consent to this change.

> Do you consent to this change, or would you rather have your name included? I consent to this change.
👍 1
n0toose commented 2025-05-17 17:18:21 +02:00
Member
Copy link

@JulianGmp The comment I left is a bit of a challenge in itself, I suggest that we wait for 2-3 weeks max. and then investigate what the best way to push REUSE compliance forward (if there is no response whatsoever or an explicit disagreement, so to say).

@JulianGmp The comment I left is a bit of a challenge in itself, I suggest that we wait for 2-3 weeks max. and then investigate what the best way to push REUSE compliance forward (if there is no response whatsoever or an explicit disagreement, so to say).
n0toose added the due date 2025-06-09 2025-05-17 17:21:22 +02:00
a-j-wood commented 2025-05-17 23:29:50 +02:00
Contributor
Copy link

Do you consent to this change, or would you rather have your name included?

I consent to this change

> Do you consent to this change, or would you rather have your name included? I consent to this change
👍 1
JulianGmp commented 2025-05-18 03:15:08 +02:00
Author
Member
Copy link

@n0toose wrote in #102 (comment):

@mikolaj @a-j-wood @yoctozepto @pyfisch @caelandb @tranzystorekk Hi there, I am mentioning you all because this change adds a copyright header 2025 Codeberg e.V. to files that you have modified.

Do you consent to this change, or would you rather have your name included? Keep in mind that I have not checked whether there is any content still present from your pull requests. If there is no response, we can check whether there is still such content present (or a derivative of it) and include your name (with the authorship year) by default (if applicable). If there is a problem with that, please let me know.

Apologies, I didn't consider that the individual contributors held the copyright for their changes and assumed Codeberg e.V. did, since it's part of the official documentaiton.

I think we could change to something generic like Copyright the XYZ Contributors, which should mean everyone keeps their copyright (I think? I'm no lawyer).

@JulianGmp The comment I left is a bit of a challenge in itself, I suggest that we wait for 2-3 weeks max. and then investigate what the best way to push REUSE compliance forward (if there is no response whatsoever or an explicit disagreement, so to say).

I honestly didn't think far enough to consider these implications. In the end this is just a small bit of documentation to guide people, I doubt people will want to reuse the actual files, but I made the PR just for the sake of completeness so here we are ^^'

@n0toose wrote in https://codeberg.org/Codeberg/Contributing/pulls/102#issuecomment-4621262: > @mikolaj @a-j-wood @yoctozepto @pyfisch @caelandb @tranzystorekk Hi there, I am mentioning you all because this change adds a copyright header `2025 Codeberg e.V.` to files that you have modified. > > Do you consent to this change, or would you rather have your name included? Keep in mind that I have not checked whether there is any content still present from your pull requests. If there is no response, we can check whether there is still such content present (or a derivative of it) and include your name (with the authorship year) by default (if applicable). If there is a problem with that, please let me know. Apologies, I didn't consider that the individual contributors held the copyright for their changes and assumed Codeberg e.V. did, since it's part of the official documentaiton. I think we could change to something generic like `Copyright the XYZ Contributors`, which should mean everyone keeps their copyright (I think? I'm no lawyer). > @JulianGmp The comment I left is a bit of a challenge in itself, I suggest that we wait for 2-3 weeks max. and then investigate what the best way to push REUSE compliance forward (if there is no response whatsoever or an explicit disagreement, so to say). I honestly didn't think far enough to consider these implications. In the end this is just a small bit of documentation to guide people, I doubt people will want to _reuse_ the actual files, but I made the PR just for the sake of completeness so here we are ^^'
n0toose commented 2025-05-18 13:42:45 +02:00
Member
Copy link

Apologies, I didn't consider that the individual contributors held the copyright for their changes and assumed Codeberg e.V. did, since it's part of the official documentation.

No worries, it's a change worth pursuing out of a matter of principle and the fact that I like getting things done 10000% correctly is on me. :P

> Apologies, I didn't consider that the individual contributors held the copyright for their changes and assumed Codeberg e.V. did, since it's part of the official documentation. No worries, it's a change worth pursuing out of a matter of principle and the fact that I like getting things done 10000% correctly is on me. :P
yoctozepto commented 2025-05-18 15:53:49 +02:00
Member
Copy link

I consent to this change.

I consent to this change.
👍 1
tranzystorekk commented 2025-05-18 17:56:26 +02:00
Contributor
Copy link

Do you consent to this change, or would you rather have your name included?

I consent to this change.

> Do you consent to this change, or would you rather have your name included? I consent to this change.
👍 1
caelandb commented 2025-05-20 11:28:41 +02:00
Contributor
Copy link

I consent to this change

I consent to this change
n0toose commented 2025-05-26 14:12:02 +02:00
Member
Copy link

Thanks for the responses, everyone. As an overview: I'm missing @pyfisch and @a-j-wood still.

Thanks for the responses, everyone. As an overview: I'm missing @pyfisch and @a-j-wood still.
pyfisch commented 2025-05-26 15:46:49 +02:00
Contributor
Copy link

I consent to this change.

I consent to this change.
a-j-wood commented 2025-05-26 20:30:21 +02:00
Contributor
Copy link

I consent to this change.

I consent to this change.
n0toose commented 2025-05-26 20:36:28 +02:00
Member
Copy link

Okay, I can't believe that this honestly worked. Thank you all very much for responding!

Okay, I can't believe that this honestly worked. Thank you all very much for responding!
👍 1
n0toose approved these changes 2025-05-26 20:38:15 +02:00
n0toose left a comment
Member
Copy link

This change has received approval from all contributors which are not affiliated with Codeberg e. V.

This change has received approval from all contributors which are not affiliated with Codeberg e. V.
fnetX was assigned by n0toose 2025-05-26 20:38:37 +02:00
n0toose commented 2025-05-26 20:40:46 +02:00
Member
Copy link

@fnetX The change is good to go and squash-mergeable. If you are OK with it (as a co-author), feel free to merge.

(I briefly considered assuming you would be before, but it didn't feel right for me to act on that assumption - hence why I didn't ask earlier.)

@fnetX The change is good to go and squash-mergeable. If you are OK with it (as a co-author), feel free to merge. (I briefly considered assuming you would be before, but it didn't feel right for me to act on that assumption - hence why I didn't ask earlier.)
fnetX merged commit 8d2f01880e into main 2025-05-26 21:33:36 +02:00
fnetX referenced this pull request from a commit 2025-05-26 21:33:36 +02:00
make repo REUSE compliant (#102)
Sign in to join this conversation.
Reviewers
No reviewers
n0toose
Labels
Clear labels   
Invalid
Off-Topic
This issue concerns a matter that is not relevant to this repository.

  
Invalid
Out Of Scope
This issue is beyond the scope of this repository.

  
Meta
Introduction

  
Needs
Contributors
This project is looking for occasional contributors

  
Needs
Leads
This project is looking for people to take the lead. You likely won't join an existing team but take some responsibility.

  
Needs
Maintainers
This needs maintainers (people taking responsibility) the most

  
Priority
High
High priority. Contribution very welcome.

  
Priority
Low
Low priority from Codeberg, contribution welcome nevertheless

  
Priority
Normal
Normal priority. Contribution welcome.

No labels
Invalid
Off-Topic
Invalid
Out Of Scope
Meta
Introduction
Needs
Contributors
Needs
Leads
Needs
Maintainers
Priority
High
Priority
Low
Priority
Normal
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
fnetX
8 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2025-06-10

Dependencies

No dependencies set.

Reference: Codeberg/Contributing#102
No description provided.
Delete branch "juliangmp/make-repo-reuse-compliant"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?