Skip to content

Instantly share code, notes, and snippets.

@baymac
Created August 27, 2019 11:43
Show Gist options
  • Save baymac/7ec870010dbb25e805869cdbdaa1c38f to your computer and use it in GitHub Desktop.
Save baymac/7ec870010dbb25e805869cdbdaa1c38f to your computer and use it in GitHub Desktop.
A retrospective document of Jenkins GSoC 2019

Application period & Before

What did work well?

I started interacting on the community gsoc-sig gitter channel from May 3rd. It was nice and cordial response from the org admins and mentors. That really helped to be motivated and have confidence. We had frequent meet ups on hangouts. Everything was very professionally managed.

What should we improve?

I only think to improve the participants count and project ideas. We can embrace new tech stacks. The millennials are more inclined towards newer programming languages like Python, JS, Kotlin etc. This is also important for Jenkins to keep up with the pace. To take advantages of all the developments.

Proposed actions

Encourage student to be familiar with their tech stacks before contributing to the project.

Community Bonding

What did work well?

My mentors were nice. I had some communication issues with Rick due to regional language barriers. It was a bit challenging initially but we planned on how to connect. It was nice to know mentors personally.

What should we improve?

Community bonding could be used by Mentors to learn about their students personally. What is their capability, assess them technically, encourage them to learn, teach them traits of good programmer etc.

Proposed actions

Instruct mentors about this.

Coding periods

What did work well?

Some mentors backed out due to their other commitments. It didn't affect my project as rest of the mentors handled everything nicely. Marky and Justin managed my project meetings, suggestions, reminders etc. Joseph helped with code reviews and sometimes contribution. Oleg also helped with presentation, reminders, sig meetings etc

What should we improve?

Mentors can also be help students with contribution. I understand there are time limitations for them due to their primary jobs but if time permits they should also write codes alongside student. It is their project as well.

Proposed actions

Encourage mentors to be participating in code contribution.

Post-GSoC

What did work well?

All evaluations were smoothly handled. The PR was also nice, lot of participants and viewers came in to show their interest.

What should we improve?

I think we can encourage participants to keep contributing to Jenkins even when GSoC is over. Although I believe everything is done nicely, maintaining that will be great in itself.

Proposed actions

Have some plans for students to contribute to their projects in the same way or in any other project(s).

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