interested / contact button

[vincent-peugnet]

When an user click on the "ask for contact" button, this should send some more preçise info related to the sharable.

should it be :

• some added contact info (email, phone, matrix, adresse, coordinate...)
• a new text bock containing text to help the user access the sharable
• both ?

Some sharable does not seems to need this contact logic. For example, thoses where managers are not responsible for it, this seems less acurate.

So, there should be a choice indicating how it need or not to be contacted :

1. don't need contact before accessing
2. auto contact, info are send automaticaly
3. manual contact, managers have to check manualy user profiles asking for it, and send them contact individualy
4. never send contact, only user needing access send contact by clicking the button, managers only can join the user using their contact infos.

There's an ideological problem with stratey number 3 and 4, as it add some judgment by the manager upon the user.
Maybe this should as well be a global parameter...

[vincent-peugnet]

This four methods have there interest, but maybe there could be a global parameters defining wich ones are authorized.

Something like :

parameters:
    AuthorizedContactMethods: [1, 2, 3, 4]

[vincent-peugnet]

Method 1 create a bunch of questions :

• this means every contactable managers have there contact info published
  • this method could deactivates the contact system
• ? I don't remember this one

Do user always need to be interested before validating an sharable ?

This could only be for methods 2 and above. Allowing a very easy type of sharable with Method 1, less sensible more like GeoCaching. That sound good.