Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment on other Wikimedia wikis #26

Open
wetneb opened this issue Nov 1, 2019 · 3 comments
Open

Deployment on other Wikimedia wikis #26

wetneb opened this issue Nov 1, 2019 · 3 comments

Comments

@wetneb
Copy link
Member

wetneb commented Nov 1, 2019

EditGroups could be useful on other Wikimedia wikis. It should be relatively easy to deploy it there, we don't even need to solve #5 for that.

Question: do we want to deploy one tool per wiki? Or rather make the current tool support all wikis in the same database?

@lucaswerkmeister
Copy link
Member

I think one common instance for all Wikimedia wikis would be more user friendly, though I don’t know if it’s possible to keep up with the edit streams of all wikis at once.

@wetneb
Copy link
Member Author

wetneb commented Nov 1, 2019

The Wikimedia event stream sends events about all wikis by default. Given that Wikidata is the wiki with the highest bot activity by far (I think?), I am not too worried about the scalability of the listener if we add interested wikis gradually. There is also room for optimization in the listener, which I have not done: Wikidata's own rate-limiting is enough to keep the tool running at the moment.

But it probably requires more work to adapt the models / UI / API to support multiple sites.

It's also worth pondering whether we really want to invest in this particular external tool or if it would be doable to have that as a MediaWiki extension (T203557). It is clearly more involved, but it would probably be healthier.

My own motivation to work on this tool was to enable Wikidata editing from OpenRefine (I did not want to launch a mass-editing tool without having a mass-revert possibility). I do not have plans to dedicate significant development efforts on this tool in the foreseeable future beyond that particular need (so, basic maintenance to keep the lights on, such as #23). My intuition is that me working as a volunteer on this would lower the priority for WMF/WMDE to tackle this problem themselves in MediaWiki, which is not really helpful on the long term. (I hope this makes sense?)

That being said there might be good reasons why the foundation would actually oppose implementing something like this themselves. In that case, an external tool will remain necessary and as a maintainer I would try to grow the contributor community and make the project sustainable as such - which again might involve stepping back a bit from development itself.

So I think the deployment of Structured Data on Commons is a good opportunity to have that conversation, to understand a bit better what is the stance of WMF/WMDE on this on the long term.

@wetneb
Copy link
Member Author

wetneb commented Sep 11, 2021

Given that we are working on support for Structured Data on Commons in the OpenRefine project, we need to be able to revert batches on Commons. Therefore I will run an instance of EditGroups for Commons. The concerns above still apply: it should just be treated as a temporary solution until there is proper support for that on MediaWiki's side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants