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

Upstreaming of GNU tools patches. #73

Open
19 of 22 tasks
jdek opened this issue Oct 22, 2016 · 26 comments
Open
19 of 22 tasks

Upstreaming of GNU tools patches. #73

jdek opened this issue Oct 22, 2016 · 26 comments

Comments

@jdek
Copy link

jdek commented Oct 22, 2016

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:

  • Pixel

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.)
@ghost
Copy link

ghost commented Oct 22, 2016

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."

@himanshugoel2797
Copy link
Contributor

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.

@artart78
Copy link
Member

I release my contributions to the psptoolchain patches change into the public domain.

3 similar comments
@dogo
Copy link
Contributor

dogo commented Oct 22, 2016

I release my contributions to the psptoolchain patches change into the public domain.

@xantares
Copy link
Contributor

I release my contributions to the psptoolchain patches change into the public domain.

@FTPiano
Copy link
Contributor

FTPiano commented Oct 22, 2016

I release my contributions to the psptoolchain patches change into the public domain.

@0xcaff
Copy link
Contributor

0xcaff commented Oct 22, 2016

My changes are minor also so:

I release my contributions to the psptoolchain patches change into the public domain.

@take-cheeze
Copy link
Contributor

I release my contributions to the psptoolchain patches change into the public domain.

@davidgfnet
Copy link
Contributor

Just noticed I'm a duplicate (davidgfnet & David Guillen Fandos), sorry for
that!

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
important to preserve history in the world we live today.

I release any of my work there into the public domain.

2016-10-23 11:27 GMT+02:00 Takeshi Watanabe [email protected]:

I release my contributions to the psptoolchain patches change into the
public domain.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#73 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC_-e_o1M58wmVPa8yFelyZrHsnIbTbNks5q2yiFgaJpZM4Kd5nE
.

@davidgfnet
Copy link
Contributor

Hey, thanks for your efforts man. I really appreciate you doing this, it's
important to preserve history in the world we live today.

I release any of my work there into the public domain.

2016-10-23 11:27 GMT+02:00 Takeshi Watanabe [email protected]:

I release my contributions to the psptoolchain patches change into the
public domain.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#73 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC_-e_o1M58wmVPa8yFelyZrHsnIbTbNks5q2yiFgaJpZM4Kd5nE
.

@libcg
Copy link
Member

libcg commented Oct 28, 2016

Thanks for doing this.

I release my contributions to the psptoolchain patches change into the public domain.

@WinterMute
Copy link
Contributor

@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.

@John-K
Copy link
Member

John-K commented Oct 28, 2016

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.

@ghost
Copy link

ghost commented Dec 14, 2016

I release my contributions to the psptoolchain patches change into the public domain.

@liclac
Copy link
Contributor

liclac commented Dec 14, 2016

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.

@ooPo
Copy link
Member

ooPo commented Dec 16, 2016

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. :)

@lukaszdk
Copy link

lukaszdk commented Dec 17, 2016 via email

@marcusrbrown
Copy link
Member

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.

@SamRH
Copy link
Member

SamRH commented Feb 22, 2017

I release my contributions to the psptoolchain patches change into the public domain.

@jdek
Copy link
Author

jdek commented Mar 31, 2018

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

@mirh
Copy link

mirh commented Apr 16, 2020

So, is this going anywhere?

@davidgfnet
Copy link
Contributor

Yeah same question. Anything we can do? I'd love to see this upstreamed, really!

@jdek
Copy link
Author

jdek commented Apr 19, 2020

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 UNLICENSE file in, preserving it as a bit of unencumbered digital history. For what it's worth, everyone in the list so far has already put their work in the public domain so we are just missing a couple. This, to me, would be a good enough compromise.


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.

@jdek jdek mentioned this issue Apr 19, 2020
@davidgfnet
Copy link
Contributor

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).
About upstreaming: is it a licensing problem the one you see? I was afraid the problems might be related to other things (like projects rejecting these contributions).

@nicolasnoble
Copy link

Pixel here. I release my contributions to the psptoolchain patches change into the public domain.

@wally4000
Copy link
Contributor

wally4000 commented Oct 4, 2020

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?

jdek added a commit to jdek/psptoolchain that referenced this issue Feb 24, 2024
All contributors released work into the public domain.

Closes pspdev#73.

Signed-off-by: J. Dekker <[email protected]>
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

No branches or pull requests