The current license management system has issues that require improvements. At present, authors can impose various restrictions on their models; however, the absence of a saved license version history makes it difficult to understand past permissions and restrictions. This problem not only affects individual models but also becomes more complicated when multiple models are involved. For instance, features like the "same" option, which can propagate to other models, can cause confusion to spread when license changes are made to merged models. To prevent such confusion, we propose managing model versions and licenses separately, with a system that can identify different combinations of model and license versions. Moreover, even if a model is deleted, it is essential to maintain its license history. Implementing these measures will enable smoother license management and prevent issues from escalating.
Please authenticate to join the conversation.
Awaiting Dev Review
π‘ Feature Request
Almost 3 years ago
284_d0w0b
Get notified by email when there are changes.
Awaiting Dev Review
π‘ Feature Request
Almost 3 years ago
284_d0w0b
Get notified by email when there are changes.