Update issue templates for mapknitter

ananyaarun commented 4 years ago

Please note we are preparing to participate in Google Code-in, and have reserved this issue for GCI participants - but we'd love to have your help with another one! Please check out https://code.publiclab.org to see more.

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

update the issue templates in the repo present in .github folder of home directory to follow the structure and files as present in plots2 repo.

Link : https://github.com/publiclab/plots2/tree/master/.github/ISSUE_TEMPLATE Reference PR : https://github.com/publiclab/plots2/pull/5967

[ ] 💾 Commit your changes
[ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

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.
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!

SidharthBansal commented 4 years ago

Published

PeculiarE commented 2 years ago

I was just about to create an issue on improving the issue templating system on MapKnitter. What we currently have is not as comprehensive as that of Plots2 and Infragram (no first-timer-only or feature-request templates on the interface, no automatic assigning of bug label to bug report templates, no weekly check-in template etc).

But fortunately, in the process of exploring, I discovered a similar issue has already been raised here.

@cesswairimu, @jywarren, @TildaDares....could I please work on this? Or is it straightforward enough to be assigned to a first-timer?

Thank you!

TildaDares commented 2 years ago

Hi @PeculiarE, I think we can create FTOs for that. Thank you!!

PeculiarE commented 2 years ago

Alright @TildaDares...thank you. Will get started on doing that

publiclab / mapknitter