Requirements:

• Talk.java gets 2 extra non-planning-variable fields: publishedTimeslot and publishedRoom.
  • they can be null, they usually are
• The spreadsheet "talks" tab gets 2 extra columns to fill them in.
• Solving does not mean publishing!
  • clicking the solve button does not affect the published fields. Nothing does.
  • Either the user copy pastes them from the timeslot/room fields in the excel to publish
  • Or better yet, we add a "publish" button in the swing UI
• Turn the HardSoftScore into HardMediumSoftScore
  • Add a medium constraint that if publishedTimeslot != null, the timeslot must be the same. This implies we'll only change the timeslot if we have other way to avoid breaking hard constraints.
  • Add a soft constraint with weight 1 that publishedRoom must equal room to avoid unneeded disruption

Once we have votes per talk, we can add a constraint to give rooms with more votes a bigger room. (separate jira - multiple ways to formalize - let's discuss)