Git First Timers

There are lots of people that need help and want to make our community of software development open and inclusive.

This list displays the top 100 Open Issues with the 'first-timers-only' tag on Github.com.

That means this is a curated list of some of the best, most open, open source projects on the internet!

1 Lint App.css correctly

Find it on GitHub

Update src/App.css. See below

2:2 ✖ Expected indentation of 2 spaces indentation 3:2 ✖ Expected indentation of 2 spaces indentation 7:2 ✖ Expected indentation of 2 spaces indentation 8:2 ✖ Expected indentation of 2 spaces indentation 9:2 ✖ Expected indentation of 2 spaces indentation 10:2 ✖ Expected indentation of 2 spaces indentation 20:2 ✖ Expected indentation of 2 spaces indentation 21:2 ✖ Expected indentation of 2 spaces indentation 22:2 ✖ Expected indentation of 2 spaces indentation 23:2 ✖ Expected indentation of 2 spaces indentation 27:2 ✖ Expected indentation of 2 spaces indentation 28:2 ✖ Expected indentation of 2 spaces indentation 29:2 ✖ Expected indentation of 2 spaces indentation 39:2 ✖ Expected indentation of 2 spaces indentation 40:2 ✖ Expected indentation of 2 spaces indentation 41:2 ✖ Expected indentation of 2 spaces indentation 45:2 ✖ Expected indentation of 2 spaces indentation 46:2 ✖ Expected indentation of 2 spaces indentation 47:2 ✖ Expected indentation of 2 spaces indentation 48:2 ✖ Expected indentation of 2 spaces indentation 52:2 ✖ Expected indentation of 2 spaces indentation 53:2 ✖ Expected indentation of 2 spaces indentation 54:2 ✖ Expected indentation of 2 spaces indentation 58:2 ✖ Expected indentation of 2 spaces indentation 59:2 ✖ Expected indentation of 2 spaces indentation 60:2 ✖ Expected indentation of 2 spaces indentation 61:2 ✖ Expected indentation of 2 spaces indentation 62:2 ✖ Expected indentation of 2 spaces indentation 66:2 ✖ Expected indentation of 2 spaces indentation 67:2 ✖ Expected indentation of 2 spaces indentation 68:2 ✖ Expected indentation of 2 spaces indentation 69:2 ✖ Expected indentation of 2 spaces indentation 70:2 ✖ Expected indentation of 2 spaces indentation 71:2 ✖ Expected indentation of 2 spaces indentation 72:2 ✖ Expected indentation of 2 spaces indentation 73:2 ✖ Expected indentation of 2 spaces indentation 77:2 ✖ Expected indentation of 2 spaces indentation 78:2 ✖ Expected indentation of 2 spaces indentation 82:2 ✖ Expected indentation of 2 spaces indentation 86:2 ✖ Expected indentation of 2 spaces indentation 87:2 ✖ Expected indentation of 2 spaces indentation 88:2 ✖ Expected indentation of 2 spaces indentation 92:2 ✖ Expected indentation of 2 spaces indentation 93:2 ✖ Expected indentation of 2 spaces indentation 94:2 ✖ Expected indentation of 2 spaces indentation 98:2 ✖ Expected indentation of 2 spaces indentation 99:2 ✖ Expected indentation of 2 spaces indentation 100:2 ✖ Expected indentation of 2 spaces indentation 101:2 ✖ Expected indentation of 2 spaces indentation 102:2 ✖ Expected indentation of 2 spaces indentation 103:2 ✖ Expected indentation of 2 spaces indentation 104:2 ✖ Expected indentation of 2 spaces indentation 108:2 ✖ Expected indentation of 2 spaces indentation 109:2 ✖ Expected indentation of 2 spaces indentation 110:2 ✖ Expected indentation of 2 spaces indentation 111:2 ✖ Expected indentation of 2 spaces indentation 112:2 ✖ Expected indentation of 2 spaces indentation 116:2 ✖ Expected indentation of 2 spaces indentation 117:2 ✖ Expected indentation of 2 spaces indentation 121:2 ✖ Expected indentation of 2 spaces indentation 122:2 ✖ Expected indentation of 2 spaces indentation 126:2 ✖ Expected indentation of 2 spaces indentation 127:2 ✖ Expected indentation of 2 spaces indentation 128:2 ✖ Expected indentation of 2 spaces indentation 132:2 ✖ Expected indentation of 2 spaces indentation 133:2 ✖ Expected indentation of 2 spaces indentation 143:2 ✖ Expected indentation of 2 spaces indentation 144:2 ✖ Expected indentation of 2 spaces indentation 145:2 ✖ Expected indentation of 2 spaces indentation 149:2 ✖ Expected indentation of 2 spaces indentation 150:2 ✖ Expected indentation of 2 spaces indentation 151:2 ✖ Expected indentation of 2 spaces indentation 161:2 ✖ Expected indentation of 2 spaces indentation 162:2 ✖ Expected indentation of 2 spaces indentation 163:2 ✖ Expected indentation of 2 spaces indentation 164:2 ✖ Expected indentation of 2 spaces indentation 165:2 ✖ Expected indentation of 2 spaces indentation 166:2 ✖ Expected indentation of 2 spaces indentation 167:2 ✖ Expected indentation of 2 spaces indentation 168:2 ✖ Expected indentation of 2 spaces indentation 169:2 ✖ Expected indentation of 2 spaces indentation 170:2 ✖ Expected indentation of 2 spaces indentation 171:2 ✖ Expected indentation of 2 spaces indentation 172:2 ✖ Expected indentation of 2 spaces indentation 176:2 ✖ Expected indentation of 2 spaces indentation 177:2 ✖ Expected indentation of 2 spaces indentation 178:2 ✖ Expected indentation of 2 spaces indentation 179:2 ✖ Expected indentation of 2 spaces indentation 180:2 ✖ Expected indentation of 2 spaces indentation 181:2 ✖ Expected indentation of 2 spaces indentation 185:2 ✖ Expected indentation of 2 spaces indentation 186:2 ✖ Expected indentation of 2 spaces indentation 187:2 ✖ Expected indentation of 2 spaces indentation 188:2 ✖ Expected indentation of 2 spaces indentation 189:2 ✖ Expected indentation of 2 spaces indentation 190:2 ✖ Expected indentation of 2 spaces indentation 194:2 ✖ Expected indentation of 2 spaces indentation 195:2 ✖ Expected indentation of 2 spaces indentation 196:2 ✖ Expected indentation of 2 spaces indentation 197:2 ✖ Expected indentation of 2 spaces indentation 198:2 ✖ Expected indentation of 2 spaces indentation 199:2 ✖ Expected indentation of 2 spaces indentation 200:2 ✖ Expected indentation of 2 spaces indentation 201:2 ✖ Expected indentation of 2 spaces indentation 205:2 ✖ Expected indentation of 2 spaces indentation 206:2 ✖ Expected indentation of 2 spaces indentation 207:2 ✖ Expected indentation of 2 spaces indentation 208:2 ✖ Expected indentation of 2 spaces indentation 209:2 ✖ Expected indentation of 2 spaces indentation 210:2 ✖ Expected indentation of 2 spaces indentation 211:2 ✖ Expected indentation of 2 spaces indentation 212:2 ✖ Expected indentation of 2 spaces indentation 213:2 ✖ Expected indentation of 2 spaces indentation 214:2 ✖ Expected indentation of 2 spaces indentation 215:2 ✖ Expected indentation of 2 spaces indentation 219:2 ✖ Expected indentation of 2 spaces indentation 223:2 ✖ Expected indentation of 2 spaces indentation 224:2 ✖ Expected indentation of 2 spaces indentation 225:2 ✖ Expected indentation of 2 spaces indentation 226:2 ✖ Expected indentation of 2 spaces indentation 227:2 ✖ Expected indentation of 2 spaces indentation 228:2 ✖ Expected indentation of 2 spaces indentation 229:2 ✖ Expected indentation of 2 spaces indentation 233:2 ✖ Expected indentation of 2 spaces indentation 234:2 ✖ Expected indentation of 2 spaces indentation 235:2 ✖ Expected indentation of 2 spaces indentation 236:2 ✖ Expected indentation of 2 spaces indentation 237:2 ✖ Expected indentation of 2 spaces indentation 238:2 ✖ Expected indentation of 2 spaces indentation 239:2 ✖ Expected indentation of 2 spaces indentation 249:2 ✖ Expected indentation of 2 spaces indentation 250:2 ✖ Expected indentation of 2 spaces indentation 251:2 ✖ Expected indentation of 2 spaces indentation 252:2 ✖ Expected indentation of 2 spaces indentation 253:2 ✖ Expected indentation of 2 spaces indentation 254:2 ✖ Expected indentation of 2 spaces indentation 258:2 ✖ Expected indentation of 2 spaces indentation 259:2 ✖ Expected indentation of 2 spaces indentation 260:2 ✖ Expected indentation of 2 spaces indentation 261:2 ✖ Expected indentation of 2 spaces indentation 262:2 ✖ Expected indentation of 2 spaces indentation 263:2 ✖ Expected indentation of 2 spaces indentation 264:2 ✖ Expected indentation of 2 spaces indentation 268:2 ✖ Expected indentation of 2 spaces indentation 269:2 ✖ Expected indentation of 2 spaces indentation 270:2 ✖ Expected indentation of 2 spaces indentation 271:2 ✖ Expected indentation of 2 spaces indentation 272:2 ✖ Expected indentation of 2 spaces indentation 273:2 ✖ Expected indentation of 2 spaces indentation 274:2 ✖ Expected indentation of 2 spaces indentation 278:2 ✖ Expected indentation of 2 spaces indentation 279:2 ✖ Expected indentation of 2 spaces indentation 280:2 ✖ Expected indentation of 2 spaces indentation 281:2 ✖ Expected indentation of 2 spaces indentation 285:2 ✖ Expected indentation of 2 spaces indentation 286:2 ✖ Expected indentation of 2 spaces indentation 287:2 ✖ Expected indentation of 2 spaces indentation 288:2 ✖ Expected indentation of 2 spaces indentation 289:2 ✖ Expected indentation of 2 spaces indentation 290:2 ✖ Expected indentation of 2 spaces indentation 291:2 ✖ Expected indentation of 2 spaces indentation 295:2 ✖ Expected indentation of 2 spaces indentation 296:2 ✖ Expected indentation of 2 spaces indentation 297:2 ✖ Expected indentation of 2 spaces indentation 298:2 ✖ Expected indentation of 2 spaces indentation 299:2 ✖ Expected indentation of 2 spaces indentation 303:2 ✖ Expected indentation of 2 spaces indentation 304:2 ✖ Expected indentation of 2 spaces indentation 305:2 ✖ Expected indentation of 2 spaces indentation 306:2 ✖ Expected indentation of 2 spaces indentation 310:2 ✖ Expected indentation of 2 spaces indentation 311:2 ✖ Expected indentation of 2 spaces indentation 312:2 ✖ Expected indentation of 2 spaces indentation 313:2 ✖ Expected indentation of 2 spaces indentation 314:2 ✖ Expected indentation of 2 spaces indentation 315:2 ✖ Expected indentation of 2 spaces indentation 316:2 ✖ Expected indentation of 2 spaces indentation 320:2 ✖ Expected indentation of 2 spaces indentation 321:2 ✖ Expected indentation of 2 spaces indentation 322:2 ✖ Expected indentation of 2 spaces indentation 323:2 ✖ Expected indentation of 2 spaces indentation 324:2 ✖ Expected indentation of 2 spaces indentation 328:2 ✖ Expected indentation of 2 spaces indentation 329:2 ✖ Expected indentation of 2 spaces indentation 330:2 ✖ Expected indentation of 2 spaces indentation 334:2 ✖ Expected indentation of 2 spaces indentation 335:2 ✖ Expected indentation of 2 spaces indentation 336:2 ✖ Expected indentation of 2 spaces indentation 337:2 ✖ Expected indentation of 2 spaces indentation 338:2 ✖ Expected indentation of 2 spaces indentation 339:2 ✖ Expected indentation of 2 spaces indentation 340:2 ✖ Expected indentation of 2 spaces indentation 341:2 ✖ Expected indentation of 2 spaces indentation 342:2 ✖ Expected indentation of 2 spaces indentation 346:2 ✖ Expected indentation of 2 spaces indentation 347:2 ✖ Expected indentation of 2 spaces indentation 348:2 ✖ Expected indentation of 2 spaces indentation 349:2 ✖ Expected indentation of 2 spaces indentation 350:2 ✖ Expected indentation of 2 spaces indentation 351:2 ✖ Expected indentation of 2 spaces indentation 352:2 ✖ Expected indentation of 2 spaces indentation 356:2 ✖ Expected indentation of 2 spaces indentation 357:2 ✖ Expected indentation of 2 spaces indentation 358:2 ✖ Expected indentation of 2 spaces indentation 359:2 ✖ Expected indentation of 2 spaces indentation 360:2 ✖ Expected indentation of 2 spaces indentation 361:2 ✖ Expected indentation of 2 spaces indentation 366:2 ✖ Expected indentation of 2 spaces indentation 367:2 ✖ Expected indentation of 2 spaces indentation 368:2 ✖ Expected indentation of 2 spaces indentation 369:2 ✖ Expected indentation of 2 spaces indentation 370:2 ✖ Expected indentation of 2 spaces indentation 371:2 ✖ Expected indentation of 2 spaces indentation 372:2 ✖ Expected indentation of 2 spaces indentation 373:2 ✖ Expected indentation of 2 spaces indentation 377:2 ✖ Expected indentation of 2 spaces indentation 382:2 ✖ Expected indentation of 2 spaces indentation 383:2 ✖ Expected indentation of 2 spaces indentation 384:2 ✖ Expected indentation of 2 spaces indentation 388:2 ✖ Expected indentation of 2 spaces indentation 389:2 ✖ Expected indentation of 2 spaces indentation 390:2 ✖ Expected indentation of 2 spaces indentation 391:2 ✖ Expected indentation of 2 spaces indentation 395:2 ✖ Expected indentation of 2 spaces indentation 396:2 ✖ Expected indentation of 2 spaces indentation 397:2 ✖ Expected indentation of 2 spaces indentation 398:2 ✖ Expected indentation of 2 spaces indentation 399:2 ✖ Expected indentation of 2 spaces indentation 403:2 ✖ Expected indentation of 2 spaces indentation 404:2 ✖ Expected indentation of 2 spaces indentation 405:2 ✖ Expected indentation of 2 spaces indentation 406:2 ✖ Expected indentation of 2 spaces indentation 407:2 ✖ Expected indentation of 2 spaces indentation 408:2 ✖ Expected indentation of 2 spaces indentation 409:2 ✖ Expected indentation of 2 spaces indentation 410:2 ✖ Expected indentation of 2 spaces indentation 411:2 ✖ Expected indentation of 2 spaces indentation 415:2 ✖ Expected indentation of 2 spaces indentation 416:2 ✖ Expected indentation of 2 spaces indentation 417:2 ✖ Expected indentation of 2 spaces indentation 418:2 ✖ Expected indentation of 2 spaces indentation 419:2 ✖ Expected indentation of 2 spaces indentation 420:2 ✖ Expected indentation of 2 spaces indentation 421:2 ✖ Expected indentation of 2 spaces indentation 422:2 ✖ Expected indentation of 2 spaces indentation 423:2 ✖ Expected indentation of 2 spaces indentation 424:2 ✖ Expected indentation of 2 spaces indentation 425:2 ✖ Expected indentation of 2 spaces indentation 426:2 ✖ Expected indentation of 2 spaces indentation 427:2 ✖ Expected indentation of 2 spaces indentation 428:2 ✖ Expected indentation of 2 spaces indentation 432:2 ✖ Expected indentation of 2 spaces indentation 433:2 ✖ Expected indentation of 2 spaces indentation 434:2 ✖ Expected indentation of 2 spaces indentation 435:2 ✖ Expected indentation of 2 spaces indentation 436:2 ✖ Expected indentation of 2 spaces indentation 437:2 ✖ Expected indentation of 2 spaces indentation 438:2 ✖ Expected indentation of 2 spaces indentation 439:2 ✖ Expected indentation of 2 spaces indentation 443:2 ✖ Expected indentation of 2 spaces indentation 444:2 ✖ Expected indentation of 2 spaces indentation 448:2 ✖ Expected indentation of 2 spaces indentation 449:2 ✖ Expected indentation of 2 spaces indentation 450:2 ✖ Expected indentation of 2 spaces indentation 451:2 ✖ Expected indentation of 2 spaces indentation 452:2 ✖ Expected indentation of 2 spaces indentation 453:2 ✖ Expected indentation of 2 spaces indentation

2 Command line CLI should allow (but not require) wrapping code in ask {}

Find it on GitHub

Currently when people wrap their code with ask {} when using the command line CLI tool, they get the following error:

``` marcin@Marcins-MacBook-Pro-2 askql % npm run cli

askql@1.2.2 cli /Users/marcin/Repositories/askql node dist/cli.js

Welcome to AskQL CLI!

For multi-line mode please type: .editor 🦄 ask {} Uncaught: Error [SyntaxError]: Expected " ", "(", ".", "//", ":", ";", "=", "[", "\n", "\r", "\t", "}", [/], or [-!<>+*^%=&|] but "{" found. Location: { "start": { "offset": 10, "line": 2, "column": 5 }, "end": { "offset": 11, "line": 2, "column": 6 } } 🦄 ```

Then command line should allow wrapping code in ask {} and not show this confusing error.

3 "All time" stats

Find it on GitHub

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/app/controllers/statscontroller.rb#L50 in the $REPO repository (press the little pen Icon) and edit the line as shown below. replace this line with `params[:start] = Date.new(2010, 01, 01).totime`

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

4 Discussion: Update .rubocop_shopify_styleguide.yml

Find it on GitHub

When I run rubocop -a app/controllers/notes_controller.rb or rubocop -a <any other file> I receive a series of errors from that show that the .rubocop_shopify_styleguide.yml has obsolete configurations.

