Skip to content

MVP Decision Log

Jump to bottom
Helmar edited this page Jan 19, 2020 · 11 revisions

We build a Q&A engine to iterate on.

This is not another functional specification. This just gathers the in/out decisions as well as links to open issues.

Remark: I gathered decisions regarding features, e.g. what does Codidact do and regarding the tech stack, not smaller stuff (e.g. snake case vs camel case of variables or stuff) even if that was MVP tagged.

This also does not try to capture the DB schema & setup debates from the forum.

MVP — What's in

  • Comments exist
    • Comments are threaded
  • Community Sites
  • Cookie Usage
    • Restrictive and not used for nasty stuff
  • Metas
    • We have meta sites for discussions about the community and the software. They either use a Q&A-based approach or a more discussion-oriented one.
    • We need to have instance-level discussions (network meta) and community-level (per-site meta) discussion sites.
    • The instance-level and the community-level meta discussion forums should be separate for now (contentious point; decision based on like-score)
    • Meta sites should be freely and easily accessible.
  • Post Deletion, Closure
    • Details of Closure & Deletion unclear
  • Post Voting
    • Up/Down Voting
    • Question Voting
      • Questions contains up and downvotes separately (Assumption on Q-List & Q-Details page)
  • Tags
    • 1-5 tags per question
    • Tag names are alphanumerics and a few punctuation signs.
    • Anybody with a certain privilege can create a tag.
    • Anybody with a certain privilege can edit tag descriptions.
    • People can browse the list of tags.
  • User Privileges
  • User Profiles
  • User Notifications exist
    • One trigger: "pinging" in comments

MVP — What's out — "Not now"

Codidact — What's out? — "Not ever"

MVP — Undecided Proposal

  • User Moderation Capabilities
  • Import Functionality
    • One-time operation sufficient for MVP
    • Is in Func-Spec without forum decision
    • What to import
  • Question Closure Mechanics
  • User Privileges
    • Privilege levels
      • Follow Up
      • The linked forum post is now in the functional spec
      • However, neither forum does not provide insight into what should be considered MVP Furthermore these trust levels bring tons of implicit requirements that are so far not within the MVP.
  • Post Order
    • For each answer we display raw upvotes and downvotes. This makes controversy visible.
    • For each answer we compute a score thus: (upvotes + bonus + N) / (upvotes + downvotes + bonus + 2N). Scores are not directly displayed. Default N is 1 but is configurable per-site.
    • We order answers by score, with newer answers winning ties.
    • For questions older than (default) 6 months, new answers are labeled “new” and given a bonus in the scoring formula for the first (default) 7 days. This allows new answers to have more visibility when there are high-scoring answers present already. The amount of the bonus is TBD. All values are configurable per-site, including turning this feature off.
    • There's discussion ongoing in the forum after the proposal was posted.

MVP — Open (One or the other) — "We need a direction, which do we pick?"

MVP — Open (In/Out) — "Do we really need that now?"

Links

Codidact

Development

Social Media

Clone this wiki locally