You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello :-)
Every now and then I look for something I can help with in NewPipe (e.g. a bugfix, an issue discussion...), but it's difficult to find an issue to focus on, since almost none of them have labels. I think labelling every issue (with bug, enhancement and so on) would benefit the project, making them simpler to navigate through and more welcoming for newcomers.
When I was a newcomer myself (some months ago), it took me ages to find something simple I could work on in order to familiarise with the codebase: there are not many issues available in the "for beginners" section.
For the reasons stated above I would like to get the permission to classify the issues. I would go through all of the open issues and add a label. The permission to close duplicates / already fixed ones would be appreciated, too, but I think that's asking too much since I've not been into the project for many months :-)
The text was updated successfully, but these errors were encountered:
Hello :-)
Every now and then I look for something I can help with in NewPipe (e.g. a bugfix, an issue discussion...), but it's difficult to find an issue to focus on, since almost none of them have labels. I think labelling every issue (with bug, enhancement and so on) would benefit the project, making them simpler to navigate through and more welcoming for newcomers.
When I was a newcomer myself (some months ago), it took me ages to find something simple I could work on in order to familiarise with the codebase: there are not many issues available in the "for beginners" section.
For the reasons stated above I would like to get the permission to classify the issues. I would go through all of the open issues and add a label. The permission to close duplicates / already fixed ones would be appreciated, too, but I think that's asking too much since I've not been into the project for many months :-)
The text was updated successfully, but these errors were encountered: