Wikipedia Abstrak/Fase

Pengembangan Wikipedia Abstrak akan berlangsung dalam dua bagian besar, masing-masing terdiri dari banyak tugas. Bagian P1 adalah tentang mengembangkan wiki fungsi, dan Bagian P2 adalah tentang konten abstrak dan penghasil bahasa alami. Di halaman ini, kami memecah tugas-tugas di Bagian P1 menjadi fase-fase yang masing-masing mencakup beberapa pekerjaan yang dilakukan untuk suatu tugas. Penjelasan di bawah berisi tautan ke Phabricator, di mana tugas dan fase dipecah lebih kecil lagi.

Halaman wiki ini mungkin tidak mutakhir. Tempat utama untuk melihat informasi tentang tugas adalah Phabricator. Cari tahu keadaan terkini kami di Phabricator.

Kami memperkirakan akan perlu sekitar sepuluh fase sebelum meluncurkan wiki fungsi.

Semua fase di bawah mencakup pekerjaan dari Tugas P1.2: Pengembangan awal, kecuali apabila disebutkan berbeda.

Bagian P1: Wiki fungsi

Fase α (alfa): menyimpan, menampilkan dan menyunting kepala — Selesai 2020-08-25

1. Membuat lingkungan pengembangan yang bisa disalin. — tugas T258893
   • Selesai Memulai ekstensi. — tugas T258893
   • Selesai Config works, upload bootstrap content.
   • Selesai Reuse existing JSON ContentHandler. — tugas T258893
   • Selesai Allow for entering JSON objects through the raw editing interface. — tugas T258893
2. Selesai 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).
   • Selesai in PHP. — tugas T258894
   • Well-formedness: key syntax, allowed keys, values are strings or proto-objects or lists of values. — tugas T258894
3. Selesai Every stored top-level ZObject must be a Z2/Persistent object. — tugas T258897
4. Selesai Create Z1/Object, offering one key, Z1K1/type.
5. Selesai Extend hardcoded validator to check Z1K1/type.
6. Selesai Create Z2/Persistent object. — tugas T258897
7. Selesai 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. — tugas T258897
8. Selesai Extend hardcoded validator for Z2/Persistent object so far. — tugas T258897
9. Selesai Provide hardcoded display for Z2/Persistent object (that is the header) (that is a pretty big task). — tugas T258898
10. Selesai Provide generic view for the Z2K2/value object. — tugas T258898
11. Selesai Turn Z2K3/proto-label into the proper Z2K3/label for multilingual text.
12. Selesai 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 instances — Selesai 2021-02-04

1. Selesai Hardcoded validators for Z4/proto-types and Z3/proto-keys. — tugas 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. Selesai Create Z4/Type and Z3/Key (Task P1.14).
3. Selesai Search for ZObjects by label. — tugas T260750
4. Selesai Use Z4 type data and key declarations for validating objects. — tugas T260861
5. Selesai Use Z4 type data and key declarations for generic view of objects. — tugas T258901
6. Selesai Use Z4 type data and key declarations for editing and creation of objects. — tugas T258903 & tugas T258904
7. Selesai Provide hardcoded display and edit interface for Z12 type. — tugas 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, errors — Selesai 2021-04-02

1. Selesai Introduce a simple error object. — tugas T261464
2. Selesai Introduce simple function. — tugas T258957
3. Selesai Introduce simple implementation, for now only built-ins. — tugas T258958
4. Selesai Create a few functions and built-ins. — tugas T261474
5. Selesai Introduce a simple function call type. — tugas T261467
6. Selesai Tester type (Task P1.10). — tugas 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 ins — Selesai 2021-05-11

1. Selesai Evaluation system for built-ins. — tugas T260321
2. Selesai Enable web users to call evaluation through an API module (Task P1.5). — tugas T261475
3. Selesai Special page for calling evaluation (Task P1.11). — tugas 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 calls — Selesai 2021-06-30

1. Selesai JavaScript implementations (Task P1.12). — tugas T275944
2. Selesai Python implementations (Task O6). — tugas T273517
3. Selesai Allow forms to be included for evaluation. — tugas 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): composition — Selesai 2021-08-27

1. Selesai Allow for composition implementations (Task P1.6). — tugas 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). — Selesai
• (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 ι.] — Selesai

Phase η (eta): generic types — Selesai 2022-04-08

1. Selesai Allow for generic types, particularly for Z10/List and Z8/Function, and replace Z10/List and Z8/Function. ― tugas T275941
2. Selesai Errors can be processed like ZObjects.
3. Selesai 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 analysis — Selesai
• Making it possible to create the following three 'user-defined' types on the wiki: positive integer, sign, and integer — Selesai
• Being able to make a generic wrapper type through composition on the wiki — Selesai

See also the newsletter posted about this phase.

Phase θ (theta): thawing and freezing — Selesai 2023-06-19

1. Selesai Freezing and thawing content (Task P1.7). ― tugas T275942
2. Selesai Task P1.9: Pass security review. — tugas T274682, …
3. Selesai Launch public test system (Task P1.4). — tugas 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. — tugas T260954 & tugas T260956
5. Extend editing to deal with Z2K4/documentation. — tugas 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:

• P1.1: Project initialization.
• P1.3: Set up testing infrastructure.
• P1.8: Launch beta Wikifunctions.

Post-launch tasks of Part 1

• P1.13: Access functions.
• P1.15: Lua-based implementations.
• P1.16: Non-functional interfaces.
• P1.17: REST calls.
• P1.18: Accessing Wikidata and other WMF projects.
• P1.19: Monolingual generation.

See also

• Part P2: Abstract Wikipedia.
• Non-core tasks (optional).