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 Error handling in cbt_clone

Find it on GitHub

Task

If the cloneobject function is not NULL and the cloneobject returns NULL for any reason it should terminate, free all the memory allocated so far for the clone and return NULL

Method

When invoking the clone_object, check if the return value is NULL. If it is, then simply terminate and return NULL. You will have to check if the return value from the recursive call is NULL because of an error or because the leafs of the trees have been reached.

Prototype

/** * cranbtree_t*, void* (*)(void*) -> cranbtree_t* * EFFECTS: clones the given cranbtree_t and clones the user objects if the * the passed function pointer is not NULL * RETURNS: a pointer to the clone, or NULL if the given cbt is not valid or on failure * NOTE: if the function is NULL, clone will copy the original object pointers to the new * clone . This you must be careful in this case when manipulating the objects and destroying * them. Otherwise, the tree will store copies of the objects */ cranbtree_t *cbt_clone(cranbtree_t * cbt)

Where to code

You will need to modify the following functions - cbtclone in src/cranbtree.c - cbtcopy_nodes in src/lib/clone.c

Tests

  1. write a new test that passes a helper that fails when being called to copy an object and make sure the return value of cbt_clone is NULL. Run valgrind to make sure there are no memory leaks

2 Fix Import Image Text Overflow

Find it on GitHub

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

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

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

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

๐Ÿค” What you will need to know.

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

What is the problem

The file input text for import-image module is overflowing whereas for the load-image(first step) it is not. Fix that by changing an id in css to a class.

Import Image:

![screenshot from 2019-01-21 11-56-10](https://user-images.githubusercontent.com/34770591/51456410-92a14d80-1d73-11e9-8840-577282335eb8.png)

Expected:

![screenshot from 2019-01-21 11-56-59](https://user-images.githubusercontent.com/34770591/51456442-afd61c00-1d73-11e9-9c57-74583606daf2.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 demo.css in the image-sequencer repository (press the little pen Icon) and edit the line as shown below.

Change

https://github.com/publiclab/image-sequencer/blob/17d79c4b44c5e5b8f7f8b4574a783d5b87cdf871/examples/demo.css#L49-L51

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

diff css - #dropzone { + .dropzone { padding: 30px; Change

https://github.com/publiclab/image-sequencer/blob/17d79c4b44c5e5b8f7f8b4574a783d5b87cdf871/examples/demo.css#L62-L64

diff - #dropzone input { + .dropzone input { max-width: 100%; }

  • [ ] ๐Ÿ“ Update the file index.html in the image-sequencer repository (press the little pen Icon) and edit the line as shown below.

Change

https://github.com/publiclab/image-sequencer/blob/17d79c4b44c5e5b8f7f8b4574a783d5b87cdf871/examples/index.html#L65-L67

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

diff - <div id="dropzone"> + <div id="dropzone" class="dropzone"> <p> <i>Select or drag in an image to start!</i>

  • [ ] ๐Ÿ“ Update the file Ui.js in the image-sequencer repository (press the little pen Icon) and edit the line as shown below.

Change

https://github.com/publiclab/image-sequencer/blob/17d79c4b44c5e5b8f7f8b4574a783d5b87cdf871/src/modules/ImportImage/Ui.js#L10-L11

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

diff var dropZone ='\ - <div style="padding: 30px;margin: 10px 20% 30px;border: 4px dashed #ccc;border-radius: 8px;text-align: center;color: #444;" id="' + dropzoneId + '">\ + <div class="dropzone" style="padding: 30px;margin: 10px 20% 30px;border: 4px dashed #ccc;border-radius: 8px;text-align: center;color: #444;" id="' + dropzoneId + '">\

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

  • [ ] ๐Ÿ’พ Commit your changes

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

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

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

  • [ ] ๐Ÿ Done Ask in comments for a review :)

๐Ÿค”โ“ 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!

3 Input text is too close to edges

Find it on GitHub

First Time?

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

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

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

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

๐Ÿค” What you will need to know.

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

The problem

After updating some of our modules to have sliders instead of text input fields, some of the styling we provided for the sliders overwrote the styling for the text input fields as well. This resulted in all of our input fields having their padding removed.

For ex: http://sequencer.publiclab.org/examples/#steps=crop{}

Solution

We will make our css declaration more specific so that it only removed padding on sliders:

On the demo.css page, for the below declaration add the attribute selector [type="range"] to the class selector .form-control so that it no longer effects the text input fields.

https://github.com/publiclab/image-sequencer/blob/17d79c4b44c5e5b8f7f8b4574a783d5b87cdf871/examples/demo.css#L45-L47

Thanks!!

Steps to Fix

  • [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
  • [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/image-sequencer/blob/main/README.md
    • [ ] Create a new feature branch with a unique name descriptive to the issue
  • [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
  • [ ] Reference this issue in your pull request body
  • [ ] Once you submit your pull request, an additional checklist will be provided for getting it merged

๐Ÿ’ฌ Get help

If you need any help - here are some options:

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

4 Harden against XSS

Find it on GitHub

Perfectly hardened example script: https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php

Hardens text - text(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L680

Hardens code in html tags / attributes - attr(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L824

Hardens code in text that also is language / location specific - xlt(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L758

Hardens code in html tags / attributes that also is language / location specific - xla(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L581

Unknown - jsescape(): https://github.com/openemr/openemr/blob/master/interface/reports/patledger.php#L945

Unknown - xlj(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L383

Here's the documentation that covers this: https://www.open-emr.org/wiki/index.php/CodebaseSecurity#Cross-ScriptingPrevention

Here's the library with these functions: https://github.com/openemr/openemr/blob/master/library/htmlspecialchars.inc.php

5 Code cleanup and organization requested

Find it on GitHub

  • [x] Remove all binary files and add create a .gitignore file
  • [ ] Put all source files in src

6 Wrong syntax for memory allocation

Find it on GitHub

Memory allocation in Assignments 1 and 2A in CS2233 Data Structures is syntactically wrong. The *s inside malloc must be removed.

Also, the submitted version must be checked with the inputs mentioned in the pdf file and Valgrind(memory leak checker for c/c++).

7 Multiple Tag Subscription on Email footers 2

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

Add multiple tag Subscription on email footers

๐Ÿ“‹Solution

Add line

<p>Subscribe to all the tags for this post by visiting https://<%= ActionMailer::Base.default_url_options[:host] %>/subscribe/multiple/tag/<%= @tags %>.</p>

to https://github.com/publiclab/plots2/blob/5c0d96274bd0be15feba69d8f30093082402ace5/app/views/subscriptionmailer/notifytag_added.html.erb#L14

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

  • [ ] ๐Ÿ“ Update

  • [ ] ๐Ÿ’พ Commit your changes

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

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

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

  • [ ] ๐Ÿ Done Ask in comments for a review :)

๐Ÿค”โ“ Questions?

Leave a comment below!

Is someone else already working on this?

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

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

8 Switch to npm for gifshot

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 package.json as following: Add the line : "gifshot": "^0.4.5", after the "get-pixels": "~3.3.0", line

  • [ ] Delete the following file gifshot.js

  • [ ] ๐Ÿ“ Update: the file index.html as following: Change line 28 from to

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

  • [ ] ๐Ÿ’พ Commit your changes

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

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

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

  • [ ] ๐Ÿ Done Ask in comments for a review :)

๐Ÿค”โ“ 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!

9 Change New PR Welcome Comment

Find it on GitHub

Remove the Dangerbot part of the comment as dangerbot has not been configured for this repository.

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

Change The File: https://github.com/publiclab/image-sequencer/blob/17d79c4b44c5e5b8f7f8b4574a783d5b87cdf871/.github/config.yml#L12-L15

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

diff newPRWelcomeComment: | - Thanks for opening this pull request! `Dangerbot` will test out your code and reply in a bit with some pointers and requests. + Thanks for opening this pull request! There may be some errors, **but don't worry!** We're here to help! ๐Ÿ‘๐ŸŽ‰๐Ÿ˜„

  • [ ] ๐Ÿ’พ 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.)

10 Create first-timers.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 first-timers.md in the test repository (press the little pen Icon) and edit the line as shown below.

diff @@ -0,0 +1,4 @@ +### First Timers Test +* [ ] Test this probot out +* [ ] Make observations +* [ ] Take notes

  • [ ] ๐Ÿ’พ 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.

11 Message Consistency on the Subscriptions Page

Find it on GitHub

First Time?

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

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

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

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

๐Ÿค” What you will need to know.

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

The problem

On the subscriptions page, we need to pluralize the word 'email' in the description around the 'Email Settings' button. While we're at, we can go ahead and standardize the styling to match that of the description above it.

Solution

Where to find the relevant lines of code:

in app/views/home/subscriptions.html.erb, the code the description and link is all written on one line: https://github.com/publiclab/plots2/blob/9f7cfc47ded41ed3a7370c66a9c4f7af9704af59/app/views/home/subscriptions.html.erb#L20

1) The link (a tag) is currently nested in the paragraph (p tag), lets move the paragraph below it instead of around it.

2) Lets change the text to "Control which emails you want to receive." to make it more succinct.

3) Add italics to the text with a style attribute and the declaration font-style:italic;

It should look something like this afterwards: <p style="font-style:italic;">Control which emails you want to receive.</p>

4) One last change. The 'Email Settings' button needs a margin under it. Add a style attribute onto the a tag with the declaration margin-bottom:10px;

The goal is for it to look just like the one above in the end:

Thanks!!

Steps to Fix

  • [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
  • [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/plots2
    • [ ] Create a new feature branch with a unique name descriptive to the issue
  • [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
  • [ ] Reference this issue in your pull request body
  • [ ] Once you submit your pull request, an additional checklist will be provided for getting it merged

๐Ÿ’ฌ Get help

If you need any help - here are some options:

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

12 Cypress Dashboard Truncates Output

Find it on GitHub

Is this a Feature or Bug?

I believe this to be a bug with Cypress dashboard where truncation of the output makes debugging issues via the dashboard or CI very difficult for developers. It is useful for instance to see body and url parameters when using something like cy.request however the output on failure is formatted in a way which inhibits the ability to debug issues.

Current behavior:

the output in the cypress dashboard for a 404 (any sufficiently large output will do) looks like

``` 1) toolbar layer style "before all" hook for "should edit style name": CypressError: cy.request() failed on:

http://xyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxy/api/customer?token=uy9aG2yVRlyPAcWxvTZEXlTvRm6O4u

The response we received from your web server was:

404: Not Found

This was considered a failure because the status code was not '2xx' or '3xx'.

If you do not want status codes to cause failures pass the option: 'failOnStatusCode: false'


The request we sent was:

Method: POST URL: http://xyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxy/api/customer?token=uy9aG2yVRlyPAcW_xvTZEXlTvRm6... Headers: { "user-agent": "E2E", "accept": "/", "accept-encoding": "gzip, deflate", "content-type": "application/json", "content-length": 74 } Body: {"clusterId":"Dev-Alpha-Cluster","name":"Fin Fang Foom e2e20190116163428","OtherStuff":"ThisIsSomeDa... ```

see that the body and url are being truncated in this final block of the log. For small payloads it's fine, but when payloads become larger (or other cy methods that produce longer lines) the truncation makes the output almost useless. This is more of a problem when the errors are only produced on the CI server.

Desired behavior:

I would like some control over the output here, several options:

  • Download the raw output (unmodified)
  • Wrap long lines preserving the entire line
  • Have an option to open raw in the browser

Steps to reproduce: (app code and test code)

Simply perform a cy.request with a sufficiently large url or body e.g.

JavaScript cy.request({ method: 'POST', url: 'http://myreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallylong.url', })

Versions

Cypress: 3.1.3

I don't believe the browser to be an issue in this specific issue.

13 Remove logs in console.

Find it on GitHub

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

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

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

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

๐Ÿค” What you will need to know.

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

๐Ÿ“‹ Step by Step

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

  • [ ] ๐Ÿ“ Update the file $FILENAME in the $REPO repository (press the little pen Icon) and edit the line as shown below.

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

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

diff $DIFF

  • [ ] ๐Ÿ’พ Commit your changes

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

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

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

  • [ ] ๐Ÿ Done Ask in comments for a review :)

๐Ÿค”โ“ 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.

Problem description:

There are logs in console which are not needed.

What happened just before the problem occurred? Or what problem could this idea solve? There are logs in console which are not needed.

What to expect after resolving the issue? See a clear console.

File to look

demo.js

What's your PublicLab.org username?

divy123

Thank you!

Your help makes Public Lab better! We deeply appreciate your helping refine and improve this site.

To learn how to write really great issues, which increases the chances they'll be resolved, see:

https://publiclab.org/wiki/developers#Contributing+for+non-coders

14 OidcIdTokenValidator ensures clockSkew is positive number

Find it on GitHub

OidcIdTokenValidator.setClockSkew() should assert that the clockSkew is >= 0.

15 Add Code of conduct to the project

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!

  • [ ] ๐Ÿ“ Create the file named [CODEOFCONDUCT.md] in the leaflet-blurred-location repository (press the little pen Icon) and edit the line as shown below.

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

The file needs to be created at the root of the repository and copy the code of conduct from https://github.com/publiclab/plots2/blob/master/CODEOFCONDUCT.md

into newly created file.

  • [ ] ๐Ÿ’พ 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!

16 "OK" Logo in Admin Mode should navigate to the main index page

Find it on GitHub

Currently, clicking the "OK" logo in the top left corner of the admin mode (or staff mode, not sure about terminology), will navigate the user to the assignments page of the first course for which the user is an admin (staff). This feels very strange to me. Clicking the "OK" logo should navigate to either the list of all courses (https://okpy.org/admin/course/) or the okpy student mode index page (https://okpy.org/).

17 Fix "Editor controls overlay #228"

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: This will resolve #228. All that needs to be done is remove the following line, https://github.com/publiclab/PublicLab.Editor/blob/ffcb496c6be2abf813c7e38f8ef3d72a8426251d/src/modules/PublicLab.RichTextModule.js#L251

  • [ ] ๐Ÿ’พ 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!

18 Update Pull Request 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: Replace @publiclab/is-reviewers by @publiclab/reviewers and @publiclab/is-reviewers.

code link : https://github.com/publiclab/image-sequencer/blob/main/.github/PULLREQUESTTEMPLATE.md

  • [ ] ๐Ÿ’พ Commit your changes

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

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

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

  • [ ] ๐Ÿ Done Ask in comments for a review :)

๐Ÿค”โ“ 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!

19 Remove the extra space after `share`

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/editor/rich.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below. https://github.com/publiclab/plots2/blob/87db5642c4f434e9eaaa3478f79d2584916c6d09/app/views/editor/rich.html.erb#L30-L37

Remove the extra space which is below the share button text.

![screenshot 152](https://user-images.githubusercontent.com/39333058/51100506-6e39f400-17fc-11e9-96c7-c6c3ead1676d.png)

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

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

```diff

-

  • ```

  • [ ] ๐Ÿ’พ Commit your changes

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

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

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

  • [ ] ๐Ÿ Done Ask in comments for a review :)

๐Ÿค”โ“ 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!

20 Document how to change project access

Find it on GitHub

Give step by step directions on how to change the status of a project ('public' to 'private', etc) including pictures of UI below within https://docs.cypress.io/guides/core-concepts/dashboard-service.html#Public-vs-Private

Click into the project you'd like to change access to, then click "Settings" in the top right corner. Here you will see a section displaying "Access to Runs". Choose the appropriate access you'd like to assign for the project here.

21 Add cypress to eslint envs (just like mocha)

Find it on GitHub

Hello!

Would be super useful to have cypress available here https://eslint.org/docs/user-guide/configuring#specifying-environments, so that we do not have to configure globals manually or use something like https://github.com/standard/eslint-config-standard which adds extra complexity.

Expected If I add in package.json: json { "standard": { "env": ["cypress"] } } I should not be getting /cypress/integration/examples/location.spec.js:3:1: 'context' is not defined. and similar.

Cheers!

22 Error reporting in cbt_visit_all

Find it on GitHub

Task

set the op_errorno appropriately when a NULL function pointer is provided or if the number of visited entries does not match the number of entries in the tree. The error codes can be found in include/cranbtree.h

Method

check for errors before and after the tree traversal

Where to code

  • src/cranbtree.c

Tests

  1. cbtvisitall_test1
  2. cbtvisitall_test2 Make sure to uncomment this tests in test/test.c, compile, the run and make sure all the tests passes and nothing is broken

23 GeoIP Blocking in PHP Code

Find it on GitHub

Moved this issue from the Docker repo to here. Much better to do this at the app level if it is going to be done.

Maybe add this at some point, would be really cool but low priority.

Here is code I have that gets the MaxMindDB GeoIP2 database. Can be executed daily via cron to update or can just make a function in PHP instead of bash to do it. You read the MMDB file by using MaxMind's PHP GeoIP2 library.

wget https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.tar.gz \ && tar -xvf GeoLite2-Country* && mkdir /usr/local/share/GeoIP \ && mv GeoLite2-Country*/GeoLite2-Country.mmdb /usr/local/share/GeoIP

24 Add test for empty bold tags functionality

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

To implement a test for detecting empty bold tags (for #198). This test would help automate builds determine whether the #198 functionality is working fine or not.

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

  • [ ] Fork and clone this repository

  • [ ] Create a new uniquely named branch and checkout to it

  • [ ] Install dependencies using npm install

  • [ ] Install grunt cli using npm install -g grunt-cli

Implement the Solution

The corresponding test for this feature can be implemented by adding the following funtion to ./spec/javascripts/rich_text_module_spec.js file.

````js it("displays alert for empty bold tags",function() {

var enter = jQuery.Event("keydown", {keyCode:13})

var temp_el = module.textarea

module.setMode('markdown');

module.textarea.innerHTML = '**';

$(temp_el).trigger(enter)

module.textarea.innerHTML = '**';

$(temp_el).trigger(enter)

expect($('.invalid-bold-tags-warning').length).not.toBeNull();

}) ``` - [ ] Build usinggrunt build`

  • [ ] Test your assertions using grunt jasmine. If all specs pass, follow next steps.

  • [ ] ๐Ÿ’พ Commit your changes

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

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

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

  • [ ] ๐Ÿ Done Ask in comments for a review :)

๐Ÿค”โ“ 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!

25 Fix SQL Issues in these files #3

Find it on GitHub

SQL Parameters need to be bound for security reasons in multiple places in these files: ~~clinicalrules.php, createssl_certificate.php, formdata.inc.php~~.

Sample Problematic and Fixed Example: 1. sqlQuery(SELECT aco_spec FROM categories WHERE name = $catname ORDER BY id LIMIT 1"); 2. sqlQuery(SELECT aco_spec FROM categories WHERE name = ? ORDER BY id LIMIT 1", array($catname));

This is a simple issue for first timers / those new to open source or PHP. Please feel free to contact myself or @bradymiller for more instructions.

Other Instructions: * to learn about how to use Github, go here: https://guides.github.com/activities/hello-world/ * For IDE's, we would recommend Visual Studio Code since it is free, well supported, and will work on whatever operating system you have

26 Fix SQL Issues in these files #2

Find it on GitHub

SQL Parameters need to be bound for security reasons in multiple places in these files: api.inc, billrep.inc, calendar_events.inc.php. Look in this directory(please note, though, that the library/classes/ directory is being worked on by another developer).

Sample Problematic and Fixed Example: 1. sqlQuery(SELECT aco_spec FROM categories WHERE name = $catname ORDER BY id LIMIT 1"); 2. sqlQuery(SELECT aco_spec FROM categories WHERE name = ? ORDER BY id LIMIT 1", array($catname));

This is a simple issue for first timers / those new to open source or PHP. Please feel free to contact myself or @bradymiller for more instructions.

Other Instructions: * to learn about how to use Github, go here: https://guides.github.com/activities/hello-world/ * For IDE's, we would recommend Visual Studio Code since it is free, well supported, and will work on whatever operating system you have

27 Fix SQL Issues in these files #1

Find it on GitHub

https://github.com/openemr/openemr/blob/54bc980dc64379d1a7cada127562d07dd9f82483/library/payment.inc.php#L109

SQL Parameters need to be bound for security reasons in multiple places in this file.

Sample Problematic and Fixed Example:

  1. sqlQuery(SELECT aco_spec FROM categories WHERE name = $catname ORDER BY id LIMIT 1");
  2. sqlQuery(SELECT aco_spec FROM categories WHERE name = ? ORDER BY id LIMIT 1", array($catname));

This is a simple issue for first timers / those new to open source or PHP. Please feel free to contact myself or @bradymiller for more instructions.

Other Instructions: - to learn about how to use Github, go here: https://guides.github.com/activities/hello-world/ - For IDE's, we would recommend Visual Studio Code since it is free, well supported, and will work on whatever operating system you have

28 Update readme

Find it on GitHub

๐Ÿ†•๐Ÿฅโ˜ First Timers Only.

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

You can see our Brazilian Portuguese version

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

`````diff @@ -89,5 +89,8 @@ Then you can access at http://localhost:8082 ##### Test environment - Rundocker-compose -f docker-compose.test.yml up`

+### First timers +Here you can start to learn how to create your first pull request and start to be a contributor: +https://github.com/worknenjoy/gitpay/issues/247 +Your name

``````

  • [ ] ๐Ÿ’พ 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.

29 Strengthen part of username and password creation process

Find it on GitHub

This file is called when a user begins setting up OpenEMR for the first time: https://github.com/openemr/openemr/blob/master/setup.php

Make the following happen via HTML5 attributes: - initial user password min length of 12 - database password min length of 12

Also: - the "initial user" of "admin" is too easy to guess - write a PHP function (or Javascript function, can be on the front end that is fine) that generates 3 random letters + "-admin-" + 2 random numbers - e.g: HLV-admin-87 - then take this functions output and fill in the HTML for "initial user" - This will make bruteforce attacks against the login page approximately 1,700,000 harder at no real cost to the user (50% less extra characters than SSN or Phone Number) - make the username a minimum of 12 characters as well to ensure if they don't go with our randomized suggestion they still pick something with some complexity (enforce with html5)

30 Sandbox policy to <iframe> tags

Find it on GitHub

A big way to improve the security of iframes is by using the sandbox policy. Example:

https://html.spec.whatwg.org/multipage/origin.html#sandboxed-modals-flag https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe

<iframe sandbox="allow-forms allow-top-navigation allow-scripts">

sandbox Applies extra restrictions to the content in the frame. The value of the attribute can either be empty to apply all restrictions, or space-separated tokens to lift particular restrictions: allow-forms: Allows the resource to submit forms. If this keyword is not used, form submission is blocked. allow-modals: Lets the resource open modal windows. allow-orientation-lock: Lets the resource lock the screen orientation. allow-pointer-lock: Lets the resource use the Pointer Lock API. allow-popups: Allows popups (such as window.open(), target="_blank", or showModalDialog()). If this keyword is not used, the popup will silently fail to open. allow-popups-to-escape-sandbox: Lets the sandboxed document open new windows without those windows inheriting the sandboxing. For example, this can safely sandbox an advertisement without forcing the same restrictions upon the page the ad links to. allow-presentation: Lets the resource start a presentation session. allow-same-origin: If this token is not used, the resource is treated as being from a special origin that always fails the same-origin policy. allow-scripts: Lets the resource run scripts (but not create popup windows). allow-storage-access-by-user-activation : Lets the resource request access to the parent's storage capabilities with the Storage Access API. allow-top-navigation: Lets the resource navigate the top-level browsing context (the one named _top). allow-top-navigation-by-user-activation: Lets the resource navigate the top-level browsing context, but only if initiated by a user gesture.

31 Delete Old Code

Find it on GitHub

@bradymiller Going to keep this issue open/recurring to ask about non-used old code and if it can be deleted.

32 Add fa-icon for store in nav

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!

  • [ ] ๐Ÿ“ Add fa fa-icon for store

code link - https://github.com/publiclab/plots2/blob/master/app/views/layouts/_header.html.erb#L70

now add this line of code <i class="fa fa-shopping-cart" style="color: white" aria-hidden="true"></i> inside <a> tag

![image](https://user-images.githubusercontent.com/24489162/50535836-09cc3300-0b74-11e9-81e3-823ac026937d.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!

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

33 add logo of Public Lab along with heading

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!

  • [ ] ๐Ÿ“ add logo of Public Lab along with heading

code link - https://github.com/publiclab/plots2/blob/master/app/views/layouts/_header.html.erb#L14

![image](https://user-images.githubusercontent.com/24489162/50479168-390b6480-09fb-11e9-9e07-005f989b7c05.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!

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

34 Routes can overrun the hover box that appears over the alias name

Find it on GitHub

Current behavior:

Routes can overrun the hover box as shown in the screenshot below: ![image](https://user-images.githubusercontent.com/5534029/50348526-0945f380-0507-11e9-8aa5-28715f4e3b2c.png)

Desired behavior:

The background expands to fit routes up to a certain higher width (say 300 px or something like that). For routes that are longer, they wrap to multiple lines using something like

word-wrap: break-word;

Steps to reproduce: (app code and test code)

1) Alias a route that has a long chunk of text with no characters that trigger a line break 2) Run your tests 3) Hover over the yellow alias name 4) Observe that the route name extends beyond the edge of the background

Versions

Cypress 3.1.3 Chrome Windows 10

35 Fix SQL Issues in these files

Find it on GitHub

sql-injection fixes in library/classes directory

SQL queries in the application need to use binded parameters.

Note, this application uses the ADODB library (basically an ORM): http://adodb.org/dokuwiki/doku.php

Please contact dan@ehrlichserver.com for more information on getting started.

36 DeviceDetectionListener useless

Find it on GitHub

My steps: 1) Run java program with listener 2) adb connect ip:port 3) We get nothing

If i create new thread with while loop and delay printing connection.getDevices().size() - it updated and print me newer devices list. But to listener it doesn't go.

37 Tests for more modules; starting with QR code module jsqr

Find it on GitHub

We are starting to grow this library substantially and could really use more tests for specific modules. One example is that this pull request is trying to update jsqr but we don't test that module, so we don't know if that update breaks the module: #532

The test could look something like this one, and be in the same folder; we could use a data-url encoded QR code as test data, and confirm that we get the correct data out of the module!

Here's the module code itself:

https://github.com/publiclab/image-sequencer/tree/main/src/modules/DecodeQr

Once this is done, we could move on to each other module. This would be a great repeat first-timers-only issue!


This has been marked as a good candidate for becoming a first-timers-only issue like these, meaning that it's simple, self-contained, and with some extra formatting, could be a great entry point for a new contributor. If you're familiar enough with this code, please consider reformatting or reposting it as a first-timers-only issue, and then ping @publiclab/reviewers to get it labelled. Or, if this is not your first time, try to solve it yourself!

38 AUT not adjusting correctly with runner resizer

Find it on GitHub

Using the runner-resizer, the top of the AUT get covered up when the top bar overflows to another row

Using the window resizer, the AUT correctly adjusts, and is not coverd

See below ---------------------------v incorrect-----------------------------------------------------------------v--- correct ![18-12-11_11 18 24](https://user-images.githubusercontent.com/14625260/49814730-40164f80-fd38-11e8-9a4e-1b1f3cd3b6a4.gif)

39 First Timers Only

Find it on GitHub

Contributing to open source for the first time can be scary and a little overwhelming. I'm willing to hold your hand so you can make your first PR. The tasks mentioned in this issue are rather a bit easier than normal. And anyone who's already contributed to open source isn't allowed to touch them!

Okay, here we go! The aim of this project is to extend http://github.com/swapagarwal/JARVIS-on-Messenger functionalities to other platforms (like Telegram). Head over to http://m.me/J.A.R.V.I.S.on.Messenger and try out the features. Pick any one simple feature and we'll add it to https://t.me/jarvis_chatbot Join the conversation on Discord: https://discord.gg/MsZ9N9n ๐Ÿ‘ˆ

I'd highly encourage you to document the process, blog and tweet about it and encourage other first timers to do the same! https://www.firsttimersonly.com/

40 Request - TV episode air date on Newsletter

Find it on GitHub

Ombi build Version:

V 3.0.3988

Update Branch:

Master

Media Sever:

Plex

Problem Description:

It would be nice to have the episode(s) air date in the Newsletter next to the respective episode. Currently it only shows the Show launch release year.

Badly edited example:

![image](https://user-images.githubusercontent.com/45718819/49689229-1ebd2580-fae4-11e8-8e33-ab7c24a3bf24.png)

Reproduction Steps:

Look at a generated newsletter with new TV episodes.

Thank you for everything!

41 Navbars should be on the same horizontal line

Find it on GitHub

Hi, this is a first-timers-only issue made from #4163. 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 profile.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!

Issue

The navbar tabs are currently spread out in 2 lines, whereas it should be on the one same horizontal line.

![image](https://user-images.githubusercontent.com/39333058/49688486-075c5780-fb39-11e8-8732-992924c03094.png)

Code link

https://github.com/publiclab/plots2/blob/master/app/views/users/profile.html.erb#L43-L119

Solution

This can be solved by using Bootstrap classes to hide the text (leaving only the icon) for narrower width screens!

You can visit https://getbootstrap.com/docs/3.3/ for reference.

  • [ ] ๐Ÿ’พ 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!

42 Friends > Plot friends only since the last year

Find it on GitHub

Description

Extend functionality of plotfriends.py to specify from and to period. Currently doing for all time. Something of the type: `python plotfriends.py --from 2018-12-01, should support both--fromand--to` flags, both optional.

Mocks

Steps to reproduce (Incase of a bug)

NA

Acceptance Criteria

Update [Required]

  • [ ] Support --from and --to flags in plot_friends.py ### Enhancement to Update [Optional]
  • [x] [LIST ITEMS]

Definition of Done

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

Estimation

4-5 hours after having an idea of original code

43 Cypress update instructions given say to update with npm, even if you're using yarn

Find it on GitHub

Current behavior:

When I open Cypress and there's a new update, the update instructions tell me to use npm install --save-dev cypress@3.1.2 rather than saying yarn add --dev cypress@3.1.2.

Desired behavior:

If a yarn.lock file is detected instead of a package-lock.json file, the message should given you the yarn instructions.

The location of the update code is found at: - packages/desktop-gui/src/update/update-banner.jsx

The location of the code that tests the update banner: - integration/update_banner_spec.coffee

Steps to reproduce:

I assume you should be able install Cypress 3.1.1, run it with `cypress open and see the update button / with instructions.

Versions

  • 3.1.1

Operating System

Windows 10

44 Fix jasmine tests for date mismatch

Find it on GitHub

Unit tests need to be fixed. Possible reasons

  • date has been passed
  • zone or UTC timing mismatch

45 Table headers not expanding for full width of table

Find it on GitHub

Played around a bit with border-collapse and 100% width but couldn't get it quite right.

46 Initial commit

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

diff @@ -0,0 +1,2 @@ +# welcome +first-timers-test

  • [ ] ๐Ÿ’พ 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!

47 Submenus do not get pushed down in landscape - iPad Safari

Find it on GitHub

Ombi build Version:

V 3.0.3981

Update Branch:

Open Beta

Media Sever:

Emby

Operating System:

Windows 10 x64

Problem Description:

iPad Air 2 Safari: submenus do not get moved down in landscape mode

48 SVG errors are emitted when hovering over steps

Find it on GitHub

Current behavior:

Cypress currently emits an <Error: <svg> attribute height: A negative value is not valid. ("-45") when you hover over the pin icon in the sidebar, see: ![screen recording 2018-11-21 at 01 24 pm](https://user-images.githubusercontent.com/156871/48861147-e81ba700-ed90-11e8-9dab-a38ca019c2f3.gif)

Desired behavior:

Don't emit an error when hovering over step in the sidebar

Steps to reproduce:

Run a test using Electron, and wait for it to complete, hover over the steps with the Developer Console open and see the errors come flying through

Versions

Cypress: 3.1.2 Operation System: Mac OS High Sierra Browser: Electron

49 Align box in center in mobile view

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!

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

The Problem:

We want the Download PNG and View GIF buttons div in the center in the mobile view.

How to Solve?

You can add responsiveness in the div.

This line can be added below this one. https://github.com/publiclab/image-sequencer/blob/bf13d5807ab34b04517a3c9d3b4c318342432a48/examples/index.html#L94

Instance Count 1

![screenshot from 2018-11-20 13-11-29](https://user-images.githubusercontent.com/26546816/48758592-91499b00-ecc6-11e8-9dba-f48fe80c0ea1.png)

50 Explain how to use meta keys with .click()

Find it on GitHub

We don't currently explain that when using .click() you can utilize meta keys from a previous .type('{meta}, { release: false })

An example of a confused user: https://github.com/cypress-io/cypress/issues/2795

In the .click() docs we need to give usage examples / notes of this specific use case.

We do explain this behavior in the .type() API, but unless you're aware of that you'll likely miss this entirely.

51 Add hints to existing rebuses

Find it on GitHub

As of #168 we can now display hints when a user has entered an incorrect answer several times. This is awesome, but almost every rebus is currently lacking the hint property so lets go ahead and add some hints ๐Ÿ™‚

This issue is very beginner friendly, just follow these steps: - Open the file src/js/rebuses.js - Have a look at the rebuses and see if you can think of any good hints - Add your hint to the rebus object: hint: 'Your hint text'

52 Create a test script that checks for broken links all the markdown files

Find it on GitHub

This repository will contain a lot of markdown documents and maybe some json or txt files.

We need a small script in any language that you like that scraps all the files and checks for broken links (404).

This task is not hard, the script will take no more than 100 lines, maybe it can be done in 5 lines depending on the programming language.

We will use the small script to automate the deployment of new manuals.

If you know PHP

I know this library does the job and here is a sample script that actually used it.

Note: There other libraries in other languages if you search for "broken link checker" or something like that.

53 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 Docker-1.12.6 repository (press the little pen Icon) and edit the line as shown below.

``````diff @@ -1,5 +1,7 @@ # Docker-1.12.6 Deploy

+ๆต‹่ฏ• bot + Docker ๅฎนๅ™จๅผ•ๆ“ŽไปŽ 1.13 ็‰ˆๆœฌๅผ€ๅง‹ๅ†…็ฝฎไบ† swarm ๅฎนๅ™จ่ฐƒๅบฆๅผ•ๆ“Ž๏ผŒๅ› ๆญคๆœ€ๆ–ฐ็‰ˆๆœฌ็š„ Kubernetes ็›ฎๅ‰ๅชๆ”ฏๆŒๅˆฐDocker 1.12็‰ˆๆœฌใ€‚

## ้…็ฝฎ ansible.cfg ``````

  • [ ] ๐Ÿ’พ 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.

54 include flow type definitions

Find it on GitHub

It would be nice to ship at least basic Flow definitions in addition to TypeScript definitions. From my experiments, we can just add index.js.flow file for example to the NPM package, something like this

```js // to point flow at these type declarations in .flowconfig set // // [libs] // node_modules/cypress/index.js.flow

// Mocha functions declare function describe(name:string, callback:Function):void; declare function before(callback:Function):void; declare function beforeEach(callback:Function):void; declare function it(name:string, callback:Function):void; declare function after(callback:Function):void; declare function afterEach(callback:Function):void;

// Cypress own types declare interface subject { should(x: string, y: any): void; should('have.length', n: number): void // a lot more }

declare interface cypress { visit(url: string): cypress; wrap(x: any): subject // a lot more }

declare var cy: cypress ```

Then user projects has to include in .flowconfig

``` [ignore]

[include]

[libs] node_modules/cypress/index.js.flow

[lints]

[options]

[strict] ``` and it gets IntelliSense and type checks

Of course it is a lot of work to properly describe all available API functions and assertions, but if we get the ball rolling, users can contribute.

55 Add default zoom level to settings

Find it on GitHub

open http://imglab.ml/ > Open left top menu > Settings > General tab

We have to add an option in settings to set the default zoom level when an image loads. It should not impact current functionality. Settings should also saved in browser's cache.

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 In TypeScript doc, mentioning restarting TS server

Find it on GitHub

we should note restarting the Typescript server (Cmd+Shift+P and then type "restart TS server) or restart VS Code (or whatever editor is used).

https://github.com/cypress-io/cypress/issues/1236#issuecomment-423824058

57 Update the constructor in `src/drone-delivery/NeedParams.ts` and add Jest tests for `src/drone-delivery/NeedParams.ts`

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/drone-delivery/NeedParams.ts class, the constructor is not defining the startLocation and endLocation objects correctly. Currently, the long key is set to the lat value.

javascript this.startLocation = { lat: values.startLocation.lat, long: values.startLocation.lat, }; this.endLocation = { lat: values.endLocation.lat, long: values.endLocation.lat, };

The Updates

Please update the constructor in src/drone-delivery/NeedParams.ts by defining the startLocation and endLocation objects correctly.

Please create Jest tests for src/drone-delivery/NeedParams.ts

1. Update the constructor

Update the constructor by defining the startLocation and endLocation objects with the associated lat and long values.

The end result will be similar to this:

javascript this.startLocation = { lat: values.startLocation.lat, long: values.startLocation.long, }; this.endLocation = { lat: values.endLocation.lat, long: values.endLocation.long, };

2. Create Jest tests

We currently do not have unit testing set up for src/drone-delivery/NeedParams.ts. Please create Jest tests for the serialize() and deserialize() methods.

A good reference point would be src/ride-hailing/MissionParams.test.ts and customize it to the expected parameters and properties. If you are unsure what is expected, run npm run jest in the terminal and it should give you a hint. Also, you can reach out to our gitter channel with any questions ๐Ÿ˜„

The test you write will be similar to this:

```javascript import NeedParams from './NeedParams'; import VehicleTypes from './VehicleTypes';

describe('NeedParams class', () => { let needParams: NeedParams; let serializedNeedParams: any;

beforeEach(() => { needParams = new NeedParams({ endLocation: { lat: 32.050382, long: 34.766149, }, location: { lat: 32.050382, long: 34.766149, }, maxAltitude: 6000, startAt: undefined, startLocation: { lat: 32.050382, long: 34.766149, }, vehicleType: VehicleTypes.drone });

serializedNeedParams = {
  davId: undefined,
  endLocation: {
    lat: 32.050382,
    long: 34.766149,
  },
  id: undefined,
  location: {
    latitude: 32.050382,
    longitude: 34.766149,
  },
  maxAltitude: 6000,
  protocol: 'drone_delivery',
  startLocation: {
    lat: 32.050382,
    long: 34.766149,
  },
  type: 'need',
  ttl: undefined,
  vehicleType: VehicleTypes.drone
};

});

describe('serialize method', () => { it('should return serialized NeedParams object with the current values', () => { expect(needParams.serialize()).toEqual(serializedNeedParams); }); });

describe('deserialize method', () => { it('should return a NeedParams instance', () => { const needParamsObject = new NeedParams(); needParamsObject.deserialize(serializedNeedParams); expect(needParamsObject).toBeInstanceOf(NeedParams); });

it('should return deserialize NeedParams instance with current parameters', () => {
  const needParamsObject = new NeedParams();
  needParamsObject.deserialize(serializedNeedParams);
  expect(needParamsObject).toEqual(needParams);
});

}); });

```

After making your changes, run npm run tslint and 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
  • [ ] Make sure the linter is working and passing by running npm run tslint
  • [ ] 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 ๐Ÿ˜„

58 Enhancement: Add Halloween Costume Ideas

Find it on GitHub

@stufinn added a feature that will randomly generate a new Halloween custom idea.

Adding a new costume idea is a very easy addition that is beginner or first-timer friendly.

  • Open scripts.js and look for // Script for Random Costume Picker
  • Add an object to the costumes array with the costume name and a link to an image (or tutorial) in the following format

["Octocat", "https://twitter.com/ryanlanciaux/status/659415196058918912"],

  • Please keep your suggested customs PG / SFW
  • Include a source for your custom in your pull request if you can
  • Limit costume additions to three to help keep the array from getting too long

Reach out if you have a question

59 Enhancement: Add a Halloween fact

Find it on GitHub

@brandonstinson added a list of random Halloween facts that generate on page load.

The facts (strings) are stored in a facts array. Adding a new item to this array is an easy, first-timer-friendly pull request.

  • Within script.js, look for the comment // Array of Halloween facts.
  • Add a new fact to the facts array (try to keep them 1-2 lines long)
  • Open a pull request with your new fact(s) and I'll get them added in.

Reach out if you have any questions.

Edit: Wow, there's been an explosion of pull requests relating to this template in the past 12 hours! To keep this array and JS file from getting out of hand, please limit your facts to no more than 3 lines total.

60 Document that Cypress.env() parses booleans

Find it on GitHub

Given CYPRESS_IS_TRAVIS=true cypress open, when I run Cypress.env() in the developer tools it returns:

{ IS_TRAVIS: true }

I would expect it to instead return this based on the docs:

{ IS_TRAVIS: 'true' }

Because the documentation does not mention that string values like "true" are parsed into boolean values.

61 Add Computer Science resources

Find it on GitHub

Hi Open source contributors,

Check my resources and if there is something missing send me pull request!

Have a nice day!

62 Add a pull request for any problem from Udacity

Find it on GitHub

63 Add implementation of red-black tree

Find it on GitHub

Add the implementation of red-black tree. It can be in any programming language though preferred ones are Java, C, Cpp or python.

64 Create tests for `src/drone-charging/NeedParams.ts` 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 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 currently do not have unit testing set up for src/drone-charging/NeedParams.ts. Please create Jest tests for the serialize() and deserialize() methods.

A good reference point for the serialize() test would be src/ride-hailing/NeedFilterParams.test.ts and src/ride-hailing/MissionParams.test.ts for the deserialize() test. Customize it to the expected parameters and properties. If you are unsure what is expected, run npm run jest in the terminal and it should give you a hint. Also, you can reach out to our gitter channel with any questions ๐Ÿ˜„

The test you write will be similar to this:

```javascript import NeedParams from './NeedParams';

describe('NeedParams class', () => { let needParams: NeedParams; let serializedNeedParams: any;

beforeEach(() => { needParams = new NeedParams({ location: { lat: undefined, long: undefined }, davId: undefined, id: undefined });

serializedNeedParams = {
  ttl: undefined,
  protocol: 'drone_charging',
  type: 'need',
  location: {
    lat: undefined,
    long: undefined
  },
  davId: undefined,
  id: undefined
};

});

describe('serialize method', () => { it('should return serialized NeedParams object with the current values', () => { expect(needParams.serialize()).toEqual(serializedNeedParams); }); });

describe('deserialize method', () => { it('should return a NeedParams instance', () => { const needParamsObject = new NeedParams(); needParamsObject.deserialize(serializedNeedParams); expect(needParamsObject).toBeInstanceOf(NeedParams); });

it('should return deserialize NeedParams instance with the current parameters', () => {
  const needParamsObject = new NeedParams();
  needParamsObject.deserialize(serializedNeedParams);
  expect(needParamsObject).toEqual(needParams);
});

}); }); ```

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
  • [ ] Install dependencies by running npm install
  • [ ] 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 ๐Ÿ˜„

65 Print the list of registered routes

Find it on GitHub

It can be a good user experience if the library can return the list of registered routes. They can be useful for debugging purpose as well.

66 Subscribe button collapsing in mobile view in mailing list.

Find it on GitHub

Please describe the problem (or idea)

Subscribe button collapsing in mobile view in mailing list.

What happened just before the problem occurred? Or what problem could this idea solve?

![subscribe](https://user-images.githubusercontent.com/22452641/47179290-56f18480-d33b-11e8-89ca-e44a4c326a92.PNG)

What did you expect to see that you didn't?

Add some margin to the subscribe button

Please show us where to look

https://publiclab.org/lists

What's your PublicLab.org username?

vikul1234

This can help us diagnose the issue:

Browser, version, and operating system

chrome, win10

Many bugs are related to these -- please help us track it down and reproduce what you're seeing!


Thank you!

Your help makes Public Lab better! We deeply appreciate your helping refine and improve this site.

To learn how to write really great issues, which increases the chances they'll be resolved, see:

https://publiclab.org/wiki/developers#Contributing+for+non-coders

67 GAN Zoo

Find it on GitHub

Tensorop will include many variants of GANs which have been covered in papers like CGANs,CycleGANs,pix2pix in a unified manner including the common components in a seperate manner and specific components in their respective directories for a flexible robust API.

68 Collaborator needed/Collaborators exchange

Find it on GitHub

I am looking for a collaborator for this repository with following conditions: - Never a collaborator before - Make me collaborator of their owned repository to expand Github knowledge

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

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

71 More metrics in vision and nlp

Find it on GitHub

There are many metrics which are to be added in tensorop. If you have implemented it and see reference of them in papers, send a PR.

72 Support for more models in vision

Find it on GitHub

Tensorop will provide strong support for Transfer Learning, and lacks support for models other than Resnet. I will be adding support for them. To add models, make sure that you test them yourself and remove the necessary layers so that they can be used for generalized purposes.

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

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

75 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 ๐Ÿ˜„

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

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

Find it on GitHub

Keep filename as described : ProblemCode.extension

78 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++

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

80 Add Math Functions

Find it on GitHub

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

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

82 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

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

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

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

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

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

88 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 ๐Ÿ˜„

89 Add codechef solution with its question code as filename

Find it on GitHub

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

91 Contribute more SVG Icons

Find it on GitHub

How to contribute?

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

93 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

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

95 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.)

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

97 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.)

98 List of small issues for beginners

Find it on GitHub

Disclaimer- Most of the issues mentioned here are created by me in other repositories. As I'm the maintainer, I'm well aware with their status and can help new contributors. If you're listing any issue, please ensure that you can support the new contributors/freshers to complete that issue.

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.

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

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