Members can leave a testimonial

[despo]

Description of the issue 📄

A member that has attended more than X events and has no testimonial associated with them can leave a testimonial

• Add controller and related view so that a new member can add a testimonial
  • Add some text to inform members that any testimonial along with their name and profile picture might be used for the promotion of codebar (website, prospectus, etc)
  • Only allow for one testimonial per member
  • Once testimonial is created the page should no longer be available to member (or maybe a read-only version only can be available)
• Extend testimonial model to have public boolean field
• Add rake task to update existing testimonials to public
• Add admin/testimonials#index page
  • List all testimonials, with member name, text, current status and actions columns
  • Enable admins to toggle the status
  • Only available to users with the admin role
• Update main page testimonials query to only retrieve public testimonials - https://github.com/codebar/planner/blob/master/app/controllers/dashboard_controller.rb#L17

To do 📋

• Claim this issue (comment below, or assign yourself if you are part of the codebar org)
• Fork and clone the repository
• Update the relevant files. Follow the steps to fix section in this issue.
• Commit your changes as one commit. Use the title of this issue as your commit message
• Submit a pull request
• Mention this issue in the PR description by including it's number
• Have your pull request reviewed & merged by a codebar team member

[claracavalcante]

I would like to claim this.

[matyikriszta]

@claracavalcante sounds good, please go ahead with this issue

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

Closing as stale.

[matyikriszta]

@despo I've been working on this issue and there are 3 questions that need clarifications:

1. How many events should a member have attended to get the prompt to fill out a testimonial? I was thinking maybe 10 but happy to go with a different amount.

2. How should the review process for testimonials look like? I'm thinking instead of a boolean public field we need an enum with at least 3 states: published, unpublished (or hidden/rejected) and in review. This way admins can be notified when a testimonial needs review and set it to either published or hidden (or rejected? Not sure what the terminology here should be). Similarly to how jobs work.

3. Should a member be able to edit a testimonial? E.g. if there's a typo etc.

CC @KimberleyCook would love to hear your thoughts as well.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

Closing as stale.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

Closing as stale.