Main page: Handling wiki content beyond plaintext
- Facilitators
- Problem statement
- Collect proposals
- Expectations
- Links
- Key contributors invited
Description
Description
Event Timeline
Comment Actions
I took the liberty of adding @daniel as a co-facilitator for this area as a response to Daniel's on-wiki comment. Daniel, I think this would be the topic for us to drill down on content model related work.
Comment Actions
Sure. Let me bring it up to date, though; maybe a new task would be best.
We've discussed two proposals for concrete "wikitext2" syntax at our
parsing team offsite, and IIRC the mandate for this topic in 2017 is
broader than the T112996 proposal I made in 2016.
Comment Actions
Agreed. It's probably best to start with the submission form, copying relevant elements from T112996 over to the new proposal.
We've discussed two proposals for concrete "wikitext2" syntax at our
parsing team offsite[...]
Wonderful! I'm eager to participate in the wider discussion about those.
Comment Actions
I submitted/tagged T149658: A new semantics for templates, T149659: Grunge, or "zoom", T114454: [RFC] Visual Templates: Authoring templates with Visual Editor, T149660: Glossaries, pronunciations, and dictionaries, and T90914: Provide semantic wiki-configurable styles for media display for this topic area. They seem to cover all the interesting bits of the old T112996.
Comment Actions
Here's the current state of the proposals in this session, ordered by the sum (comments + tokens + subscribers) as a proxy for interest:
| owner | proposal title | comments | tokens | subscribers |
| Yaron_Koren | T149612 Bringing "Enterprise MediaWiki" to the Wikimedia Foundation | 25 | 3 | 17 |
| daniel | T149534 Scaling the MediaWiki database schema | 2 | 11 | 22 |
| cscott | T90914 Provide semantic wiki-configurable styles for media display | 0 | 0 | 24 |
| ssastry | T149282 Improved editability, tooling, reasoning, and performance by adopting DOM-based… | 7 | 2 | 15 |
| daniel | T149532 Why Multi-Content-Revisions? Use cases and requirements. | 0 | 3 | 20 |
| ssastry | T142803 [RFC] STUB: Creating a spec for legacy wikitext / future wiki content… | 9 | 0 | 11 |
| Nikerabbit | T44495 Subtitle translation with Translate extension | 0 | 2 | 18 |
| cscott | T148734 Moving associated content out of the wikitext | 2 | 1 | 16 |
| TheDJ | T150461 Story Builder | 0 | 2 | 13 |
| cscott | T114454 [RFC] Visual Templates: Authoring templates with Visual Editor | 0 | 1 | 13 |
| cscott | T149658 A new semantics for templates | 0 | 3 | 10 |
| cscott | T149667 Amazing Article Annotations | 2 | 2 | 8 |
| None | T149056 Supporting Vertical Writing Mode in MediaWiki | 4 | 1 | 7 |
| brion | T147604 Cross-functional support for rich media | 0 | 3 | 8 |
| cscott | T149659 Grunge, or "zoom" | 0 | 0 | 11 |
| TheDJ | T149554 What's next for Audio and Video ? | 0 | 1 | 9 |
| None | T148828 What should we do for ProofreadPage content models | 0 | 2 | 7 |
| Yurik | T149547 Making articles more interesting with data visualizations | 0 | 0 | 8 |
| cscott | T149660 Glossaries, pronunciations, and dictionaries | 0 | 1 | 6 |
Comment Actions
It looks like there is interest in 5 sessions here, sorted again by (comments+tokens+subscribers) -- but note that the summed subscriber counts are likely overestimates since they are not deduped:
| Session | Title | Comments | Tokens | Subscribers |
| A | Wikitext 2.0 (T149282, T142803, T149658, T149659) | 16 | 5 | 47 |
| B | Audio/Video/Media/Viz/Layout (T90914, T150461, T147604, T149554, T149547) | 0 | 6 | 62 |
| C | Annotations (T44495, T148734, T149667, T149660) | 4 | 6 | 48 |
| D | Page Forms + Cargo (T149612) | 25 | 3 | 17 |
| E | Multi-content Revisions (T149534, T149532) | 2 | 11 | 22 |
The following sessions are moved to Unconference: T114454: [RFC] Visual Templates: Authoring templates with Visual Editor, T149056: Supporting Vertical Writing Mode in MediaWiki, T148828: What should we do for ProofreadPage content models.
Comment Actions
Thank you for all this work organizing your main topic, @cscott! Probably the next step is to know whether the promoters of the proposals affected agree with the merges affecting them.
Comment Actions
Facilitation happened. Hence closing as resolved.
(I assume all open subtasks should also get closed.)