Identify open issues that has to do with design, of the projects included in the library

[ifeneris]

Is your feature request related to a problem? Please describe.
Designers visiting the platform are looking for ways to contribute, and they can find projects in the "projects" library, but:

• Some projects may not have open design issues at that time. Designers will visit them but find nothing, leading to frustration.
• They cannot have a view of open issues across projects. They must visit each one and search for issues, leading to friction.
• Designers with no prior knowledge of OSS project structures may find the process of searching for suitable design tasks overwhelming.

Describe the solution you'd like
We are looking for a technical way to identify open tasks that need design for those projects, automatically. As each project may follow a different taxonomy of tags, this is not trivial. We can either search by similarity to some specific keywords, or look for what tag is mentioned in the ".design" documentation as the used "design" tag and search for that, or use advanced (AI) solutions to run the cognitive tasks of analyzing the used tags and identifying the design tasks.

This technical way will be the enabler for solutions like

• Providing indicators in our projects of how many issues are available on each one
• Providing lists of available design tasks to users, across projects
• Provide more advanced categorization and filtering options, so that users can locate suitable issues for them, easily

[ifeneris]

We can start simple, by just checking the tags that contain "design", "ux", "ui", and also the tag "good first issue". This solution has of cource limited accuracy and may give false positives, but its a low-effort start in order to build some functionalities on that, like:

• On each project on "Projects" page, and on each project page, show indicators of open design issues, and identified design tags for this project
• Offer a new "Find Issues" page to users, providing a list of available open design issues across projects, along with searching and filtering functionality

Then, as this technical solution is becoming better, the accuracy will improve and that functionality will expand.

I am opening the issues #61 and #62 to design and implement new or enchanced functionalities, based on this technical enabler.

[fivenp]

I do agree with this on the long run a lot. I think right now it's already super hard to even have "some" sort of guidelines for designers in the .md file of a project.

Small/Mid OSS projects typically do not have a lot of structure around and there is no real process in tagging / issue creation / etc

Maybe we can start educating and most importantly handhold projects to create a basic structure for their project?