What is the actual name of this project? It seems to be mostly called 'mwcli', but this page is 'Cli', and the first sentence says "mw is a MediaWiki focused command line tool…". I think it'd be good to be consistent (and probably 'mwcli' is best, although I also think 'mwcli-dev' would be more expressive of its purpose/audience).
I have an older project called mwcli and am thinking I should probably rename it to avoid confusion: https://github.com/samwilson/mwcli
Yeah, some changes to the naming could make some sense. I was thinking rebranding to "Wikimedia" rather than referencing mediawiki might make more sense, as it is slowly evolving into a general development tool in the Wikimedia space, for example it has gitlab integration which right now doesn't relate to mediawiki at all. Also, Gerrit, tools etc.
I should maybe look at how GitHub and gitlab do their branding in terms of the name of the tool, name of the docs and name of the executable etc
@Addshore: (Sorry about my slow reply; notifications from Flow aren't great!) That all makes sense, I think. A Wikimedia-centric tool would be great. I guess the obvious wmcli would be a bit close to mwcli… although no more than the usual wikipmedia stuff. :-)
Now I understand why Toolhub and others were supported. It confused me for a while.
Yeah, the "MediawWiki" part of the mwcli is defintly confusing now. So, "wmcli" is currently on the short list? Any other ideas? That also might clear up most of the confusion and naming conflicts here. And the mediawiki.org page could then be "wmcli" or similar? Maybe with a redirect from "Cli"
@Addshore: I can't think of any other names, other than perhaps spelling it out as wikimedia-cli and telling people to create whatever alias they want (e.g. wm). And yep, I think redirecting Cli → wmcli sounds fine, although the existing mwcli (which currently redirects to cli) should perhaps be made into a disambig.
I will carry on with the above mwcli name for that project that's about generic stuff to do with MediaWiki (and will probably move it to our GitLab).
