MVP Decision Log

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
  • Custom CSS
  • Custom Color Set / Header Images
    • Implicit design decision: There are header images
  • Adaptable Help / FAQ pages
    • Implicit decision: There are Help/FAQ pages in MVP
• 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
  • Progress to further privileges displayed on profiles
• User Profiles
  • User name, free text bio/profile
  • Activity Log
  • Associated SE account
  • Implicit: Contains list of user's questions
    • Said list of questions contains up and downvotes separately
• User Notifications exist
  • One trigger: "pinging" in comments

MVP — What's out — "Not now"

• Area 51 to launch new sites
• Community Sites
  • Custom JS
• Moderator Elections
• No publicized user reputation number
• Post Voting: Extend mechanism
  • Out by conflicting with simpler MVP definition (s.a.)
• Printable Pages
  • We don't break it on purpose but there's no focus on it.
• Tags
  • Each tag has an optional text description.
• [User Profiles Avatars]((https://forum.codidact.org/t/user-public-profiles-in-mvp/44/21)
  • By affiliation out: Avatar Picture Host Discussion

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.

MVP — Open

• Authentication
  • Suggestion: ASP.NET Core Identity
• Breadth of Notifications
  • Another one
• Community Customization beyond CSS/Design
• Community Launch Customizations
  • Lowered trust levels
• Computation of Post Scores
• Degree of Mobile & Accessibility support
• Draft Posts
• Image Uploading
• Licensing of Content
• Localization
  • Current idea: No focus but trying to enable it down the line
• MathJax
• Meta beyond "there are metas"
• Mod Tool Capabilities
• Post Editing Mechanics
• (Semantic) Versioning
• SE Score Import
• Rating of questions and askers
  • This wants to go beyond up/down for questions
• Requirements and Mechanics of Downvotes
• Unlocking Upvote Privilege
• URL Schemata