Abstrakt Wikipedia/Faser

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
This page is a translated version of the page Abstract Wikipedia/Phases and the translation is 2% complete.

Development of Abstract Wikipedia will proceed in two major parts, each consisting of a large number of tasks. Part P1 is about developing the wiki of functions, and Part P2 is about abstract content and natural language generation. On this page, we further break down the tasks of Part P1 into phases that each cover some of the work under a given task. The below contains links to Phabricator, where tasks and phases are broken down even further.

This wiki page might be stale. The canonical place for information about the tasks is Phabricator. Find our current state on Phabricator.

We expect to take about ten phases before launching the wiki of functions.

All the below phases cover work under Task P1.2: Initial development, unless marked otherwise.

Part P1: Wiki of functions

Phase α (alpha): store, display and edit headerYes check.svg Udført 2020-08-25

  1. Set up replicable development environment.opgave T258893
    • Yes check.svg Udført Start extension.opgave T258893
    • Yes check.svg Udført Config works, upload bootstrap content.
    • Yes check.svg Udført Reuse existing JSON ContentHandler.opgave T258893
    • Yes check.svg Udført Allow for entering JSON objects through the raw editing interface.opgave T258893
  2. Yes check.svg Udført Extend and hardcode checker for JSON objects to check for ZObject well-formedness. Nothing that is not well-formed will be further handled or stored. Well-formedness should probably be checked both in the PHP and the JS code (should be easy to write anyway).
    • Yes check.svg Udført i PHP. — opgave T258894
    • Well-formedness: key syntax, allowed keys, values are strings or proto-objects or lists of values.opgave T258894
  3. Yes check.svg Udført Every stored top-level ZObject must be a Z2/Persistent object.opgave T258897
  4. Yes check.svg Udført Create Z1/Object, offering one key, Z1K1/type.
  5. Yes check.svg Udført Extend hardcoded validator to check Z1K1/type.
  6. Yes check.svg Udført Create Z2/Persistent object.opgave T258897
  7. Yes check.svg Udført Z2/Persistent object has the keys Z2K1/ID and Z2K2/value, and Z2K3/Proto-Label, the latter being counterfactually just a single string with no language information.opgave T258897
  8. Yes check.svg Udført Extend hardcoded validator for Z2/Persistent object so far.opgave T258897
  9. Yes check.svg Udført Provide hardcoded display for Z2/Persistent object (that is the header) (that is a pretty big task).opgave T258898
  10. Yes check.svg Udført Provide generic view for the Z2K2/value object.opgave T258898
  11. Yes check.svg Udført Turn Z2K3/proto-label into the proper Z2K3/label for multilingual text.
  12. Yes check.svg Udført Extend viewing for Z2K3/label with multilingual text.

Phase completion condition: As a user [of a site with the MediaWiki extension installed], I can create and store a string as a new ZObject, e.g. "Hello world!".

Phase β (beta): create types and instancesYes check.svg Udført 2021-02-04

  1. Yes check.svg Udført Hardcoded validators for Z4/proto-types and Z3/proto-keys.opgave T258900
    • A Z4 has a Z4K2/keys with a json List of Z3s.
    • A proto-key has a Z3K1/ID and Z3K2/type and Z3K3/label (mirror the development of label for Z2K3?).
  2. Yes check.svg Udført Create Z4/Type and Z3/Key (Task P1.14).
  3. Yes check.svg Udført Search for ZObjects by label.opgave T260750
  4. Yes check.svg Udført Use Z4 type data and key declarations for validating objects.opgave T260861
  5. Yes check.svg Udført Use Z4 type data and key declarations for generic view of objects.opgave T258901
  6. Yes check.svg Udført Use Z4 type data and key declarations for editing and creation of objects.opgave T258903 & opgave T258904
  7. Yes check.svg Udført Provide hardcoded display and edit interface for Z12 type.opgave T258900

Phase completion condition:

As a user, I can create and store an object implementing any on-wiki defined type, e.g. the positive integer one

Phase γ (gamma): functions, implementations, errorsYes check.svg Udført 2021-04-02

  1. Yes check.svg Udført Introduce a simple error object.opgave T261464
  2. Yes check.svg Udført Introduce simple function.opgave T258957
  3. Yes check.svg Udført Introduce simple implementation, for now only built-ins.opgave T258958
  4. Yes check.svg Udført Create a few functions and built-ins.opgave T261474
  5. Yes check.svg Udført Introduce a simple function call type.opgave T261467
  6. Yes check.svg Udført Tester type (Task P1.10).opgave T261465

Phase completion condition: As a user, I can store a function call, a function, and a tester (only the objects, no actual evaluation yet), e.g. if(true, false, true) (read "if true then false else true", i.e. negation)

