Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update font format in section 3 #251

Open
5 tasks
IgorWilbert opened this issue Jan 24, 2019 · 29 comments · May be fixed by #253 or #961
Open
5 tasks

Update font format in section 3 #251

IgorWilbert opened this issue Jan 24, 2019 · 29 comments · May be fixed by #253 or #961

Comments

@IgorWilbert
Copy link
Member

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 fix Change font to Arial in section 3 #241. All that needs to be done is replace this line

<h4><b>By place name :</b></h4>

With this line <p class="ple-map-content"><b>By place name:</b></p>.
This line

<h4><b>By entering co-ordinates :</b></h4>

With this line <p class="ple-map-content"><b>By entering co-ordinates:</b></p>.

And finally, paste the following line (with the same indentation/format of the rest of the code)

.ple-map-content { font-size: 16px; }

on the file named PublicLab.Editor/dist/PublicLab.Editor.css, just after line number 36.

  • 💾 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.)

@NitinMore7
Copy link

please, can I work on this

@grvsachdeva
Copy link
Member

Hi @NitinMore7, go ahead and feel free to ask your doubts here. Thanks!

@NitinMore7
Copy link

so I need to clone this repo, make the given changes & then commit them and start a pull request ,is that's right?

@rexagod
Copy link
Member

rexagod commented Jan 24, 2019

@NitinMore7 You'll need to clone your forked repo instead of this one.

@NitinMore7
Copy link

Its done can you please check and confirm

@akshaygupta533
Copy link

Can I work on this?

@IgorWilbert
Copy link
Member Author

@akshaygupta533 please check other FTO issues, @NitinMore7 already claimed this one, sorry. @NitinMore7 did you remember to open a PR?

@NitinMore7
Copy link

@IgorWilbert i just did

@IgorWilbert
Copy link
Member Author

Good job @NitinMore7, thanks! Do you know how to squash your commits (turn your commits into a single commit with all the changes)? Would you mind doing it?

@NitinMore7
Copy link

@IgorWilbert how do I squash my commits if I've already pushed them

@IgorWilbert
Copy link
Member Author

@NitinMore7 you will have to rebase your branch. Run the command $ git rebase -i HEAD~4 and in the text editor that comes up, replace the words "pick" with "squash", except for the one at the top of the list. Then use $ git push origin branch-name --force to push to upstream. Please see this page for reference, and ask for help if something goes wrong. This can be a bit annoying to make.

@NitinMore7
Copy link

I've squashed those commits into one can you please check and confirm it

@grvsachdeva
Copy link
Member

Hi @NitinMore7, please paste the link of your PR here or tag this issue in the PR. Thanks!

@NitinMore7
Copy link

#253

@lohitha02
Copy link
Member

Hello, I think the issue is still open, If yes then can I work on this?

lohitha02 added a commit to lohitha02/PublicLab.Editor that referenced this issue Feb 18, 2019
@grvsachdeva
Copy link
Member

this issue has a PR open at #253

@NitinMore7 NitinMore7 linked a pull request Feb 18, 2019 that will close this issue
5 tasks
@Kirti2502
Copy link

Hi, I am an outreachy applicant. Can i work on this issue?

@Srija616
Copy link

Srija616 commented Mar 8, 2020

Hey! I am applying to Outreachy. I have no experience in open source. Can I work on this?

@Shulammite-Aso
Copy link
Collaborator

Shulammite-Aso commented Mar 9, 2020

Hello @Kirti2502 and @Srija616 I'm also an outreachy applicant, and looking to get started contributing to this project by working on the first-time-only issues. But this issue as well as all other first-time-only issues I've come across seem to have been claimed by someone else already.

I'm thinking of asking the mentors and reviewers for this project if more FTO issues can be created for us, or if we can go ahead to create these issues by ourselve. What do you two think?

@Srija616
Copy link

Srija616 commented Mar 9, 2020 via email

@Shulammite-Aso
Copy link
Collaborator

Good one. I should probably tag them here, if that will mean a quicker response.

@Shulammite-Aso
Copy link
Collaborator

Shulammite-Aso commented Mar 9, 2020

Hello @emilyashley @jywarren

Can you please suggest a way around this? #251 (comment)

@nicoleiocana
Copy link

@Shulammite-Aso

Hi! I am also an Outreachy applicant; have the mentors @jywarren and @emilyashley reached out to you? I was about to contact them via email until I read this thread. Thanks in advance.

@Shulammite-Aso
Copy link
Collaborator

Hello! @nicoleiocana

I think the best way to reach out to the community is through the chat Chanels. There's a link to the chat Chanel on outreachy project description page, you can check it out if you have not already.

Also you can mention the mentors on the chat channels if you have any question for them.

@vaishnavighiradkar
Copy link

Hey! This issue is still open. Can I work on this? I've never contributed to open source before. I'm trying to learn.

@MAYANK816
Copy link

I worked on this issue please check that.

@joannasjohnraj
Copy link

Is this issue still open? I would like to work on it.

@ghost
Copy link

ghost commented Sep 30, 2022

I find you all very friendly. I am newbie to open source added to it, and have no one around to ask for guidance not even one , just a first-generation learner who want to learn new things but after hours spending seeing videos of open source I just cannot understand there are so many files,please help me

@UmeraGhori UmeraGhori linked a pull request Sep 27, 2023 that will close this issue
5 tasks
@UmeraGhori
Copy link

i have fixed this issue please review it @IgorWilbert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet