The Curse Client refused to install WeakAuras2 until after I'd deleted WeakAuras, and even then it didn't install it correctly (it installed all the folders except the main "WeakAuras" folder) until after I'd completely exited and restarted the Curse Client. (Seems like a lot of work for an addon I only have installed for one encounter I haven't done in months, but oh well...)
If you manually installed WeakAuras2 without uninstalling WeakAuras through the Curse Client, then the CC will probably have trouble updating WA2 in the future, so at some point you will have to uninstall what it thinks is WA, and then re-install WA2 (possibly by hand). Make sure you un check the "also delete my settings" box when you're uninstalling WA.
Does anyone know why the addon was forked in the first place? Both projects appear to have the same authors. Wouldn't it have been easier to avoid all this confusion by just continuing the original? :confused:
Yeah, that was my thought as well. Feel free to rename the project, but what is the point of creating a new project? It just confuses everyone for no reason. Probably also gets you more Curse author points than you deserve, too, which was the only thing I could think of when I was wrestling with the Curse Client over the update.
Sounds like all of this nonsense could have been avoided if the people in question had just RTFM and had the project reassigned to a different manager. :rolleyes:
Nope. If someone wants to continue the work on a project with a permissive license, they can only do so on that project if the author gives explicit permission. In that case, we can transfer ownership if the original author asks us to do so. Otherwise, the interested party can fork the project using the same or a compatible license and the name of the new project must be different from the originating project.
That has not been my experience. I've requested and received ownership of several projects with permissive licenses, where the original project manager was long gone and not responding to contact attempts, some where I was already listed as an author, others where I was not. There is no requirement for a name change in most OSS licenses, and forcing one (especially in a way you handled it with WeakAuras, where the projects have different names but the addon folders do not, and thus cannot both be installed at the same time, which is a situation the Curse Client does not handle gracefully at all) just creates a lot of unnecessary confusion and hassle for users.
One could argue that the same project name with an increased version number is not a "different name" though, as it blocks any advancement possibilities for the original project. What if the author ever wants a WeakAuras, version 2? :)
That's true, and the OSS licenses that do require a name change for forks also require that the fork does not prevent the original version from being installed at the same time (eg. Artistic License, or Open Font License).
Yeah, it "happened" and you can't change that, but that doesn't mean it's immune to criticism, and public complaints may even discourage others from doing the same thing in the future.