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

Create first-timers-only issues for newcomers #842

Closed
7 of 17 tasks
harshkhandeparkar opened this issue Mar 9, 2019 · 75 comments
Closed
7 of 17 tasks

Create first-timers-only issues for newcomers #842

harshkhandeparkar opened this issue Mar 9, 2019 · 75 comments

Comments

@harshkhandeparkar
Copy link
Member

harshkhandeparkar commented Mar 9, 2019

Hi everyone!

We, at Public Lab, are known for welcoming new contributors into the Open Source world but a number of times, newcomers were not able to find first-timers-only issues to start their journey or face troubles making their first contribution with us.

Reasons being:

  1. Lack of first-timers-only issues
  2. Struggle in finding a good issue to start and lack of enough support?

We are working on both of the above aspects to support and help the maximum number of people to take their first step in their OSS journey with us, through our various projects but we need more support for this. So, this is a call to all the Public Lab members to try and create a first-timers-issue for someone who wants to start their journey and waiting for an FTO being assigned to them.

If you are interested in creating first-timers-only issue, follow these instructions:

  1. Browse through the publiclab.org and see if there's a bug which can be easily solved.

  2. Solve this issue but don't create a PR this time, instead create an FTO issue.

  3. Click on this link to start creating a new issue.

  4. We follow a specific template for FTO issues, so copy the template from here.

  5. Edit the issue body to add the goal of the issue, code snippet required, file to be updated, add screenshots(if required). Don't add code snippet required to solve in case, the issue just requires minor HTML or CSS change or equivalent.

  6. Add a catchy and relevant title to the issue but don't include "FTO", "first-timers-only" or equivalent in the title.

  7. Get the issue you just created labeled by mentioning @publiclab/reviewers or @publiclab/is-reviewers.

  • If you have labeling privileges, feel free to do so yourself but ensure that you have used FTO template.

  • If you are not able to mention the above-mentioned teams and don't have labeling privileges, then drop a line in Gitter channel - https://gitter.im/publiclab/publiclab or mention @jywarren @tech4GT and any one of us will surely follow-up with you. You can also mention any other member, you can think of with labeling privileges.

note: all of the members of publiclab/is-reviewers team have labelling rights.
  1. It's time to invite a new contributor to your issue. If there are unchecked names in the below list, then those people are still looking for FTO issue to start with, so mention them in your FTO by writing - This issue is created for @[contributor-name]. Thanks!

Also, if you see, a new contributor is looking for an issue, feel free to point them to your FTO.

fto-candidate Issues

These are issues which can become good first-timers-only issues but have to be reformatted using the fto issue template. If you feel like reformatting any of these, please feel free to do so. Please let us know if you are going to reformat the issue in the issue comments and link to the new issue in the comments of the original issue and this issue. You can mention @publiclab/is-reviewers to get the new issue labeled and then the old issue closed.

note: please do not reformat fto-candidate issues which have a has-pull-request as well.
note: if somebody is working on one of these issues, please notify the contributor about the reformatted issue.

Contributors looking for first-timers-only (FTO) issues

To first-time contributors: If you are looking for FTO and want your name to be added to the above list then, feel free to comment below to show your interest. If you are looking for working on specific language/framework, mention that too in your comment.

To Public Lab members who have comment edit privileges: Please add names of newcomers who have shown into for FTO in below comments. Also, add the names of other newcomers who are looking for FTO and shown their interest by commenting on other issues.

Currently open first-timers-only and fto-candidate issues in image-sequencer repo.

See also #879

For any query, feel free to ask below or at Public Lab gitter channel - https://gitter.im/publiclab/publiclab


Thank you!

cc @jywarren @publiclab/reviewers @publiclab/is-reviewers @tech4GT

Original issue template by @gauravano

Sent from my OnePlus3 using FastHub

Sent from my OnePlus3 using FastHub

@harshithpabbati
Copy link

Good idea!! We need new contributers..

@harshkhandeparkar
Copy link
Member Author

@harshithpabbati would you mind breaking up #833 ?

@harshithpabbati
Copy link

What should I do ?? Documentation ??

@harshkhandeparkar
Copy link
Member Author

harshkhandeparkar commented Mar 9, 2019 via email

@harshkhandeparkar
Copy link
Member Author

But I think the documentation part should be split up into a new first-timers-only

@Divy123
Copy link
Member

Divy123 commented Mar 9, 2019

One suggestion I have already opened up an issue regarding documentation.
So you could do the other part.
Documentation needs a considerable change so I woulkd like to discuss upon it.
Thanks.

@harshithpabbati
Copy link

ok @Divy123

@Divy123
Copy link
Member

Divy123 commented Mar 9, 2019

@jywarren Please look into issue #753 as it may greatly enhance the ease of understanding codebase making it much easier for new contributors to participate.

Also please review #251, it needs to be merged urgently as with merging PR's every time the code has to be enhanced. Also I will be updating README.md once the changes are ok to you.
Thanks