Should it be updated?

![Screenshot 2020-10-20 at 21 46 14](https://user-images.githubusercontent.com/7622875/96631069-88342f00-131e-11eb-97c9-0cffd3764fa3.png)

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 rubocopshopifystyleguide.yml in the PLOT2 repository (press the little pen Icon) and update any errors that show that rubocop_shopify_styleguide.yml contains deprecated lines of configuration.

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

  • [ ] 💾 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!

5 Fix Spelling Errors (first timers only)

Find it on GitHub

This will be a running issue to let people know how to add events to `historicalevents.py`_


NOTE: this issue is only for you if you'd consider yourself a Code Newbie.


Have you seen a typo you'd like to fix? Go ahead and fix it.

Need help? Check out this article on using the github website to navigate git or use this repo as an example to use the command line. You're also welcome to comment on this issue and I'll be happy to help.

Proposed workflow:

  1. Fork this repo
  2. Find the file with spelling errors and fix them.
  3. Once you are done and checked for typos, commit it & push your work to your fork
  4. Submit a PR against this repo

Someone will look it over and, if deemed appropriate, will merge your PR.

Thanks for contributing!


Don't forget to follow the bot on Twitter to see the hard work you put in.

6 Change http to https in db/seeds.rb

Find it on GitHub

🔊 NOTE: (This issue is a part of Issue #8587 and has been claimed at the time of writing this issue. However, there are several places in the codebase where this change needs to happen, and issues haven't been made for each instance yet. If you are a first-time contributor, please refer to #8587 for more info on how to find instances of 'http' in the codebase. From there, you can make your own FTO issue and pull request to solve it.)

Please see #8587 for more context behind this issue.

7 Change http to https in notify_moderators_of_comment_spam.html.erb

Find it on GitHub

🔊 NOTE: (This issue is a part of Issue #8587 and has been claimed at the time of writing this issue. However, there are several places in the codebase where this change needs to happen, and issues haven't been made for each instance yet. If you are a first-time contributor, please refer to #8587 for more info on how to find instances of 'http' in the codebase. From there, you can make your own FTO issue and pull request to solve it.)

Please see #8587 for more context behind this issue.

8 Change http to https in notify_moderators_of_spam.html.erb

Find it on GitHub

🔊 NOTE: (This issue is a part of Issue #8587 and has been claimed at the time of writing this issue. However, there are several places in the codebase where this change needs to happen, and issues haven't been made for each instance yet. If you are a first-time contributor, please refer to #8587 for more info on how to find instances of 'http' in the codebase. From there, you can make your own FTO issue and pull request to solve it.)

Please see #8587 for more context behind this issue.

9 Change http to https in drupal_content_type_map.rb

Find it on GitHub

🔊 NOTE: (This issue is a part of Issue #8587 and has been claimed at the time of writing this issue. However, there are several places in the codebase where this change needs to happen, and issues haven't been made for each instance yet. If you are a first-time contributor, please refer to #8587 for more info on how to find instances of 'http' in the codebase. From there, you can make your own FTO issue and pull request to solve it.)


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 /app/models/drupalcontenttype_map.rb (press the little pen Icon) and edit the line as shown below.

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 - l = "<a href='http://creativecommons.org/publicdomain/zero/1.0/'>Public Domain</a>" if field_license_value == 'publicdomain' - l = "<a href='http://creativecommons.org/licenses/by/3.0/'>CC-BY</a>" if field_license_value == 'cc-by' - l = "<a href='http://creativecommons.org/licenses/by-sa/3.0/'>CC-BY-SA</a>" if field_license_value == 'cc-by-sa' + l = "<a href='https://creativecommons.org/publicdomain/zero/1.0/'>Public Domain</a>" if field_license_value == 'publicdomain' + l = "<a href='https://creativecommons.org/licenses/by/3.0/'>CC-BY</a>" if field_license_value == 'cc-by' + l = "<a href='https://creativecommons.org/licenses/by-sa/3.0/'>CC-BY-SA</a>" if field_license_value == 'cc-by-sa'

  • [ ] 💾 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!

10 Organize the repo for cleaner look and a beautify the readme

Find it on GitHub

Currently the repo is a complete mess with a wide variety of naming conventions and folder structures 1. reorganize the scripts in a different folder in the root called scripts 2. the script folder names are quite inconsistent for example: first-name ,First_name, First_Name so rename them to First_Middle_Name format 3. update the readme to point to the scripts in the new structure 4. make a more elegant readme

Note: This issue will be awarded to person commenting first and would be given a week to finish the task.

11 Remove map marker button from tags input

Find it on GitHub

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 app/views/tag/_form.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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

Here, we'll be removing the map marker button as shown in this screenshot:

![image](https://user-images.githubusercontent.com/24359/96514927-6bbac880-1232-11eb-933b-0b32672b030e.png)

The button appears in a form on the sidebar of pages like https://publiclab.org/notes/warren/09-14-2020/congratulations-to-our-outreachy-and-gsoc-2020-fellows (login required to see it)

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

diff @@ -8,10 +8,7 @@ <span class="input-group-text"><i class="fa fa-tags"></i></span> </div> <input aria-label="Enter tag name" autocomplete="off" class="tag-input form-control" name="name" type="text" placeholder="<%= translation('tag._tagging.enter_tags') %>" data-provide="typeahead" /> - <div class="input-group-append"> - <a class="btn btn-outline-secondary blurred-location-input" rel="tooltip" title="Link with a location" style="border-color:#ccc;"> - <i class="fa fa-map-marker"></i> - </a> + <div class="input-group-append"> <%= render partial: 'tag/advanced_tagging' %> </div> </div>

  • [ ] 💾 Commit your changes

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

  • If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

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

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

Part of #6593 !

12 Change emoji on weekly-check-in

Find it on GitHub

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

13 Refactor `dist` and `plugin` to be at the root level of this project

Find it on GitHub

I noticed that dist and plugin folders in the 2nd and 3rd slides were redundant since in both I was using the revealjs library,

both of the folders can be moved out at top level and the links to them can be updated

This should be a good issue for first timers in open source

14 Add to list a companies, a company which you think is good to work for

Find it on GitHub

Add a new company to already existing list of companies, by adding following details:

  • website of company
  • start year
  • remote jobs (Yes/No)
  • degree required(Yes/No)

A friendly guide to create a pull request:

  1. Star this repository (you must be logged on to your GitHub account, duh!)
  2. Fork this repository
  3. To add a company you need to modify the following files:
    • the main file (List.md) (add a company in ascending alphabetic order)
    • company file (company_name.md) in the list directory
  4. This can be done in either of the two ways:
    • Method 1: clone the repo locally on your PC
    • Method 2: or make changes online on GitHub

Method 1:

This is the not-so beginner friendly way (or hard way, to say the least). But you got to do it if you really want to learn Git. Follow this guide.

Method 2:

This is the easy-peasy way. You just: * create a new file with the company's name(suffixed by .md) and all the following details * company website * company's career page * start year * remote work * no degree required * any other detail you find relevant * modify the List.md to add the company's name to the original list with few more details

P.S:

Try combining multiple companies into a single pull request, instead of creating separate pull for every company.

After your PR has been successfully merged with the main branch, you will be automatically added to our Contributors list!!! (if, for whatever reason you find yourself missing from the contributors list, let us know and we'll be more than happy to add you.)

15 Users might pass arguments using CLI flag=value

Find it on GitHub

From Gitter https://gitter.im/cypress-io/cypress?at=5f8a04b73d172d78b37c71ba

![](https://user-images.githubusercontent.com/2212006/96319744-872d9580-0fde-11eb-899c-5840856a4b80.png)

Weird that it converts the value to Infinity?!

16 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -13,12 +13,12 @@ Browsers

-Load @octokit/plugin-request-log and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-request-log and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { requestLog } from "https://cdn.pika.dev/@octokit/plugin-request-log"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { requestLog } from "https://cdn.skypack.dev/@octokit/plugin-request-log"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

17 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -13,12 +13,12 @@ Browsers

-Load @octokit/plugin-rest-endpoint-methods and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-rest-endpoint-methods and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { restEndpointMethods } from "https://cdn.pika.dev/@octokit/plugin-rest-endpoint-methods"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { restEndpointMethods } from "https://cdn.skypack.dev/@octokit/plugin-rest-endpoint-methods"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

18 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -13,12 +13,12 @@ Browsers

-Load @octokit/plugin-paginate-rest and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-paginate-rest and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { paginateRest } from "https://cdn.pika.dev/@octokit/plugin-paginate-rest"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { paginateRest } from "https://cdn.skypack.dev/@octokit/plugin-paginate-rest"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

19 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -32,11 +32,11 @@ For other GitHub authentication strategies see [octokit/auth.js](https://github. Browsers

-Load @octokit/auth-app directly from cdn.pika.dev +Load @octokit/auth-app directly from cdn.skypack.dev

html <script type="module"> - import { createAppAuth } from "https://cdn.pika.dev/@octokit/auth-app"; + import { createAppAuth } from "https://cdn.skypack.dev/@octokit/auth-app"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

20 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -31,11 +31,11 @@ It implements authentication using an OAuth app’s client ID and secret as well Browsers

-Load @octokit/auth-oauth-app directly from cdn.pika.dev +Load @octokit/auth-oauth-app directly from cdn.skypack.dev

html <script type="module"> - import { createOAuthAppAuth } from "https://cdn.pika.dev/@octokit/auth-oauth-app"; + import { createOAuthAppAuth } from "https://cdn.skypack.dev/@octokit/auth-oauth-app"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

21 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -33,11 +33,11 @@ It is useful if you want to support multiple authentication strategies, as it’ Browsers

-Load @octokit/auth-token directly from cdn.pika.dev +Load @octokit/auth-token directly from cdn.skypack.dev

html <script type="module"> - import { createTokenAuth } from "https://cdn.pika.dev/@octokit/auth-token"; + import { createTokenAuth } from "https://cdn.skypack.dev/@octokit/auth-token"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

22 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -12,11 +12,11 @@

Browsers -Load @octokit/request-error directly from cdn.pika.dev +Load @octokit/request-error directly from cdn.skypack.dev

html <script type="module"> -import { RequestError } from "https://cdn.pika.dev/@octokit/request-error"; +import { RequestError } from "https://cdn.skypack.dev/@octokit/request-error"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

23 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -17,11 +17,11 @@ See [GitHub’s Developer Guide for the OAuth web application flow](https://deve

-Load @octokit/oauth-authorization-url directly from cdn.pika.dev +Load @octokit/oauth-authorization-url directly from cdn.skypack.dev

html <script type="module"> - import { oauthAuthorizationUrl } from "https://cdn.pika.dev/@octokit/oauth-authorization-url"; + import { oauthAuthorizationUrl } from "https://cdn.skypack.dev/@octokit/oauth-authorization-url"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

24 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

```diff @@ -31,7 +31,7 @@ GitHub supports 4 authentication strategies. They are all implemented in@octok Browsers

-Load @octokit/auth directly from cdn.pika.dev +Load @octokit/auth directly from cdn.skypack.dev

html <script type="module"> @@ -40,7 +40,7 @@ Load `@octokit/auth` directly from [cdn.pika.dev](https://cdn.pika.dev) createAppAuth, createOAuthAppAuth, createTokenAuth, - } from "https://cdn.pika.dev/@octokit/auth"; + } from "https://cdn.skypack.dev/@octokit/auth"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

25 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -19,12 +19,12 @@ As a compromise, this plugin is reverting changes such as the one above to remai Browsers

-Load @octokit/plugin-enterprise-compatibility and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-enterprise-compatibility and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { enterpriseCompatibility } from "https://cdn.pika.dev/@octokit/plugin-enterprise-compatibility"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { enterpriseCompatibility } from "https://cdn.skypack.dev/@octokit/plugin-enterprise-compatibility"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

26 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -13,12 +13,12 @@ Browsers

-Load @octokit/plugin-retry and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-retry and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { retry } from "https://cdn.pika.dev/@octokit/plugin-retry"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { retry } from "https://cdn.skypack.dev/@octokit/plugin-retry"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

27 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

```diff @@ -17,12 +17,12 @@ Besides the admin-specific endpoints, there are differences betweenapi.github. Browsers

-Load @octokit/plugin-enterprise-server and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-enterprise-server and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { enterpriseServer220Admin } from "https://cdn.pika.dev/@octokit/plugin-enterprise-server"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { enterpriseServer220Admin } from "https://cdn.skypack.dev/@octokit/plugin-enterprise-server"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

28 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -15,12 +15,12 @@ Implements all [recommended best practises](https://docs.github.com/en/rest/guid Browsers

-Load @octokit/plugin-throttling and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-throttling and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

`html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { throttling } from "https://cdn.pika.dev/@octokit/plugin-throttling"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { throttling } from "https://cdn.skypack.dev/@octokit/plugin-throttling"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

29 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -29,11 +29,11 @@ Browsers

-Load @octokit/graphql directly from cdn.pika.dev +Load @octokit/graphql directly from cdn.skypack.dev

html <script type="module"> - import { endpoint } from "https://cdn.pika.dev/@octokit/graphql"; + import { endpoint } from "https://cdn.skypack.dev/@octokit/graphql"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

30 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -15,12 +15,12 @@ Browsers

-Load @octokit/plugin-enterprise-cloud and @octokit/core (or core-compatible module) directly from cdn.pika.dev +Load @octokit/plugin-enterprise-cloud and @octokit/core (or core-compatible module) directly from cdn.skypack.dev

html <script type="module"> - import { Octokit } from "https://cdn.pika.dev/@octokit/core"; - import { enterpriseCloud } from "https://cdn.pika.dev/@octokit/plugin-enterprise-cloud"; + import { Octokit } from "https://cdn.skypack.dev/@octokit/core"; + import { enterpriseCloud } from "https://cdn.skypack.dev/@octokit/plugin-enterprise-cloud"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

31 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -70,11 +70,11 @@ request("POST /repos/:owner/:repo/issues/:number/labels", {

Browsers -Load @octokit/request directly from cdn.pika.dev +Load @octokit/request directly from cdn.skypack.dev

html <script type="module"> -import { request } from "https://cdn.pika.dev/@octokit/request"; +import { request } from "https://cdn.skypack.dev/@octokit/request"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

32 Replace "cdn.pika.dev" with "cdn.skypack.dev" in README

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

The Pika CDN is now Skypack, see https://www.pika.dev/cdn. The CDN at https://cdn.pika.dev/ no longer works, all URLs must be replaced with the new CDN: https://cdn.skypack.dev/. We currently recommend using cdn.pika.dev to import the library into the browser, but that no longer works. Replacing it with cdn.skypack.dev will make it work again.

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -32,11 +32,11 @@

Browsers -Load @octokit/endpoint directly from cdn.pika.dev +Load @octokit/endpoint directly from cdn.skypack.dev

html <script type="module"> -import { endpoint } from "https://cdn.pika.dev/@octokit/endpoint"; +import { endpoint } from "https://cdn.skypack.dev/@octokit/endpoint"; </script> ````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

33 Replace cdn.pika.dev with cdn.skypack.dev

Find it on GitHub

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 What you will need to know.

Pika's CDN has been deprecated and no longer works. We have to replace it with cdn.skypack.dev in all places

📋 Step by Step

  • [ ] 🙋 Claim this issue: Comment below.

More than one person can work on this issue, don't worry if it's already claimed.

  • [ ] 📝 Update the file \README.md (press the little pen Icon) and edit as shown below:

````diff @@ -12,11 +12,11 @@

Browsers -Load @octokit/rest directly from cdn.pika.dev +Load @octokit/rest directly from cdn.skypack.dev

html <script type="module"> -import { Octokit } from "https://cdn.pika.dev/@octokit/rest"; +import { Octokit } from "https://cdn.skypack.dev/@octokit/rest"; </script>

````

  • [ ] 💾 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 edit files directly in your browser
  • [ ] 🏁 Done Ask for a review :)

If there are more than one pull requests with the correct change, we will merge the first one, but attribute the change to all authors who made the same change using @Co-authored-by, so yo can be sure your contribution will count.

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

34 Change http:// to https:// in several places (Fix for #6391)

Find it on GitHub

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.

:nerd_face: A little background:

Basically we need to remove http:// and replace it with https:// in multiple files, so that the site can continue to load content as normal. See below and issue #6391 for more information.

Chrome will soon start blocking any http content loaded from an https page - not just scripts and iframes, but images, etc. https://www.bleepingcomputer.com/news/google/google-chrome-to-gradually-start-blocking-mixed-content-by-default/

✒️ What to Change

There are a few places in the codebase where we can make this change. Please select ONE file to make a pull request (more info below), and leave the rest for other first-timers!

  • [ ] drupalcontenttype_map.rb: https://github.com/publiclab/plots2/blob/76f000c8dcc82576910590f9699c92256179c20e/app/models/drupalcontenttype_map.rb#L32-L34
  • [ ] notifymoderatorsof_spam.html.erb: https://github.com/publiclab/plots2/blob/76f000c8dcc82576910590f9699c92256179c20e/app/views/adminmailer/notifymoderatorsofspam.html.erb#L15
  • [ ] notifymoderatorsofcommentspam.html.erb: https://github.com/publiclab/plots2/blob/76f000c8dcc82576910590f9699c92256179c20e/app/views/adminmailer/notifymoderatorsofcomment_spam.html.erb#L20
  • [ ] _history.html.erb: https://github.com/publiclab/plots2/blob/76f000c8dcc82576910590f9699c92256179c20e/app/views/notes/_history.html.erb#L24
  • [ ] tools_places.html.erb: https://github.com/publiclab/plots2/blob/76f000c8dcc82576910590f9699c92256179c20e/app/views/notes/tools_places.html.erb#L9
  • [ ] db/seeds.rb: https://github.com/publiclab/plots2/blob/76f000c8dcc82576910590f9699c92256179c20e/db/seeds.rb#L75
  • [ ] Find your own! You can search this repository for instances of "http" like so: ![Untitled 3](https://user-images.githubusercontent.com/4361605/96181359-b95ccb80-0ee8-11eb-811e-8be766753dd0.gif)

📋 Step by Step

  • [ ] 🙋 Claim this issue: Make a comment on this page, claiming one of the files above. If someone else has already 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 you've chosen by navigating to it. You can edit the line directly by clicking on the little pen icon.

  • [ ] 💾 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 :)

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

35 [Installer] Add ffmpeg

Find it on GitHub

Add ffmpeg

We want to add ffmpeg because...

  • it's normally ridiculously complicated to install and requires hundreds of dependencies through package management systems... but now we've got https://github.com/zimbatm/ffmpeg-static

Note: this is a break to the general rule of no 3rd party builds... because in this case the 1st party builds either don't exist, or are terrible.

This could be as simple as copying _example, updating the github releases info, and doing a find and replace on a few file system path names.

Notes: - The windows binaries seem to be missing the .exe suffix. That will need to be accounted for in the releases.js and install.ps1. - Should be able to get version with ffmpeg -version | head -n 1 | cut -d' ' -f 3.

How to create a webi installer

![Video Tutorial: How to create a webi Installer](https://user-images.githubusercontent.com/122831/91064908-17f28100-e5ed-11ea-9cf0-ab3363cdf4f8.jpeg)

Skills required

  • Basic Command Line knowledge (mkdir, mv, ls, tar, unzip, variables)

Steps

  1. Clone and setup the webi packages repo bash git clone git@github.com:webinstall/packages.git pushd packages/ npm install
  2. Copy the example template and update with info from Official Releases: https://github.com/ugeneware/ffmpeg-static/releases bash rsync -av _example/ ffmpeg/
    • [ ] update ffmpeg/release.js to use the official repo
    • [ ] Learn how ffmpeg unpacks (i.e. as a single file? as a .tar.gz? as a .tar.gz with a folder named ffmpeg?)
    • [ ] find and replace to change the name
      • [ ] update ffmpeg/install.sh (see bat and jq as examples)
      • [ ] update ffmpeg/install.ps1 (see bat and jq as examples)
  3. Needs an updated tagline and cheat sheet
    • [ ] update ffmpeg/README.md
      • [ ] official URL
      • [ ] tagline
      • [ ] Switch versions
      • [ ] description / summary
      • [ ] General pointers on usage (and perhaps "gotchas")

It's also okay to have multiple people work on part of this (i.e. the Cheat Sheet can be done independently from the install.sh)

36 Unable to take screenshot with allure when using multiremote feature

Find it on GitHub

Unable to have screenshot from the failed test when using combination of browserstack/appium and selenium stand alone services

Environment (please complete the following information): - WebdriverIO version: 6.6.4 - Mode: multiremote feature - If WDIO Testrunner, running sync/async: sync - Node.js version: 12.18.0 - NPM version: 6.14.4 - Browser name and version: chrome - Platform name and version: win10 + BS - Additional wdio packages used (if applicable):

``` "dependencies": { "@wdio/browserstack-service": "^6.6.3", "@wdio/cli": "^6.6.4", "eslint": "^7.11.0", "frisby": "^2.1.3", "wdio-chromedriver-service": "^6.0.4", "webdriverio": "^6.6.4" }, "devDependencies": { "@wdio/allure-reporter": "^6.6.3", "@wdio/appium-service": "^6.6.3", "@wdio/dot-reporter": "^6.6.0", "@wdio/local-runner": "^6.6.4", "@wdio/mocha-framework": "^6.6.3", "@wdio/selenium-standalone-service": "^6.6.5", "@wdio/spec-reporter": "^6.6.3", "@wdio/sync": "^6.6.4", "@wdio/concise-reporter": "^6.6.0", "chai": "^4.2.0", "mocha": "^8.1.3" }

``` Config of WebdriverIO

```

services: [ ['selenium-standalone', { args: { seleniumArgs: ['-port', '4444'] }, }],
['browserstack'], // ['appium',{ // command : 'appium', // args: { // debugLogSpacing: true, // sessionOverride: true, // port: 4728, // allowInsecure:'chromedriver_autodownload' // }, // }] ], afterTest: function(test, context, { error, result, duration, passed, retries }) { if (error !== undefined) { browser.takeScreenshot(); } },

reporters: ['dot','spec',['allure', {
    outputDir: 'allure-results',
    disableWebdriverStepsReporting: true,
    disableWebdriverScreenshotsReporting: false,
    disableMochaHooks: true
}]],

```

Describe the bug Unable to take screenshot for failed test when using multiremote feature

To Reproduce Steps to reproduce the behavior: use multi-remote feature with broswerstack/appium and selenium

Expected behavior Screenshot should be taken either from Browser or mobile app once test is failing

37 Fix translation helper functions and leave helpful notice to future coders

Find it on GitHub

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 app/views/like/_like.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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 @@ -106,23 +106,25 @@ <hr style='clear:both;' /> <div> <span> + <!--translation()` javascript does not work in this area because it is within a Bootstrap Popover and is rendered later --> <% if node.type == 'note' %> - <%= numberwithdelimiter(node.views) %> <%= translation('notes.show.views') %> + <%= numberwithdelimiter(node.views) %> <%= t('notes.show.views') %> <% if node.comments %> - | <%= node.comments.size %> <%= translation('notes.show.comments') %> + | <%= node.comments.size %> <%= t('notes.show.comments') %> <% end %> - | <%= raw translation('wiki.show.lastedited', url1: "/profile/" + node.latest.author.name, author: node.latest.author.name, time: timeagoinwords(node.latest.createdat)) %> + | <%= raw t('wiki.show.lastedited', url1: "/profile/" + node.latest.author.name, author: node.latest.author.name, time: timeagoinwords(node.latest.createdat)) %> <% end %>

             <% if node.type == 'page' %>
  • <%= numberwithdelimiter(node.views) %> <%= translation('wiki.show.views') %>
  •                <%= number_with_delimiter(node.views) %> <%= t('wiki.show.views') %>
                 <% if node.comments %>
    
                     | <a href='<%= node.path %>/comments'><%= node.comments.length %> Comments</a>
    
                 <% end %>
    
  •                | <%= raw translation('wiki.show.last_edited', url1: "/profile/" + @revision.author.name, author: @revision.author.name, time: time_ago_in_words(@revision.created_at)) %>
    
  •                | <%= raw t('wiki.show.last_edited', url1: "/profile/" + @revision.author.name, author: @revision.author.name, time: time_ago_in_words(@revision.created_at)) %>
             <% end %>
    
  •            <!-- END OF: `translation()` javascript does not work in this area because it is within a Bootstrap Popover and is rendered later -->
         </span>
     </div>
     <br />
    

    ```

  • [ ] 💾 Commit your changes

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

  • If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

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

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

38 Add configuration management section to the docs

Find it on GitHub

Add a configuration.rst to sphinx_source. Write how config is handled in Shopyo.

39 Enhance homepage using html/css/javascript

Find it on GitHub

Style the homepage the way you like

40 Add the ability to customize the name of the before hook that shows up in the allure report because it takes the name of the first test by default

Find it on GitHub

Is your feature request related to a problem? Please describe. We use before hooks to setup all of our tests and make sure we're on the right page before we start executing a series of negative test cases, but in the report, the before hook takes on the name of the first test when instead we feel it should take on the name of the entire suite.

As you can see, the before test has the same name, in quotes, as the first actual test in the sequence (test number 2) even though the "before" is for all tests in the suite.

Mocha has the ability to pass a title to before hooks, but wdio/allure-reporter seems to ignore them.

Describe the solution you'd like I can't imagine that this is the behavior most people would want, but since I'm not in their shoes, we have to assume changing the default behavior could break stuff. It would be great to be able to pass in a custom title to before and then have that appear in the report instead.

``` before('before hook with custom title, () => { // do the before stuff here );

it('should ...', () => { // test 1 });

it('should ...', () => { //test 2 and so forth .... ```

Describe alternatives you've considered

I have tried hacking the test titles via the currentTest and this.test JavaScript objects, which are accessible in the before block, however, changing the values doesn't seem to affect the report.

Another alternative is to disable the before and after hook reporting, but that won't help us if there is a problem in the before/after hooks.

41 UI to reflect when a user leaves the application

Find it on GitHub

Currently when a user leaves the application the UI just freezes for the person and does not remove the placeholder for the client.

Requirements 1.) The other clients should know that the User has left by receiving an event 2.)The UI should also reflect the left client.

42 Delete answer.rb

Find it on GitHub

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 app/models/answer.rb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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 @@ -1,35 +0,0 @@ -class Answer < ApplicationRecord - include CommentsShared - include NodeShared

- extend RawStats

  • belongsto :node, foreignkey: 'nid'
  • belongsto :user, foreignkey: 'uid'
  • hasmany :answerselections, foreign_key: 'aid'

- hasmany :comments, foreignkey: 'aid', dependent: :destroy

- validates :content, presence: true

  • scope :pastweek, -> { where("createdat > ?", (Time.now - 7.days)) }

- scope :pastmonth, -> { where("createdat > ?", (Time.now - 1.months)) }

  • def body
  • finder = content.gsub(Callouts.constget(:FINDER), Callouts.constget(:PRETTYLINKMD))
  • finder = finder.gsub(Callouts.constget(:HASHTAGNUMBER), Callouts.constget(:NODELINKMD))
  • finder.gsub(Callouts.constget(:HASHTAG), Callouts.constget(:HASHLINKMD))

- end

  • def body_markdown
  • RDiscount.new(body, :autolink).to_html

- end

  • # users who like this answer
  • def likers
  • answer_selections
  • .joins(:user)
  • .references(:rusers)
  • .where(liking: true)
  • .where('rusers.status': 1)
  • .collect(&:user)
  • end -end ```

  • [ ] 💾 Commit your changes

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

  • If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

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

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

43 Delete answer_selection.rb

Find it on GitHub

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 app/models/answer_selection.rb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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 @@ -1,24 +0,0 @@ -class AnswerSelection < ApplicationRecord - belongsto :answer, foreignkey: :aid, dependent: :destroy

- belongsto :user, foreignkey: :user_id

  • def user
  • User.findby(username: User.find(userid).name)

- end

  • def self.set_likes(uid, aid, value)
  • like = where(userid: uid, aid: aid).firstor_create
  • like.liking = value
  • if like.liking_changed?
  • answer = Answer.find(aid)
  • if like.liking
  • answer.cached_likes += 1
  • else
  • answer.cached_likes -= 1
  • end
  • like.save
  • answer.save
  • end
  • like.liking
  • end -end ```

  • [ ] 💾 Commit your changes

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

  • If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

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

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

44 [mesheryctl] Update error message in `mesheryctl version` failure to connect to server

Find it on GitHub

Description The error message shown when Meshery server is unavailable could be better phrased.

``` ➜ .meshery mesheryctl version Client Version: 0.4.12 GitSHA: 6f7a527f3fa5e713c52686f3387c3ae1b54de1f2 Server Version: GitSHA: 6f7a527

failed to check for latest version of Meshery ```

Expected Behavior Error message should be:

"Meshery server unreachable. Please confirm that Meshery is running and available. "

45 Select DEMO #SUIC-321

Find it on GitHub

Acceptance Criteria

The Select demo viewed on sui-studio is not following the agreements. It can be previewed on the following link: sui-studio Select DEMO

Definition Of DONE

  • [ ] in English
  • [ ] Sort by
    • [ ] Size
    • [ ] Styles
    • [ ] Options

Jira Task

SUIC-321

46 Tag DEMO #SUIC-330

Find it on GitHub

Acceptance Criteria

The Tag demo viewed on sui-studio is not following the agreements. It can be previewed on the following link: sui-studio Tag DEMO

Definition Of DONE

  • [ ] Organise by
    • [ ] Size S M L
    • [ ] Types (show them all)
    • [ ] Actionable yes no
    • [ ] Icons
    • [ ] Right, Left, both
    • [ ] Responsive

Jira Task

SUIC-330

47 RadioButton DEMO #SUIC-340

Find it on GitHub

Acceptance Criteria

The RadioButton demo viewed on sui-studio is not following the agreements. It can be previewed on the following link: <!--sui-studio RadioButton DEMO-->

Definition Of DONE

  • [ ] Rename "Use Cases” to "States"
  • [ ] Add description

Jira Task

SUIC-340

48 Checkbox Demo

Find it on GitHub

Acceptance Criteria

The Checkbox demo viewed on sui-studio is not following the agreements. It can be previewed on the following link: sui-studio checkbox DEMO

Definition Of DONE

  • [ ] Rename "Use Cases” to "States"
  • [ ] Add description

SUIC-322

49 convert all contributions to python 3.8 syntax

Find it on GitHub

There are few contributions which still include python 2.7 syntax, which needs to be converted to python 3.8 syntax

50 Make UI For above bash script

Find it on GitHub

Develop a simple registration/login portal front end. You can refer to the repository for more. You can choose any language or framework for front-end

51 Add Jest testing framework with Babel support

Find it on GitHub

Is your feature request related to a problem? Please describe. We have various github actions to check for integrity, ci and lint checks. What's missing is thorough unit test coverage which tests code logic.

Features like #106 must be testable.

Describe the solution you'd like Add jest testing framework;

See; https://jestjs.io/docs/en/getting-started.html ; In the deps in package.json add ONLY latest versions "dependencies": { "babel-core" "babel-jest" "babel-preset-env" "jest" }

Add presents like: ```javascript

// babel.config.js module.exports = { presets: [ ['@babel/preset-env', {targets: {node: 'current'}}], + '@babel/preset-typescript', ], }; ```

Make sure to follow our README guide and see how to run tsc runner once you have set this up;

Describe alternatives you've considered alternatives considered were karma, jasmine. but jest has a good OSS backing as well and looks easy to use.

Additional context We need to make sure developer productivity is not hindered while adopting a new test framework.

52 Document how to connect easily plots2 and PL.editor projects for local development

Find it on GitHub

Hi,

We have already written amazing documentation on how to connect the 2 projects here , however it requires us to do yarn install --force in plots2 every time we do change in PL.editor.

Let's use yarn link instead and make it seamless 😄

Resources: https://classic.yarnpkg.com/en/docs/cli/link/

53 feat: Add Typescript support for Aliases

Find it on GitHub

Current behavior

Aliases are not Typescript friendly. When using aliases to share values between hooks/tests, the alias value is automatically typed as any because TS has no way of following the chained .as method through to its new value on this. This results in needing to revert to using the let method to share context if one wants TS to keep track of the variables.

Desired behavior

I think there are a few different options here. Ideally, it would be great if the alias method, .as, could determine the type of the passed in value and somehow let TS know that this property now exists on this. I'm not sure how one would do that, so if that is not possible then I think we might need a way of passing a variable to .as that is used instead of this and gives us more control over its type. As a final option, if Cypress could expose or make typeable (maybe as a type param for describe?) this, then we could just append our custom variables manually.

All that said, I'm very open to suggestions for other ways of approaching making Aliases TS friendly.

54 Check and fix labels for Settings->Categories, Data export and Users

Find it on GitHub

There are two ways labels are handled in the platform, depending on the markup of the form:

<label for="username">Username</label> <input id="username" type="text" /> and

<label>Username <input id="username" type="text" /> </label>

Go through the following forms and make sure the element is either using the for-attribute to associate the form-control or is encapsulating the form-control like the second example:

Categories The code is found here:

https://github.com/ushahidi/platform-client/blob/develop/app/settings/categories/categories-edit.html

You find the view by logging in as an admin, then click on Settings and select "Categories", then click the "+" icon:

Data export The code is found here: https://github.com/ushahidi/platform-client/blob/develop/app/settings/data-export/data-export.html

You find the view by logging in as an admin, then click on Settings and select "Export and tag data". Then click on "Select fields".

Users The code is found here: https://github.com/ushahidi/platform-client/blob/develop/app/settings/users/users-edit.html

You find the view by logging in as an admin, click on Settings and select "Users", then click the "+" icon.

If no adjustments is needed, just comment in this issue that you have worked through the issues and checked, if any adjustment is needed, make the necessary changes and create a PR 🎉 If changes are needed, make sure the form still looks the same as before and that is has no effect on the visual appearance of the form.

Aha! Link: https://ushahiditeam.aha.io/features/PROD-840

55 Create a pull request template

Find it on GitHub

Create a pull request template an example can be found at https://github.com/americanexpress/one-app/blob/main/.github/pullrequesttemplate.md

This tutorial can be followed

https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository

56 Create a pull request template

Find it on GitHub

Create a pull request template an example can be found at https://github.com/americanexpress/one-app/blob/main/.github/pullrequesttemplate.md

This tutorial can be followed

https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository

57 Create a pull request template

Find it on GitHub

Create a pull request template an example can be found at https://github.com/americanexpress/one-app/blob/main/.github/pullrequesttemplate.md

This tutorial can be followed

https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository

58 Add a PR template

Find it on GitHub

Add the following check list in the PR template:

  • [ ] Created a folder with the name of language you code inside directory for the day you are making the contribution to
  • [ ] Added your Codes
  • [ ] Tested your codes
  • [ ] Added credits (author and date) at the top of the code
  • [ ] Updated README.md of the day you are contributing to
  • [ ] Added yourself as a contributor using all-conributors-cli

59 Add generic contribution guidelines

Find it on GitHub

The idea and requirements for this project will be finalized soon,

Till then we can go on with some generic contribution guideline template,

This should be an easy issue, feel free to take this and raise the PR

60 [Docs] README: incorporate SMP logo into Service Mesh Performance section

Find it on GitHub

Current State: The section of the Meshery README that covers service mesh performance does not include a copy of the SMP project logo.

Desired State: Incorporate a small SMP logo into this section of the README.md. Find the SMP brand kit here - https://layer5.io/brand


Contributor Resources - Meshery documentation site - Meshery documentation source - Instructions for contributing to documentation

61 Update L.DistortableImage.Keymapper method creation to ES6 syntax II

Find it on GitHub

First Time?

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.

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax from ES5 to ES6 for several methods in src/components/DistortableImage.Keymapper.js.

Solution

  1. For the following 3 L.DistortableImage.Keymapper methods, remove the function keyword and attach the method arguments to the method name instead:
    • [ ] _setMapper
    • [ ] _toggleKeymapper
    • [ ] _injectIconSet

Here is an example of how this will look for a different method. These ones should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; },

ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

  1. [ ] Update the anonymous function used in addInitHook to an arrow function:

diff - L.DistortableImage.Keymapper.addInitHook(function() { + L.DistortableImage.Keymapper.addInitHook(() => {

  1. [ ] Update the class factory function at the bottom of the file to an arrow function:

diff - L.distortableImage.keymapper = function(map, options) { + L.distortableImage.keymapper = (map, options) => {

Thanks!!

Step by Step

  • [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
  • [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
    • [ ] Create a new feature branch with a unique name descriptive to the issue
  • [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
  • [ ] Reference this issue in your pull request body
  • [ ] Once you submit your pull request, if there's an additional checklist provided for getting it merged, get those boxes checked off. Either way, mention me @sashadev-sky 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, 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.

💬 Get help

If you need any help - here are some options:

  • Comment below
  • Join our gitter chat at https://gitter.im/publiclab/publiclab

62 craft zip file for symlink testing

Find it on GitHub

We need a special zip file that cannot be created with normal commandline tools. It requires crafting with an API. This should be possible with archive/zip#Writer, for example.

We want a double entry of a file - the first being a symlink such that the second will be placed in an arbitrary location:

txt ./goodfile.txt "hello world" (file) ./bad/file.txt => ../../badfile.txt (symlink) ./bad/file.txt "Mwa-ha-ha" (file) ./morefile.txt "hello world" (file)

This should go in testdata/testarchives/evilarchives/ as double-evil.zip and double-evil.tar (if it is allowed).

See also https://github.com/mholt/archiver/issues/242#issuecomment-703086020

63 Add badges that might be applicable for this repo

Find it on GitHub

Example! ![Screenshot_2020-10-04 devcer hydrator](https://user-images.githubusercontent.com/3799600/95014087-23ac7b00-0662-11eb-8d24-0113ff95bb94.png)

64 Add additional badges that might be applicable for this repo

Find it on GitHub

Addition to this in readme.md! ![Screenshot_2020-10-04 devcer hydrator](https://user-images.githubusercontent.com/3799600/95014066-fc55ae00-0661-11eb-96f3-4e267f6a2bb8.png)

65 Add more popular sources

Find it on GitHub

See the list of sources documented at https://github.com/gautamkrishnar/blog-post-workflow#popular-sources

Add more RSS Feed sources to the list.

66 Better styling

Find it on GitHub

Im a CSS newbie, if you see any better styling, feel free to help..

67 Implement query params on /choice of mock-server to emulate the next choice action

Find it on GitHub

Following the https://github.com/bancodobrasil/stop-analyzing-api/issues/16#issuecomment-667519483 spec, this issue is about enchancing the db and the /choice endpoint of the mocking server so it can return different values with sequentials invocations to emulate how the real API will behave so we can work on the progress visual interaction and the final interaction when the user reaches "the end of the line".

68 Fetch choices from an endpoint

Find it on GitHub

Add a useEffect to the useChoiceBoardModel.ts that fetches the initial choices from an endpoint and set the initial options from that.

Tip: this endpoint could be the mock server endpoint

69 Implement script to run mock server from `npm run`

Find it on GitHub

Add to package.json a script to bring up the mock-server. The command will be npm run mock-server.

70 removed package lock from .gitnore, Bumped node-fetch for DOS vuln

Find it on GitHub

This change is  <!-- Reviewable:end -->

71 Briefly Explain your favourite algorithm

Find it on GitHub

What to do

Which is that algorithm that you find intriguing? Edit the README.md file, by adding the algorithm's name as a heading and then add a brief description of it. Keep the description as unique as possible and avoid repetitions.

New to markdown?

See GitHub Markdown Guide

This issue is open for all

72 🍁💻 Welcome to Hacktoberfest 2020 💻🍁

Find it on GitHub

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

73 🍁💻 Welcome to Hacktoberfest 2020 🍁💻

Find it on GitHub

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

74 🍁💻 Welcome to Hacktoberfest 2020 💻🍁

Find it on GitHub

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

75 🍁💻 Welcome to Hacktoberfest 2020 💻🍁

Find it on GitHub

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

76 🍁💻 Welcome to Hacktoberfest 2020 💻🍁

Find it on GitHub

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

77 🍁💻Welcome to Hacktoberfest 2020💻🍁

Find it on GitHub

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

78 💻🍁 Welcome to Hacktoberfest 2020 💻🍁

Find it on GitHub

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

79 Organise the list in alphabetical order

Find it on GitHub

Feel free to open a pull request organizing the list in alphabetical order every time you find something out of order.

80 Broken link in 'README.md'

Find it on GitHub

Describe the bug The 'CONTRIBUTING.md' link is not loading 'CONTRIBUTING.md' file

To Reproduce Steps to reproduce the behavior: 1. Go to 'Contributing section of README.md' 2. Click on 'CONTRIBUTING.md link' 3. It doesn't load the file

Expected behavior It should have loaded 'CONTRIBUTING.md' file

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information): - OS: [e.g. iOS] - Browser [e.g. chrome, safari] - Version [e.g. 22]

Smartphone (please complete the following information): - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22]

Additional context Add any other context about the problem here.

81 Hacktober Feature Request: Add Azure Links to Learn page

Find it on GitHub

Describe the feature

Add the following links under a Learn Azureheader:

  • [ ] Azure documentation - https://docs.microsoft.com/en-gb/azure/?product=featured#languages-and-tools&WT.mc_id=cloudskills-stream-ajack

  • [ ] Quickstart: Create a function in Azure that responds to HTTP requests - https://docs.microsoft.com/en-gb/azure/azure-functions/functions-create-first-azure-function-azure-cli?pivots=programming-language-csharp&tabs=bash%2Cbrowser&WT.mc_id=cloudskills-stream-ajack

Advantages

  • Helps those new to Azure find resources

Acceptance Criteria

Functional and non-functional criteria that should be met by this work

  • [ ] Listed linked have been added to the Learn page

82 [Books] Add second edition of The Enterprise Path to Service Mesh Architectures

Find it on GitHub

Current Behavior There is a new edition of this book coming out shortly - https://layer5.io/books/the-enterprise-path-to-service-mesh-architectures

Desired Behavior 1. The second edition should be added as a new entry. This description may be used: ``` Planning to build a microservice-driven cloud native application or looking to modernize existing application services? Consider using a service mesh. A service mesh approach can help you create robust and scalable applications, but it also introduces new challenges. This updated report answers common questions regarding service mesh architectures through the lens of a large enterprise.

Author Lee Calcote, founder and CEO of Layer5, shows developers, operators, architects, and IT leaders how to evaluate your organization’s readiness for using a service mesh—and provides a clear path to help you adopt one. You’ll evaluate several factors when deciding which applications should be built from the ground up and which can be converted with a new service mesh architecture.

This updated edition discusses several service meshes available and the tools you need to implement them. You’ll explore:

  • Service mesh concepts, architecture, and components, such as control planes and data planes
  • How a service mesh provides observability, resiliency, security, and traffic control of distributed application services
  • Differences among service meshes and service mesh components from several vendors
  • How service meshes compare to related technologies, including container orchestrators, API gateways, and client-side libraries
  • Practical steps for service mesh adoption, deployment, customization, and integration
  • The intelligence of the service mesh management plane and the power of the data plane

Author: Lee Calcote Publisher: O’Reilly Publish Date: October 2020 ``` 2. The first edition entry should remain as-is.

Book Cover Use this image as the book cover for the second edition entry. Resize as needed. ![the-enterprise-path-to-service-mesh-architectures_2nd-edition](https://user-images.githubusercontent.com/7570704/94847905-d376b400-03e8-11eb-8985-3c4a1f0aeb21.png)


[Optional] Alternatives <!-- A brief description of any alternative solutions or features you've considered. -->

[Optional] Additional context <!-- Add any other context or screenshots about the feature request here. -->


Contributor Resources The layer5 repo contains two websites. The current generation and the next-generation of the layer5.io site.

If the layer5-ng label is absent on this issue, then this issue pertains to the current generation of the layer5.io website, which uses Jekyll and GitHub Pages. Site content is found under the master branch. - See layer5 contributing instructions

If the layer5-ng label is present on this issue, then this issue pertains to the next-generation of the layer5.io website, which uses Gatsby, Strapi, and GitHub Pages. Site content is found under the layer5-ng branch. - See layer5-ng contributing instructions

83 Replace Moment.js within the Cypress project.

Find it on GitHub

Current behavior

Cypress requires Moment.js in the desktop-gui, cli, driver, and server packages.

Moment.js is now considered legacy and is in maintenance mode. They recommend moving to other projects. See https://momentjs.com/docs/#/-project-status

Desired behavior

Replace Moment.js with other smaller, more up to date package(s). See their recommendations. We would be open to PRs that replace parts of Moment.js one piece at a time. Also - using newer libraries for any new Date uses is recommended.

Versions

5.3.0

84 Sauce Service - set cacheId automatically

Find it on GitHub

Is your feature request related to a problem? Please describe. Sauce Labs supports setting cacheId property. It's pretty easy to set it if tests are running with a concurrency of 1, but managing cacheIds becomes tricky when we are running, say, 10 tests with a max concurrency of 3 (using maxInstances capability).

Describe the solution you'd like Add a boolean argument named autoSetCacheId in the config file. If this argument is set to true, reuse same 3 devices for those 10 tests with the help of cacheId.

Describe alternatives you've considered - An alternative would be to not use maxInstances capability, and just run each test in a separate process (essentially having my own maxInstances implementation in bash) - Implement this feature ourselves in our project. Something like: have an array of "released cacheIds". Whenever a new test starts, we can check if there is a cacheId available in that array. If there is, use it. If there isn't, generate a new one. Whenever the test finishes, add the cacheId used in that test to that array.

85 Code your favourite data structures and algorithms!

Find it on GitHub

Implement any algorithm or data structure or solve any programming problem in any language you want, when done, share your success by making a PR. Include the file in your pull request. Keep the name of the file as: Language-Problem Short Name eg: Python-Knapsack.py

86 Nadeem Update LICENSE

Find it on GitHub

This change is  <!-- Reviewable:end -->

87 Please add resources

Find it on GitHub

88 Center align the card on the page and added a box-shadow property

Find it on GitHub

89 [sec] check if symlink points outside of destination directory

Find it on GitHub

I was able to confirm that os.Create() will happily follow symlinks.

Although standard tools like tar will not likely allow you to add two files with the same name to an archive file, it's certainly easy enough to do in code. This means that we need to add an additional check before writing to a destination to make sure that it's not a symlink outside of the destination.

The vulnerability only exists if OverwriteExisting is also turned on.

What file is affected?

filecompressor.go: ```go // DecompressFile reads the source file and decompresses it to destination. func (fc FileCompressor) DecompressFile(source, destination string) error { if fc.Decompressor == nil { return fmt.Errorf("no decompressor specified") }

if !fc.OverwriteExisting && fileExists(destination) {
    return fmt.Errorf("file exists: %s", destination)
}

// TODO needs check here

in, err := os.Open(source)
if err != nil {
    return err
}
defer in.Close()

out, err := os.Create(destination)
if err != nil {
    return err
}
defer out.Close()

return fc.Decompress(in, out)

} ```

Possible solution

If the destination exists we should always check if it's a symlink first:

```go if fileExists(destination) { // TODO check if destination is a symlink with an outside target // should be a simple os.Lstat()

    if !fc.OverwriteExisting {
        return fmt.Errorf("file exists: %s", destination)
    }
}

```

Also, we could block ALL symilnks that have a target outside of the destination directory.

I think the former approach is the best for now, as some archives may link outside of the destination directory for legitimate reasons.

Please link to any related issues, pull requests, and/or discussion

This is related to

  • https://github.com/mholt/archiver/pull/203
  • https://github.com/mholt/archiver/pull/169
  • https://github.com/mholt/archiver/pull/70
  • https://github.com/snyk/zip-slip-vulnerability/issues/41

90 [style] Use error instance rather than an error string

Find it on GitHub

Recently we had a PR that was necessary, but had some code style issues that we'd like to fix:

The PR in question: https://github.com/mholt/archiver/pull/231/files

What would you like to have changed?

There are a few ways I think could work really well:

  1. Follow the style of os.IsNotFound
    • Let's add function something like IsIllegalPath in archiver.go
    • Let's replace lines like strings.Contains(err.Error(), "illegal file path") with IsIllegalPath
  2. Follow the style of csv.ParseError
    • Let's add a struct IllegalPathError to archiver.go
    • Let's replace things like fmt.Errorf("illegal file path: %s", filename) with the use of that error
  3. Let's do both!

Why is this feature a useful, necessary, and/or important addition to this project?

We just want to make the code more durable and maintainable.

91 [Site] Create a difference in color on either side of the blog posts

Find it on GitHub

Current Behavior A lack of formatting on the individual blog pages has them not looking as much like articles as they could be.

Desired Behavior Add color to the left and right margins or some other styling to the blog post page layout to offset the text from the page.

Screenshot

92 Add your name in Contributors.md

Find it on GitHub

If you are a beginner and wants to become a open source contributor then add your name in our contributors list and be a part of open source community.

93 Update Readme

Find it on GitHub

  • [ ] Create CONTRIBUTING.md file in the root folder
  • [ ] Add How to Contribute instructions to the file

Please use markdown!

94 Update Readme

Find it on GitHub

  • [ ] Create CONTRIBUTING.md file in the root folder
  • [ ] Add How to Contribute instructions to the file

Please use markdown!

95 Update Readme

Find it on GitHub

  • [ ] Add Install and Run instructions to run this React-Native project generated with expo-cli

96 Integrate domain check feature [Hacktoberfest]

Find it on GitHub

Clicking on a proposed name takes the user to another screen where the user can see availability of that domain

To keep things simple, as of now we can probably open some website like https://namechk.com/ and pre-fill the domain name

97 Improve text in Donation section on landing page

Find it on GitHub

Donation section on landing page currently contains lorem ipsum text. Write something else in place of that.

98 Redesign the CONTRIBUTING.md file

Find it on GitHub

If you are a first-time contributor you can contribute to this project by re-designing the CONTRIBUTING.md file. Use your imagination and make it more beautiful. However, please do not remove important information from the CONTRIBUTING.md file. Feel free to add more information as you see fit.

99 update readme for first timers so they can get started quickly

Find it on GitHub

100 Improve UI of the QuoteCard component

Find it on GitHub

Find the component under components/QuoteCard.tsx * [ ] Update the color codes to the tailwind present from this demo -> https://theme-ui.com/demo * [ ] Copy icon should be on the bottom right of the card. No need of text Copy. * [ ] Adjust alignments and font-sizes. Test with large captions of 100 characters. * [ ] Add a screenshot of the new UI along with your PR