[BUG] Essential fixes list on the community events dashboard

[RiyaMathew-11]

Describe the bug

Referenced from this discussion: #324

• [x] Make event publishing workflow connected to status changes

  • Proposed status labels: Draft, Live, Concluded, Cancelled
  • Event will be published if the status is live/concluded

• [ ] Standard routing guideline for event links

• [ ] Fix typos and mark mandatory fields needed.

• [ ] A lead can add or remove members, but do not have the provision to edit roles.

• [ ] The drop down for select members to add - potentially gives a list of all website users - this isnt a good practice, explore to see if this can be a data field and not a drop down

  • The username/email can be entered - if the user exists, get's added else gives an error alert - User does not exist

• [ ] Cross-verify removal permissions - the volunteer seem to be able to remove lead (PS: could be because of my desk access)

• [ ] The event description field needs to be bigger - to give detailed descriptions if needed - tried one for Kochi meetup:

  • The <br/> tags weren't working on the event page
  • Would be good if we can make the field as the rich text editor

(PS: Made it the needed way from desk later)

• [ ] The session of event dashboard logs out too fast - it got signed out within 10 min of signin and then had to login again.

[harshtandiya]

The drop down for select members to add - potentially gives a list of all website users - this isnt a good practice, explore to see if this can be a data field and not a drop down The username/email can be entered - if the user exists, get's added else gives an error alert - User does not exist

We are not changing to this, as I don't see a problem with the current thing? There's anyway going to be a public page showing all the foss profiles in future, and hopefully a way to "Follow" or something of similar lines.

Cross-verify removal permissions - the volunteer seem to be able to remove lead (PS: could be because of my desk access)

A team member can remove anyone other than himself. Moreover, this feature may be too much unwanted complexity. Not changing this atm.

[RiyaMathew-11]

I don't see a problem with the current thing? There's anyway going to be a public page showing all the foss profiles in future, and hopefully a way to "Follow" or something of similar lines

The concept of public profile listing and follow feature is different and has the potential to be a valuable feature.

• but this is an organiser's dashboard

• The selection list that is being visible by logic would have all the users in it ? even users who choose not to make their profiles public ?

• There could be this near to alternative:

  • The user list shouldn't be coming abrupt initially.
  • As the name is being searched, a shortened list of matching names can be visible in the drop-down, making the checking process smoother.

We could ideate better on this I think. @rahulporuri please share your thoughts too?

[RiyaMathew-11]

A team member can remove anyone other than himself.

I am thinking slightly different here - the lead should be having the entire admin access. The workflow IMO should be other way around.

• A team member should be able to leave a volunteering team on their own - why would they have the permission to remove someone else - only the community lead or some one of a maintainer status should do it ?