-
Notifications
You must be signed in to change notification settings - Fork 123
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
Upstreaming of GNU tools patches. #73
Comments
My changes are pretty minor and I am not against licensing them in any way. I explicitly allow my changes to be released into public domain. "I release my contributions to the psptoolchain patches change into the public domain." |
I agree. My changes are also extremely minor and am not against releasing my changes to the public domain. I release my contributions to the psptoolchain patches change into the public domain. |
I release my contributions to the psptoolchain patches change into the public domain. |
3 similar comments
I release my contributions to the psptoolchain patches change into the public domain. |
I release my contributions to the psptoolchain patches change into the public domain. |
I release my contributions to the psptoolchain patches change into the public domain. |
My changes are minor also so: I release my contributions to the psptoolchain patches change into the public domain. |
I release my contributions to the psptoolchain patches change into the public domain. |
Just noticed I'm a duplicate (davidgfnet & David Guillen Fandos), sorry for 2016-10-24 9:48 GMT+02:00 David Guillen [email protected]:
|
Hey, thanks for your efforts man. I really appreciate you doing this, it's I release any of my work there into the public domain. 2016-10-23 11:27 GMT+02:00 Takeshi Watanabe [email protected]:
|
Thanks for doing this. I release my contributions to the psptoolchain patches change into the public domain. |
@WinteMute & Dave Murphy are both me & I have an FSF copyright assignment for binutils, gcc & newlib on file. For any other packages I release my contributions to the psptoolchain patches into the public domain. |
If any of the VFPU stuff I did is still in there, or other code: |
I release my contributions to the psptoolchain patches change into the public domain. |
I release my contributions to the psptoolchain patches change into the public domain. I'm # 1 on the "other git contributors" list, but I'd prefer if you'd use my username instead. |
I release my contributions to the psptoolchain patches change into the public domain. Good luck, it'll be awesome if you can pull this off. :) |
I release my contributions to the psptoolchain patches change into the public domain.Den 16. dec. 2016 19.40 skrev Josh de Kock <[email protected]>:I'd like to attempt to upstream the patches to preserve a bit of digital history, and to ensure that PSP support in the GNU toolchain is always up-to-date (I will take up maintainership of the PSP specifics in the GNU toolchain).
I see there were some efforts to upstream the psptoolchain patches, but they hit a roadblock because of no one trying to get a assignment to copyright FSF or public domain.
In order for the patches to be upstreamed there are some legal prerequisites. Please don't hesitate to ask if you have any queries.
Would you be willing to assign the copyright to the Free Software Foundation or sign a copyright disclaimer to put this change in the public domain, so that it could be integrated into the patches' respective package? (This means if you contributed to the GCC patch then you release your contributions into the public domain or assign copyright to the FSF, same for the binutils patch etc).
Below is a list of the contributors I have found who would need to agree to the terms in order to make this a reality.
GitHub Contributors:
@Bracket- @elsonLee @SopaXorzTaker @WinterMute @himanshugoel2797 @davidgfnet @dogo @FTPiano @xantares @n00neimp0rtant @caffinatedmonkey @SamRH @artart78 @uppfinnarn @take-cheeze @libcg @John-K @ooPo @igetgames @lukaszdk
Other git contributors: (hopefully no duplicates)
Scott Marnik elson nem
Original ps2dev contributors:
Mr Brown Pixel Lukasz
Reply with either:
I assign copyright to the Free Software Foundation of all my contributions to the psptoolchain patches.
I release my contributions to the psptoolchain patches change into the public domain.
No, I don't want this. (With a reason, preferably.)
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
|
I release my contributions to the psptoolchain patches change into the public domain. I am also listed under 'Original ps2dev contributors' as 'Mr Brown' (I used my abbreviated full name, M. R. Brown in my copyright notices, and went by the handle 'mrbrown'), so this release also covers that pseudonym. |
I release my contributions to the psptoolchain patches change into the public domain. |
I have emailed the last two contributors with actual contact information, @n00neimp0rtant and @elsonLee. I will have a look at the git history to see how considerable the contribution by the remaining unknown persons. It might be good enough as is |
So, is this going anywhere? |
Yeah same question. Anything we can do? I'd love to see this upstreamed, really! |
We are still missing some contributors releasing their into the public domain/copyright assignment, but I looked into it further and it seems like we might really struggle to upstream it specifically. If you can help contact these last people that would be the final things which would need to be done. I have tried to in the past without success. Regardless, I think the goal should switch here to just getting everything public domain and then slapping an Edit: Following on from this we could say 'look some of these contributions are trivial' such as @elsonLee's f8fc9c6 and forgo requiring an explicit approval to relicense. Mozilla did something similar when they relicensed one of their libraries. |
Looking at some of the contribs I'd call some trivial, perhaps not even worth discussing. I mean adding 5 lines into a few thousand line soup can't be realistictly claimable. Particularly since most of the contribs are not really source (but scripts, yeah well it's source but you know what i mean). |
Pixel here. I release my contributions to the psptoolchain patches change into the public domain. |
It looks as if some of these non-responding contributions are directly related to the toolchain script itself rather than part of the upstreaming, is it possible that we can ignore these contributions as they're not directly related to patches for gcc / binutils? |
All contributors released work into the public domain. Closes pspdev#73. Signed-off-by: J. Dekker <[email protected]>
I'd like to attempt to upstream the patches to preserve a bit of digital history, and to ensure that PSP support in the GNU toolchain is always up-to-date (I will take up maintainership of the PSP specifics in the GNU toolchain).
I see there were some efforts to upstream the psptoolchain patches, but they hit a roadblock because of no one trying to get a assignment to copyright FSF or public domain.
In order for the patches to be upstreamed there are some legal prerequisites. Please don't hesitate to ask if you have any queries.
Would you be willing to assign the copyright to the Free Software Foundation or sign a copyright disclaimer to put this change in the public domain, so that it could be integrated into the patches' respective package? (This means if you contributed to the GCC patch then you release your contributions into the public domain or assign copyright to the FSF, same for the binutils patch etc).
Below is a list of the contributors I have found who would need to agree to the terms in order to make this a reality.
GitHub Contributors:
Original ps2dev contributors:
Reply with either:
The text was updated successfully, but these errors were encountered: