...
In order to kick off the ONAP intern program, we need first to settle down the program structure and several practical issues.
This page is to host the TSC discussion for this purpose. The bulk of the content here has been leveraged from the OPNFV and ODL , ODL and FD.io intern programs
Timeline
TSC to decide many cycles do we want to execute once a year and when we should target to start selection cycle in 2019.
...
Steps | Items | Notes |
T0 | Start of cycle | LF kicks off the cycle per TSC request/decision (with input of the budget). |
T1=T0+3m | Submission deadline | Intended Intern Mentors Submit the project proposals. |
T2=T1+1w | Rank list for TSC review | Review group provided rank list of the received proposals for TSC to review. |
T3=T2+1w | Proposal selection | Proposals are selected as ranked according to the allowed TSC budgeting for this cycle. |
T4 = T3 + 6w | Candidate Selection | The intended mentor selects the intern candidate(s) for each approved project. |
T5 = T4 + 1w | Project Execution | The intern starts to work with mentor's supervision. |
Mentor Guide
If you're a developer and you wish to participate as a Mentor please assess what your project needs or what you feel ONAP should have. Feel free to submit ideas even if you cannot elaborate too much on them. However, the more detail you can provide, the more likely your potential interns will understand what you are looking for.
...
- Provide ample documentation for your proposed project, including a getting started guide.
- Prepare and test any packages or VMs prior to your Interns start date
- Verify all patches submitted by your Intern
- Ensure that you have sufficient bandwidth to meet with your Intern a minimum of once per week and respond to any questions that may arise.
- Share contact information with community members who may be able to help your Interns in case you are not available.
- Set expectations and milestones for your Intern each week and discuss outcome of expectations during evaluations.
- Keep track of milestone progress to share with the Linux Foundation as midterm and final evaluations.
- Notify Internship Program Leadership of any Intern issues (Lack of participation, communication or vacations).
- Provide Midterm and Final evaluation reports within 1 week the perspective dates.
Interns
General information regarding the application process, payment schedule and eligibility can be found at Linux Foundation Networking Wiki Internship Page. Technical questions about specific Internship projects should be addressed by the Project Mentor. General questions about the Internship Program can be addressed by .
...
- Please be prepared to work 40 hours per week for 3 month Internships and 20 hours per week for 6 month Internships.
- If you are not able to keep this schedule, please communicate a suggested alternative plan with your project proposal.
- Interns must show that they have at least 1 commit to any open source project before your internship starts.
- You can work with your mentor during the application period to accomplish this goal.
- Attend at least 1 meeting per week with your assigned Mentor.
- Attend at least 1 meeting per week with your fellow Interns
- At least 1 commit to the appropriate project repository by the end of your Internship.
- Provide a weekly project status update to the Interns group.
Project Template/Sample
- Title: Provide a short but descriptive title of what the intern project is
- Description: Provide at least two or three paragraphs describing the task. Include the problem/opportunity in need of effort, as well as a description of the task to fix the problem or realize the opportunity. If there is a probable implementation path... "this will need steps X, Y, and Z to be completed" please describe it. If part of the task is evaluating one or more potential implementation paths and selecting/executing on one of them, please describe the options and the potential paths to be explored.
- Additional Information: Provide links to Jira entries, release-plan notes, and/or other web-references that would be helpful information to potential interns.
- Desirable Skills: List both the skills needed and the tools to be used. EXAMPLE:
- Java programming with working knowledge of OpenStack and the principals behind NFV.
- Experience fighting evil galactic overloads and time travel will also be very helpful.
- Expected Outcome: List the deliverable(s) (features/application(s)/report(s) etc.) expected
- Difficultly: Easy/Medium/Hard
- Mentors: (use @ macro ) Hosty McHostface
- Additional Contacts: Identify the IRC channel(s) and mailing list(s) where potential interns can ask questions and further interact with members of OpenDaylight project they would be working with.
...