Change emoji on weekly-check-in

[cesswairimu]

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!

• 📝 Update the file https://github.com/publiclab/plots2/blob/main/.github/ISSUE_TEMPLATE/--weekly-check-in.md (press the little pen Icon) and edit the line as shown below.

• Change line 2 from name: "\U0001F41B Weekly Check-in" to name: ":loudspeaker: Weekly Check-in"

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

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

$DIFF

• 💾 Commit your changes

• 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• 🏁 Done Ask in comments for a review :)

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a 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!

[cesswairimu]

Reserved for @aissshah

[Suhas1998]

Hi, Im first time trying to contribute. Is this issue still open for me to work on?

[cesswairimu]

Hey @Suhas1998 , this is reserved for @aissshah, adding your name here #7683 and will ping when we get a issue for you. Thanks

[aissshah]

Hi @cesswairimu very happy to work on this!
Thank you so much

[IC1101Virgo]

Hello @cesswairimu can I work on this? 😃

[cesswairimu]

Hi @aissshah, we free-up FTOs if a week goes by with no updates or replies because we assume they have been abandoned. This is to give other contributors a chance, as these types of issues are high in demand.
If you'd like to try again with a new FTO, we welcome you to!

Hi @IC1101Virgo you can go ahead and work on this. Thanks all

[aissshah]

Ok @cesswairimu thanks for letting me know.

[IC1101Virgo]

@cesswairimu Thank you! 😄

[IC1101Virgo]

@cesswairimu Hello 😃 I have made the PR 💃
Please review and tell me if something needs change 🙉
Thank you!