Denying project membership requests

Open
#1,005 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start at the project page's Join Project flow and trace the owner/admin membership-request denial path. Confirm how the requester sees membership status and how denial is submitted; done means denial requires a reason and the requester receives a clear message explaining the decision.

Written by the indexing model from the issue text.

Description

Problem

Currently, when a user clicks "Join Project" on the project page, it sends a membership request to the owner/admin of the project. The owner/admin of the project can approve or deny the request. If the owner/admin denies the project, the user who requested to join won't receive a message telling them so. This could lead to a few situations.

  1. Nothing.

  2. The user asking to join will assume that the request didn't go through, so they request again, adding noise to the project owner/admin's request feed. The project owner/admin could deny again and the same process could repeat. Or, the project admin/owner will simply keep the request in their inbox, not accepting, not denying which would give the user a "membership pending" under their profile picture every time they visited that project.

Possible Solution

When the project owner selects "deny", they will be asked to give a reason before they are allowed to actually submit the denial. The reasons could be populated and selected in a drop down menu. Potential reasons could be: Too many contributors with similar skills, not enough work for skill set, other, not taking on new coders, etc.

Adding the extra step could also decrease accidental denying, where the project owner/admin meant to click approve, but instead hits deny.

Dominant language
JavaScript
Stars
120
Forks
75
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from code-corps/code-corps-ember

All issues in code-corps/code-corps-ember

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.