More first good issues #2228
Replies: 3 comments 6 replies
|
We would need at least 3 'good first issues' that we would discuss in our report and eventually pick a first, and if we fix that we would pick a second etc. I do see three open good first issues, but one is from very long ago which doesn't fill us with confidence we will be able to fix it before the end of the course |
|
hi! yes the list of issues is partly a bit of a mess. Do you have some preferences on what you'd like to do (python, react, flutter)? |
|
alright, will try to mark / write some this weekend! |
|
BTW, which ones did you find? |
|
#2104 should also be well doable |
|
But as I said we'd need at least like 3 tickets to be marked as good first issues, and then we would like to look into them and choose the best ones to start with. |
|
alright, I have a few, all these should be pretty self-contained: wger-project/react#1210 If you have questions or need anything just ask me or ping me on the discord server. (I'll still do another round tomorrow and mark some more) |
Uh oh!
There was an error while loading. Please reload this page.
Hello! Me and my team need to pick a project for a university (Master's) course, for which we need to contribute to an OSS. We are really interested in wger since we like the concept of the app and looking through the open issues these look like they're definitely things we would be able to pick up, but the course has a requirement that we need to start with and propose to fix issues with the label 'good first issue'. We were wondering if it would be possible to classify more open issues as good first issues in the coming week, so that we can propose this project to our course.
We hope we can start contributing to this project, thanks in advance!
Luca van der Wijngaart
All reactions