Hi! Seeing some activities in this thread means that I'm not too late to share some thoughts.
:ehappy:
As a complementary subject of the section "Team Projects", I think it could be useful to specify the rules with projects shared with VCS tools like GitLab, GitHub and their friends. As an adept of Open Source solutions and programming, I tend to always set "public" my projects, even if I'm the only one contributing. As well I would do with my RM game projects. But, as mentioned in the EULA of the main soft and in the majority of the DLC, distributing the materials are not allowed. That means that if I work in a team group, or simply use VCS tools to sync my projects between several PC (home, work, portable), I have to make my Git projects/repositories private!
Regarding the section "Copyrights and Patents", may I have a question: do you know if it exists a licence similar to the
Open Game Licence that can be applied for RM games? I like the fact that with a similar licence we could distinguish the final product "game" as an all (universe, story, game mechanic, ...) and the materials used to build it (tilesets, sounds, graphics, ...). The fact is that most Open Source licences (CC, GNU, ...) are only considering the final product, and so restrict the materials used to follow the same rules. Therefore, to create an Open Source RM game, the only solution is to create myself all the materials, or use only DLC materials that are under one of these licences. Correct?
In the same subject, don't you think useful to add two files systematically in the game package: one for the credits (as the complement of the final credits of the game that are always showing at the end), and one for the terms of use of the game (to specify for whom: kids, adults, ...; for what: education, fun, ....; if can we remix/extend the game with prequels, sequels, ...; what we can't do with it: promote hatred, politics, ...) ?
Thanks for your feedback.