cncf/clotributor

Discover great opportunities to become a Cloud Native contributor

clotributor's Issues

tag each work item with either "bug fix" or "enhancement"

Consider adding some stats

Add projects to clotributor

How do we add projects to clotributor?

I've added a 'help wanted' label to Vitess' vitessio/website#1169 issue, and it is open and unassigned, but I can't find it in the clotributor search.

Am I missing something? Do projects need to be added to a list to be crawled?

not all projects in the CNCF Sandbox are listed

How often is the CNCF Sandbox list updated? I am a maintainer for KubeStellar. We we were granted sandbox in Dec. 2023. I dont see us listed in the search criteria.

tag each work item with "easy"/"medium"/"hard" or something like that.

Possibility to add TAG repos to CLOTributor

How can I add a TAG's repo to CLOTributor?

It would be nice to list this issue there for example: cncf/tag-contributor-strategy#140

Ship v1.0 (and git-tag it)

I think clotributor is stable enough for a v1.0 with the embed feature shipped.

Add a mentor's name to each work item

It will be great to add a mentor's name to each work item so that the new contributor knows whom to ask for guidance/help.

Filter quickly for issues involving docs

We should find a way to easily filter issues for docs related projects + issues.

I guess this can just be a "docs" issue label but maybe there's something more clever we can do

Feature request: Badge for GH repo README

It would be great to have a badge one could put in their README file that lists the number of issues listed for the project on CLOtributor.

Embed feature

It would be cool to have an "embed" feature where a project like AWSF or CNCF can "embed" a page on their website which lists all their clotributor issue

contribute.cncf.io could have a simple embed
if contribute.aswf.io existed they could have one too

Be able to filter by issues that have a "willing to mentor"

Essentially we should be able to filter and surface issues from community members who are willing to put in EXTRA mentoring time. This should be some type of label "mentoravailable"

Be able to filter by project

We can filter by foundation, we should be able to just filter by project

Proposal: Add Color to Issue Labels for Tech Stacks on Clotributor

Hello Clotributor team,

I'm reaching out as a participant of the Zero to Merge cohort, under the guidance of Taylor Dolezal (@onlydole ).

I propose enhancing Clotributor by adding color to issue labels corresponding to tech stacks (e.g., React, Angular). This simple visual improvement would make issue selection more intuitive and user-friendly.

I'm eager to contribute to this if it resonates with your vision. Looking forward to your thoughts.

Best regards,
@MaheshMoholkar

Add a link to the project's contributor guide if the guide is available

In addition to the project link, a link to the project's contributor guide will help the new contributor ramp up and deliver the design/code properly.

Be able to filter by difficulty

It would be nice to filter by difficulty of issue

maybe we can have a label standard like "level" or "complexity"

"level/1"
"level/2"
"level/3"
"level/4"
"level/5"

Where 1 is easy and 5 is difficult

Feature Request: Functionality to view or filter whether a pull request (PR) has been created for an issue

Issue:

Currently, there is no functionality available to view or filter whether a pull request (PR) has been created for an issue.

Problem:

There are numerous issues that meet the following criteria: labeled as "help wanted," in the state of "OPEN," unassigned, and updated within the last year. However, many of these issues have been resolved by PRs that have not yet been merged. Consequently, these issues remain open without an assignee. Additionally, some issues have PRs linked to them, indicating that work is in progress.

This issue arises due to contributors opening PRs without assigning the related issues to themselves.

Desired Outcome:

It would be beneficial to have an option to filter the results and determine whether a PR has been linked to an issue. This addition would greatly assist in identifying unresolved issues and enhance the filtering capabilities.

Feedback from ASWF

From @jfpanisset

• The top level page https://clotributor.dev/ could use a few more hints as to how to search for a specific foundation, or until there are too many foundations, maybe have tiles to easily navigate to a foundation's issues? Right now just entering "aswf" in the search box doesn't find anything.
• Once you navigate to a search result, for instance https://clotributor.dev/search?foundation=aswf&page=1 it might be good to still have something in the banner for the page reminding you where you are / what the tool does?
• Don't know if this is feasible, but would be great to get some kind of stats such as how many people read an issue / commented on an issue that got to it via this tool

Be able to filter by programming language

Might need to use more than just Clomonitor

Many subprojects are missing from Clotributor because it uses clomonitor to pull in CNCF projects which skips over most of the sub-projects.

What should be the the route to take here, have it so every project needs to manually request it be added to clomonitor?

See these two tickets for reference when I asked for some subprojects to be added:
cncf/clomonitor#1503
cncf/clomonitor#1504

Highlight projects that want maintainers in some way

The use case is here: projects should be able to specify that they are interested in attracting more maintainers

This probably is some type of github issue projects can create with a label specifying they'd like new maintainers that we can highlight in some special way and feature it.

Be able to filter by project

right now, if I type "meshery" or "istio" in the search box, I get a mix of issues

Ideally I'd like to have a search query like "project: istio" and it only have things from the istio org

Istio not lised in the projects

I cannot see Istio listed down in the projects list to apply as filter. Any specific reason?

https://clotributor.dev/search?page=1