Skip to content

New Filter that only Admins can apply to projects - but available to all when browsing projects #164

Open

Description

@rmcmillen50

As a:

  • Code for Philly organizer
  • Interested in helping new volunteers find projects

I want

  • A new "Volunteers Wanted" filterable project atribute created
  • That is usable when anyone browses the site,
  • but can only be applied to projects when an Admin chooses to do so.

So that

  • new members can find projects that are actively interested in onboarding new volunteers
  • and that Admins can verify/validate projects are in fact "ready" to receive and onboard new volunteers

Activity

  1. aharley40 commented on Mar 9, 2017

    @aharley40
    Contributor

    @rmcmillen50 I don't think we could implement this before finding solutions to #123.

    • Do we already have mockups/user stories for a project-member-management page?
      • If yes, could you send them over?
      • If no, how about the following:
        • List similar rounded profile images with names on page titled "Members"
        • Elements vertical in order include:
          • Circular Photo
          • Name
          • Role
          • Status dropdown(Requested, Maintaining)
            -We'll put a save button where "Edit Project" goes. It becomes clickable if data has changed
            -Additionally, if the user scrolls below the fold, a fixed menu and save button will appear on screen.
  2. themightychris commented on Mar 21, 2017

    @themightychris
    Member

    I feel like a simple on/off "volunteers wanted" might not go far enough to be useful, check out the "project needs" column in the feature roadmap which is an extension of this idea: https://github.com/CodeForPhilly/laddr/projects/1

  3. rmcmillen50 commented on Mar 22, 2017

    @rmcmillen50
    Author

    @themightychris - I don't disagree, but I want to learn our way into this. Goal number 1a is to let users know which projects are actively seeking help. Goal 1b -from an internal admin perspective - is to control that value so that we validate that projects are ready and able to really solicit for new volunteers. This speaks to our "validated project" status that Dawn and I want to experiment with.

    In the short term, exact volunteer needs and jobs can be continued to be inferred by the project team's issues/trello board + existing tags that describe what tech is being done. Let's be honest, new volunteers that are able and ready to make a contribution won't have issues determining what tech skills are needed to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions