[GSoC2016] - Jenkins Web Interface Improvements

[sto...@gmail.com]

Hi everyone,

I am Winston, a senior studying Computer Science at the National University of Singapore and my concentration is in Software Engineering and UI/UX. From 2014-2015, I went to Silicon Valley to intern as a front-end web developer at an ed-tech startup. When I was there, I discovered that I love building things that can have a positive impact on people's lives and that they like to use. Apart from honing my craft, I enjoy reading technical and entrepreneurial articles/books.

The reason I am interested in Jenkins because I think that it is a meaningful project that I can work on. Improving user experience is always my goal, and with my technical expertise I hope to provide a positive impact on the users of Jenkins. Hence, what better way to do so than to be working on the product that they use day in day out building their own projects. My personal mission is to make people's lives better through technology and I think Jenkins is one of those products that matters to developers a lot.

Here are some of my links:

Github

Linkedin

Medium

Personal Website

Feel free to contact me for a chat! Thank you :)

Warm regards,
Winston

[Oleg Nenashev]

Hi Winston,

Thanks for contacting us!
I've added Michael Neale to Cc. He is a potential mentor in this project, and he has a good timezone overlap with you.

See the schedule of Office Hours here: https://wiki.jenkins-ci.org/display/JENKINS/Google+Summer+Of+Code+2016. We prefer discussing project ideas publicly at the jenkinsci-dev mailing list and such office hours. You can also go through the pending GSoC2016 threads on this topic.

Do you have an experience with Jenkins? If no, we recommend to try automating one of your previous projects in order to get some hands-on experience. If yes, please let us know about your Jenkins UX. Such feedback would be useful to define the project area.

Best regards,
Oleg Nenashev

вторник, 8 марта 2016 г., 18:56:03 UTC+3 пользователь sto...@gmail.com написал:

[Michael Neale]

Hi Winstone. Yes if you had some concrete ideas on an area you think you could contribute to - start and share a Google doc (we can flesh out the idea on it). Otherwise there are office hours where ideas can be thrown around.

[sto...@gmail.com]

Hey guys,

Thank you so much for the response. I am sorry for the late reply because of school and I would like to find a good time to write this email. I will be integrating Jenkins with my project and share a Google Docs with you guys about my thoughts and what features I think can be useful to the platform asap. Thank you!!

Warm regards,

Winston

[Oleg Nenashev]

Hi Winston,

Thanks for the prototype! // To other Jenkinsdevs - see the links here: https://docs.google.com/document/d/19IuOT50nSbP627ocQFEwauRsAQTazYd7fN2_zm6ZkQ8/edit?ts=56e4fb07

Maybe I've lost the discussion track, but I do not exactly understand what you want to implement during the project.
Could you please add the list of changes to the Google Doc?

The proposed technology stack may be good, but it requires some justification IMHO.

Thanks in advance,
Oleg

пятница, 11 марта 2016 г., 8:02:32 UTC+3 пользователь sto...@gmail.com написал:

[sto...@gmail.com]

Hi Oleg,

Thanks for the reply. I will add the list of stuff that I wish to work on as well as justifications of the proposed stack in the Google Docs.

May I also understand the number of hours that we are expected to put into the project each week? Thanks in advance!

Warm regards,

Winston

[Oleg Nenashev]

Hi Winston,

Please check the GSoC Student Guide.
There is a time management section + much other useful stuff.

"GSoC is a job and needs an investment of about 40 hours a week. If you know in advance that you'll need to take a couple of days during the summer of code, you should communicate that with your mentor beforehand and plan to make up for lost days. "

Best regards,
Oleg Nenashev

воскресенье, 13 марта 2016 г., 14:44:00 UTC+3 пользователь sto...@gmail.com написал:

[sto...@gmail.com]

Hi Oleg,

I just thought that the commitment may vary from project to project. Thanks for the reference anyways!!

Warm regards,

Winston