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 INTERNSHIP : Add Summer and Winter Internship Programs offered by University across the world

Find it on GitHub

Every year lots of Universities accept a student for Summer and Winter Internship across the world. But lots of students fails to grab these opportunities due to lack of awareness.

If you know about such programs, please add the link in the specified section in table of content on README.md page.

2 SCHOLARSHIP : Add Scholarship Programs for Students

Find it on GitHub

3 EVENT : Add Student Competition and Challenges

Find it on GitHub

Please add in specified section

4 FIX : Search for Typo error and Fix It

Find it on GitHub

5 Add "from:____" tag to question breakout prompts

Find it on GitHub

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

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

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

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

πŸ€” What you will need to know.

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

πŸ“‹ Step by Step

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

  • [ ] πŸ“ Update the file app/views/notes/_comment.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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

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

```diff @@ -126,7 +126,7 @@ <% end %>

 <% if comment.body.include?('?') %>
  • Is this a question? Questions page.

  •  <p class="alert alert-info">Is this a question? <a href="/questions/new?title=<%= comment.body %>&tags=from:<%= comment.cid %>">Click here</a> to post it to the <a href="/questions">Questions page</a>.
    

    <% end %> <% if comment.parent.haspowertag('activity') && currentuser && currentuser.id == comment.uid %> ```

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

(This issue was created by First-Timers-Bot.)

6 HACKTOBERFEST : ADD your Introduction in Contributor list.

Find it on GitHub

Want to win a Hacktoberfest Tshirt ??

Just Add your name in new-contributors.md file and you are done.

Don't forget to give a :star: if you like the content.

7 Resource : Update CheatSheet of different programming Language

Find it on GitHub

8 Documentation: Remove "fonts folder" link from CONTRIBUTING.md

Find it on GitHub

This request is for

[x] Beginners [x] First Timers [x] Non-Coders (Markdown knowledge needed)

I'm submitting a...

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

Current behavior

The Fonts folder link in CONTRIBUTING.md (line 61 as of this writing) gives a 404 error, since the folder does not currently exist.

Expected behavior

Remove the link so there is no 404 error :)

Important

Before you make a pull request, please comment on the issue that you would like to work on it. That way, we can avoid duplicate PRs and a first-timer can work on this.

9 Documentation: Remove or Update "New features" link from CONTRIBUTING.md

Find it on GitHub

This request is for

[x] Beginners [x] First Timers [x] Non-Coders (Markdown knowledge needed)

I'm submitting a...


[ ] Bug report  
[ ] Feature request
[X] Documentation issue or request

Current behavior

Currently, the New features link on CONTRIBUTING.md (line 32, as of this writing) links to the very first issue I created last year. This doesn't work anymore as that issue has been closed (it was made for the 2017 version / branch) and there are no uses of a tag named "New Features"

Expected behavior

I think this link should either be removed entirely or replaced with a link to a different issue label

For example,