@harshkhandeparkar
Copy link
Member Author

Divy123 we were talking about the documentation part of #833

@Divy123
Copy link
Member

Divy123 commented Mar 9, 2019

Oh! proceed with it all the best.
But since it is a pinned issue I want to up raise the overasll doc as well.
Thanks and great work @harshkhandeparkar

@harshithpabbati
Copy link

Created an first timers issue #846

@harshkhandeparkar
Copy link
Member Author

Harshith, thanks for your enthusiasm and help and the issue of course. But the issue has to based on the fto template. Please reformat it and add the label later. Thanks and apologies as you have to take trouble.

@harshithpabbati
Copy link

Done with that @harshkhandeparkar

@harshkhandeparkar
Copy link
Member Author

Awesome!!

@harshkhandeparkar
Copy link
Member Author

@mgroovyank shall I add your name to this list? There are currently 0 fto issues open but there are some fto-candidate issues.

@harshkhandeparkar
Copy link
Member Author

@mgroovyank welcome! Your name has been added 🎉. I have a few questions that you can answer if you like:

  • What programming language are you good at/like? (JS, HTML, CSS, something else?)

  • Do you have experience with GitHub?

  • If JS is your cup of tea, what framework/package/environment are you comfortable with?(nodejs, some specific nodejs package, libs like jquery or frameworks like react)

  • Are you good at ruby? You can check out plots2 which is another project of publiclab.

Thank You!

@harshkhandeparkar
Copy link
Member Author

Opened a new fto #874. @mgroovyank this one is for you but if you don't want to solve it then it will be assigned to someone else. Do not worry as new ones are yet to come. I have some ideas for better ftos. You can either solve this one or wait for another one. Thank you!

@An0u
Copy link

An0u commented Mar 18, 2019

I'm looking for first-time issues to solve ;)

@harshkhandeparkar
Copy link
Member Author

@An0u Welcome! You have come to the right place. Your name has been added to the list !!:tada:

@harshkhandeparkar
Copy link
Member Author

Hello! Newcomers can see issue #879 also to find a bug and get the bug formatted as an FTO(first timers only issue). This new FTO will be reserved for the one who finds the bug. Thank you!

@An0u

@adisapphire adisapphire unpinned this issue Mar 22, 2019
@rmcorre
Copy link

rmcorre commented Mar 22, 2019

Hi HarshKhandeparkar,
Please add me to the FTO list.
Thanks

@grvsachdeva grvsachdeva pinned this issue Mar 22, 2019
@grvsachdeva
Copy link
Member

Hi @rmcorre, added your name to the above list. Thanks!

@Michaellin250
Copy link

Can you add me to the list? I want to get started with open source contributions.

@sashadev-sky
Copy link
Member

@Michaellin250 added!

@harshkhandeparkar
Copy link
Member Author

@Jaya738 has not replied. His issue has been reassigned to @Michaellin250

@harshkhandeparkar
Copy link
Member Author

@scheleon welcome! your name has been added.

@harshkhandeparkar
Copy link
Member Author

@harshithpabbati do you have any ideas for an fto?

@harshithpabbati
Copy link

#951 I will reformat it to fto issue.

@harshkhandeparkar
Copy link
Member Author

👍

@Divy123
Copy link
Member

Divy123 commented Mar 29, 2019

#959 can also be seen.

@Divy123
Copy link
Member

Divy123 commented Apr 5, 2019

#992 is up here.

@irasanchez
Copy link

Hey there, may I be added to the list? I am familiar with CSS, HTML, and JavaScript (vanilla, nodejs, React) and am looking for more practice in real projects. Thanks!

@harshithpabbati
Copy link

@irasanchez you can start your contributions with this issue #951

@konolga
Copy link

konolga commented May 17, 2019

Hi, please add me to the FTO list.

@harshithpabbati
Copy link

@konolga added your name. You will be assigned with an issue.
Thanks

@aashna27
Copy link

A new fto added #1084 please have a look and proceed.

@garg3133
Copy link
Member

Hey there, can you please add my name to the FTO list. Thanks!

@harshkhandeparkar
Copy link
Member Author

@jmauriciowebdev your name has been added. You can try to solve #894 btw.

@jywarren
Copy link
Member

Hi @harshkhandeparkar or @publiclab/is-reviewers would you be able to open an FTO for @freerangeandy ? I'll add him to the list!

@aashna27
Copy link

aashna27 commented Jul 14, 2019

There is a new fto issue #1167 @freerangeandy please have a look !

Sorry it has been done! hope we create one soon for you.

@amreshk005
Copy link

Hey there, can you please add my name to the FTO list.

@harshkhandeparkar
Copy link
Member Author

Done. You can search for existing ones though.

@Tanish0019
Copy link
Member

@harshkhandeparkar Can you add me to the FTO list. I can work with HTML, CSS, JavaScript and Python. Thank you :)

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

No branches or pull requests