Phase δ (delta): built insYes check.svg Udført 2021-05-11

  1. Yes check.svg Udført Evaluation system for built-ins.opgave T260321
  2. Yes check.svg Udført Enable web users to call evaluation through an API module (Task P1.5).opgave T261475
  3. Yes check.svg Udført Special page for calling evaluation (Task P1.11).opgave T261471

Phase completion condition: As a user, I can use a special page to evaluate a built-in function with supplied inputs, e.g. to check whether the empty list is empty.

Phase ε (epsilon): native function callsYes check.svg Udført 2021-06-30

  1. Yes check.svg Udført JavaScript implementations (Task P1.12).opgave T275944
  2. Yes check.svg Udført Python implementations (Task O6).opgave T273517
  3. Yes check.svg Udført Allow forms to be included for evaluation.opgave T261472

Phase completion condition: As a user, I can use a special page to evaluate a user-written function in one of the supported languages, e.g. call a user-written function in Python to add up two numbers.

Phase ζ (zeta): compositionYes check.svg Udført 2021-08-27

  1. Yes check.svg Udført Allow for composition implementations (Task P1.6).opgave T261468

Phase completion condition:

  • As a user, I can implement a function using composition of other functions, rather than writing it myself, e.g. negate(Boolean → Boolean).Yes check.svg Udført
  • (Stretch condition) As a user, I can see the results of testers on the relevant function implementation's page. [This might need to be moved to a later phase as not all requirements may be met this point. Must be done by phase ι.]Yes check.svg Udført

Phase η (eta): generic typesYes check.svg Udført 2022-04-08

  1. Yes check.svg Udført Allow for generic types, particularly for Z10/List and Z8/Function, and replace Z10/List and Z8/Function.opgave T275941
  2. Yes check.svg Udført Errors can be processed like ZObjects.
  3. Yes check.svg Udført User-defined types work with validators.

Phase completion condition:

  • Being able to implement curry as a composition on the wiki, but without requiring strict static analysisYes check.svg Udført
  • Making it possible to create the following three 'user-defined' types on the wiki: positive integer, sign, and integerYes check.svg Udført
  • Being able to make a generic wrapper type through composition on the wikiYes check.svg Udført

See also the newsletter posted about this phase.

Phase θ (theta): thawing and freezing

  1. Freezing and thawing content (Task P1.7).opgave T275942
  2. Task P1.9: Pass security review.opgave T274682, …
  3. Launch public test system (Task P1.4).opgave T261469

Phase completion condition:

  • As a sysop, I can freeze and unfreeze any user-written object (akin to, or maybe the same as, MediaWiki's protection system); all system-supplied objects are permanently frozen.
  • As a user editing a frozen page, I can change the label, but not the implementation, whereas on an unfrozen page both are possible.
  • ZObjects are stored using the new canonical form for typed lists, and all parts are still working
  • View and edit function is implemented and tested successfully
  • When several implementations are available, the "best" is chosen. (Fitness determination to potentially be changed later.)
  • We measure the clock time & memory use of each function run, and display it on the execution result & in the implementation/test table.
  • Edits to system-defined ZObjects are restricted to users with the correct rights. Understandable diffs are emitted. Results are cached.
  • Text with fallback, references, strings, lists is implemented and tested successfully
  • A shared understanding with the community of how the team will contribute to Wikifunctions, and why, is documented
  • Designs for viewing and editing multi-lingual documentation on mobile and desktop are approved. UX is instrumented and data collected.

Phase ι (iota): documentation of objects

  1. This is a preliminary assignment, moving the documentation tasks here.
  2. Provide editing for the header (additionally to full raw editing) (that is a pretty big task) — this refers only to the labels, actually.
  3. Extend editing for Z2K3/label with multilingual text.
  4. Extend the header with Z2K4/documentation.opgave T260954 & opgave T260956
  5. Extend editing to deal with Z2K4/documentation.opgave T260955

Phase completion condition: As a user, I can document a ZObject in any and all supported languages, using a wikitext.

Phase κ (kappa): cleanup

  1. Tightening up and clean up tasks, to close all pre-launch tasks.

Phase completion condition: As the Abstract Wikipedia Team, we feel ready for launch, including sign-off from all relevant colleagues.

Phase λ (lambda): launch

  1. Phase λ (lambda) is meant for launch. If there are pre-launch tasks that prevent that, so be it, obviously.
  2. Set up a new Wikimedia project.
  3. Move some of the wiki pages about the project from Meta to Wikifunctions.

Phase completion condition: As a person on the Web, I can visit and use Wikifunctions.org to write and run functions directly on the site.

Unphased tasks

Pre-launch tasks that need to happen but are not phased in yet:

Post-launch tasks of Part 1

Se også