Collaborators

[elsiehupp]

I've mentioned to several people that I became involved in this initiative somewhat by accident, and I haven't really been able to stay on top of Issues and Pull Requests myself.

Because of this, I have been adding contributors as "collaborators" on the repository, which allows you to do several things:

• Create branches directly on this repository,
• Work directly on each other's branches on this repository, and
• Approve each other's Pull Requests to python3 (i.e. the main branch).

If something needs my attention, and I haven't responded, or you think I should add someone as a collaborator, please feel free to email me at github@elsiehupp.com. (You can also feel free to email me for any other reason, as well.)

EDIT: I just set up another email alias specifically for personal correspondence regarding this project: if you email me at wikiteam@elsiehupp.com your message will go to my personal inbox rather than getting buried in all the automated notifications I get from GitHub.

[robkam]

Wikiteam is great for quickly/non-interactively backing up wikis, but is stuck at Python 2.7. Your moving it forward to Python 3 is much appreciated.

[elsiehupp]

I appreciate the appreciation, but I also appreciate that you have been doing much more of the heavy lifting recently!

[yzqzss]

I am glad to be a collaborator.
Also, my English writing is very poor (I'm OK on reading) and I often need to use some machine translation sites. I hope you won't be surprised when you see strange sentences, lol.

[elsiehupp]

I just noticed that GitHub "organization" membership is private by default, so feel free to go to the People tab and toggle your membership visibility to "Public" if you'd like it as a badge on your profile.

(On a related note, if anyone would like to create a proper GitHub avatar for MediaWiki Client Tools, just let me know, and I can apply it!)

[robkam]

For the avatar I'd look for something simple/distinctive on Wikimedia commons, e.g. an icosahedron.

[elsiehupp]

I threw together a logo with a snake and a rake to represent scraping wikis with Python. It's far from perfect, but I can definitely elaborate on it (and/or upload the SVG to a repository).

[elsiehupp]

I mean obviously one scrapes with a putty knife or a razor scraper, but those weren't quite as immediately visually distinctive as a rake (though, again, the icon I made is just a very rough first draft).

[elsiehupp]

It would be fairly easy for me to replace the rake layer of the image, though.

[robkam]

I'm not keen on an aggresive snake.
MediaWiki is sort of associated with the sunflower.

[elsiehupp]

I could try and make something g along these lines, but I would probably have to make it from scratch.

[elsiehupp]

Perhaps a good starting place:

[elsiehupp]

This is extremely WIP (i.e. imagine it's basically a wireframe), but here's like 45 minutes' work today:

[robkam]

Transplanting a sunflower.

[elsiehupp]

Well, technically a Gerbera daisy.

[robkam]

Monty Python, with flower petal background. From here on Flickr (CC-BY-SA file).

[elsiehupp]

I mean that works, too. I had initially thought of the flower petal motif, too. (I threw together the snake and rake in like 15 minutes.)

[robkam]

Something like this (from https://commons.wikimedia.org/wiki/File:MediaWiki_bureaucrat.svg)?

[elsiehupp]

The problem is that I have just enough artistic ability to be picky lol

[robkam]

It took a few years to get a wiki logo I'm happy with. I had to get somebody else to do the drawing.

[elsiehupp]

I'm okay doing this myself, and a non-license-appropriate transplantation image feels like an okay placeholder (compared to, e.g., a snake).

[yzqzss]

Sorry, I quit MW-client-tools.

Reasons:

• Lack of real developers and CODE REVIEWERs.
• wikitools3 is a completely useless repo, its classes can't even be instantiated! Nobody uses it, so I don't know why it needs to be maintained? A more complete py3 refactoring branch exists upstream.
• scraper is an evil name. (for webmasters)
• git log: "Update *.md" x99

[elsiehupp]

I'm sorry to hear that things have gotten to this point. You could have contacted me earlier about any and all of these issues.

I hope it's okay if I respond to these concerns...

Lack of real developers and CODE REVIEWERs.

I am aware of this. This is part of why I previously asked if you wanted to take ownership of this repository.

wikitools3 is a completely useless repo, its classes can't even be instantiated! Nobody uses it, so I don't know why it needs to be maintained? A more complete py3 refactoring branch exists upstream.

wikitools3 dates from the very, very beginning of my effort to make WikiTeam work in Python 3. I did not see that there was an unpublished Python 3 branch upstream until I had already made my own version. I published it on PyPI because someone on the upstream WikiTeam repository asked me to.

Merging the upstream branch and doing a version bump or merely deprecating the repository would be fine by me.

(When researching the original developers, I found that one of them is also using a derived version of wikitools for another project, so they would be the obvious point person for this. I just never got around to contacting them.)

scraper is an evil name. (for webmasters)

I don't have any strong attachment to the name, and anyway this tool has not been published on PyPI, so there isn't any reason the name can't change.

There was an open Issue regarding the initial name change, so I don't consider the existing name necessarily final.

I did the various name changes largely in order to (a) remove my own name from the repository, and (b) facilitate a PyPI upload that has yet to happen.

git log: "Update *.md" x99

I had previously set the repository to mandate squash merges, but somebody else complained about it, so I made it optional.

If you want to change this (or set up other administrative processes), that's fine; and, anyway, you would be free to make these changes yourself if I were to transfer you the repository.

---

Would any of these things help?

Best,
Elsie