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 Fix missing embed icon

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 files in the plots2 repository and edit the line as shown below.

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

Problem:

The embed icon is not displayed on the map ![stable publiclab org_map (2)](https://user-images.githubusercontent.com/29401459/72712227-9cc97800-3b90-11ea-8fb2-f1b1a5894d02.png)

Solution:

  1. Add "@fortawesome/fontawesome-free": "^5.12.0", to the list of dependencies here: https://github.com/publiclab/plots2/blob/3ad76794ddeb6ddba3712a9abab072148be4ca25/package.json#L20

  2. Add <link href="/lib/@fortawesome/fontawesome-free/css/all.min.css" media="all" rel="stylesheet" type="text/css" /> above the line shown here: https://github.com/publiclab/plots2/blob/3ad76794ddeb6ddba3712a9abab072148be4ca25/app/views/layouts/application.html.erb#L25

  • [ ] πŸ’Ύ 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!

2 Colobar default image is not correct.

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!

You will have to fix a module name colorbar. The issue is that the starting of the colorbar overlay is shifted a bit right. Refer the below GIF. ![output](https://user-images.githubusercontent.com/31132760/72668198-4d792f80-3a4a-11ea-8412-72cc2e678d9d.gif)

πŸ€” 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 src/modules/colorbar/module.js.

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:

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

3 Module Selector dropdown showing error in console

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 is to be done?

After searching module name in module search input if we clear the input field a error is shown in console, try to remove that error. Refer to below GIF for more info!

![err](https://user-images.githubusercontent.com/42492389/72648050-059dce00-39a0-11ea-9b67-5a7b10be00f5.gif)

Files to refer to: https://github.com/publiclab/image-sequencer/blob/c22c6c70d098715d610c72afe83ef8f6b3d9d57a/examples/lib/defaultHtmlSequencerUi.js#L27

  • [ ] πŸ’Ύ 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 UI Learn More Link Should Lead to the README

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 is to be done?

The UI of ImageSequencer has a link with the text Learn More in the header that leads to the wiki page of ImageSequencer on publiclab.org. This link is just a mini README. You have to change this link to the full README of ImageSequencer. ![Screenshot from 2020-01-18 00-14-07](https://user-images.githubusercontent.com/34770591/72637512-813f5100-3987-11ea-9c60-8cf319c61598.png)

Files to refer to: 1. https://github.com/publiclab/image-sequencer/blob/d1b9b8beccdbe5ba98cf4e352af103b4913a5fe6/examples/index.html#L69

πŸ€” 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!

  • [ ] πŸ“ Modify the file index.html

  • [ ] πŸ’Ύ 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 it 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 UI Chatroom Link Should Link to the Gitter Channel

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 is to be done?

The UI of ImageSequencer has a link in the footer that leads to one of the general chatrooms on publiclab.org. However, ImageSequencer has its own gitter chatroom now -> https://gitter.im/publiclab/image-sequencer.

You will have to update this link

Files to refer to: 1. https://github.com/publiclab/image-sequencer/blob/d1b9b8beccdbe5ba98cf4e352af103b4913a5fe6/examples/index.html#L221

πŸ€” 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!

  • [ ] πŸ“ Modify all the files where this code is found.

  • [ ] πŸ’Ύ 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 it 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!

6 Load Image Docs Link Should Not Be Displayed (as it doesn't exist)

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 is to be done?

The first step in every sequence of ImageSequencer is the load-image step where the input image is loaded. This is just a sequencer method and not an actual module. It has no dedicated documentation.

All the other modules of ImageSequencer have their own docs here

Even though load-image has no docs, there is a link in the UI for load-image which leads to nothing. ![Screenshot from 2020-01-17 23-35-45](https://user-images.githubusercontent.com/34770591/72636459-1d1b8d80-3985-11ea-9162-c40fe2456cd4.png)

Files to refer to: 1. https://github.com/publiclab/image-sequencer/blob/d1b9b8beccdbe5ba98cf4e352af103b4913a5fe6/examples/lib/defaultHtmlStepUi.js#L48-L50

πŸ€” 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!

  • [ ] πŸ“ Modify the file defaultHtmlStepUi.js

  • [ ] πŸ’Ύ 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 it 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!

7 Add location modal script to dashboard

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 sidebar/_dashboard 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!

At the end of the file add this line: <%= render partial: 'tag/location' %>

  • [ ] πŸ’Ύ 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!

8 Remove All Instances of `mode: 'test'`

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 is to be done?

In ImageSequencer module tests, the following option is passed to the sequencer https://github.com/publiclab/image-sequencer/blob/423422a61f61f1a4fa9149b9dafee1508bbe350e/test/core/templates/module-test.js#L38

Due to recent changes, this option is no longer required. We would want to remove any unnecessary code and keep the codebase clean and tidy.

You will have to find all the instances of mode: 'test' and remove the code. There are many ways of searching lines of code in a whole project. One of the easiest ways is to use the feature provided by most code editors. Some examples are: 1. VSCode 2. Atom 3. Sublime Text

πŸ€” 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!

  • [ ] πŸ“ Modify all the files where this code is found.

  • [ ] πŸ’Ύ 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 it 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!

9 The width of the timer in the Test Runner is 'jumpy'

Find it on GitHub

Current behavior:

Currently, the Cypress GUI has a timer that shows during test progress. The current implementation shows the time out to two decimal places, but drops trailing zeroes. So your timer jumps from 10 to 10.53 to 10.8 to 10.92 and then to 11. (As a crude example). This causes the visual space it takes up on the screen to frantically jump around in size. It's a bit dis-concerting.

Desired behavior:

Any visually cleaner implementation. I suggest just showing exactly to two decimal places at all times on the timer. 10 seconds would then be 10.00 seconds. You could also make other adjustments to the sizing of the element container, etc. to help alleviate this as well, but those feel like half measures.

This implementation would still have the element resize, but only at non-frequent, important breaks ( on the # of digit switches)

Test code to reproduce

Run any test suite that takes over 10 seconds to complete. A specific example is not required, as this is a visual UI improvement that should be noticeable for any long-running test.

Versions

Noticed it enough to annoy me at the current version 3.8.x, so not sure if that element has changed or if that changing element has just finally made me roll my eyes enough to open a ticket.

I'd love other suggestions or feedback on whether this bothers anyone else, as well.

10 Add a Comment Explaining External Module Definitions

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 is to be done?

https://github.com/publiclab/image-sequencer/blob/bfff7e7b999bf256205d412a13f16e154a63beb1/src/Modules.js#L33-L34

In the above code, the commented line imports the invert module from a different repository altogether (using a require statement). This is a powerful feature of ImageSequencer, the modules are independent of the rest of the library's source.

The above example depicts this feature perfectly. You have to add a comment next to the commented code, explaining the feature and the code.

πŸ€” 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!

  • [ ] πŸ“ Modify the file Modules.js

  • [ ] πŸ’Ύ 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 it 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!

11 Redundant changePixel Function

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 Module.js in the image-sequencer repository (press the little pen Icon) and edit the line as shown below. In the above file the changePixel function which is called for each pixel outputs the same as the input which is redundant. We need to remove this function and also its return.

This above file is just one case. Try to find different modules in which similar thing is happening

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:

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

12 .type() does not enter a - or + after a valid number in an input of type number

Find it on GitHub

Current behavior:

Similar to to now closed 6055, if I try to type 123- into an input of type number, the field only contains 123. This is a bit of an edge case, we use these valid characters to make an invalid number to test field validation messages for our NumberTextField component.

This behavior is a discrepancy between Cypress and manual in Chrome as strings like 123- and 1+1 can be entered manually. Our tests are passing in 3.7 but failing in 3.8.2

Desired behavior:

.type() allows valid characters to be added to an input of type number even if the positioning of the characters makes the end value invalid.

Steps to reproduce:

use .type('123-') on an input of type number. use .type('1+1') on an input of type number.

Versions

Chrome 79, Windows 10, Cypress 8.3.2

13 Paint bucket module is getting wrong input for fillColor

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 PaintBucket.js in the $REPO repository (press the little pen Icon) and edit the line as shown below.

    ```diff

    +27. fillColor[3] = fillColor[3] * 256; ``` 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!

14 Displayed Version Number is not Visible

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 is to be done?

The current version of IS that is used is displayed in the UI at the top right corner but it is not visible. NOTE: The version number has been highlighted manually in the image below. ![Screenshot from 2020-01-12 23-20-07](https://user-images.githubusercontent.com/34770591/72223594-96d30600-3596-11ea-81e1-d35d0ddee9fa.png)

You have to change the appearance of this text to make the text more readable.

Files to refer: 1. https://github.com/publiclab/image-sequencer/blob/12c422a07b55233ae94e13fc3700da2101916c65/examples/demo.js#L38-L42 2. https://github.com/publiclab/image-sequencer/blob/12c422a07b55233ae94e13fc3700da2101916c65/examples/demo.css#L318-L328

πŸ€” 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!

  • [ ] πŸ“ Modify the file demo.css

  • [ ] πŸ’Ύ 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 it 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!

15 Add command anomaly

Find it on GitHub

js Cypress.Commands.add('getAlias', (alias:string) => cy.get(`@${alias}`));

results in

TypeError: command.get is not a function

but

js Cypress.Commands.add('alias', (alias:string) => cy.get(`@${alias}`));

does not

what trickerypokery?

16 Emails from same research note should display in same thread

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 $FILENAME in the $REPO repository (press the little pen Icon) and edit the line as shown below.

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

The issue

As noted in #6230, comments and like messages from multiple people on the same research note show up as separate threads in an email inbox. Instead, they should show up in the same thread. In order to achieve this, we have to make sure the titles of the emails match exactly.

The fix

In the files subscription_mailer.rb and comment_mailer.rb, there are different methods for each type of event (e.g., when a note is updated, liked, or initially created. To make all the messages show up in the same email thread, we need to make all the subject lines look the same.

Changes to make in subscription_mailer.rb

Let's make all the subject lines look like this one, on line 7: https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L7

First, replace the following three lines with the exact text from line 7 (above): https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L22-L24

Then, in the notify_tag_added method, paste the exact text from line 7 right below the method header (i.e., right before the line saying @tag = tag): https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L32-L59

Finally, on this line: https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L57 Replace "#{node.title} (##{node.id})" with subject.

Changes to make in comment_mailer.rb

Change line 11 of the file: https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/comment_mailer.rb#L11

to match line 18: https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/comment_mailer.rb#L18

  • [ ] πŸ’Ύ 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!

17 Fix minor typo in LABELS.md

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 $FILENAME in the $REPO repository (press the little pen Icon) and edit the line as shown below.

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

Changes Requested:

In LABELS.md (https://github.com/publiclab/plots2/blob/master/doc/LABELS.md), there is a typo on line 25: "Issues which need discussion and requirements needs to be elicitated" should be changed to "Issues that need discussion and requirements need to be elucidated"

Please fix this typo.

  • [ ] πŸ’Ύ 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!

18 Suggest a Python driver conception based on the notebook

Find it on GitHub

Notebook in this repo, is a demonstration of interacting with https://github.com/bacloud14/exec The web service.

In real production environment, this should turn into a Python library, to approach this, there are zillions of ways (writing a driver); The most important consideration, is that not only Python is subject to a driver, many languages will come next, so a basic conception of how an Exce driver should be is very important. Guys that already conceived HTTP clients, you could propose a way to start the implementation.

19 cypress-cli type for CypressRunResult::runs is incorrect (can be null/undefined)

Find it on GitHub

Current behavior:

In the event that the browser fails to connect, the run promise resolves with results which has runs of null or undefined. (Which is likely a separate issue altogether. It should probably not resolve at all - it should reject).

However, the typings indicate that the type of runs is RunResult[] which doesn't match null

Desired behavior:

The type should indicate that runs can be undefined or null, or run() should not resolve on an error running the tests altogether.

Test code to reproduce

  1. Clone https://github.com/xdumaine/cypress-test-tiny
  2. npm i && npm test

20 add function to scrape eclipse

Find it on GitHub

http://metservice.intnet.mu/sun-moon-and-tides-info-eclipses.php

![meteomoris_eclipse](https://user-images.githubusercontent.com/22630684/71894112-cfbe4580-3166-11ea-9ff0-c8fdcb4e3604.png)

get the surrounded text till end as string

21 Add function to scrape cyclone info

Find it on GitHub

![meteomoris_currentcyclone](https://user-images.githubusercontent.com/22630684/71893907-43138780-3166-11ea-8021-8e69cf31c89b.png)

22 Invoke binary directly warning showing always from `cypress verify` (debug mode)

Find it on GitHub

While trying to debug an issue w/ cypress verify getting stuck occasionally (related #6082), I'm getting the following stdout message from running cypress verify in debug mode (via DEBUG=cypress:* yarn cypress verify)

"It looks like you are running the Cypress binary directly. This is not the recommended approach, and Cypress may not work correctly."

Is this is an expected output from the smoke-test?

Current behavior:

`` ❯ DEBUG=cypress:* npx cypress@latest verify cypress:cli installing Cypress from NPM +0ms cypress:cli installing with options {} +0ms cypress:cli version in package.json is 3.8.1 +1ms cypress:cli Reading binary package.json from: /Users/*********/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/Resources/app/package.json +0ms cypress:cli no binary installed under cli version +4ms cypress:cli checking local file /Users/*********/.npm/_npx/47203/lib/3.8.1 cwd /Users/*********/.npm/_npx/47203/lib/node_modules/cypress +0ms cypress:cli preparing to download and unzip version 3.8.1 to path /Users/*********/Library/Caches/Cypress/3.8.1 +0ms cypress:cli needed Cypress version: 3.8.1 +0ms cypress:cli source url https://download.cypress.io/desktop/3.8.1?platform=darwin&arch=x64 +0ms cypress:cli downloading cypress.zip to "/var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip" +0ms cypress:cli Downloading package { url: 'https://download.cypress.io/desktop/3.8.1?platform=darwin&arch=x64', proxy: null, downloadDestination: '/var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip' } +1ms cypress:cli redirect version: 3.8.1 +341ms cypress:cli expected checksum 64ba19b0fe70e5b4eda6dad53c16a8de0234a09871462c510f8e44e5226e5bf17bcbbb87051117aba114bca0f1e875be3ebe1331d4376e8c9f30dac9e11c3c5e +136ms cypress:cli expected file size 167102535 +0ms cypress:cli downloading finished +6s cypress:cli verifying checksum and file size +1ms cypress:cli downloaded file has the expected checksum and size βœ… +505ms cypress:cli finished downloading file: /var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip +7s cypress:cli:unzip unzipping from /var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip +0ms cypress:cli:unzip into /Users/*********/Library/Caches/Cypress/3.8.1 +0ms cypress:cli:unzip zipFile entries count 40147 +7ms cypress:cli:unzip unzipping viaditto` +0ms cypress:cli:unzip unzip completed { yauzlMs: 7, unzipMs: 26116 } +26s cypress:cli removing zip file /var/folders/ds/cwtxfpmd76z4rg8r94tbc0000gn/T/cypress.zip +26s cypress:cli finished installation in /Users/******/Library/Caches/Cypress/3.8.1 +17ms cypress:cli:cli cli starts with arguments ["/usr/local/bin/node","/Users/******/.npm/npx/47203/bin/cypress","verify"] +0ms cypress:cli NODEOPTIONS is not set +0ms cypress:cli:cli program parsing arguments +3ms cypress:cli parsed cli options {} +3ms cypress:cli verifying Cypress app +0ms cypress:cli checking environment variables +1ms cypress:cli checking if executable exists /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/MacOS/Cypress +2ms cypress:cli Binary is executable? : true +1ms cypress:cli binaryDir is /Users/***/Library/Caches/Cypress/3.8.1/Cypress.app +0ms cypress:cli Reading binary package.json from: /Users/***/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/Resources/app/package.json +0ms cypress:cli Found binary version 3.8.1 installed in: /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app +3ms cypress:cli could not read binarystate.json file +3ms cypress:cli {} +0ms cypress:cli is Verified ? undefined +1ms cypress:cli force verify +0ms cypress:cli running binary verification check 3.8.1 +0ms It looks like this is your first time using Cypress: 3.8.1 cypress:cli clearing out the verified version +3ms cypress:cli needs Xvfb? false +0ms cypress:cli spawning, should retry on display problem? false +1ms cypress:cli disabling Electron sandbox +0ms cypress:cli running smoke test +0ms cypress:cli using Cypress executable /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/MacOS/Cypress +0ms cypress:cli smoke test command: /Users/***/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/MacOS/Cypress --no-sandbox --smoke-test --ping=965 +0ms cypress:cli smoke test timeout 30000 ms +0ms β ΄ Verifying Cypress can run /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app cypress:cli smoke test stdout "It looks like you are running the Cypress binary directly.

This is not the recommended approach, and Cypress may not work correctly.

Please install the 'cypress' NPM package and follow the instructions here:

https://on.cypress.io/installing-cypress 965" +2s cypress:cli write verified: true +1ms βœ” Verified Cypress! /Users/*********/Library/Caches/Cypress/3.8.1/Cypress.app ```

Desired behavior:

I did a little digging myself & here what I've found:

  • Cypress prints out the message above when options.invokedFromCli === false https://github.com/cypress-io/cypress/blob/v3.8.1/packages/server/lib/cypress.coffee#L59
  • This options.invokedFromCli is computed based off the options.cwd value https://github.com/cypress-io/cypress/blob/v3.8.1/packages/server/lib/util/args.js#L172
  • This options.cwd is inherited from the --cwd flag, which is injected here https://github.com/cypress-io/cypress/blob/v3.8.1/cli/lib/exec/spawn.js#L84

Based on the findings above, I "believe" this is what's happening under the hood:

  • The cypress verify command runs the a smoke test via runSmokeTest() https://github.com/cypress-io/cypress/blob/v3.8.1/cli/lib/tasks/verify.js#L43
  • runSmokeTest() starts the test by exec'ing the Cypress binary & spawns a child process https://github.com/cypress-io/cypress/blob/v3.8.1/cli/lib/tasks/verify.js#L113
  • Since the binary was exec'ed via the smoke test, the --cwd flag isn't injected
  • Hence the Cypress child-process (spawn'ed from cypress verify) determines that it wasn't being launched directly from the CLI & prints out the message

(From what I've seen so far, seems like this is the intended behaviour & it's harmless since the verify task succeeded.)

Steps to reproduce:

  1. Open a terminal
  2. Run DEBUG=cypress:* npx cypress@latest verify (getting the same output if one were to run DEBUG=cypress:* yarn cypress verify in their project directory)

Versions

Node@LTS (v12.14.0) Cypress@latest (v3.8.1) macOS High Sierra (v10.13.6)

23 Better performance

Find it on GitHub

Note process seems to eat a lot of memory running : ps -o pid,user,%mem,command ax | sort -b -k3 -r These tutorials https://www.valentinog.com/blog/memory-usage-node-js/ https://www.fiznool.com/blog/2016/10/01/running-a-node-dot-js-app-in-a-low-memory-environment/ https://stackoverflow.com/questions/21694567/optimize-node-js-memory-consumption

seems to be very helpful.

24 Better code

Find it on GitHub

Code refactoring: The purpose is to reduced complexity and improve source-code maintainability. Better use of small functions in a modular programming style.

25 Secure and performant code

Find it on GitHub

All code is concerned.

26 "By type" button does not have padding at the right on a tag page

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!

Problem

"By type" button does not have padding at the right ![image](https://user-images.githubusercontent.com/17945250/71669729-45f62d00-2da0-11ea-8d9a-8fd665f9fb76.png) Expected view: ![image](https://user-images.githubusercontent.com/17945250/71669803-8a81c880-2da0-11ea-90cb-7d7d9c4ca148.png)

πŸ€” 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/show/navtabs.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:

Edit line 2. diff - <div class="dropdown" style="margin-top:10px; float:right;"> + <div class="dropdown mr-1" style="margin-top:10px; float:right;">

  • [ ] πŸ’Ύ 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!

27 Content area horizontal overflow

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.

:fire: Problem

![Screenshot20191231181905](https://user-images.githubusercontent.com/35997844/71628896-caa74680-2bfa-11ea-8f43-19cdd70b455f.png)

PublicLab editor is causing problems on tablets and mobile devices. It makes big horizontal scroll bars and we need to solve this.

That's why we need you :)

🚩 Goal

![Screenshot20191231183803](https://user-images.githubusercontent.com/35997844/71629249-be23ed80-2bfc-11ea-9c66-d59f6a80bcab.png)

πŸ“‹ 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!

  • [ ] πŸ“ Open the file PublicLab.Editor/dist/PublicLab.Editor.css

  • Line 24, add this code: css .ple-content { overflow-x: hidden; }

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!

28 Standardise Util Functions Comments

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 is to be done?

We are working towards standardizing all the comments in the codebase to make the docs look professional. New developers will get benefitted if we add comments to some of the most commonly used util functions. They are listed below. 1. pixelSetter.js 2. getDefaults.js

You will have to update the comments in the above files based on the guidelines mentioned below. 1. Methods must be described using JSDoc comments 2. Misc code comments should be inline unless it is a long sentence. 3. No use of continuous tenses, no pronouns. 4. No redundant comments. 5. Each comment should start with an uppercase letter and end with a full stop.

πŸ€” 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!

  • [ ] πŸ“ Modify the file pixelSetter.js

  • [ ] πŸ“ Modify the file getDefaults.js

  • [ ] πŸ’Ύ 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 it 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!

29 Homepage modal buttons not scaled

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.

:fire: Problem

![Screenshot20191225171442](https://user-images.githubusercontent.com/35997844/71448295-73a4fb80-273a-11ea-84be-331ed93d3924.png)

![Screenshot20191225171519](https://user-images.githubusercontent.com/35997844/71448296-77388280-273a-11ea-972b-1732a7e3cfa0.png)

On mobile phone and tablets, buttons are not of the same height. It results in bad UI/UX and it should be fixed.

🚩 Solution

![Screenshot20191225171912](https://user-images.githubusercontent.com/35997844/71448308-b961c400-273a-11ea-9283-da0d1018c97d.png)

πŸ“‹ 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!

  • [ ] πŸ“ Open the file ./mapknitter/app/views/front_ui/index.erb

  • Line 55 -> add inline styles to paragraph html <p style="display:flex;justify-content:space-around;"><i style="color:#aaa;">A Community Atlas hosted by <a href="https://publiclab.org">PublicLab</a></i></p>

  • Line 64 -> add an inline style to the anchor tag html <a class="btn btn-primary btn-lg" style="display:flex;align-items:center;justify-content:center;" href="" data-toggle="collapse" data-target="#anonymous-map">

  • Line 66 -> add margin-left to inline styles html <i class="fa fa-plus fa-fw" style="font-size:12px;color:white;margin-left:2%;"></i>

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!

30 Add Image source to urlHash upon loading an image

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 is to be done?

ImageSequencer's UI can read module information from the URL. e.g. https://beta.sequencer.publiclab.org/examples/#steps=contrast{contrast:-31},saturation{} will load a sequence with contrast and saturation. Similarly, a URL containing #src={some-dataurl/link} will start a sequence with a preloaded image. But when a new image is added through the UI, the #src for the image is not added to the URL.

You will have to make it so that the dataURL of the loaded image is added to the URL. Refer: - https://github.com/publiclab/image-sequencer/blob/main/examples/lib/urlHash.js - #src from URL is loaded https://github.com/publiclab/image-sequencer/blob/c370a8b4ea20267462f8fa559608618ca168e457/examples/demo.js#L78-L83 - https://github.com/publiclab/image-sequencer/blob/main/src/ui/LoadImage.js

You can refer to the above files but your final changes will mostly be in the demo.js file. You can make changes to other files if you feel it is necessary.

πŸ€” 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!

  • [ ] πŸ“ Modify the file demo.js

  • [ ] πŸ’Ύ 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 it 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!

31 Update translations

Find it on GitHub

Update translations in readme.md file.

32 Add example card xml

Find it on GitHub

Follow the instructions in the docs to make an xml file with example cards, and make sure the program works on it!

33 Make the site responsive

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.

:fire: Problem

![Screenshot20191220191525](https://user-images.githubusercontent.com/35997844/71281006-1f2a0680-235d-11ea-91bc-cbf9f0155eaf.png)

![Screenshot20191220191502](https://user-images.githubusercontent.com/35997844/71281013-25b87e00-235d-11ea-9d0b-9634dc32266e.png)

The current version of the site is not responsive. :cry: Your job is to make it look great on mobile devices. :iphone:

Don't worry though, it will only take you a few simple edits. πŸ“

🚩 Goal

![Screenshot20191220191935](https://user-images.githubusercontent.com/35997844/71281381-053cf380-235e-11ea-9d71-407e357d48b6.png)

![Screenshot20191220192013](https://user-images.githubusercontent.com/35997844/71281399-0ec65b80-235e-11ea-9847-343e3271add6.png)

πŸ“‹ 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!

  • [ ] πŸ“ Open image-sequencer/examples/demo.css Below #gif selector(line 154) add this code:

  • line 47 -> remove min-width rule

  • line 69 -> remove min-width rule

css @media(max-width: 768px) { #dropzone { margin: 0 0% 30px; } }

Open image-sequencer/examples/index.html - line 58 remove inline styles from header

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!

34 Make footer topics section responsive

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.

:fire: Problem

![Screenshot20191219195245](https://user-images.githubusercontent.com/35997844/71201320-102e5000-229a-11ea-9557-28afd203efe1.png)

![Screenshot20191219195354](https://user-images.githubusercontent.com/35997844/71201326-13294080-229a-11ea-807b-5019af12cec7.png)

![Screenshot20191219195422](https://user-images.githubusercontent.com/35997844/71201329-16243100-229a-11ea-94c4-d0512945a508.png)

The footer topics section looks really bad :( That's why you are here, right?

Make it responsive 😎

🚩 Goal

![Screenshot20191219195507](https://user-images.githubusercontent.com/35997844/71201360-29cf9780-229a-11ea-97c1-4d5584de1140.png)

![Screenshot20191219195553](https://user-images.githubusercontent.com/35997844/71201408-3f44c180-229a-11ea-81f7-7d27d3157337.png)

![Screenshot20191219195633](https://user-images.githubusercontent.com/35997844/71201414-44a20c00-229a-11ea-9704-d26c7d1b33c9.png)

πŸ“‹ 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!

  • [ ] πŸ“ Open plots2/app/assets/stylesheets/style.css After the footer ul selector(line 278) add this code:

```css .footer-topics .row { justify-content: space-around; }

.footer-topics .row .col-md-3 { flex-basis: 50%; max-width: fit-content; }

@media(max-width: 768px) { .footer-topics .row .col-md-3 { max-width: none; text-align: center; } } ```

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!

35 Replace dep @types/blob-util (it's deprecated)

Find it on GitHub

Current behavior:

We include @types/blob-util as a dep in the cli here: https://github.com/cypress-io/cypress/blob/v4.0-release/cli/package.json#L64:L64

As mentioned in this PR https://github.com/cypress-io/cypress/pull/5684#pullrequestreview-316174984, this dep has been deprecated since blob-util provides it's own types in their package as mentioned here: https://www.npmjs.com/package/%40types/blob-util

Desired behavior:

Replace use of @types/blob-util to include the types correctly.

Versions

3.8.0

36 cy.wrap does not respect timeout

Find it on GitHub

This example spec file fails with the error below:

js describe('Cypress wait', () => { it('wrap does not wait', () => { cy.wrap( new Promise((resolve) => setTimeout(resolve, 5000)), {timeout: 20000}); }); });

``` Cypress wait 1) wrap does not wait

0 passing (4s) 1 failing

1) Cypress wait wrap does not wait: Error: Cypress command timeout of '4000ms' exceeded. at http://localhost:57838/_cypress/runner/cypressrunner.js:103532:25 ```

Shouldn't cy.wrap respect the timeout option? The test passes if I pass --config defaultCommandTimeout=6000 on the command line, but I want to pass a specific timeout for this cy.wrap command.

37 Add PWA for our reacties application

Find it on GitHub

To implement PWA for our codingAI reactjs application.

38 Change script path in map dependancies to match with LEL

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 _mapDependencies.html.erb in the plots2 repository .

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

Remove the line here:

https://github.com/publiclab/plots2/blob/3f239088f6028b2e87668f7cd9076295dfe4e79d/app/views/map/_mapDependencies.html.erb#L20-L21

and add: <%= javascript_include_tag('/lib/leaflet-environmental-layers/lib/glify.js') %> <%= javascript_include_tag('/lib/leaflet-environmental-layers/lib/leaflet-fullUrlHash.js') %>

to match what we currently have on the leaflet environmental layers library.

  • [ ] πŸ’Ύ 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!

39 Links on Homepage redirects to 400 Bad Request page

Find it on GitHub

Description

As a user, I need the links on the homepage to be correct, so that I can learn more about AnitaB.org communities.

When clicking some buttons on the homepage, I get redirected to 400 Bad Request, because old website - http://anitaborg.org/ - does not redirect to the current AnitaB official website - https://anitab.org/.

E.g.: http://anitaborg.org/get-involved/systers/systers-initiatives/ should be http://anitab.org/get-involved/systers/systers-initiatives/ (which actually like this, redirects to https://anitab.org/systers/systers-initiatives/)

I think the file that handles this is /develop/systers_portal/templates/common/index.html.

Mocks

What I get right now: ![image](https://user-images.githubusercontent.com/11148726/70841402-0fb53580-1e12-11ea-969c-efcd03be8ecd.png)

Acceptance Criteria

Update [Required]

  • [ ] Make all links on homepage redirect to a valid page instead of 400 Bad Request

Definition of Done

  • [ ] All of the required items are completed.
  • [ ] Approval by 1 mentor.

Estimation

1 hour

40 should('not.be.visible') fails for non visible elements dur to overflow: hidden and set height

Find it on GitHub

Current behavior:

There continues to be issues with visibility tests. I saw the list of issues compiled at https://github.com/cypress-io/cypress/issues/1242 but I am not sure this is one of the issues still listed as open.

In summary: an element that is not visible due to parent overflow: hidden is still reported as visible.

Desired behavior:

Elements not visible due to parent overflow: hidden should be reported as not visible by cypress.

Steps to reproduce: (app code and test code)

Use this code:

``js describe('', () => { before(function() { let html =<!DOCTYPE html>

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin fermentum, velit at eleifend tempus, mi mauris dapibus nunc, vitae semper tellus augue non purus. Suspendisse potenti. Praesent laoreet ornare lorem. Quisque pellentesque tempor magna sit amet facilisis. Pellentesque eleifend dui in nunc tempor, lacinia ullamcorper nunc aliquam. Mauris pretium tincidunt nunc, quis vehicula purus volutpat non. Donec consequat erat velit, nec tincidunt mauris dignissim quis. Sed consectetur, diam dictum feugiat faucibus, dui ex ullamcorper odio, ac rhoncus risus lacus et eros. Sed et vestibulum neque, a viverra felis. Ut quam nisi, dapibus efficitur arcu quis, mollis rhoncus justo. Morbi tristique consectetur tortor. Phasellus posuere, nulla et tempus mollis, est lacus malesuada felis, ac tempor risus ipsum at sapien. Nam ac urna purus. Ut vitae urna ornare, convallis magna vitae, posuere tellus.

Vestibulum

Morbi nisl nunc, tincidunt vel est eu, commodo venenatis lorem. Etiam malesuada sagittis magna, sed suscipit orci tristique vel. Proin vulputate rhoncus dictum. Suspendisse volutpat congue metus, ut egestas magna sollicitudin in. Morbi mollis malesuada urna, vitae laoreet elit rutrum rutrum. Cras at tincidunt justo. Donec varius nisi a dolor vehicula sodales. Quisque eu nisl hendrerit, cursus massa sit amet, convallis nulla. Phasellus dapibus facilisis tellus, sed faucibus mauris gravida ultricies. Sed facilisis efficitur nunc, et vehicula augue dictum ac. Nunc sed ante lorem. Vivamus dapibus ante quis urna dignissim rutrum quis a elit. Nam at mi sit amet felis eleifend ultrices.

Curabitur

In risus ligula, fermentum nec libero eget, faucibus rutrum libero. Proin ligula turpis, porttitor ac nisl pulvinar, aliquet pretium nulla. Aliquam vel porta ante. Nullam dictum enim a justo elementum, et accumsan magna malesuada. Suspendisse lacinia, urna sed egestas scelerisque, lectus arcu congue sapien, quis sollicitudin nibh massa ut lorem. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Sed mattis aliquet libero, ac porta enim sagittis quis. Pellentesque interdum ipsum euismod, sollicitudin est eu, commodo orci. Sed a arcu justo. Sed dignissim, arcu vitae vehicula imperdiet, diam neque pellentesque leo, quis bibendum dolor lectus eu tellus. In faucibus, tellus nec malesuada consectetur, quam dolor pretium diam, at vehicula massa lacus nec ligula. Aliquam ornare, mi in vehicula commodo, sem magna dignissim felis, vel hendrerit erat elit quis nulla.

`; cy.document().then(document => { document.write(html); document.close(); }); });

it('', function() { cy.get('.accordion-content').should('exist').should('not.be.visible'); }); }); ```

Versions

cypress 3.8.0

41 Add Commenting Guidelines to CONTRIBUTING.md

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 is to be done?

We are working towards standardizing all the comments in the codebase to make the docs look professional. One of the main steps towards this would be to add some guidelines to the CONTRIBUTING.md file. Some guidelines are listed below (you can add your own too if you feel it is necessary)

  1. Methods must be described using JSDoc comments
  2. Misc code comments should be inline unless it is a long sentence.
  3. No use of continuous tenses, no pronouns.
  4. No redundant comments.
  5. Each comment should start with an uppercase letter and end with a full stop.

πŸ€” 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!

  • [ ] πŸ“ Modify the file [CONTRIBUTING.md]

  • [ ] πŸ’Ύ 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 it 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!

42 Improve application performance

Find it on GitHub

Improve our CodingAI application performance.

43 Add / List the React Component

Find it on GitHub

List out / Add React component for codingAI application and it improve our application.

44 file name contains character ”+β€œ not run

Find it on GitHub

the file cy_web+_20191207220608.js is exsite, but run cypress,

Cannot find module web _20191207220608.js, this character ”+β€œ instead of " ", so not find the file.

Current behavior:

``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Cypress: 3.7.0 β”‚ β”‚ Browser: Electron 73 (headless) β”‚ β”‚ Specs: 1 found (web+20191207220608/web+20191207220608.js) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

────────────────────────────────────────────────────────────────────────────────────────────────────

Running: web+20191207220608/web+20191207220608.js (1 of 1)

Oops...we found an error preparing this test file:

/home/admin/cypress/web _20191207220608/web _20191207220608.js

The error was:

Error: Cannot find module '/home/admin/cypress/web _20191207220608/web _20191207220608.js' from '/home/admin/cypress'

This occurred while Cypress was compiling and bundling your test code. This is usually caused by:

  • A missing file or dependency
  • A syntax error in the file or one of its dependencies

Fix the error in your code and re-run your tests. ```

45 Secure and performant code

Find it on GitHub

I just jumped to JavaScript manipulating Dom and Asyn programming. So I am a n00b x) JS code is executed in client side, so a webmaster is only responsible for the exact first version served to client through the requested URL; However, even for this JS file, I want to be sure it meets minimum security for the client and other endpoints (cdnjs is requested to load JavaScript libraries) All code is concerned.

46 Better code

Find it on GitHub

I just jumped to JavaScript manipulating Dom and Asyn programming. This is very new to me, I know code is very poorly written. There is only one JS file and one HTML file. All code is concerned. Task: code review or pass into : https://jshint.com/

47 Add popover to list authors on wiki page headings

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.

What is to be done.

Wiki pages now have this great header showing Authors, Revisions, and the talk page:

![image](https://user-images.githubusercontent.com/24359/70264384-4c27c800-1766-11ea-80aa-168dab23f0c0.png)

Let's make it so you can click the Authors item and see a Bootstrap popover listing the authors' usernames.

The code for that is here:

https://github.com/publiclab/plots2/blob/6d417a384801e4c20b77c4d6360788f19a78b41c/app/views/wiki/_header.html.erb#L34-L36

We can get the authors listing using node.authors, as shown here:

https://github.com/publiclab/plots2/blob/6d417a384801e4c20b77c4d6360788f19a78b41c/app/models/node.rb#L278-L280

And for each one, we could do the following so that their names are clickable and lead to their profile pages!

html <ul> <% node.authors.each do |author| %> <li><a href="/profile/<%= author.username %>">@<%= author.username %></a></li> <% end %> </ul> That code can go inside the popover!

πŸ“‹ 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 $FILENAME in the $REPO 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 $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!

48 Convert reactjs into redux component

Find it on GitHub

  1. Convert our reactjs applications into redux applications as separate branch.
  2. We have created the separate folder name as redux-coding-ai and will create the branch.
  3. We have to create the components

49 Add reactjs deployment / build feature

Find it on GitHub

We have create the deployment / build feature or improvement in our codingAI applications .

50 Add contribution list dynamically

Find it on GitHub

Dynamically create the contributions list who participated in our applications like bot create contributions list once we have configure.

51 Add some needed bot for reactjs application

Find it on GitHub

List out useful needed bot for reactjs applications.

52 Update readme file

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 $FILENAME in the $REPO 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 $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!

53 Make Join and Readings pages cross-link better

Find it on GitHub

Maybe as simple as putting a link/button to the Readings page on the Join page (and maybe change the link to the Join page to a button on the Readings page)

54 mixed content error

Find it on GitHub

Describe the bug Firefox is giving mixed content error because http urls are used for music album images: http://assets.fanart.tv/fanart/music/11ae9fbb-f3d7-4a47-936f-4c0a04d3b3b5/cdart/white-blood-cells-55fcd7d5b036b.png

To Reproduce Request music album, your browser will then show mixed content error.

Screenshots ![afbeelding](https://user-images.githubusercontent.com/1236301/69956837-69a82800-1501-11ea-8c1a-f9e1b54c7c24.png)

Desktop (please complete the following information): Running ombi Docker

Ombi Version (please complete the following information): 3.0.4892

55 create template for mentor profile

Find it on GitHub

  1. To create template for mentor profile and creativity way
  2. It allow different types of color based themes displaying mentors profiles as user selections.
  3. Showing the white background as default theme.

56 create the logo

Find it on GitHub

create the logo for 10secondsofcode and size will be 100100, 200200, 300300, 400400

57 Feature request: --cypress-env-file flag

Find it on GitHub

I have various different "scenarios" that are saved in cypress.env.json-like files. It would be favorable if I could override the file to be used as the cypress.env.json file at the command line.

Something like:

$ cypress open --cypress-env-file=cypress.env.my-test-scenario.json

58 [C++]Add more test code in unit test of the Rank type

Find it on GitHub

The unit test in https://github.com/HenryRLee/PokerHandEvaluator/blob/master/cpp/test/rank.cc only covers a small number of cases. Especially the TestRankCategory and TestRankDescription, only a full house and a straight flush appears in the test. I am expecting 3 to 5 hands from each ranking category are covered in the test code. For example, choose 3 hands from the straights, 5 hands from the pairs, etc.

You may refer to the source code in 7462.c, rank.c and rank.h when coding the unit test cases.

PS: When running the unit tests, you can use ./unit_tests --gtest_filter="Rank*" to test only the test cases related to the Rank type, and skip the time-costing enumeration test.

59 `cypress run` does not log `stderr` from plugins

Find it on GitHub

Current behavior:

Run this existing spec that has a plugin which logs to process.stderr:

npm run cypress:run -- --project ./packages/server/test/support/fixtures/projects/system-node npm run cypress:open -- --project ./packages/server/test/support/fixtures/projects/system-node

https://github.com/cypress-io/cypress/blob/99ec5c7b41dd6865dda9a597cc686b19280d6a39/packages/server/test/support/fixtures/projects/system-node/cypress/plugins/index.js#L1-L5

It will log in cypress open, but not cypress run.

Desired behavior:

The pluginsfile should log either way.

60 UI / UX designer help

Find it on GitHub

  1. Creativity create the logo for our website and it size will be 100 X 100, 200 X 200, 300 X 300, 75 X 75.

  2. Create the background image for mentors and it will help to find this projects mentors.

61 Fix pluralization logic III

Find it on GitHub

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

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

![image](https://user-images.githubusercontent.com/41092741/69100165-8f75fd00-0a2a-11ea-99fb-cb42733cbaa4.png)

The pluralization in the screenshot above is incorrect (ie. should be "1 person" not "1 people")

Solution

This is a simple one -- lets find the relevant line of code first:

https://github.com/publiclab/plots2/blob/a5d3392c3d6f5f4daaa56d5a4431e1bc0de5c46c/app/views/tag/_profileCard.html.erb#L7

As you can see, this line has no conditional and "people" will always just be plural.

Let's correct this: - Rails gives us a really convenient way to resolve it through the pluralize method.

Update the inner a tag to use the method like so:

ERB <a href="/tag/<%= tag.name %>"><%= pluralize(Tag.follower_count(tag.name), 'person') %> discussing</a>

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/plots2
    • [ ] 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, an additional checklist will be provided for getting it merged

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.

πŸ’¬ Get help

If you need any help - here are some options:

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

62 Create mentor tweeter retweet

Find it on GitHub

Create mentor tweeter retweet node app

63 Create sponsors template for our project

Find it on GitHub

Create sponsor template for our projects.

64 Add any feature to improve app

Find it on GitHub

Anyone will suggest to improve our app.? Let us know your thoughts..!

65 Fix codacy code quality issues

Find it on GitHub

Fix issues listed on codacy. https://app.codacy.com/manual/faruktoptas/FancyShowCaseView/issues

66 Change function t to translation in grids/_wikis

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

On line 18 the function t(...) needs to be changed to translation(...) https://github.com/publiclab/plots2/blob/50b355aca3a58bdbfe5fffe6c37f0b902ee1bd00/app/views/grids/_wikis.html.erb#L18

Change to: <td><%= distance_of_time_in_words(Time.at(wiki.latest.created_at), Time.current, { include_seconds: false, scope: 'datetime.time_ago_in_words' }) %> <%= raw translation('wiki._wikis.by') %>

  • [ ] πŸ’Ύ 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!

67 After all hook is masking syntax errors

Find it on GitHub

Current behavior:

With code like this:

js before(() => { notExistingFunction() // syntax error }) after(() => { cy.get('foo').type('bar'); })

Cypress reports:

```js CypressError: cy.type() failed because it requires a DOM element.

The subject received was:

undefined

The previous command that ran was:

cy.get()

Because this error occurred during a 'after all' hook we are skipping the remaining tests in the current suite ```

Desired behavior:

The one that is happening when you remove after hook, so: ``` ReferenceError: notExistingFunction is not defined

Because this error occurred during a 'before all' hook we are skipping the remaining tests in the current suite: ``` <!-- A clear concise description of what you want to happen -->

Steps to reproduce: (app code and test code)

Above - it think it also mask errors in tests as well (it) <!-- Issues without reproducible steps WILL BE CLOSED -->

Versions

Cypress 3.6.1 (bug is at least since 3.4) MacOS Mojave Chrome Version 78.0.3904.87 (Official Build) (64-bit) <!-- Cypress, operating system, browser -->

68 3.6.1 Special characters wrongly displayed in runner UI assertions

Find it on GitHub

Current behavior:

![cypress](https://user-images.githubusercontent.com/13650820/68743031-d52d6280-05f1-11ea-9541-ed2608b1cc4e.PNG)

Desired behavior:

Special characters properly displayed

Steps to reproduce: (app code and test code)

for e.g. use assertion with regex: should('match', /width: (50.*|49.*|48.*)%;/)

Versions

3.6.1

69 Create a Wikipedia Page for Gaphor

Find it on GitHub

I'm submitting a...

  • [ ] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
  • [ ] Feature request
  • [X] Documentation issue or request

Gaphor isn't found on Wikipedia, and is absent in the list of UML tools. It would be great if it was represented. Creating a wiki page is some work, see this overview.

70 Remove unused variable

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.

Problem

There is one unused variable f in the parse() method.

πŸ“‹Solution

Delete the variable

https://github.com/publiclab/simple-data-grapher/blob/49a1971eac1dad800ab37fe56db4fae235a65da8/src/CsvParser.js#L74 - [ ] πŸ™‹ 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

  • [ ] πŸ’Ύ 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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

71 change function t to translation in app/views/notes/_comments.html.erb

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 _comments.html.erb in the $REPO 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 are the lines where you need to change t() to translation() :

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/_comments.html.erb#L4

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/_comments.html.erb#L18

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/_comments.html.erb#L21

  • [ ] πŸ’Ύ 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.

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

72 change function t to translation in app/views/notes/_coauthored_notes.html.erb

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 coauthorednotes.html.erb in the https://github.com/publiclab/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 are the lines where we have to make changes change t() to translation():

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/coauthorednotes.html.erb#L14

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/coauthorednotes.html.erb#L15

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/coauthorednotes.html.erb#L16

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/coauthorednotes.html.erb#L18

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/coauthorednotes.html.erb#L31

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/view s/notes/coauthorednotes.html.erb#L34

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/coauthorednotes.html.erb#L51

https://github.com/publiclab/plots2/blob/c7d8fe5ed09ac4df932e9309ceb44621e6091aeb/app/views/notes/coauthorednotes.html.erb#L55

  • [ ] πŸ’Ύ 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!

73 Help me to review my pull request

Find it on GitHub

Help me to review my pull request

I migrate this project from netcore 2.2 to netcore 3

https://github.com/rullyrmd/firsttimersonly/pull/4

thank you

74 Features/migrate to netcore 3

Find it on GitHub

pls review my pull request

I migrate this project from dotnet core 2.2 to dotnet core 3 and also add sln. to this project for visual studio support

75 Add instructions for adding git upstream remote in the README

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.

The issue is to update the setup instructions in the readme to include the command for adding the publiclab/plots2 repo as the upstream remote. By adding this repo as a remote the contributor can easily pull the latest changes of the repo. Read more about setting git remotes here.

πŸ“‹ 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 README.md 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:

go to this section of the README and make the following changes.

diff - 3. Enter the new plots2 directory with `cd plots2`. + 3. Enter the new plots2 directory with `cd plots2` and then enter `git remote add upstream https://github.com/publiclab/plots2.git` in the command line.

  • [ ] πŸ’Ύ 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!

76 change function t to translation of views/grids/_thumbnail

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 $FILENAME in the $REPO 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: change the function t to translation in lines 23 and 26. After changing the lines should look like below:

diff <%= translation('notes._notes.last_edit_by') %> <a href="/profile/<%= node.latest.author.name %>"><%= node.latest.author.name %></a> | <i class="fa fa-eye"></i> <%= number_with_delimiter(node.views) %> <span class="d-none d-md-inline"><%= translation('notes._notes.views') %></span>

  • [ ] πŸ’Ύ 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!

77 change function t to translation in layouts/application.html.erb

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 $FILENAME in the $REPO 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 $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!

78 change function t to translation in sidebar/_author.html.erb

Find it on GitHub

Taking one issue from #6579

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 sidebar/_author.html.erb in the https://github.com/publiclab/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 showing where to make changes:

https://github.com/publiclab/plots2/blob/a720e67ec6a5bb425ad23cae21da96456c993eca/app/views/sidebar/_author.html.erb#L8

change this to: <h4><%= raw translation('sidebar._author.recent_tags_for_author', :url1 => "/people/"+@user.name, :author => @user.name) %></h4>

  • [ ] πŸ’Ύ 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!

79 Change function t to translation in layouts/_alerts.html.erb

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 layouts/_alerts.html.erb in the https://github.com/publiclab/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 showing where to make changes:

In plots2/app/views/sidebar/_author.html.erb file, change occurrences of function t(...) to translation(...) on line number 26.

<div class="alert alert-warning"><button type="button" class="close" data-dismiss="alert">Γ—</button><i class="fa fa-exclamation-mark"></i><%= t('layout._alerts.request_access') %><a href="/openid/resume"><%= t('layout._alerts.approve_or_deny') %> &raquo;</a></div><% end %><% cache('feature_sitewide-alert', skip_digest: true) do %><%= feature('sitewide-alert') %><% end %></div><script> setTimeout("$('.alerts-container .alert-success').fadeOut('slow')", 7000)</script>

change this to:

<div class="alert alert-warning"><button type="button" class="close" data-dismiss="alert">Γ—</button><i class="fa fa-exclamation-mark"></i><%= translation('layout._alerts.request_access') %><a href="/openid/resume"><%= translation('layout._alerts.approve_or_deny') %> &raquo;</a></div><% end %><% cache('feature_sitewide-alert', skip_digest: true) do %><%= feature('sitewide-alert') %><% end %></div><script> setTimeout("$('.alerts-container .alert-success').fadeOut('slow')", 7000)</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 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!

80 Profile dropdown menu gets cut off on smaller screens

Find it on GitHub

Referencing Issue #6574 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 $FILENAME in the $REPO repository (press the little pen Icon) and edit the line as shown below.

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!

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

diff $DIFF Problem Currently, the navigation bar is fixed on top. The issue is that on a smaller screen( ie mobile phone or minimize Pc screen to phone screen size), one is unable to view all the elements in the dropdown menu. as shown below url https://publiclab.org/ or https://publiclab.org/blog

![image](https://user-images.githubusercontent.com/49034794/68250053-1a212a00-0031-11ea-8581-99c3d2a1dbf4.png)

Expected the menu should be scrollable so as to view all menu elements. (see image below) ![image](https://user-images.githubusercontent.com/49034794/68250915-11c9ee80-0033-11ea-8e4d-11f8e939c382.png)

to make changes, navigate to plots2/app/views/layouts/_header.html.erb at the extreme end of the file in ()and the code below (add lines 188 to 194) code to be added as shown in blue on the right side of the picture ![image](https://user-images.githubusercontent.com/49034794/68249709-6750cc00-0030-11ea-9b1a-a5a0678012de.png)

81 Add storybook / components snapshots in readme

Find it on GitHub

82 Contribute more snippets!

Find it on GitHub

check out the files in the snippets/ folder, and try to contribute something nice. Include pic/gif or vid in PR.

83 Browse and find the errors

Find it on GitHub

Finding the bug in https://mentors.10secondsofcode.com website and create the issue and will add reproduce able steps

84 Change function t to translation in dashboard/_comment_moderate

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

In this template we need to change the function named t(....) to be named as translation(...) on lines 4, 5, 6, and 8.

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/commentmoderate.html.erb#L4-L8 change to: <%= translation('dashboard._comment_moderate.first_time_post') %> <a class="btn btn-outline-secondary btn-sm" href="/admin/publish_comment/<%= comment.id %>"><%= translation('dashboard.moderate.approve') %></a> <a class="btn btn-outline-secondary btn-sm" href="/admin/mark_comment_spam/<%= comment.id %>"><%= translation('dashboard.moderate.spam') %></a> <% else %> <%= raw translation('dashboard.moderate.pending_approval', :url => '/wiki/moderation') %>

  • [ ] πŸ’Ύ 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!

85 Change function t to translation in dashboard/_activity

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

In this template we need to change the function named t(....) to be named as translation(...) on lines 1, 19, 27, 36, 42, 48, 54, 61, 72, and 74.

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L1 change to ```

<%= translation('dashboard.activity.activity') %>

```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L19 change to ```<%= translation('dashboard.activity.all_updates') %>```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L27 change to ```<%= translation('dashboard.activity.dropdown.all') %>```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L36 change to ```<%= t('dashboard.activity.dropdown.research_notes') %>```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L42 change to ```<%= translation('dashboard.activity.dropdown.question') %>```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L48 change to ```<%= translation('dashboard.activity.dropdown.events') %>```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L54 change to ```<%= translation('dashboard.activity.dropdown.comments') %>```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L61 change to ```<%= translation('dashboard.activity.dropdown.wiki') %>```

https://github.com/publiclab/plots2/blob/9027525dbe504db82276e12ec59dfb00c7a45961/app/views/dashboard/activity.html.erb#L72-L75 on these lines notice that there are 4 instances to change! ``` <%= translation('dashboard.activity.fromother') %> <%= translation('dashboard.activity.communityscientists') %> <%= translation('dashboard.activity.pastweek') %> <% if currentuser %> | here is a great tutorial on how to send a pull request using the terminal.

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

    • [ ] 🏁 Done Ask in comments for a review :)

    Please keep us updated

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

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

    Is someone else already working on this?

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

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

    πŸ€”β“ Questions?

    Leave a comment below!

    86 add tests for {moveToStart} / {moveToEnd} special sequences

    Find it on GitHub

    add better tests for {moveToStart} / {moveToEnd} special char sequences

    they were added in #4870 but not called out in changelog / documented / or tested, making it one of those "undocumented features")

    • after this is fixed, we can open PR for adding to docs

    87 Added Quote

    Find it on GitHub

    Added Confucius quote.

    Source of Truth: https://www.goodreads.com/quotes/3214-it-does-not-matter-how-slowly-you-go-as-long

    88 Add space in the button for clarity

    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.

    Problem

    πŸ“‹Solution

    • [ ] πŸ™‹ 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 Add space after Create Spreadsheet in this line below https://github.com/publiclab/simple-data-grapher/blob/49a1971eac1dad800ab37fe56db4fae235a65da8/dist/PublicLab.Grapher.js#L1463

    • [ ] πŸ’Ύ 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 :)

    πŸ€”β“ Questions?

    Leave a comment below!

    Is someone else already working on this?

    We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

    89 Update No. of downloaded pics after online update

    Find it on GitHub

    90 Add Linux Support

    Find it on GitHub

    91 Add Mac Os support

    Find it on GitHub

    92 add inspirational quotes from Elon Musk, Steve Jobs and Will Rogers

    Find it on GitHub

    add inspirational quotes from Elon Musk, Steve Jobs and Will Rogers

    93 Change function t to translations in dashboard/_comment_moderate

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

    In this template we need to change the function named t(....) to be named as translations(...) on lines 4, 5, 6 and 8.

    https://github.com/publiclab/plots2/blob/50164b13d612be00c5f700bb302af103a881e63c/app/views/dashboard/commentmoderate.html.erb#L4-L8

    After the changes it should look like this: <%= translation('dashboard._comment_moderate.first_time_post') %> <a class="btn btn-outline-secondary btn-sm" href="/admin/publish_comment/<%= comment.id %>"><%= translation('dashboard.moderate.approve') %></a> <a class="btn btn-outline-secondary btn-sm" href="/admin/mark_comment_spam/<%= comment.id %>"><%= translation('dashboard.moderate.spam') %></a> <% else %> <%= raw translation('dashboard.moderate.pending_approval', :url => '/wiki/moderation') %>

    • [ ] πŸ’Ύ 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!

    94 Update Signature.html

    Find it on GitHub

    Changed some font-size and font-weight

    95 Run espresso tests on travis-ci

    Find it on GitHub

    All test cases should be run on each push.

    96 [easier if you have familiarity with node] review contributing docs and ensure project builds

    Find it on GitHub

    IT would be nice to review our contributing docs and make sure they have all the info you need in order to build this project.

    Task:

    1. Clone this repo and read through the contributing md.
    2. Try to build a working copy of im-tables. If you're unsure about anything please ask for help by mentioning @yochannah and make sure to add these notes to our contributing docs for the next person.
    3. Make a PR with any changes you've made to the docs.

    if you want to pick up this task

    1. Take a look at the InterMine contributing guidelines
    2. Comment on this issue stating that you intend to work on the task
    3. When you're ready, add your work to the repo and create a pull request.

    What to do if you need help

    Mention @yochannah, tweet @yoyehudi, pop by to say hi on chat or if needed email yo@intermine.org. Don't forget we're usually only available during uk office hours and will not be able to respond at other times :)

    97 New Template added for email signature

    Find it on GitHub

    98 Updated my portfolio

    Find it on GitHub

    99 Making ParDow platform independent

    Find it on GitHub

    The project need to be ported to docker for cross-platform support. All clients and server will be spawned as a new docker container. Networking between all the container needs to be taken care of while creating the dockerfile.

    100 GUI hangs while downloading file.

    Find it on GitHub

    Tkinter runs in the main loop so while the file is downloading it freezes till the file is not downloaded. We need to run Tkinter in another thread so that it doesn't freeze the main loop.