Hello OpenWisp, I hope with the 2019 google code-in event I get a lot of 
lessons like: 1. Python code conventions 2. Javascript code conventions 3. 
OpenWRT related conventions
and I hope to participate with OpenWisp this year.
On Sunday, October 20, 2019 at 12:43:28 PM UTC-4, Federico Capoano wrote:
>
> Hi everyone,
>
> we are applying again as a mentoring organization for the Google Code-In 
> 2019.
>
> This year I want to propose that our main goals should be:
>
> - train as many students as we can, with the goal that they may become 
> mentors in the future
> - keep improving OpenWISP and fixing bugs
> - improve the work done during GSoC by our GSoC students
> - improve our documentation further (although in my experience it's pretty 
> hard for new students to write good docs)
>
> What do you think about these? Is there anything you would add or remove?
>
> I want to put particular importance on the first point, because one of the 
> main complaints given by our students in the past editions was the number 
> of available mentors. If we can increase the amount of competent mentors, 
> we will be able to train more students and multiply our impact on Open 
> Source.
>
> If you're interested in participating as a mentor, please fill this form:
>
> https://docs.google.com/forms/d/e/1FAIpQLSczt_VDztWZ7ZYnuoZoNpdIjWXiTH2iVFShLzeZs1Vi0DmGcg/viewform
>  
>
> Best
> Federico
>

On Sunday, October 20, 2019 at 12:43:28 PM UTC-4, Federico Capoano wrote:
>
> Hi everyone,
>
> we are applying again as a mentoring organization for the Google Code-In 
> 2019.
>
> This year I want to propose that our main goals should be:
>
> - train as many students as we can, with the goal that they may become 
> mentors in the future
> - keep improving OpenWISP and fixing bugs
> - improve the work done during GSoC by our GSoC students
> - improve our documentation further (although in my experience it's pretty 
> hard for new students to write good docs)
>
> What do you think about these? Is there anything you would add or remove?
>
> I want to put particular importance on the first point, because one of the 
> main complaints given by our students in the past editions was the number 
> of available mentors. If we can increase the amount of competent mentors, 
> we will be able to train more students and multiply our impact on Open 
> Source.
>
> If you're interested in participating as a mentor, please fill this form:
>
> https://docs.google.com/forms/d/e/1FAIpQLSczt_VDztWZ7ZYnuoZoNpdIjWXiTH2iVFShLzeZs1Vi0DmGcg/viewform
>  
>
> Best
> Federico
>

On Sunday, October 20, 2019 at 12:43:28 PM UTC-4, Federico Capoano wrote:
>
> Hi everyone,
>
> we are applying again as a mentoring organization for the Google Code-In 
> 2019.
>
> This year I want to propose that our main goals should be:
>
> - train as many students as we can, with the goal that they may become 
> mentors in the future
> - keep improving OpenWISP and fixing bugs
> - improve the work done during GSoC by our GSoC students
> - improve our documentation further (although in my experience it's pretty 
> hard for new students to write good docs)
>
> What do you think about these? Is there anything you would add or remove?
>
> I want to put particular importance on the first point, because one of the 
> main complaints given by our students in the past editions was the number 
> of available mentors. If we can increase the amount of competent mentors, 
> we will be able to train more students and multiply our impact on Open 
> Source.
>
> If you're interested in participating as a mentor, please fill this form:
>
> https://docs.google.com/forms/d/e/1FAIpQLSczt_VDztWZ7ZYnuoZoNpdIjWXiTH2iVFShLzeZs1Vi0DmGcg/viewform
>  
>
> Best
> Federico
>

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to openwisp+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/openwisp/eb3efbd7-414a-4aa0-a055-5b1351aac535%40googlegroups.com.

Reply via email to