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
Reia is currently licensed under AGPLv3. To the best of my knowledge, that means that even though I am the one that initially started this project, once other people start contributing I can't freely make some of the work private. All derived work has to be made public.
Why does the work need to be made public?
Console
Well, I'm not entirely sure it does. It really depends on whether or not PS5, XBOX, and Switch requires their ports to be private. Which I don't think would be possible when I lose the ability to legally make the work private for those changes.
Hidden Bosses, Activities, Puzzles, & Events
Having absolutely everything be public would kill surprises in the game. I actually want there to be a handful of content that you have to explore and work together to find.
So what is the solution?
That depends. If console doesn't need to be private, then great. I can ditch the CLA idea and probably go the route of "mods" that add outside functionality on top of the existing game. The mods would be installed on top of the base game when it's distributed. It's only for specific content so it's feasible in a small update.
If consoles do need to be private, then the solution would be to implement a CLA. The focus would be to primarily maintain the right to take the code private to enhance the overall experience for everyone. The other focus would be to allow people to still maintain their rights to their contributions.
There may be more "whys" and "solutions" but this should be a good start for the discussion.
The text was updated successfully, but these errors were encountered:
I've implemented cla-assistant for future contributions. This issue isn't done. If it turns out it's no longer needed and this project can achieve all of its goals without it, I'll revoke all signatures.
Reia is currently licensed under AGPLv3. To the best of my knowledge, that means that even though I am the one that initially started this project, once other people start contributing I can't freely make some of the work private. All derived work has to be made public.
Why does the work need to be made public?
Console
Well, I'm not entirely sure it does. It really depends on whether or not PS5, XBOX, and Switch requires their ports to be private. Which I don't think would be possible when I lose the ability to legally make the work private for those changes.
Hidden Bosses, Activities, Puzzles, & Events
Having absolutely everything be public would kill surprises in the game. I actually want there to be a handful of content that you have to explore and work together to find.
So what is the solution?
That depends. If console doesn't need to be private, then great. I can ditch the CLA idea and probably go the route of "mods" that add outside functionality on top of the existing game. The mods would be installed on top of the base game when it's distributed. It's only for specific content so it's feasible in a small update.
If consoles do need to be private, then the solution would be to implement a CLA. The focus would be to primarily maintain the right to take the code private to enhance the overall experience for everyone. The other focus would be to allow people to still maintain their rights to their contributions.
There may be more "whys" and "solutions" but this should be a good start for the discussion.
The text was updated successfully, but these errors were encountered: