Page MenuHomePhabricator

A page to collect news reports, papers, etc. on Abstract Wikipedia
Closed, ResolvedPublic

Description

What is the problem?

Abstract Wikipedia currently doesn't have a page where it collects news articles, videos, and other external resources.

How can we help you?

Set up such a page. It would be good to keep it easily editable so that the community can take over the maintenance of the page.

What does success look like?

A page exists and is reasonably well populated.

What is your deadline?

By June 2021. Earlier is obviously fine too.

Event Timeline

Aklapper renamed this task from A page to collect news reports, papers, etc to A page to collect news reports, papers, etc on Abstract Wikipedia.Jan 5 2021, 9:45 PM
Jdforrester-WMF renamed this task from A page to collect news reports, papers, etc on Abstract Wikipedia to A page to collect news reports, papers, etc. on Abstract Wikipedia.Jan 6 2021, 5:14 PM

There are three existing pages related to this topic:

  1. Abstract Wikipedia/Related and previous work|Abstract Wikipedia/Related and previous work
  2. Abstract Wikipedia/Ideas
  3. Abstract Wikipedia/User stories

The third one being indexed in:

  • Abstract_Wikipedia/Notes (related to support ongoing development works, mostly with transient info, which may be archived later)

External new coverage and research papers can effectively bring concepts to realize, enhance, or at least experiment in the "Ideas" page; users and searchers can also submit their experiments in the "User stories". However the Wikilambda toolkit and extension for Mediawiki could have a broader use than just for Wikifunctions: notably we are creating a language and a possible computing grid infrastructure (or private computing for use at home by individual users, e.g. for local domotics projects, or use on other social networks and medias; or even gaming: imagine that their would be a Wikilambda support in Steam, allowing gamers to develop and share their works as gaming extensions; there's also a commercial market for if and possibly sold as a webservice, and existing infrastructures could extend their computing cacity by using some external hosting providers: Wikilambda could potentially be neutral about the computing resources it requires to run the functions, collect and use data, secure it, handle privacy requirements...).

So "functions" could as well have uses in private external projects outside Wikimedia open projects (which will use Wikifunctions) for their own repository. As well Wikilambda could be connected to local host services in a OS or in a database engine (including with a driver, or as a datastore or SQL plugin). The concept is generic enough to work like other repositories in various languages (like node.js for Javascript, or for Python). Implementations may not be restricted to virtualizations languages or environments (Lua, Javascript, Java, PHP, Python...) and there should be a way to interconnect all these solutions, and define a way to select them (would require a "resolver", and adding a mechanism for security scopes/realms and permissions would also be required; scopes/realsm could be "global", or with "groups", or with individual user accounts or identities, allowing distinct reposirtories to share all or part of their content; or to be used as "proxies"; scheduling the execution over a netwrok of repositories and implementations, managing the resource usage if a real long-term challenge, as much complex as creating a new OS, however hosted on the global network, and fully virtualized, with minimal dependacy on the physical computing nodes, managing failover and redundancy and needing to avoid waste of ressources by parallelizing too many resources than what is needed: this requires a resource monitoring system where "computing nodes" could be added/removed/relocated dynamically, and mostly transparently).
We must also be aware that once it will start working, there will be numerous attempts to abuse the system (notably by tons of bots and malwares that we must be able to track and stop or at least isolate without too much damage to the rest of the infrastructure: this also requires communication and technical contacts, in addition to policies and contracts).

@Verdy_p: Hi. Your comment seems off-topic. This task is about collecting news articles, videos, and other external resources which are about Abstract Wikipedia.

This now exists, with the most relevant entries I could find from past newsletters and emails, and various web-searches. (I purposefully omitted the press articles that simply replicated info from elsewhere). https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Papers,_press,_and_videos