I don't know if this fit better in general support category.
I don't know if this fit better in general support category.
VenedasCurious if they are going to move it to a paid site? Great plugin, big loss for the community if it is gone without a replacement.
It was removed per request as the author was unable to follow our community guidelines and rules. The author is no longer on our site as well. I'm sure that with enough intererest, a replacement will be created.
PsyHawk0I don't mean to beleaguer a point but every page has "The uMod open-source projects licensed by their respective contributors" and nothing on the old page nor in the 1.9.0 code says anything about it NOT being open source.With the statement "The uMod open-source projects licensed by their respective contributors" & with the community guidelines, it stands to reason that no one could continue it without a complete rewrite, especially if the author asked for it to be removed (since I doubt they'd give permission to run with the current version/software).So... If it weren't an "open source license" - why was it even allowed on oxide/umod (as it has been around for quite some time)?
Software/plugins/code do not necessarily automatically fall under another project's license; that would depend on the license. Both Oxide and uMod have fairly flexible licenses that do not force licenses on other projects that utilize it. If a plugin (any code really) does not have a license attached, it would generally be assumed as "all rights reserved", which would mean that the author has all rights to their work.
We did not start encouraging license use until the move to umod.org, though in light of this and past instances with these same plugins and others, we may require a license going forward in order for plugin submissions to be accepted.
Wulf
Software/plugins/code do not necessarily automatically fall under another project's license; that would depend on the license. Both Oxide and uMod have fairly flexible licenses that do not force licenses on other projects that utilize it. If a plugin (any code really) does not have a license attached, it would generally be assumed as "all rights reserved", which would mean that the author has all rights to their work.
We did not start encouraging license use until the move to umod.org, though in light of this and past instances with these same plugins and others, we may require a license going forward in order for plugin submissions to be accepted.
If the developer has spent all their time creating the plugin and updating it to continue working with Rust why shouldnt they retain "all the rights" to the work ?
That's completely up to them, but also detrimental to a community that relies on those plugins. Free plugins will be required to have a license attached where the plugin can be continued should the author wish to abandon them, paid (marketplace) will not. While it is up to the author how they wish to handle their works, we have a project and community resources to upkeep and maintain.pookins
If the developer has spent all their time creating the plugin and updating it to continue working with Rust why shouldnt they retain "all the rights" to the work ?