Page MenuHomePhabricator

Address early feedback on the Architecture overview docs
Closed, ResolvedPublic

Description

  • T273756 Many empty sections: fill all of them or remove/leave empty some?
  • Clarify the relationship between “Wikibase Client system[s]” and the WikibaseClient extension in the repo context & scope: are they the same thing?
  • What is the meaning of “Mediawiki extensions cannot have extensions of their own.” in the client architecture constraints?
  • Solution Strategy: Remove the pointer to “this section in WikibaseClient” from Repo? (The Client’s two-sentence paragraph is actually duplicated in Repo.)
  • various users/editors not explained
  • Client uses Overview Glossary instead of the one in the Client subsection
  • separate Glossaries: try to avoid and rather use the same language across components: different meanings in different contexts sound like a smell and should possibly be refactored
  • link Glossaries to each other
  • switch order of ADRs and early architecture decision headings
  • Quality Goals could list something like a product vision/mantra
  • "Data updates from the repo are available ..." - what is data, what is repo?
  • Quality Goals: "Entity data which is included in a client wiki's article content is eventually consistent with updates on the corresponding repo." needs discussion: what does “eventually” mean -- align with repo quality goals and discuss push vs pull concepts (possibly not in Quality Goals)
  • "Fix and add values on Wikidata." - Be more specific about what "values" are/can be
  • Building Blocks: Add DataValues, Wikibase Item etc. to the Glossary
  • Explain difference between “Wikibase” and “Wikidata” to allow better understanding of terms like “Wikibase Item”
  • Explain the relation between "Wikipedia page connections", "interwiki links" and "connected pages" -- are they essentially the same?
  • “Special Page”: it might be worth while digging a little deeper here and listing at least the major kinds of special pages there are. I guess that might hint at some use cases
  • tie building block diagrams to domain concepts: make use of Runtime diagrams?
  • Building Block view and Runtime view look great, but: try to add the missing link between “How things are happening” and “What is happening / what is the purpose?” (Most probably it is “Use Cases”)

Event Timeline

Addshore claimed this task.