Requested gerrit repo here: https://www.mediawiki.org/w/index.php?title=Git%2FNew_repositories%2FRequests%2FEntries&type=revision&diff=1882626&oldid=1881552

@JanZerebecki we already have a gerrit repo https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/ValueView (created long ago but think this would work and is what we want)

But this is supposed to be a library/component, not an extension, right? So it's the wrong name. Renaming a gerrit repo is not something that is done. So lets directly use the correct name. I'll create request to delete the wrong name.

+1

@JanZerebecki it is an extension. Do we want to change that? If/how does i18n stuff work in a library?

As I recently wrote in T75020#1629613:

Even if some component does not depend on MediaWiki, I'd still consider it a MediaWiki extension if it optionally provides MediaWiki integration. Currently, all our resource loading happens through ResourceLoader, and that won't change soon.

In T112120#1643078, @aude wrote:

If/how does i18n stuff work in a library?

I don't know about how the JavaScript use the i18n json files. I assume translatewiki.net only cares about there being i18n files in a location in a git repo not about extension vs component.

In T112120#1644064, @adrianheine wrote:

As I recently wrote in T75020#1629613:

Even if some component does not depend on MediaWiki, I'd still consider it a MediaWiki extension if it optionally provides MediaWiki integration. Currently, all our resource loading happens through ResourceLoader, and that won't change soon.

If it is declared a Mediawiki extension or a composer component depends only on if we use composer to depend on it or if it is a submodule in the deployment branch of mediawiki/core. If we want our deployment being sane, we should only do one at the same time. Both have different technical consequences. Some features are currently only provided by one of them. (Now it is confusing that we currently use composer to make a build of extensions in Wikidata, in the long run we want to stop that.)

Regarding that we won't remove the ResouceLoader dependency soon: That might work in practice ok even as a component. The downside of that is that we need some custom CI glue to run the QUnit tests. That might possibly look like: add a composer depencency on data-values/value-view into an installation of Mediawiki, run composer, run qunit tests as is normally done with Mediawiki.

(Btw. breaking out ResourceLoader out of Mediawiki into a component that does not depend on Mediawiki, would be an alternative to removing the dependency on it.)

I requested to not create the repo until we decided. Another thing is how to name the repo if it should be a component: The composer name is data-values/value-view. Should we name it wikibase/data-values/value-view?

We talked about this in person. Outcome:
We don't want to miss the feature of dependency resolution with versioning. Extensions don't yet get that from Mediawiki.
In practice data-values/value-view will work as is in a possible future deployment where we have abandoned our Wikidata build and everything is in mediawiki/vendor.
So we go with it being a component.

I'll go with the name: data-values/value-view

@JanZerebecki is this blocked on something?

There was a question during the repo creation process I now answered.

The repo was created: https://gerrit.wikimedia.org/r/#/admin/projects/data-values/value-view,branches

This is now moved, please don't change the repo on github.com yourself. I.e. creating a tag needs to happen through gerrit.

https://gerrit.wikimedia.org/r/#/c/243677/ needs to be merged for the CI to pass.

Creating a tag then works like this:
git tag TAGNAME master
git push gerrit tag TAGNAME

@JanZerebecki is there still something missing or can this be moved to done?