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).
@Samwilson I didn't end up changing the name yet, but at the hackathon there were discussions and the target name will now be "kiwi" i think!
@Addshore: Sounds good! (Have you run that name by Wikimedia Aotearoa New Zealand by the way? :-P)
Hahah, I have not! `wicli` was also just suggested, but seems harder to type!
I think pretty much anything other than "cli" would be an improvement for the title of this page and the name of the GitLab repo. Naming a project related to software development after a general class of software programs is a Go level of naming confusion.
The CLI page can be a disambig that lists all related CLI tools (if we are so inclined hehe). I don't think the existing redirect from CLI → Cli makes sense whatever happens.
Thumbs up all around, I'll aim to make all of these name related changes before the year is out.
mw dev mw exec composer phan
iirc, I could not use Quibble to run Phan. Then, is it possible to run Phan directly?
Yes, where not explicitly stated as WORK IN PROGRESS etc.
@Addshore How to become a MediaWiki hacker#Docker describes mwcli as experimental. I would consider it stable at this point and an easier solution to point beginner developers towards than setting up a MediaWiki and MySQL in Docker manually. For this reason I would like to remove the "experimental" description. Thoughts?
Hey hey, I think stable might be a bit far, as I'm still planning on some large ish wide reaching changes. However the current docker development environment I'd consider fairly stable. Maybe we should list it as beta?
I wanted to make a way to mark certain commands as beta, and that might allow me to release a 1.0.0 by the end of the year :)
I went ahead and tweaked this slighlty, https://www.mediawiki.org/w/index.php?title=How_to_become_a_MediaWiki_hacker&diff=prev&oldid=5818601&diffmode=source now it just says "new" And I'll aim for a 1.0.0 for the end of the year :)