You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a disclaimer of Graion Dilach, aka Gyula Zimmermann.
I am hereby granting the agreement of relicensing all my commits made within the repositories contained in https://github.com/Ares-Developers to the WTFPL (and every compatible license, which includes the public domain in areas where WTFPL is not acknowledged) or any other license compatible with Phobos, depending on your local rules or jurisdiction. In the scenarios/areas where there isn't a Phobos-compatible relicensing public domain license available, I am willing to relicense the above contributions (direct or indirect) to the license currently employed by this project.
This is a non-rectactable, legally binding statement, granted in a public ticket for transparency and reference material.
Thank you.
Phobos Version
N/A
Conditions to reproduce
N/A
INI code
N/A
Steps to reproduce
N/A
Expected behaviour
N/A
Actual behaviour
N/A
Additional context
N/A
Checklist
The issue happens on the latest official version of Phobos and wasn't fixed yet.
I agree to elaborate the details if requested and provide thorough testing if the bugfix is implemented.
I added a very descriptive title to this issue.
I used the GitHub search and read the issue list to find a similar issue and didn't find it.
I have attached as much information as possible (screenshots, gifs, videos, debug and exception logs, etc).
As one of the project founders I want to express my (and our collectively) gratitude for this decision, especially considering the circumstances under which the project was born and the fact that currently Phobos de-facto is a successor of Ares.
It's absolutely not a problem, but we can convert it (or just repost it there) to a discussion (and remove the unused fields, the edit history will show it anyways) if you want.
Honestly, I don't trust GH discussions for this. They've already changed formatting twice, despite being a lot younger feature. Providing the statement in a ticket sounds more futureproof to me.
Ares was never open-source. The 4-clause BSD license it uses isn't an open-source license because it includes the advertising claim. Additionally, all contributors need to agree to a possible relicensing. I've made this statement because I've retired from the C&C community, there aren't many people I still keep contact with from it and I wanted to prevent any opportunity incase such a relicensing option ends up blocked on me.
This statement allows me to enjoy my time in a community which welcomes and heavily appreciates my contributions to it while also allows any Phobos-affiliate to mediate with the other Ares developers in my name and/or consent. It's a blanket statement, sure, but these are the blanket statements required for such an option.
Activity
Metadorius commentedon Jun 17, 2023
As one of the project founders I want to express my (and our collectively) gratitude for this decision, especially considering the circumstances under which the project was born and the fact that currently Phobos de-facto is a successor of Ares.
Thank you!
GraionDilach commentedon Jun 18, 2023
Yeah, sorry for abusing the bugtracker for this, but I wanted to have a written statement publicly available somewhere.
Metadorius commentedon Jun 18, 2023
It's absolutely not a problem, but we can convert it (or just repost it there) to a discussion (and remove the unused fields, the edit history will show it anyways) if you want.
GraionDilach commentedon Jun 18, 2023
Honestly, I don't trust GH discussions for this. They've already changed formatting twice, despite being a lot younger feature. Providing the statement in a ticket sounds more futureproof to me.
GraionDilach commentedon Aug 25, 2023
Ares was never open-source. The 4-clause BSD license it uses isn't an open-source license because it includes the advertising claim. Additionally, all contributors need to agree to a possible relicensing. I've made this statement because I've retired from the C&C community, there aren't many people I still keep contact with from it and I wanted to prevent any opportunity incase such a relicensing option ends up blocked on me.
While I didn't do much, my permission is required due to my contributions to Ares AttachEffect, Abductor.ChangeOwner and some preparations for HouseColorBolts. More exactly; these: https://github.com/Ares-Developers/Ares/commits?author=GraionDilach.
This statement allows me to enjoy my time in a community which welcomes and heavily appreciates my contributions to it while also allows any Phobos-affiliate to mediate with the other Ares developers in my name and/or consent. It's a blanket statement, sure, but these are the blanket statements required for such an option.