search

GSA / code-gov

An informative repo for all Code.gov repos
Other
266 stars 65 forks source link

Allow Help Wanted labels to be used to specify skillset required #27

Closed jordangov closed 5 years ago

jordangov commented 6 years ago

Expected Behavior

Right now when looking at the "Help Wanted" issues it seems to be pulling the "language" from the repo directly. I would like to have the ability (as an option) to override this language with another label. This would allow people reviewing issues to say "only show me ones that are CSS because I'm a designer".

Current Behavior

Right now developers can't specify that an issue is only JS, or only HTML in the "language" field.

Possible Solution

Allow new labels to be harvested, specifically something like: [skillset] javascript or [skillset] graphic design

DanielJDufour commented 6 years ago

Hi, @jordangov . Thanks for the feedback! We're definitely always looking at ways to improve the help wanted experience. I think skillset could definitely make it easier for people to find tasks to contribute to. But the challenge would be to get enough people to add this skillset label...

After a few months of trying to get help wanted tasks and speaking with folks who have tried to tackle the same problem as us, we were left with the conclusion that we bit off more than we could chew with the first iteration of help wanted. We're currently focused on providing a MVP of the help wanted page that requires minimal curation and manual labeling.

After we get more participation from agencies and a record of substantial contributions, we'll be able to revisit how to enhance the experience with new labels like skillset. In other words, we're just not there yet.

Personally speaking, I'd love for us to set up an auto-tagging system with Latent Semantic Indexing. For example, if someone manually labels 5 issues with [skillset] graphic design, an LSI system would be able to find and all the other issues related to "graphic design". (To be clear, I'm suggesting the auto-labeling would just be to enhance the search on our end. It would not affect that source repos themselves.)

Additionally, (still personally speaking), I'd love it if someone created a tool that auto-matched people with federal/civic tasks based on their GitHub profile. Or maybe a system that sends an email every month suggesting an issue one could pick up.

Anyway, the future is bright... happy to discuss more :-)

jordangov commented 6 years ago

Bright future indeed! But I understand the need to step back and re-evaluate. Feel free to mark this issue as "nice to have, but..." or whatever makes sense.

DanielJDufour commented 5 years ago

Hey, @jordangov . I'm moving this code-gov because this repo is about to be archived (new front-end repo is code-gov-front-end) and it's a higher level discussion that affects both back and front-end.

saracope commented 5 years ago

Closing this as it's not in our current roadmap. Can revisit in the future.

jordangov commented 5 years ago

:sadpanda:

Why can't we add this to the roadmap? How will we know that this is being tracked in the future if the issue is closed?