Instead of this [New features](https://github.com/scrabill/how-many-days-until-halloween/issues/1)

Something like this [Discussion](https://github.com/scrabill/how-many-days-until-halloween/issues?q=is%3Aissue+is%3Aopen+label%3Adiscussion)

Other examples would be to link to the Hacktoberfest tag

Important

Before you make a pull request, please comment on issue that you would like to work on it. That way, we can avoid duplicate PRs and a first-timer can work on this.

10 Typo in info.json

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 info.json by navigating to "\src\modules\FisheyeGl\info.json" and edit the lines as shown below.

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

  1. Go to lines 57 and 62:

```diff "desc": "Patht to a WebGL fragment shader file",

  "desc": "Patht to a WebGL vertex shader file",

2. Then change them as: diff "desc": "Path to a WebGL fragment shader file",

  "desc": "Path to a WebGL vertex shader file",

```

And you are done !!! πŸ‘

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

11 Remove Redundant text and Capitalize first word

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 as explained. See this page for some help in taking your first steps!

Navigate to the path "src\modules\Blur\info" and make changes to the info.json file

  1. Go to line 3 and line 7: ```diff "description": "Gaussian blur an image by a given value, typically 0-5",

"desc": "amount of gaussian blur(Less blur gives more detail, typically 0-5)", 2. Then modify them as follows: diff "description": "Gaussian blur an image by a given value",

"desc": "Amount of gaussian blur(Less blur gives more detail, typically 0-5)",

```

Before: ![image](https://user-images.githubusercontent.com/26546120/46913856-f36dfc80-cfb2-11e8-8a66-1f58b95561d7.png)

After: ![image](https://user-images.githubusercontent.com/26546120/46913975-9ecb8100-cfb4-11e8-9ffc-4a0fd71a0bdb.png)

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

12 Add more programming languages

Find it on GitHub

Add your favourite programming language to support TcSO: https://github.com/gautamkrishnar/tcso#contributing

Please see a list of currently available languages: https://github.com/gautamkrishnar/tcso#available-languages

Please comment on this issue and let the world know you are working on it.

13 Make it clearer that `timeout` configuration affects mocked as well as non-mocked requests

Find it on GitHub

In cy.request() and also main configuration doc, make it clearer that responseTimeout applies to mocked as well as non-mocked requests.

14 Document how to cause the test to fail after catching "fail" events.

Find it on GitHub

From this comment, we should document how to have the test fail when listening to "fail" events like:

js Cypress.on("fail", (err, runnable) => { // do what you want here // then fail test by returning err return err })

Place to document: https://docs.cypress.io/api/events/catalog-of-events.html#Catching-Test-Failures

15 Add link to view issues of entire organization

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 $index.html in the $community-toolbox repository (press the little pen Icon) and edit the line 45 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 + <p>To explore issues of entire organization. Check out <a href="https://code.publiclab.org/#r=all">Public Lab</a></p>

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

(This issue was created by First-Timers-Bot.)

16 Add link and explanation to tagging template

Find it on GitHub

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

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

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

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

πŸ€” What you will need to know.

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

πŸ“‹ Step by Step

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

  • [ ] πŸ“ Update the file app/views/tag/_tagging.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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

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

```diff @@ -1,5 +1,5 @@

Tags

-Tags help organize our knowledge base. Click to find more on a topic. +Tags organize our knowledge base. Click to learn more or subscribe to a topic.

<% if @node %> <%= render partial: 'tag/replication' %> ```

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

(This issue was created by First-Timers-Bot.)

17 Test issue #2

Find it on GitHub

18 Test Issue

Find it on GitHub

19 UI - Cypress logo scaling issue

Find it on GitHub

docs.cypress.io:

current (css width 100px)

![image](https://user-images.githubusercontent.com/14625260/46714395-346bb700-cc29-11e8-837b-92016edf72f8.png)

expected (css width 102px)

![image](https://user-images.githubusercontent.com/14625260/46714495-ae9c3b80-cc29-11e8-8049-03ecbf7ee9ef.png)

docs cypress logo looks blurred because it's scaled to 100px. We should consider using an image already sized.

20 Update `serialize()` object in `src/vessel-charging/BidParams.ts` and associated tests in `src/vessel-charging/BidParams.test.ts` using Jest

Find it on GitHub

first-timers-only

This issue is tagged πŸ•Ί first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

Find more first-timers-only issues from DAV Foundation here.

Thank you for your help :heart:

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

dav-js

This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.

How you can help

In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.

Here is a good opportunity to update one of our tests.

The Issue

In the src/vessel-charging/BidParams.ts class, the serialize() method is not returning our arguments correctly. provider, manufacturer and model are being set to this.amenities but they should be set to their associated arguments.

Currently: javascript public serialize() { const formattedParams = super.serialize(); Object.assign(formattedParams, { entranceLocation: this.entranceLocation, exitLocation: this.exitLocation, availableFrom: this.availableFrom, availableUntil: this.availableUntil, energySource: this.energySource, amenities: this.amenities, provider: this.amenities, manufacturer: this.amenities, model: this.amenities, }); return formattedParams; }

The Updates

Please update the test file src/vessel-charging/BidParams.test.ts to ensure amenities, provider, model, manufacturer are being handled correctly and update src/vessel-charging/BidParams.ts by passing the associated arguments to provider, manufacturer, model.

1. Update the tests

The test should ensure amenities, provider, model and manufacturer are being passed through and returning correctly in the test file src/vessel-charging/BidParams.test.ts.

Please update this test by:

  1. Adding Amenities to the ./enums import

javascript import { EnergySources, Amenities } from './enums';

  1. Add arguments amenities, provider, model and manufacturer to the instantiation of BidParams

javascript const bidParams = new BidParams({ // existing params amenities: [Amenities.Docking, Amenities.Grocery], provider: 'Charging Co', model: 'iCharger', manufacturer: 'Vessel Chargers', });

  1. Update serializedBidParams object with the arguments (amenities, provider, model and manufacturer) passed above

javascript const serializedBidParams: any = { // existing properties amenities: [Amenities.Docking, Amenities.Grocery], provider: 'Charging Co', model: 'iCharger', manufacturer: 'Vessel Chargers', };

After making your changes, run npm run jest.

You should receive an error similar to below.

![BidParams Error]error

This is expected as the serialize() method in src/vessel-charging/BidParams.ts is still returning provider, manufacturer and model as this.amenities.

The next update will fix this error.

2. Update serialize() in BidParams

The serialize() method in src/vessel-charging/BidParams.ts should return the arguments associated with provider, manufacturer and model.

  1. Update the serialize() method

javascript public serialize() { const formattedParams = super.serialize(); Object.assign(formattedParams, { entranceLocation: this.entranceLocation, exitLocation: this.exitLocation, availableFrom: this.availableFrom, availableUntil: this.availableUntil, energySource: this.energySource, amenities: this.amenities, provider: this.provider, manufacturer: this.manufacturer, model: this.model, }); return formattedParams; }

After making your changes, run npm run jest to make sure our tests are now passing.

Contributing to dav-js

  • [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
  • [ ] Comment on this issue that you would like to do it (if you're the first you can start working on it immediately)
  • [ ] Open dav-js GitHub page and click the β˜… Star and then β‘‚ Fork buttons
  • [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
  • [ ] Install dependencies by running npm install
  • [ ] Make sure everything is working and all tests pass by running npm run jest
  • [ ] Code Code Code
  • [ ] Make sure everything is still working and all tests pass by running npm run jest again
  • [ ] Commit all your changes
  • [ ] Push your local changes back to github with $ git push -u origin master
  • [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
  • [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
  • [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help

We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help πŸ˜„

21 videoRecording should be video in doc

Find it on GitHub

The key is wrongly referred to as videoRecording in the doc below although it's been renamed to video.

https://docs.cypress.io/guides/core-concepts/screenshots-and-videos.html#Videos

22 run-linux-mac.sh needs to updated to support python3

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 run-linux-mac.sh in the infragram-js 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 - python -m SimpleHTTPServer + python3 -m http.server

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

(This issue was created by First-Timers-Bot.)

23 Adding Space between Asking a Question And Exploring Projects Button

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

  • [x] πŸ™‹ 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!

Steps to be done:

Fork up the Repo

Clone your forked repo on local machine

Create a new branch and checkout using this

sh git branch SolvesSpacing git checkout SolvesSpacing - [x] πŸ“ Update

Go to app/assets/stylesheets/dashabord.css from your root structure

Code up this

sh @media (max-width:269px) { .btn.btn-sm.btn-default { margin-top:10px; } } - [x] πŸ’Ύ Commit using given syntax

Finally Commit and push code

sh git commit -am SolvesSpacing

  • [x] πŸ”€ 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 :)

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

(This issue was created by First-Timers-Bot.)

24 Spruce up our README

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

We would :heart: someone to craft a new README. We need a better description of what Gaphor is and is not, a nice gif showing it in action, and details about how to install it on the different platforms.

A good starting point may be to get the sections setup first, and then we can get the information added. https://github.com/matiassingers/awesome-readme has many resources and examples showing great READMEs for other projects.

25 Add SPOJ solutions that are not already present in the repo

Find it on GitHub

Keep filename as described : ProblemCode.extension

26 Add Codeforces solutions with filename as described

Find it on GitHub

Keep file name as follows: For question asked in Round#479(Div3) and falling in category B : Name should be 479div3b followed by the extension accoding to the programming language. Desired Languages : Python, Java, C, C++

27 Have proper documentation

Find it on GitHub

More often than not, the hobbyist developers will need to know about the methods in detail. Provide proper documentation for all the methods.

28 Add Math Functions

Find it on GitHub

Add the necessary math functions which Hobby kernels make use of.

29 Change the "maxLength" route registration syntax

Find it on GitHub

A route can be registered with the following syntax

yaml - route: uri: "/list/transactions/:creditCard(:credit-card:)" maxLength: 1024 * 1024 to: CreditCardService after: [ authentication, monitoring ] then: compress

To improve readability, we want to change the framework to support following syntax

A route can be registered with the following syntax

yaml - route: uri: "/list/transactions/:creditCard(:credit-card:)" with: maxLength: 1024 * 1024 to: CreditCardService after: [ authentication, monitoring ] then: compress

Check routesManager to find the relevant code. Please updates the tests accordingly.

30 getting game log should be streamlined

Find it on GitHub

Using AB.getLog() should also include AB.restoreGame() along with the match data as parameter.

There should also be AB.getLog(raw) that would output the game data without AB.restoreGame().

31 Disable the Save Sequence button until one step is added

Find it on GitHub

First Timers Only

Hi, this is a first-timers-only issue. This means this has been 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 you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

The Issue

The save-sequence button in the UI should be disabled until some step is added in the sequence.

Here's where the save-sequence button is made:

https://github.com/publiclab/image-sequencer/blob/9168c15cf9ece28521e92c5fb1d5dd453518c937/examples/index.html#L99

We can make the button disable at the start and then enable it on first click of Add step button. We have to also disable the button if all the steps are removed.

32 Register multiple URLs to the same handler

Find it on GitHub

As per the current implementation, we can map only one URL to one handler.

js router.on('GET', '/', (req, res, params) => { //process the request response here })

We want to support and an array of URL in the above method. So that multiple URLs can be registered at a time.

```js router.on('GET', ['/404.html', '/503.html', 'anyerror.html' ], (req, res, params) => { //process the request response here })

```

33 Enhancement: Improve Rendering for Mobile Devices

Find it on GitHub

I'm submitting a...


[ ] Bug report  
[x ] Feature request
[ ] Documentation issue or request

Current behavior

On smaller screens (simulated in a browser window) the spooky text is really small and everything seems squashed at the top of the screen. The default CSS can be tweaked so that there is a better visual for anyone viewing this on a mobile device.

For example

![screen shot 2018-10-05 at 9 42 37 pm](https://user-images.githubusercontent.com/17805262/46566196-fc423c80-c8e7-11e8-84d1-b4c6a9defb30.png)

Expected behavior

Larger text on mobile. Assets take up more of the mobile device real estate

If this is a feature request please fill out the following:


As a (user, developer, contributor, etc): User
I want: Better read the text on screen
So that: I know how many days there are until Halloween πŸ™ƒ

Environment


Browser:
- [ ] Chrome (desktop) version XX
- [x] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [x] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

34 Fix alignment of message in Add step box

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

Fixing the alignment of message "Select a new module to add to your sequence." in the Add step box on home page.

πŸ“‹ 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 index.html and demo.css in the image-sequencer 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 steps as to how to approach the solution:

  1. Go to https://github.com/publiclab/image-sequencer/blob/2e7e042baab7e0bf43b821ea9e197cacf6efeac2/examples/index.html#L81 and change it to - <p class="info">Select a new module to add to your sequence.</p>

  2. Go to demo.css and add the following lines in the end of the stylesheet: .info { padding: 8px; text-align: center; }

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

35 Remove wrong hint--you can require as a const

Find it on GitHub

πŸ†•πŸ₯☝ First Timers Only.

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

About First Timers Only.

πŸ€” What you will need to know.

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.

Once claimed we add you as contributor to this repository.

  • [ ] πŸ‘Œ Accept our invitation to this repository. Once accepted, assign yourself to this issue

  • [ ] πŸ“ Update the file getting-started/your-first-template.md in the squirrelly.js.org repository (press the little pen Icon) and edit the line as shown below.

```diff @@ -14,10 +14,6 @@ var Sqrl = require("squirrelly") //Or, if you're in the browser, Sqrl is already global

-{% hint style="info" %} -Don't import as a const,otherwise you won't be able to define your own helpers and filters.

-{% endhint %}

## 2. Create a Template

text ```

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

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

  2. You can edit files directly in your browser

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

πŸ€”β“ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

36 Add output of getTimeStampFromCurrentDateFormat

Find it on GitHub

Add output of the usage in readme file here

https://github.com/arshadkazmi42/custom-date-formatting#gettimestampfromcurrentdateformat

Add this output

Output: 1503858600000

37 Add an option to generate session id

Find it on GitHub

Currently, we use hyperid npm package to generate session id, which appends a counter to previously generated session-id. It might give a chance to hacker to guess next/previous session-id.

38 Add an options to ignore particular url from creating session automatically

Find it on GitHub

if autoCreate:true option is set, a session is created for all the URLs automatically. Instead, we want to give a pattern to include or exclude paths from creating a session automatically.

39 Write unit tests

Find it on GitHub

Following cases are tested manually. Need to write unit tests for auto-testing.

Scenarios auto-create: on * [DONE] Cookies are sent to the client * Client can send the session-id to the server either in header or cookies * Cookies are not created for all the routes but selected : not implemented yet * [DONE] When user makes request without cookies : create new * [DONE] When user makes request with expired cookies : create new * [DONE] When user makes request with about to expire cookies : renew * [DONE] When user makes request with invalid session-id : create new

auto-create: off * [DONE] When user makes request with invalid session-id : error * [DONE] When user makes request for secure page without cookies : redirect to login page * [DONE] When user makes request for secure page with cookies : do nothing * [DONE] When user makes request for secure page with expired cookies : redirect to login page * [DONE] When user makes request for secure page with about to expire cookies : renew cookies

check session_test.js for more detail.

40 Find an alternate way of encrypting cookie

Find it on GitHub

Currently, we're using cookie-signature npm package to sign the session-id. It attaches the actual string with the encrypted string. Hence we're planning to change this approach.

One of the possible solutions is saving actual str along with encrypted str in the session store instead of attaching it within the session-id.

41 Gracefully transition from old secret to new secret key

Find it on GitHub

A user may not want to use the same secret to encrypt/decrypt the session-id. But if he/she changes the secret, it'll invalidate all the previously encrypted session-ids. So we want to introduce an option "transition"

js { transition: { duration: 3600, //in seconds secret: "some complex secret" } }

When this property is present, all the previous sessions will be renewed using the new secret And all the new sessions will be created using the new secret. Next time when the user wants to update the key, he needs to copy new key to the old key and very new key to transition.secret.

42 Add clarifications to broken-down regEx

Find it on GitHub

πŸ†•πŸ₯☝ First Timers Only.

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

About First Timers Only.

πŸ€” What you will need to know.

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.

Once claimed we add you as contributor to this repository.

  • [ ] πŸ‘Œ Accept our invitation to this repository. Once accepted, assign yourself to this issue

  • [ ] πŸ“ Update the file src/regexps.js in the squirrelly repository (press the little pen Icon) and edit the line as shown below.

``````diff @@ -45,9 +45,10 @@ export function replaceParamHelpers (params) { }) return params } -// The initial RegExp broken down: +// The whole regular expression can be hard to comprehend, so here it's broken down. +// You can pass the string between "START REGEXP" and "END REGEXP" into a regular expression +// That removes whitespace and comments, and outputs a working regular expression.

-// Total RegEx: /* START REGEXP {{ *? //the beginning (?: //or for each possible tag ``````

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

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

  2. You can edit files directly in your browser

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

πŸ€”β“ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

43 Add serialize test for `src/ride-hailing/NeedFilterParams.test.ts` using Jest (first-timers-only)

Find it on GitHub

first-timers-only

This issue is tagged πŸ•Ί first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

Find more first-timers-only issues from DAV Foundation here.

Thank you for your help :heart:

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

dav-js

This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.

How you can help

In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.

Here is a good opportunity to simplify one of our tests.

The Issue

We need to add a test for the serialze() method in src/ride-hailing/NeedFilterParams.test.ts. This test is for src/ride-hailing/NeedFilterParams.ts.

Please add a test similar to this: javascript describe('serialize method', () => { it('should return serialized need params object with the current values', () => { expect(messageParams.serialize()).toEqual(serializedMessageParams); }); });

An example can be found here.

After making your changes, run npm run jest to make sure our tests are passing.

Contributing to dav-js

  • [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
  • [ ] Comment on this issue that you would like to do it (if you're the first you can start working on it immediately)
  • [ ] Open dav-js GitHub page and click the β˜… Star and then β‘‚ Fork buttons
  • [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
  • [ ] Install dependencies by running npm install
  • [ ] Make sure everything is working and all tests pass by running npm run jest
  • [ ] Code Code Code
  • [ ] Make sure everything is still working and all tests pass by running npm run jest again
  • [ ] Commit all your changes
  • [ ] Push your local changes back to github with $ git push -u origin master
  • [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
  • [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
  • [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help

We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help πŸ˜„

44 Update README

Find it on GitHub

Update readme file to look something like this

https://github.com/arshadkazmi42/android-contacts-scifiui/blob/master/README.md

45 Add codechef solution with its question code as filename

Find it on GitHub

46 Add explanation of lastIndex

Find it on GitHub

πŸ†•πŸ₯☝ First Timers Only.

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

About First Timers Only.

πŸ€” What you will need to know.

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

πŸ“‹ Step by Step

  • [x] πŸ™‹ Claim this issue: Comment below.

Once claimed we add you as contributor to this repository.

  • [x] πŸ‘Œ Accept our invitation to this repository. Once accepted, assign yourself to this issue

  • [ ] πŸ“ Update the file src/compile.js in the squirrelly repository (press the little pen Icon) and edit the line as shown below.

``````diff @@ -11,7 +11,7 @@ import { import P from './partials'

function Compile (str) { - var lastIndex = 0 + var lastIndex = 0 // Because lastIndex can be complicated, and this way the minifier can minify more var funcStr = '' var helperArray = [] var helperNumber = -1 ``````

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

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

  2. You can edit files directly in your browser

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

πŸ€”β“ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

47 Edit example default filter

Find it on GitHub

πŸ†•πŸ₯☝ First Timers Only.

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

About First Timers Only.

πŸ€” What you will need to know.

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

πŸ“‹ Step by Step

  • [x] πŸ™‹ Claim this issue: Comment below.

Once claimed we add you as contributor to this repository.

  • [x] πŸ‘Œ Accept our invitation to this repository. Once accepted, assign yourself to this issue

  • [ ] πŸ“ Update the file src/filters.js in the squirrelly repository (press the little pen Icon) and edit the line as shown below.

``````diff @@ -27,7 +27,7 @@ export var defaultFilters = { each of the default filters the user Has set to true. This opens up a realm of possibilities like autoEscape, etc. */ - // e: false, // Escape is turned off by default for performance + // somefilter: false, }

export var defaultFilterCache = { ``````

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

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

  2. You can edit files directly in your browser

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

πŸ€”β“ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

48 Documentation: ISSUE_TEMPLATE.md

Find it on GitHub

The purpose of an issue template is to guide Githubbers in providing detailed information when creating a new issue.

The main information I would like this issue template to include is as follows

  • Description of the feature, request or problem. Be specific. If it is a bug, what happened? What were you expecting to happen? If you are looking to make an improvement, outline what you are suggesting and how it might be achieved. You do not know how exactly to solve a problem or how to implement a new feature, but an idea can help to get the information started.

Here is an example of an issue template https://github.com/thepracticaldev/dev.to/blob/master/.github/ISSUE_TEMPLATE.md

Ours does not need to be that detailed but think about what information you would like to know as a maintainer or would be helpful for contributors to know.

49 Update README.md: Add Issue link

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 README.md in the image-builder-rpi repository (press the little pen Icon) and edit the line as shown below.

the line to be changed:-

-Check planning issue # 5 for other plans.

Replace # 5 with :- Issue_number- [5] Link- https://github.com/publiclab/image-builder-rpi/issues/5

Adding [tag] bracket followed by (link) without any space in between is used for adding links in Docs. Refer https://help.github.com/articles/basic-writing-and-formatting-syntax/#links

πŸ’Ύ Commit your changes

πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

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

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

🏁 Done Ask in comments for a review :) πŸ€”β“ 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 seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

50 Contribute more SVG Icons

Find it on GitHub

How to contribute?

51 Replace ez_setup and update setup.py and setup.cfg

Find it on GitHub

ez_setup is now no longer part of the official packaging process using setuptools. It would be :sparkles: to have someone remove this and make sure setup.py is up to date using the latest packaging guide: https://packaging.python.org/guides/distributing-packages-using-setuptools/

You may also be able to reference the Cookiecutter Templates to get a copy of a recent Python packaging format.

52 New Documentations for this API

Find it on GitHub

Need to make Documentations for this API. Either using Normal HTML or Use any Documentation Library.

53 Add yourself to Contributors.md

Find it on GitHub

Go ahead and add yourself to Contributors.md file

Steps to work on the issue

  • Create PR.
  • Add this in your PR description #8 (Note: This should not go as a commit message.)
  • Do not work on forked master branch. Create a new branch when working on this.

54 Add yourself to Contributors.md

Find it on GitHub

Add your self to Contributors.md .

Do not add yourself at the top. or bottom of the list. Add yourself to in between the list, doing this there will less chances of getting conflicts.

Also do tag the issue number in the PR description

55 Copy labelled shape meta data to pasted shape

Find it on GitHub

This issue is suitable for first-timers. But can be picked by other contributors too.

@alextychan has implemented a nice feature to copy paste labeled shapes in #53 . As a part of this issue, we've to copy paste the metadata of the labeled shape to the pasted shape: category, labels, tags, and attributes.

Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

56 'No file chosen' wrongly placed in Import Image module

Find it on GitHub

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

First Timers Only

Hi, this is a first-timers-only issue. This means this has been 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 you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

The Problem

'No file chosen' option in import image module is misplaced, ie. out of the box

![screenshot from 2018-09-29 22-14-47](https://user-images.githubusercontent.com/26546816/46248308-5ef18f00-c435-11e8-9fab-2db0722440ed.png)

The Solution

We need to modify css such that it comes inside border or under Choose file button. The line which needs to be mdified is:

https://github.com/publiclab/image-sequencer/blob/88364decf6a6111a0be31fd98010576d5c6f918e/src/modules/ImportImage/Ui.js#L16

https://github.com/publiclab/image-sequencer/blob/88364decf6a6111a0be31fd98010576d5c6f918e/src/modules/ImportImage/Ui.js#L11

You need to add class to it and add the new css for the specific class.

Instance Count = 1

57 Update tests for `src/vessel-charging/messages/ChargingCompleteMessageParams.test.ts` using jest (first-timers-only)

Find it on GitHub

first-timers-only

This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

Find more first-timers-only issues from DAV Foundation here.

Thank you for your help :heart:

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

dav-js

This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.

How you can help

In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.

Here is a good opportunity to simplify one of our tests.

The Issue

In src/vessel-charging/messages/ChargingCompleteMessageParams.test.ts we defined the following parameters at the beginning of the describe() block.

```javascript const messageParams = new MessageParams({ senderId: 'TOPIC_ID', });

const serializedMessageParams: any = { ttl: undefined, protocol: 'vesselcharging', type: 'chargingcompletemessage', senderId: 'TOPICID', }; ```

These parameters will need to accommodate additional unit tests.

Please update these parameters to be more dynamic by defining them to be mutable similar to src/vessel-charging/MissionParams.test.ts.

![Parameters]parameters

After making your changes, run npm run jest to make sure our tests are passing.

Contributing to dav-js

  • [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
  • [ ] Comment in this issue that you would like to do it.
  • [ ] Open dav-js GitHub page and click the β˜… Star and then β‘‚ Fork buttons.
  • [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
  • [ ] Code Code Code
  • [ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
  • [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
  • [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
  • [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help

We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help πŸ˜„

58 Add sorting button options to tag show template

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.

This will add some nice buttons to tag pages such as these: https://publiclab.org/tag/mobius

Which will allow for sorting what's displayed!

![screen shot 2018-09-25 at 11 58 38 am](https://user-images.githubusercontent.com/24359/46026912-7d186180-c0ba-11e8-815d-b5d49b991c09.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!

  • [ ] πŸ“ Update the file app/views/tag/show.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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

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

```diff @@ -2,11 +2,11 @@

<%= render partial: 'tag/show/header' %>

+ <% if @tags.first && params[:id][-1..-1] != "*" %> - <%= render :partial => "tag/graph", locals: { tags: @tags } %> + <%= render partial: "tag/graph", locals: { tags: @tags } %>

<% end %>

+ <%= render partial: 'tag/show/contributors' %>

<% unless @tags.try(:first).try(:parent).nil? %> @@ -20,7 +20,10 @@ <%= render partial: "tag/show/relatedtags" %> <%= render partial: 'tag/show/navtabs' %>

<%= render partial: 'tag/show/tab_content' %>

```

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

(This issue was created by First-Timers-Bot.)

59 Add handlers from a folder automatically

Find it on GitHub

Currently, there are 2 ways to add the handlers.

  1. from a folder
  2. from the code

We need to provide the way to add handlers automatically when a folder with name "handlers" presents either in the root of the project or in the same folder. You can take the reference of step 1 to know how to do it. Check muneem.js for more detail.

Bookmark this project to support us to grow.

60 Add ability to sort tag pages by likes/view counts

Find it on GitHub

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

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

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

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

πŸ€” What you will need to know.

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

πŸ“‹ Step by Step

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

  • [ ] πŸ“ Update the file app/controllers/tag_controller.rb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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

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

```diff @@ -85,6 +85,9 @@ def show @nodetype = params[:nodetype] || defaulttype @start = Time.parse(params[:start]) if params[:start] @end = Time.parse(params[:end]) if params[:end] + orderby = 'noderevisions.timestamp DESC' + orderby = 'node.views DESC' if params[:order] == 'views' + orderby = 'node.cachedlikes DESC' if params[:order] == 'likes'

 node_type = 'note' if @node_type == 'questions' || @node_type == 'note'
 node_type = 'page' if @node_type == 'wiki'

@@ -99,7 +102,7 @@ def show .references(:termdata, :noderevisions) .where('termdata.name LIKE (?) OR termdata.parent LIKE (?)', params[:id][0..-2] + '%', params[:id][0..-2] + '%') .paginate(page: params[:page], perpage: 24) - .order('noderevisions.timestamp DESC') + .order(order_by) else @tags = Tag.where(name: params[:id])

@@ -115,14 +118,14 @@ def show .references(:termdata, :noderevisions) .where('termdata.name = ? OR termdata.name = ? OR termdata.parent = ?', params[:id], othertag, params[:id]) .paginate(page: params[:page], perpage: 24) - .order('noderevisions.timestamp DESC') + .order(orderby) else nodes = Node.where(status: 1, type: nodetype) .includes(:revision, :tag) .references(:termdata, :noderevisions) .where('termdata.name = ? OR termdata.parent = ?', params[:id], params[:id]) .paginate(page: params[:page], perpage: 24) - .order('noderevisions.timestamp DESC') + .order(orderby) end end nodes = nodes.where(created: @start.toi..@end.to_i) if @start && @end ```

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

(This issue was created by First-Timers-Bot.)

61 List of small issues for beginners

Find it on GitHub

As you're willing to get support for your open source project, please let us know followings; Here is the list of issues suitable for @socialat/interns . feel free to add more or give your feedback

Please bookmark this project for future updates. And join it to support opensource community.

Non-technical Visit stubmatic for documentation issues.

62 Add "next step" to welcomebot message on pull requests

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 .github/config.yml in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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

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

```diff @@ -16,7 +16,7 @@ newPRWelcomeComment: >

# Comment to be posted to on pull requests merged by a first time user firstPRMergeComment: > - Congrats on merging your first pull request! πŸ™ŒπŸŽ‰βš‘οΈ Your code will likely be published to PublicLab.org in the next few days. In the meantime, can you tell us your Twitter handle so we can thank you properly? + Congrats on merging your first pull request! πŸ™ŒπŸŽ‰βš‘οΈ Your code will likely be published to PublicLab.org in the next few days. In the meantime, can you tell us your Twitter handle so we can thank you properly? Next, read https://code.publiclab.org/ to try helping someone else make their first contribution too!

```

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

(This issue was created by First-Timers-Bot.)

63 Update development guidelines

Find it on GitHub

We created technical.md to help new developers to understand the project structure and it's component better. However as the new features are being added, and existing code is being refactored, we need to improve the guideline.

Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

64 Fix full screen modal bug in mobile web

Find it on GitHub

Description

In mobile Chrome, there's a bug with our modal where the address bar is blocking the top part of the modal. Let's fix this!

This post may give you some insights on how to fix it.

Reproduction Steps

  1. Open mobile Chrome
  2. Open any modal (Notifications for example)

Screenshots

![image](https://user-images.githubusercontent.com/3010728/45913290-810b6180-bde4-11e8-9ce9-429ae6c74b5b.png)

Do you want to be the assignee to work on this?

🚫 <!--[NO, remove line if not applicable]-->

65 Update README.md

Find it on GitHub

πŸ†•πŸ₯☝ First Timers Only.

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

About First Timers Only.

πŸ€” What you will need to know.

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.

Once claimed we add you as contributor to this repository.

  • [ ] πŸ‘Œ Accept our invitation to this repository. Once accepted, assign yourself to this issue

  • [ ] πŸ“ Update the file README.md in the myfirstrepository repository (press the little pen Icon) and edit the line as shown below.

diff @@ -1,3 +1,5 @@ +# first-timers-only + # myfirstrepository A test repository changes made in testbranch_one

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

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

  2. You can edit files directly in your browser

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

πŸ€”β“ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

66 Urls redirecting to Cypress docs/dashboard do not stand out

Find it on GitHub

We should make the actionable item (visiting the link to the dashboard / error docs) more pronounced by changing the color of urls

67 Initial load screen disappears after a brief display

Find it on GitHub

Actual: When starting Check It Out in a large project, the initial loading text will display before promptly disappearing for the remainder of the load time.

Expected: The loading text should be displayed during the entire load process.


I think this has to do with the order of operations that take place during initial start up time. The loading text should persist until we successfully fetch and parse all of our information needed.

This is much easier tested on a large project. https://github.com/liferay/liferay-portal This is a large enough project with years of git refs.

Note: Please refer to Contributing guidelines before starting development. Thanks!

68 Add missing alt tags and aria-label to links and images

Find it on GitHub

Description

Add missing alt tags and aria-label to links and images

Helpful: https://a11yproject.com/

Do you want to be the assignee to work on this?

🚫 <!--[NO, remove line if not applicable]-->

69 Add shortcuts for zoom in/out

Find it on GitHub

We've to add shortcuts for zoom in/out feature in zoom-action.tag.html to improve usability. We also need to mention them in shortcuts.tag.html

Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

70 Document newly added functionalitities

Find it on GitHub

@alextychan has recently added a feature to copy paste labels across the images. We've to create a demo GIF to display it on Features.md / README.md. We also need to add keymappings in https://github.com/NaturalIntelligence/imglab/blob/master/tags/shortcuts.tag.html

@Alvin-Voo has added a feature for zoom in/out. We need to create a demo GIF to display it on Features.md / README.md to aware users for the same.

Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

71 Add yourself to Contributors.md

Find it on GitHub

If you are starting with opensource contributions, this is best to start with. just go ahead and add your details to Contributors.md file in the same format as other's details.

@vvscode @markost2549 Since you guys have already contributed for us, why don't your name to Contributors.md and create a PR

72 footer clashes with side menu in small windows

Find it on GitHub

Describe the bug When we view any page on this site in a small browser window, the footer will clash with the side menu

To Reproduce Steps to reproduce the behavior: 1. Go to https://my-first-pr.github.io 2. Resize the window small enough for the error to occur.

Expected behavior The footer should clash with the side, it should wrap or go off the page to scroll to.

Screenshots ![screen shot 2018-09-12 at 10 45 37](https://user-images.githubusercontent.com/956290/45417107-50eff000-b679-11e8-9e38-93d17bebe63a.png)

Desktop (please complete the following information): - OS: macOS High Sierra (blergh) - Browser: Chrome - Version: 68.0.3440.106

Additional context Add any other context about the problem here.

73 Upgrade request dependency

Find it on GitHub

Current behavior:

We are getting a request dependency error when using Cypress version 2.1 warning cypress > request > hawk > hoek@2.16.3: The major version is no longer supported. Please update to 4.x or newer

This is preventing us from installing Cypress and running our UI tests in our build pipeline.

Desired behavior:

We would like this dependency to be updated

Steps to reproduce:

Versions

74 Set the appropriate error codes on failure

Find it on GitHub

Task

An error number should be set whenever a search, delete, update is performed on the tree but no corresponding key was found

Method

new Error code: #define CBT_KEY_NOT_FOUND 2 set this error whenever the helpers of search, delete, or update returns NULL.

Where to code

src/cranbtree.c

Tests

This should pass the following: 1. cbtkeynotfounderrortest1 2. cbtkeynotfounderrortest2

75 Add range buttons to /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!

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

We have a nice way of displaying activity on a topic for just a given time period: https://publiclab.org/tag/data-logging?start=16-03-2016&end=14-04-2017 (from #2439) --

...but no easy way to get to such a range-limited page from the basic page of https://publiclab.org/tag/data-logging. So this adds some nice buttons!

πŸ“‹ 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.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

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

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

```diff @@ -51,7 +51,11 @@ <% end %>

<% unless @tags.try(:first).try(:parent).nil? %>parent: <%= @tags.first.parent %><% end %>

- <%= render :partial => "notes/formattoggle" if @nodetype == "note" %> +
+
+ 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 :)

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

    (This issue was created by First-Timers-Bot.)

    76 Create tests for `ride-hailing/MessageParams` using jest.

    Find it on GitHub

    first-timers-only

    This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

    Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

    Find more first-timers-only issues from DAV Foundation here.

    Thank you for your help :heart:

    What is this project?

    DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

    As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

    dav-js

    This SDK enabled integrating any client side JS and NodeJS code with the DAV Network.

    How you can help

    The Issue

    Create tests for ride-hailing/MessageParams using jest.

    You need to create tests to check that the serialize and deserialize methods work as expected.

    Please use the test file for class NeedParams as a basis for your new code.

    • Function serialize in class MessageParams must return a JSON object that contains all properties defined in the MessageParams instance.

    • Function deserialize in class MessageParams receives a JSON string and must initialize all the properties of the MessageParams instance with the values in the JSON string.

    messageParams1.desrialize(messageParams2.serialize()) == messageParams2 must therefore always be true.

    NOTE: Some names are changed between protocol string representation of instance properties: * location is internally represented as { lat , lon } but serialized as { latitude , longitude } * Private properties are internally prefixed with _ but serialized without the prefix. i.e. _protocol becomes protocol

    Contributing to dav-js

    • [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
    • [ ] Comment in this issue that you would like to do it.
    • [ ] Open dav-js GitHub page and click the β˜… Star and then β‘‚ Fork buttons.
    • [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
    • [ ] Code Code Code
    • [ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
    • [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
    • [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
    • [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

    Asking for help

    We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help πŸ˜„

    77 Create tests for `vessel-charging/messages/ProviderStatusMessageParams` using jest.

    Find it on GitHub

    first-timers-only

    This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

    Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

    Find more first-timers-only issues from DAV Foundation here.

    Thank you for your help :heart:

    What is this project?

    DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

    As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

    dav-js

    This SDK enabled integrating any client side JS and NodeJS code with the DAV Network.

    How you can help

    The Issue

    Create tests for vessel-charging/messages/ProviderStatusMessageParams using jest.

    You need to create tests to check that the serialize and deserialize methods work as expected.

    Please use the test file for class NeedParams as a basis for your new code.

    • Function serialize in class MessageParams must return a JSON object that contains all properties defined in the MessageParams instance.

    • Function deserialize in class MessageParams receives a JSON string and must initialize all the properties of the MessageParams instance with the values in the JSON string.

    messageParams1.desrialize(messageParams2.serialize()) == messageParams2 must therefore always be true.

    NOTE: Some names are changed between protocol string representation of instance properties: * location is internally represented as { lat , lon } but serialized as { latitude , longitude } * Private properties are internally prefixed with _ but serialized without the prefix. i.e. _protocol becomes protocol

    Contributing to dav-js

    • [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
    • [ ] Comment in this issue that you would like to do it.
    • [ ] Open dav-js GitHub page and click the β˜… Star and then β‘‚ Fork buttons.
    • [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
    • [ ] Code Code Code
    • [ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
    • [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
    • [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
    • [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

    Asking for help

    We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help πŸ˜„

    78 Create tests for `vessel-charging/messages/ChargingStartedMessageParams` using jest.

    Find it on GitHub

    first-timers-only

    This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

    Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

    Find more first-timers-only issues from DAV Foundation here.

    Thank you for your help :heart:

    What is this project?

    DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

    As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

    dav-js

    This SDK enabled integrating any client side JS and NodeJS code with the DAV Network.

    How you can help

    The Issue

    Create tests for vessel-charging/messages/ChargingStartedMessageParams using jest.

    You need to create tests to check that the serialize and deserialize methods work as expected.

    Please use the test file for class NeedParams as a basis for your new code.

    • Function serialize in class MessageParams must return a JSON object that contains all properties defined in the MessageParams instance.

    • Function deserialize in class MessageParams receives a JSON string and must initialize all the properties of the MessageParams instance with the values in the JSON string.

    messageParams1.desrialize(messageParams2.serialize()) == messageParams2 must therefore always be true.

    NOTE: Some names are changed between protocol string representation of instance properties: * location is internally represented as { lat , lon } but serialized as { latitude , longitude } * Private properties are internally prefixed with _ but serialized without the prefix. i.e. _protocol becomes protocol

    Contributing to dav-js

    • [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
    • [ ] Comment in this issue that you would like to do it.
    • [ ] Open dav-js GitHub page and click the β˜… Star and then β‘‚ Fork buttons.
    • [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
    • [ ] Code Code Code
    • [ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
    • [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
    • [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
    • [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

    Asking for help

    We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help πŸ˜„

    79 Create tests for `ride-hailing/NeedParams` using jest.

    Find it on GitHub

    first-timers-only

    This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

    Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

    Find more first-timers-only issues from DAV Foundation here.

    Thank you for your help :heart:

    What is this project?

    DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

    As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

    dav-js

    This SDK enabled integrating any client side JS and NodeJS code with the DAV Network.

    How you can help

    The Issue

    Create tests for ride-hailing/NeedParams using jest.

    You need to create tests to check that the serialize and deserialize methods work as expected.

    Please use the test file for class NeedParams as a basis for your new code.

    • Function serialize in class NeedParams must return a JSON object that contains all properties defined in the NeedParams instance.

    • Function deserialize in class NeedParams receives a JSON string and must initialize all the properties of the NeedParams instance with the values in the JSON string.

    needParams1.desrialize(needParams2.serialize()) == needParams2 must therefore always be true.

    NOTE: Some names are changed between protocol string representation of instance properties: * location is internally represented as { lat , lon } but serialized as { latitude , longitude } * Private properties are internally prefixed with _ but serialized without the prefix. i.e. _protocol becomes protocol

    Contributing to dav-js

    • [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
    • [ ] Comment in this issue that you would like to do it.
    • [ ] Open dav-js GitHub page and click the β˜… Star and then β‘‚ Fork buttons.
    • [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
    • [ ] Code Code Code
    • [ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
    • [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
    • [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
    • [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

    Asking for help

    We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help πŸ˜„

    80 Minify CSS

    Find it on GitHub

    This issue is suitable and prioritized to first-timers. But can be picked by other contributors if not handled within initial 4 weeks.

    To decrease the loading time, we should minify js, and css files. fontello.css is one of them which is less frequently get changed.

    Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


    Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

    81 Assertion shows as spinning after passing in interactive mode

    Find it on GitHub

    Cypress 3.1.0 on Mac

    In one of the tests that uses a DOM alias, the assertion passes, but the command log keeps the spinner going

    Recreate

    • clone https://github.com/cypress-io/testing-workshop-cph and switch to branch mot-rio-demo

    git clone git@github.com:cypress-io/testing-workshop-cph.git cd testing-workshop-cph git checkout mot-rio-demo npm install

    • start local server npm start
    • open Cypress from another terminal npm run cy:open
    • select spec file 02-adding-items/spec.js

    The problem is the test "can alias items"

    second problem

    When hovering or clicking over the alias, only the initial elements in the alias are highlighted, not the later ones, that are actually passing the assertion

    82 Exporting data in YOLO format

    Find it on GitHub

    This feature is suitable for first-timers. But can be picked by any contributor.

    Currently imglab supports exporting labelled data in Pascal VOC, COCO format. We want to let users export data in YOLO format as well.

    target folder : data formaters

    Please check how export feature is implemented for other formats in data formaters

    Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


    Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

    83 Import Pascal VOC format

    Find it on GitHub

    This feature is suitable for first-timers. But can be picked by any contributor.

    Currently, imglab supports exporting labeled data in Pascal VOC format. We want to let users importing data in Pascal VOC format.

    target file : pascal_voc.js

    Please check how the export feature is implemented in pascal_voc.js

    Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


    Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

    84 Make a Jupyter notebook tutorial for the analysis of a simple circuit

    Find it on GitHub

    Goal

    PSO can be utilized in a wide variety of fields. To broaden our collection of tutorials, we'd like to have another example where we analyse a simple circuit with PSO. For some inspiration, you can visit the example section. I propose that, for the beginning, we start by analysing the circuit shown below. It has a resistor and a diode. The end-goal is to have a nice Jupyter notebook that goes through the whole process of writing this optimization program.

    Method

    ![circuit](https://user-images.githubusercontent.com/39431903/43938822-29aaf9b8-9c66-11e8-8e54-01530db005c6.png) As there are many models for diodes, let us use a more realistic one (a simplified Shockley equation) for this tutorial:

    where: - : diode current - : reverse bias saturation current - : diode voltage - : thermal voltage (use 25.3 mV in this tutorial)

    to use it in the tutorial I'd recommend to solve for :

    Using the Kirchhoff voltage law we get this:

    where denotes the voltage over the resistor. We can restructure it to be our cost function (optimally it is 0) for the optimization:

    The absolute value is necessary because we don't want to obtain negative currents. If we write this more verbosely we see that the current is the parameter we want to optimize:

    These are some sample values for the other parameters: - : 10 V - : 9.4 pA - : 100 Ohm

    Of course, if you know an alternative way to solve this or you have any questions about the issue don't hesitate to write a comment! I'm looking forward to seeing a first-timer writing this Jupyter notebook! πŸ’―

    Notes

    Please work on the development branch. You can find a good StackOverflow question about forking here. For a more advanced beginner guide to the GitHub workflow, there is this cheatsheet available. It is quite detailed and gives a simple overview.

    85 Add example of testing `datalist` to `.next()` and `.type()`

    Find it on GitHub

    From: https://github.com/cypress-io/cypress/issues/445#issuecomment-411432996

    Can add example to next.md and type.md.

    Testing a datalist:

    html <input list="fruit" /> <datalist id="fruit"> <option>Apple</option> <option>Banana</option> <option>Cantaloupe</option> </datalist>

    javascript cy.get('#fruit option').should('have.length', 3) .first().should('have.text', 'Apple') .next().should('have.text', 'Banana') .next().should('have.text', 'Cantaloupe') cy.get('input').type('Apple')

    86 Exception in root level after() doesn't fail test run in interactive mode

    Find it on GitHub

    Current behavior:

    If there's an after() outside of any describe, it or context ("rool level"), which throws an exception, that doesn't fail the test run. This is different from how it works in mocha, where you get a "after all" hook failure.

    Also, if it's a synchronous failure, the exception doesn't show up anywhere. If it's async, it shows up like this:

    ![screen shot 2018-08-07 at 5 13 10 pm](https://user-images.githubusercontent.com/394320/43781286-37cbe08c-9a65-11e8-9a76-68f7cca5be42.png)

    Desired behavior:

    The whole test run should fail (sometimes you would want to place an assertion there that is possible only after all tests have run).

    Steps to reproduce:

    Add this to your tests: after(() => { cy.then(() => { throw new Error('bla bla'); }); });

    Versions

    Cypress: 3.0.3 OS: Mac OS X 10.12.6 (Sierra) Browser: both Electron (59) and Chrome (68)

    87 Support typescript

    Find it on GitHub

    88 Cursor movement effect

    Find it on GitHub

    We've already added blinking cursor effect. Now we've to experiment by moving the cursor inside the text.

    A rough idea to give this effect by appending a span tag after the cursor. check this code to append a span.

    HTML tag will look like this

    html <p id="paper">This is the text being typed</p><span cursor="shabdawali-cursor">|</span><span id="paper-after"></span>

    On cursor move remove a char from #paper and add it to #paper-after.

    html <p id="paper">This is the text being type</p><span cursor="shabdawali-cursor">|</span><span id="paper-after">d</span>

    and so on

    89 101 test

    Find it on GitHub

    90 hello world

    Find it on GitHub

    91 Edit readme to make it more descriptive

    Find it on GitHub

    Please add more description to readme

    92 FAQ - explain command chain retry logic

    Find it on GitHub

    https://github.com/cypress-io/cypress/issues/1210#issuecomment-359075731

    93 Multiple `.not` calls are not parsed correctly

    Find it on GitHub

    I can write an assertion like so:

    expect(image).to.not.be.visible;

    I can also write it like so:

    expect(image).not.to.be.visible;

    So, to check my test was working, I tried the following:

    expect(image).not.to.not.be.visible;

    Current behavior:

    If I expect something not to not be visible, then I expect it to be visible.

    But, my test passed! So it doesn't seem as though the assertion is being parsed properly.

    To test this even further, I tried this:

    expect(image).not.not.not.not.to.not.be.visible;

    Again, my test passed.

    For avoidance of doubt, my test fails (as expected) when I run this: expect(image).to.be.visible;

    Desired behavior:

    I would expect double-negatives to be disallowed from the application.

    expect(image).not.to.not.be.visible; -> Error: multiple uses of 'not' detected. Please limit your assertion to one 'not' - it is far easier to read!.

    Steps to reproduce:

    Check out https://github.com/cypress-io/cypress-test-tiny/pull/33 (ChrisBAshton:not-not branch of cypress-io/cypress-test-tiny).

    Versions

    Cypress: 3.0.1 OS: OSX 10.12.3.

    94 Support ONNX format

    Find it on GitHub

    This feature is suitable for first-timers. But can be picked by any contributor.

    Just like other data formats we're supporting, we have to import-export labeled data in ONNX format. You can get more detail about that here

    https://github.com/onnx/onnx/blob/master/onnx/onnx.proto

    You can check dataformaters folder to understand how you can implement it for this application.

    Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue


    Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

    95 Bundled Node Version 8.2 is too old

    Find it on GitHub

    Any plan to upgrade the Cypress bundled node version to latest v8.11? The currently bundled version 8.2 is too old to prevent us easily create more useful plugins.

    96 Enhance the demo

    Find it on GitHub

    Provide the buttons to set repeat flag, add text content etc (index.html)

    97 no information about test error source/location

    Find it on GitHub

    i have to do many clicks to rig and test a feature, and when cypress fails to click, i get the following error:

    1) whatever: CypressError: cy.click() can only be called on a single element. Your subject contained 3 elements. Pass { multiple: true } if you want to serially click each element. at Object.cypressErr (https://shopware.vanilla/__cypress/runner/cypress_runner.js:68076:11) at Object.throwErr (https://shopware.vanilla/__cypress/runner/cypress_runner.js:68041:18) at Object.throwErrByPath (https://shopware.vanilla/__cypress/runner/cypress_runner.js:68068:17) at Context.click (https://shopware.vanilla/__cypress/runner/cypress_runner.js:54585:16) at Context.<anonymous> (https://shopware.vanilla/__cypress/runner/cypress_runner.js:63943:21) at https://shopware.vanilla/__cypress/runner/cypress_runner.js:63656:33 at tryCatcher (https://shopware.vanilla/__cypress/runner/cypress_runner.js:7091:23) at Promise._settlePromiseFromHandler (https://shopware.vanilla/__cypress/runner/cypress_runner.js:5113:31) at Promise._settlePromise (https://shopware.vanilla/__cypress/runner/cypress_runner.js:5170:18) at Promise._settlePromiseCtx (https://shopware.vanilla/__cypress/runner/cypress_runner.js:5207:10) at Async._drainQueue (https://shopware.vanilla/__cypress/runner/cypress_runner.js:2028:12) at Async._drainQueues (https://shopware.vanilla/__cypress/runner/cypress_runner.js:2033:10) at Async.drainQueues (https://shopware.vanilla/__cypress/runner/cypress_runner.js:1907:14) at <anonymous>

    how do i know which of the cy.click() cypress has a problem? at the moment i do it by trial-and-error, but that cant be the way... why not simply show the test file name and line number in the error?

    $ ./node_modules/.bin/cypress --version Cypress package version: 3.0.2 Cypress binary version: 3.0.2

    98 Update editor to customize the appearance of typing effect

    Find it on GitHub

    I've created a simple page where a user can enter the text to record it as typing effect. It'll be good to give options to decorate the text as per your need, like speed, CSS style etc.

    https://github.com/amitguptagwl/shabdawali/blob/master/riotjs/index.html

    99 Example of drag and drop to element

    Find it on GitHub

    I think it would make sense to have a third example in the drag and drop recipe which shows how straightforward it is in Cypress to drag one element to another. A colleague of mine was trying to figure this out for a while, before I noticed that you could just use something like this:

    ```javascript cy.get(".drag-handle") .trigger("mousedown", { which: 1 })

    cy.get(".drag-target") .trigger("mousemove") .trigger("mouseup") ```

    Drag and drop that is this straightforward to use is a massive advantage of Cypress compared to other testing frameworks, so it would make sense to have this information more readily available in the recipe for people using Cypress with a mindset from a less intuitive framework.

    100 Tutorial 0 doesn't cover the button.style.flex line in example code

    Find it on GitHub

    The example app at https://toga.readthedocs.io/en/latest/tutorial/tutorial-0.html#write-the-app has a line that isn't covered in the tutorial: button.style.flex = 1 (and I would love to know what t does since the 1 is non-obvious πŸ˜‰ ).