├── README.md └── pull_request_template.md /README.md: -------------------------------------------------------------------------------- 1 | If interested in any of the internships, submit application using https://github.com/tapaswenipathak/Internship#submitting-application and then book a slot using https://calendly.com/tapaswenipathak. 2 | 3 | **Make sure you are present in the meeting on time**, feel free cancelling or rescheduling, make sure you do it on time. 4 | 5 | # Internships 6 | 7 | - [Code Reviewers Internship](#code-reviewers-internship) 8 | - [Data Visualisation Internship](#data-visualisation-internship) 9 | - [Research Internship](#research-internship) 10 | - [Social Media Intern](#social-media-intern) 11 | - [Open Source Internship](#open-source-internship) 12 | - [field-interns](#field-interns) 13 | - [Tester Internship](#tester-internship) 14 | - [Technical Writer](#technical-writer) 15 | 16 | For each internship - 17 | 18 | - Stipend: depends (max 19K INR) 19 | - Duration: 1 Month (expandable) 20 | - Location: AoE/Home/Remote 21 | - Vacancies: Multiple 22 | 23 | I would only be available for Research Interns and Technical Blogger Intern. 24 | 25 | # Technical Writer 26 | 27 | You would write technical paper, manuscripts as an intern. You should be knowing 28 | 29 | - Latex 30 | - .bib 31 | - Markdown 32 | - .rst 33 | 34 | # Tester Internship 35 | 36 | Tester intern should test the tickets and code submitted by the interns. You should write test case as well. 37 | 38 | # Code Reviewers Internship 39 | 40 | You can apply as an intern who would do code reviews. I am mostly on writing tickets and plan. Code interns would submit code and you should review the code. Intern Code Reviewers would be assigned per project. You can work on writing code for a project and can be intern code review for more project. You should know the technology that the intern is submitting the code in. No extra stipend if you are reviewing code. 41 | 42 | # Data Visualisation Internship 43 | 44 | Any or all of these 45 | 46 | - Arrow 47 | - Bokeh 48 | - Dora 49 | - Matplotlib 50 | - Pandas 51 | - Plotlib 52 | - Seaborn 53 | - tableau 54 | 55 | If interested, please get on a call https://calendly.com/tapaswenipathak 56 | 57 | # Research Internship 58 | 59 | I will only be focusing on writing 60 | 61 | I am in dire need of research interns. 62 | Pitching is my work. If you work w/ me, you would be the co-writer. 63 | 64 | Tasks/Work is listed in https://github.com/alice-sieve/Research-Internship 65 | Reading list for interns https://github.com/alice-sieve/Interns-Reading-Material 66 | 67 | If interested, please get on a call https://calendly.com/tapaswenipathak 68 | 69 | # Repository information 70 | 71 | - Intern should submit the timelines in https://github.com/tapaswenipathak/Timelines, @tapaswenipathak will submit her timeline as well. 72 | - Intern should add a per day log in https://github.com/tapaswenipathak/Interns-day-log. 73 | - Intern can use https://github.com/tapaswenipathak/Interns-qna for writing any questions/help you need from @tapaswenipathak. 74 | 75 | # Submitting Application 76 | 77 | https://youtu.be/J8QxCjCyvFI 78 | 79 | Feel free in submitting application without any call as well. You should 80 | - Create a PR using https://github.com/tapaswenipathak/Internship#pr-template 81 | - Close any 9 tickets from https://github.com/tapaswenipathak/Internship#close-minimum-9-tickets-from-in-your-free-time 82 | - Close one task from https://github.com/tapaswenipathak/Internship-project-tasks/issues 83 | 84 | Let people you know, know https://github.com/tapaswenipathak/Internship#campus-ambassador. Use https://github.com/tapaswenipathak/Internship#campus-ambassador-post sample.' 85 | 86 | Feel free in scheduling a call https://calendly.com/tapaswenipathak. 87 | 88 | # Selected Intern 89 | 90 | - Commit the timeline. 91 | - Get the paperwork signed. 92 | - Update the calendar. 93 | - Update the PR you created w/ a blog on how you closed the ticket you closed. 94 | - You would write a day log. The day log should be public, you can send me that as information for daily morning updates. 95 | - You can setup a meeting if you are really stuck. 96 | - I will have a timeline w/ you and will work on just different issues. 97 | - Intern should just focus on getting the assigned tickets closed. You can use open source. Let me know if you do. 98 | 99 | # Projects timeline 100 | 101 | These are strict timelines that I w/ you will be adhering. No focusing on when I review and merge the PRs you create, just open a PR and work on closing more assigned tickets. I will be involved w/ quite a few things, please bear w/ me.Feel free using me, focus on getting the tickets closed. I am just a call away if you get stuck. If you are selected you I trust you w/ the work you can put up. 102 | 103 | - https://github.com/tapaswenipathak/Internship/issues/39 - Closed on 1/6/19. 104 | - https://github.com/tapaswenipathak/Internship/issues/40 - Closed on 1/6/19. 105 | - https://github.com/tapaswenipathak/Internship/issues/41 - Closed on 1/6/19. 106 | - https://github.com/tapaswenipathak/Internship/issues/42 - Closed on 1/6/19. 107 | - https://github.com/tapaswenipathak/Internship/issues/24 - Closed on 1/6/19. 108 | - https://github.com/tapaswenipathak/Internship/issues/43 - Closed on 1/6/19. 109 | - https://github.com/tapaswenipathak/Internship/issues/21 - Closed on 1/6/19. 110 | - https://github.com/tapaswenipathak/Internship/issues/52 - Closed on 1/7/19. 111 | 112 | 113 | # Social Media Intern 114 | 115 | You would be handling social media channels. If you are creative, entertaining, funny, write exhilirating tweets/posts join as social media intern! :boom: 116 | 117 | # Data Interns 118 | 119 | The data intern will work on collecting data on these topics from the internet. If you know any programming language, API, parsing, scraping, great, if no, manual. The data you collect will be used in https://github.com/tapaswenipathak/Internship/issues/52. You will given a stipend. I won't be helping you in any data collection task. 120 | 121 | # Open Source Internship 122 | 123 | Project list - https://github.com/tapaswenipathak/Internship/issues 124 | 125 | ## During Interview / Selection Phase 126 | 127 | ### Independent Test 128 | 129 | #### Close minimum 9 tickets from in your free time 130 | 131 | The tasks are having `internship` and the technology label. 132 | 133 | - https://github.com/tapaswenipathak/Open-Source-Internships/issues 134 | - You can add any internship you know or close any open ticket. 135 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 136 | - https://github.com/tapaswenipathak/Photography-Competitions/issues 137 | - Write `Ref #ticket_number` while working on any open tickets. 138 | - If you open a ticket write `Fix #ticket_number` in the description of the PR while closing the ticket. 139 | - https://github.com/tapaswenipathak/Women-Communities/issues 140 | - Write `Ref #ticket_number` while working on any open tickets. 141 | - If you open a ticket write `Fix #ticket_number` in the description of the PR while closing the ticket. 142 | - https://github.com/tapaswenipathak/Scholarships-STEM/issues 143 | - Write `Ref #ticket_number` while working on any open tickets. 144 | - If you open a ticket write `Fix #ticket_number` in the description of the PR while closing the ticket. 145 | - https://github.com/tapaswenipathak/GitGIFs/issues 146 | - Write `Fix #ticket_number` in the description of the PR while closing any ticket. 147 | - https://github.com/tapaswenipathak/Societal-Publications/issues 148 | - Write `Ref #ticket_number` while working on any open tickets. 149 | - If you open a ticket write `Fix #ticket_number` in the description of the PR while closing the ticket. 150 | - https://github.com/tapaswenipathak/Linux-Kernel-Infer/issues 151 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 152 | - https://github.com/tapaswenipathak/pyQTopic/issues 153 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 154 | - https://github.com/tapaswenipathak/Research-Paper-Publications/issues 155 | - Write `Ref #ticket_number` while working on any open tickets. 156 | - If you open a ticket write `Fix #ticket_number` in the description of the PR while closing the ticket. 157 | - https://github.com/tapaswenipathak/Open-Source-OS-and-Kernels/issues 158 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 159 | - https://github.com/tapaswenipathak/OSP-Graded/issues 160 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 161 | - https://github.com/tapaswenipathak/Travis-CI/issues 162 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 163 | - https://github.com/OpenSourceHelpCommunity 164 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket present under the organisation. 165 | - https://github.com/tapaswenipathak/Internship-project-tasks/issues 166 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 167 | - https://github.com/tapaswenipathak/Dictionary/issues 168 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 169 | - https://github.com/tapaswenipathak/Bot-list/issues 170 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 171 | - https://github.com/alice-sieve/Linux-Kernel/issues 172 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 173 | - https://github.com/alice-sieve/Open-Source/issues 174 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 175 | - https://github.com/alice-sieve/Social-Research/issues 176 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 177 | - https://github.com/alice-sieve/Market-Research/issues 178 | - Write `Fix #ticket_number` in the description of the PR while closing any open ticket. 179 | 180 | 181 | *Just making sure you know GitHub. My open source work is on GitHub.* 182 | 183 | *Follow proper English and casing while creating a pull request.* *PR slang means pull 184 | request, feel free creating a ticket on GitHub or tweeting at me if you have any questions.* 185 | 186 | If I miss any of the PRs please ping @tapaswenipathak. 187 | 188 | ## GitHub communication 189 | 190 | Please keep the communication on GitHub focused on the tickets/work. 191 | 192 | ## Scheduling calls 193 | 194 | Calendar is only open for interns calendly.com/tapaswenipathak. 195 | 196 | If you have [internet issues](https://gyazo.com/e006580e3ee8d1d3f57a6e10ac19569c) just drop a ping, I will call you. 197 | 198 | I add tasks after calls, please feel free in closing any in the area you know about. 199 | You would be opening PR following the [PR template](https://github.com/tapaswenipathak/Internship#pr-template). 200 | 201 | **Tickets I open you can find code repositories for them on my GitHub, feel free in using code repositories, no reason you should waste time. Just get the tickets closed.** 202 | 203 | If you are stuck on a thing after spending time, please feel free in scheduling a call https://calendly.com/tapaswenipathak. 204 | If I miss answering any question, please post on the ticket or just ping @tapaswenipathak on GitHub. 205 | 206 | Please feel free in rescheduling the call on time if you are unavailable, no need joining the call, I miss my commute at times. 207 | 208 | Please set up the call if you can join the call, no setting the call at odd schedule and than being unavailable. 209 | 210 | #### PR Template 211 | 212 | - Description of the PR should have 213 | - file interns.md, format `Name [\github-username\]\(github-username-url\)` 214 | - Name as heading 215 | - Description should have 216 | - Name 217 | - Mail id 218 | - Tickets closed 219 | - PRs created 220 | - Timezone 221 | - Independent side projects work/writeup 222 | - Timeline doc 223 | - Channel availability (Calendly url) 224 | - Daily meeting preffered timing (Calendly url) 225 | 226 | ### Work w/ @tapaswenipathak 227 | 228 | - I will reach you w/ further details / a scheduled meeting. 229 | - You submit one month timeline/plan. 230 | 231 | *The tasks would only be shared w/ the selected intern*. 232 | 233 | ## Work phase 234 | 235 | - Follow the timeline you create, work w/ @tapaswenipathak if you need anything, she 236 | would be working w/ you in this month just on different tasks as per her schedule. 237 | - Daily mail sync up (mornings). Meeting only if required. 238 | 239 | I have listed few internship projects as [tickets](https://github.com/tapaswenipathak/Internship/issues) in this repository. 240 | **If you have any questions please discuss on GitHub, feel free re-pinging if I miss responding.** 241 | 242 | 243 | 244 | # Field Interns 245 | 246 | I am hiring field interns. 247 | 248 | You should know the local language, should be decent in talking, energetic, fearless. 249 | 250 | You would be collecting information from police stations, courts, NGOs, restricted areas, villages. Every intern per locality assigned information collected would be given a 9k stipend, negotiable. You would be remibursed for cycle commute. If you like travelling in remote areas in your city, I will be funding the travel as well. Any Indian government permission required would be on me. 251 | 252 | I am hiring people from remote areas, please help me in reaching out people who live in remote areas by letting the people you know, know. 253 | -------------------------------------------------------------------------------- /pull_request_template.md: -------------------------------------------------------------------------------- 1 | - [ ] file interns.md, format Name [\github-username\]\(github-username-url\) 2 | - [ ] Name as heading 3 | - [ ] Description should have 4 | - [ ] Name 5 | - [ ] Mail id 6 | - [ ] Tickets closed 7 | - [ ] PRs created 8 | - [ ] Timezone 9 | - [ ] Independent side projects work/writeup 10 | - [ ] Timeline doc 11 | - [ ] Channel availability (Calendly url) 12 | - [ ] Daily meeting preffered timing (Calendly url) 13 | --------------------------------------------------------------------------------