Feature dump

[plaindocs]

• Tagging talks

• Talk states - I'm not 100% certain how we want this. But Submitted -> Selected / Rejected / Wait list -> Confirmed would be a good start.

  • And while we're doing states, being able to define per conference what you will need from speakers, and be able to check those off and store states, even if we're not directly working with them in the app might be cool.

• In Grorg we've ended up with a mess of talk allocations, because even though you can set talks types per conf (ie, 30 min talk, 60 min talk), the allocation doesn't restrict that. But that is deep in the weeds.

• We've already mentioned anonymous rating round

• Proposal form that does not require login. However it would be useful to give accepted speakers a login that lets them update talk title, upload photo etc.

  • And while we're here, how much of a PITA would storing history of those types of edits be? I definitely don't want to have people be able to change talk titles without some form of approval required. :-p

• Email speakers, with reject / waitlist / selected with Templates, and variables. (Reject all except selected.)

  • Email all confirmed speakers, with editable template

• Speaker export to yaml compatible with current yaml structure.

[baggerspion]

For the flight home:

• [x] Tagging talks
• [x] Talk states

@plaindocs I assume you are looking for reviewers to be able to apply tags at will... or would you prefer some predefined taxonomy?

[plaindocs]

At will, I think. It is a pretty loose affair.

[baggerspion]

OK, I've finished CRUDing all the basic tables in the DB, including support for: tags (stored as JSON, per submission) and talk states (Draft -> Submitted -> Reviewed -> Rejected / Accepted by default). I am going to move on with Issue #25 before moving on with this feature dump.