Plots2: Weed out issues in the Candidate List that have already been worked on.

Created on 19 Apr 2021  ยท  7Comments  ยท  Source: publiclab/plots2

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open-source software!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you ๐Ÿ’

If you have contributed before, consider leaving this one for someone new and looking through our general help wanted issues. Thanks!

๐Ÿค” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

๐Ÿ“‹ Step by Step

  • [ ] ๐Ÿ™‹ Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

  • [ ] The aim of this Issue is to weed out issues that have already been fixed in the Candidate for FTO list on the PublicLab website. Below is how to do it:

  • [ ] Go to the Publiclab website

  • [ ] Scroll to the Candidates section.
  • [ ] Go through the list to find issues that have been fixed by reading through the issue thread.
  • [ ] If fixed, write down the issue number here, as a comment
  • [ ] ๐Ÿ Done Ask in comments for a review :)

Since no code is being changed, we don't need to create a pull request for this issue. We just need to weed out the fixed issues for the FTO candidate list.

See this page for some help in taking your first steps!

Please keep us updated

๐Ÿ’ฌโฐ - We encourage contributors to be respectful to the community and provide an update within a week of claiming the first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

๐Ÿ”—- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

๐Ÿ‘ฅ- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

๐Ÿค”โ“ Questions?

Leave a comment below!

discussion

Most helpful comment

@willow19 ,hi ,yes go ahead ๐Ÿš€๐Ÿ’ช๐Ÿ™‚๐Ÿ‘.
Also the candidates list isn't on the publiclab website , it's here .
Scroll down till you see ๐Ÿ‘€๐Ÿ‘€ the Candidates heading ,there are issues there that have already been fixed.
All you have to do is;

  • ๐Ÿ•ต๏ธโ€โ™€๏ธ look for fixed issues
  • ๐Ÿ“ note down their issue's number on this PR.
  • โ˜‘๏ธ When done tag @RuthNjeri ,@cesswairimu and @jywarren or any other mentor you know.

All 7 comments

@TildaDares , does this sound interesting for you to work on?

@Elukoye can I try?

Also I do not see any issues under 'candidates' on the Publiclab website. Should I instead look for the issues with label FTO here?

@willow19 Yeah you're right. You should look under the issues section.

@willow19 ,hi ,yes go ahead ๐Ÿš€๐Ÿ’ช๐Ÿ™‚๐Ÿ‘.
Also the candidates list isn't on the publiclab website , it's here .
Scroll down till you see ๐Ÿ‘€๐Ÿ‘€ the Candidates heading ,there are issues there that have already been fixed.
All you have to do is;

  • ๐Ÿ•ต๏ธโ€โ™€๏ธ look for fixed issues
  • ๐Ÿ“ note down their issue's number on this PR.
  • โ˜‘๏ธ When done tag @RuthNjeri ,@cesswairimu and @jywarren or any other mentor you know.

@RuthNjeri can you please have a look at the list below. I need help with the 'Need Confirmation' list to be sure they are done. I have given brief comments on all open items in the 3rd portion 'Overview on all open items'

Done

  1. 395 - done in PR 424
  2. 71 - done in PR
  3. 4624 - done alongwith this 4594 is done too
  4. 108 - done in PR
  5. 3865 - done
  6. 3861 - done , there are additional tasks which can be made out of this
  7. 3549 - done in PR
  8. 6391 - has been broken up into FTOs 6834 (closed) and 8587 (closed) - done

Need confirmation

  1. 69 - seems done, @jywarren can you please confirm if this can be closed
  2. 3513 - not sure if this is done. e.g. PR 9384 has media demo-ing new feature
  3. 3460 - seems done, no more work seems pending
  4. 3458 - seems done - looks more like guidelines than a task

Overview on all open items

  1. 9533 has been split up into 9535 and 9539. If both of those are solved, should we mark 9533 as done?
  2. 8731 - not apparent that it has been solved
  3. 1757 - not solved
  4. 7798 - does not seem solved
  5. 1569 - a volunteer wants go ahead
  6. 315 - has a linked break-me-up task 450 - if 450 is broken up we'd have converted this candidate into an FTO
  7. 310 - many volunteers, but can't see the main guy assigned
  8. 1355 - not solved
  9. 284 - has an open PR but no activity there
  10. 574 - not done
  11. 879 - some bugs have been reported for this one. Can some of them be converted to FTOs?
  12. 178 - not done
  13. 135 - waiting on @jywarren to review PR
  14. 4178 - open, a volunteer needs go ahead
  15. 4092 - not done
  16. 3523 - not done

Wow! Thanks for going through all of those @willow19. I think I noticed that there is a stale bot that marks an issue as stale and closes issues that do not have any activity for a long time. I have seen that the stale bot has marked some issues as stale in the past.

The Done list you have shared is very useful, I have closed https://github.com/publiclab/community-toolbox/issues/395, https://github.com/publiclab/community-toolbox/issues/108, and https://github.com/publiclab/plots2/issues/3549

I will revisit the list again tomorrow and see what I can update, thanks again @willow19 โค๏ธ

@willow19 Feel free to pick up another first-timer issue, it seems like this one will be more of a discussion

Thanks @RuthNjeri , sure I'll pick up another issue. Thanks again for the appreciation!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jywarren picture jywarren  ยท  3Comments

grvsachdeva picture grvsachdeva  ยท  3Comments

first-timers[bot] picture first-timers[bot]  ยท  3Comments

RuthNjeri picture RuthNjeri  ยท  3Comments

grvsachdeva picture grvsachdeva  ยท  3Comments