Add a new chapter on speakers, relation and membrane

[pbauer]

Add a chapter that refactors parts of the website once it went online. The plan is to use a speaker-type as members using membrane.

Topics:

• Refactoring of code and functionality
• Relations II (automatic relations)
• Members as content

Tasks:

• Create a new content-type 'speaker' chapter
• Use the behaviors from dexterity.membrane to create members from speakers
• Enable self-registration as speakers
• Use a subscriber to automatically create a relation to the speaker on creation of a talk
• Remove speaker-fields from ct talk (the data in the old fields will still exists as attributes on the instances)
• create speaker-view
  • show their talks if they are published
  • show review_state of talks (only for spakers)
• modify talks-view and talks-list to show a link to the speaker-page

Add migration-steps

• Create speakers from the information stored on talks
• Link these speakers to their talks
• Send membership-emails to these newly-created speakers

[pbauer]

We tried to implement this but ran into a couple of issues that led us to table that for now

Mostly, self-registration does not work well with membrane . A approach was to open ++add++speaker upon registration. That would require:

• Add a folder where anonymous has the permissions Add portal content and Add speaker (via a placeful workflow or manage_access or a bustom type with a custom workflow)
• Change the link to register-action link to /Members/++add++speaker or similar

The problem with this are:

• Registration looks like a normal add-form and not like a registration-form. Could be solved by Custom form title and using a redirect after adding with immediate_view.
• The user is not forced to confirm the registration by mail
• Speaker cannot change his setting. Solution would be to ping the action personal-preferences to the edit-form of the current speaker
• Password is no required field in IProvidePasswordsSchema. Could be solved by overriding the schema

Alternatives:

• Add Membrane-Speaker with subscriber after self-registration
• Use default MemberdataSchema