As seen in wikimedia-dev IRC:
<Krinkle> qgil: You might find this interesting https://krinkle.github.io/#wikimedia - it takes very long to load (uses recursive GitHub API and has to page through 100s of mediawiki extensions) - but something I ripped off of https://twitter.github.io
Interesting, but... what is it? Why these repos and not other? What is the color schema of the cards trying to tell?
Source code:
Interesting, but... what is it?
A page showcasing that Wikimedia is open source and here are the projects we created, maintain and actively use as part of our infrastructure.
Why these repos and not other?
Because our convention to also serve as git host for third parties developing MediaWiki-related software, I had to filter these out as they are not maintained by Wikimedia, not used by Wikimedia, and more importantly, because they may be abandoned or falsely claim credit (e.g. they might not want us claiming credit, and we may not want our stamp on it either.)
For the moment it includes:
It excludes (source code):
What is the color schema of the cards trying to tell?
It signifies the programming language primarily used by an individual project (as determined by GitHub's search index)
Thank you for the explanation. Did you want to just give a shot to this script, or did you have more ambitious goals in mind?
I'm not sure what to do with this. It gives the impression that these are all the Wikimedia projects in GitHub, but it is not true. It also gives the impression that we are encouraging participation via GitHub, but this is also probably not true...
It has nothing to do with GitHub. The goal is outlined in the previous comment. Those goals apply to dev.wikimedia.org. I used GitHub in my demo because:
We'd obviously use our own APIs (or curate the input) and point urls to Gerrit (or Phabricator).
I don't have a further ambition with it at this time. I'll leave that up to the folks working on dev.wikimedia.org. It's an example of something I think dev.wikimedia.org should have. An easy overview for developers to discover re-usable projects for third-parties (e.g. cssjanus). And to discover useful tools (e.g. ChromeWikimediaDebug). Neither of which are sufficiently discoverable right now.
This is useful as a list of Interesting Wikimedia software projects. So where does it go on mediawiki.org? Starting from How to contribute:
I'd add these links today but https://krinkle.github.io/#wikimedia is a bit too slow. Maybe with a loading "Loading Wikimedia software projects [loading dots]]". Or should we build an equivalent on-wiki page that lists 30 {{Wikimedia software}} templates, where possible pulling in a Labelled Section Transclusion from existing project pages?
It's an example of something I think dev.wikimedia.org should have.
Caution: "dev.wikimedia.org" is like the blind men and an elephant, it lets people project whatever they want onto it :)
To be clear, what I'm working on is "A central place for third-party developers to access our data sets and experiment with our APIs." Maybe that'll morph into the integrated documentation site of everyone's disparate dreams for everything.
I'm still not sure what can we do with this list of projects. Maybe @Jhernandez sees a potential use integrated or complementary with his project about T91633: Create a user friendly encouraging-to-contribute site?
I've posted these links in T91633#1409133 and will keep it in mind when brainstorming the content.
Thanks for the mention @Qgil
I only just learned of https://www.mediawiki.org/wiki/Upstream_projects. It's not as attractive but it's more in our expertise to maintain (maybe we could apply some JS or CSS from this to it).
Need to check this for github projects missing from Upstream_projects or elsewhere. E.g. the Wikipedia phone apps.
At this point I think it is better to close this task as Declined. I don't see how can we maintain this effectively and integrate it with the documentation we already have.