Skip to content

Apply a Guiding Defuault Filter to the Explore Projects Page for at Least Beginer Contributors #7087

@Pseudorandom-Pseudonym

Description

@Pseudorandom-Pseudonym

Is your feature request related to a problem? Please describe.

When starting out as a contributor it can be quite overwhelming. As more experienced contributors and project creators/managers we should be guiding them toward projects they are motivated to contribute to and are of an appropriate difficulty level for them. When I was starting out I'd just lock a task of a projects to see if I could make heads or tails of the imagery.

Currently there are over 1,000 projects published and this can easily lead to decision fatigue as sometimes only having more than 6 options can already become overwhelming. They will not even have the relevant permissions to contribute to some of these projects, as the permissions will be restricted to above a certain level, or to specified team(s).

This makes filtering essential. Applying only the 2 filters I suggest reduces this to ~ 200 projects. Implying that the vast majority of projects shown to beginers are likely poor options and cause a significant time sink. Why should the assumtion be that beginers would be able to effectively contribute to moderate+ difficulty projects, or validate the contributions of others?

Describe the solution you'd like

  • The filters "easy and projects to map" to be applied by default for users of at least beginer level.

  • The map view to be enabled by default for them too as this will help them select projects in their areas of interest, since you can only currently filter by country which may lead to 0 results, even if there are projects nearby.

Contributors should be able to overide these default filters, if they wish and choose their own. Clearing filters is easy to do with just one button.

Filtering by default for projects which align with the interests users submit on the settings page should also be explored.

The ideal sort by value (if one exists) should be explored. I have a few ideas for this but it may be more complex.

perhaps certain key words in project titles should be filtered like e.g. "mapathon" if this means that a contributor will be unlikley to have their contributions validated etc. unless they participated in some event i.e. that they are more likely to have a worse experience.

Describe alternatives you've considered

There have been discussions and ideas of having beginer friendly projects make an apperance on the front page or marking them with HTML colours etc.

Additional context

Image Fig.1. Number of Published Projects with no other filters applied

Image Fig.2. Number of Published and easy and to map Projects with map view enabled

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