Skip to content

Conversation

@ooPo
Copy link
Member

@ooPo ooPo commented Mar 29, 2019

No description provided.

@ooPo ooPo mentioned this pull request Mar 29, 2019
@top-sekret
Copy link
Contributor

When is this getting merged? Or should I merge it into #102?

@ooPo
Copy link
Member Author

ooPo commented Apr 11, 2019

It's free to merge whenever, and however you want to do it. :)
I let it sit in case people wanted to talk about it first.

@top-sekret
Copy link
Contributor

At least according to the Free Software Foundation, insignificant contributions (they say <10 lines) do not need any disclaimer. Thus, the only people to ask are large contributors. Also, this license would not cover psp-sdk, so this only concerns the scripts and patch sets.

@jdek
Copy link

jdek commented Apr 19, 2020

@ooPo I think this should be an UNLICENSE file rather, following on from the discussion at #73 we have most of this in the public domain now.

@marcusrbrown
Copy link
Member

I think any public domain disclaimer should suffice. Public domain means no license, afaik.

@sharkwouter
Copy link
Member

Let me add to this that I approve of my changes in this repo being relicensed to this bsd license.

@sharkwouter
Copy link
Member

Public domain also requires a license, especially since public domain does not exist in some countries. That's why the Unlicense has a clause saying the MIT license applies if public domain is not possible.

This change requires explicit approval from all contributors who made more than very minor changes, though.

@marcusrbrown
Copy link
Member

Public domain also requires a license, especially since public domain does not exist in some countries. That's why the Unlicense has a clause saying the MIT license applies if public domain is not possible.

This change requires explicit approval from all contributors who made more than very minor changes, though.

Got it. That process was completed, I'll defer to @ooPo for the PR.

@jdek
Copy link

jdek commented Jan 14, 2022

I don't think anything is going to come from deferring it further, someone with write access should just push it with UNLICENSE or BSD 2-clause as the PR currently is but with a public domain disclaimer as suggested.

@diamant3
Copy link
Member

Maybe this can help to decide what license is needed with choosealicense

@sharkwouter
Copy link
Member

sharkwouter commented Nov 25, 2025

Lets try this one more time. These are all the people that have made significant contributions to this repo:

Please confirm if you're okay with this if you're on this list, then I'll tick you off. If we get everyone to agree we can merge this. I've already ticked off the people who have said they are okay with this. I don't know if we'll ever get everyone here, though. I can go through which contributions are still here and increase our chances, since this repo was stripped down a lot.

@csnover
Copy link
Contributor

csnover commented Nov 25, 2025

Hi! Thanks for approaching relicensing the right way by checking with prior contributors. However, you may want to double-check whatever you used to generate that list of significant contributors since the only code contribution I can find myself ever making in this org is https://github.com/pspdev/psptoolchain/pull/86/files. Notwithstanding, I don’t care which open source license you use for whatever I did contribute. BSD-2-clause is fine. Thanks!

@fjtrujy
Copy link
Member

fjtrujy commented Nov 25, 2025

I'm fine with whatever you want to do!
Cheers!

@caiomadeira
Copy link
Contributor

it's ok for me

@sharkwouter
Copy link
Member

@csnover I just looked at line count for now, but I will look into what was committed if we have some people who don't reply. In many cases the code will no longer be in this repo.

@CheezeCake
Copy link
Contributor

I'm ok with this 👍

@xantares
Copy link
Contributor

ok too

@dogo
Copy link
Contributor

dogo commented Nov 25, 2025

It's ok for me.

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.