Seeds for MVP Functional Requirements

MVP features are being discussed on the forum. Feel free to link them here, but treat the forum as authoritative for now. When we start reaching consensus on the forum we can update this page.

Let's make sure we all agree, broadly, on what we're building. This page is ideas for functional requirements, not implementation details, and focuses on the minimum viable product (MVP). When items here get added to the "real" requirements/spec pages, delete them here.

Questions and answers

• On-site notifications of answers. Email can come later.
• Some on-hold/reopen mechanism? (We'll need this at some point, but is it MVP?) Arguably at least some hold will be needed for the first time (probably day 1!) that a question gets posted that is messed-up-but-not-intentionally-bad/spam.

Site features

• Some way to leave feedback on posts, whether that's comments, a "talk" page, or something else.
• Not MVP: chat.
• Some sort of sockpuppet detection mechanism, available to admins only for MVP (it might start as a collection of select statements).

Integration with Stack Exchange

• A new site can be seeded from a Stack Exchange site in a way that adds the links needed by the license.
• A site can be periodically updated from SE to get new posts and non-conflicting edits. For MVP: if a post has been edited locally it's ok to just not accept edits from SE any more, instead of trying to merge. Later we'll want to do something better here. We probably do not want to take deletion events from SE.
• A user can "claim" the corresponding SE user (verification method TBD probably OAuth will work, but if that is unavailable then maybe require a profile edit to add a specified random code, like Let's Encrypt and some other systems can use DNS TXT records to verify domain control?) and content, which should let us stop maintaining backlinks for that content.

...