-
Notifications
You must be signed in to change notification settings - Fork 209
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
Comments
Good idea!! We need new contributers.. |
@harshithpabbati would you mind breaking up #833 ? |
What should I do ?? Documentation ?? |
Any one or both or you can even solve one of those(if you want). Thanks.
…On Sat 9 Mar, 2019, 5:12 PM Harshith pabbati, ***@***.***> wrote:
What should I do ?? Documentation ??
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#842 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhKOn-qdKIBbgipIVnplQUakH5bZWf-Gks5vU54ogaJpZM4bmlfr>
.
|
But I think the documentation part should be split up into a new first-timers-only |
One suggestion I have already opened up an issue regarding documentation. |
ok @Divy123 |
@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. |
Divy123 we were talking about the documentation part of #833 |
Oh! proceed with it all the best. |
Created an first timers issue #846 |
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. |
Done with that @harshkhandeparkar |
Awesome!! |
@mgroovyank shall I add your name to this list? There are currently 0 fto issues open but there are some fto-candidate issues. |
@mgroovyank welcome! Your name has been added 🎉. I have a few questions that you can answer if you like:
Thank You! |
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! |
I'm looking for first-time issues to solve ;) |
@An0u Welcome! You have come to the right place. Your name has been added to the list !!:tada: |
Hi HarshKhandeparkar, |
Hi @rmcorre, added your name to the above list. Thanks! |
Can you add me to the list? I want to get started with open source contributions. |
@Michaellin250 added! |
@Jaya738 has not replied. His issue has been reassigned to @Michaellin250 |
@scheleon welcome! your name has been added. |
@harshithpabbati do you have any ideas for an fto? |
#951 I will reformat it to fto issue. |
👍 |
#959 can also be seen. |
#992 is up here. |
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! |
@irasanchez you can start your contributions with this issue #951 |
Hi, please add me to the FTO list. |
@konolga added your name. You will be assigned with an issue. |
A new fto added #1084 please have a look and proceed. |
Hey there, can you please add my name to the FTO list. Thanks! |
@jmauriciowebdev your name has been added. You can try to solve #894 btw. |
Hi @harshkhandeparkar or @publiclab/is-reviewers would you be able to open an FTO for @freerangeandy ? I'll add him to the list! |
Sorry it has been done! hope we create one soon for you. |
Hey there, can you please add my name to the FTO list. |
Done. You can search for existing ones though. |
@harshkhandeparkar Can you add me to the FTO list. I can work with HTML, CSS, JavaScript and Python. Thank you :) |
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:
first-timers-only
issuesWe 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:Browse through the publiclab.org and see if there's a bug which can be easily solved.
Solve this issue but don't create a PR this time, instead create an FTO issue.
Click on this link to start creating a new issue.
We follow a specific template for FTO issues, so copy the template from here.
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.
Add a catchy and relevant title to the issue but don't include "FTO", "first-timers-only" or equivalent in the title.
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.
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 ahas-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) issuesscopeQuery
helper method #885)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
andfto-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
The text was updated successfully, but these errors were encountered: