@Aarnav: yes we should prepare some of those again, those were good to help students to learn, we could also design them to be executed in succession, eg:
1. install linux 2. setup development environment 3. python tutorial 4. django tutorial 5. DRF tutorial @okraits: sounds like a great time to start upgrading to pipenv! In practice what would the task consist in? Do we have to change the code of each project or what? To the new comers: welcome! Last year we had many people joining only to mentor GCI students. It was nice to have some helping hands but these new mentors needed training as well and that added even more burdened to our already burdened contributors. In order to avoid adding even more burden to the stable contributors I advise to get involved in OpenWISP, once you understand how OpenWISP works and you show that you are able to contribute it will be natural for you to become mentor. The people of Google Open Source Program Office explicitly advised me to avoid accepting mentors who don't have experience and knowledge of the project. Federico On Tue, Sep 11, 2018 at 6:52 AM Oliver Kraitschy <[email protected]> wrote: > Hi Federico, > > I just had an idea for for a possible task for someone already a bit > familiar how developing with python works. > > The python community is slowly moving from using virtualenv (or > virtualenvwrapper or other derivatives) and requirements.txt files to using > pipenv and pipfiles. > > pipenv is a tool written by Kenneth Reitz (author of the well known > requests library) which manages both virtual environments and package > dependencies: > > https://pipenv.readthedocs.io/en/latest/ > > I think pipenv would make it easier both for beginners and intermediates to > get started with OpenWISP development. So I think we should migrate our > projects to using pipfiles and pipenv. pipenv even creates an equivalent > Pipfile if it encounters an existing requirements.txt file! > > What do you think about it? > > Greetings, > Oliver > > On Wed, Aug 29, 2018 at 10:51:41PM +0200, Federico Capoano wrote: > > Hi everyone, > > > > I think the last Google Code-In was great for our community, it pushed > us to > > improve our documentation, fix a lot of issues, add new features and > helped us > > to grow our community. > > Moreover, one of the winners, Aarnav is still very actively helping us to > > improve and grow. > > > > Last year the main complaints we had from students was that there weren't > > enough mentors to help out, it would be wonderful if this year we could > fix > > this by expanding our pool of mentors! > > The mentor who will be voted the best by students will win a trip to San > > Francisco to meet the GCI winners at Google Headquarters in San > Francisco and > > or Mountain View (this year we visited both offices). > > The privileged mentor chosen by students will stay in a great hotel, eat > great > > food, attend to very interesting presentations given by Google employees > about > > interesting topics (this year they talked about Kubernetees, Open source > > licenses, AI, self-drived cars and many more incredibly cutting-edge and > > interesting topics). > > This year they let us eat in the Mountain View HQ with the rest of the > > employees, it was a really nice experience, it felt a bit like being in > "The > > Interns" movie EHEH. > > > > If you're interested in helping us out please read on, below is the > official > > communication from the Google crew. > > > > Federico > > > > ---------- Forwarded message --------- > > From: 'sttaylor' via Google Summer of Code Mentors List < > > [email protected]> > > Date: Wed, Aug 29, 2018 at 9:35 PM > > Subject: [GSoC Mentors] Google Code-in 2018 is on - org apps open Sept > 6-17 > > To: Google Summer of Code Mentors List < > > [email protected]> > > > > > > > > Hello GSoC mentors, > > > > We are pleased to announce Google Code-in (GCI) 2018, the 9th > consecutive year > > of our contest for pre-university students ages 13-17. Please be aware > GCI will > > start about a month earlier this year than in previous years - the > contest > > starts for students October 23rd! > > > > The GCI timeline, FAQs, Rules and flyers have been updated on the > contest site. > > > > Organizations -- If you would like to apply for the 2018 program please > start > > thinking about the tasks you would like students to work on and reach > out to > > your community members to ask if they would like to be mentors for the > program. > > Organization applications open for GCI orgs next week on Thursday, > September > > 6th, and close less than 2 weeks later on Monday, September 17th. We will > > announce organizations on Tuesday, September 18th giving orgs 5 weeks to > create > > their tasks before the contest begins on October 23rd. > > > > The major changes for GCI 2018 are: > > > > • Orgs will evaluate the 20 students completing the most tasks with > their org > > when deciding on finalists and winners > > > > • Orgs will choose 6 finalists (instead of 5) > > > > • We have renamed the User Interface category to Design > > > > • Students will have to wait until Google reviews their Parental > Consent form > > before they can claim their first task. This will slow things down > but it > > is a requirement to be able to continue the program. > > > > • No tasks asking for personal information about students will be > allowed > > (this includes tasks asking for students to introduce themselves > with info > > like what country they are from, or photos of the students, etc.). > > > > We are looking to continue the growth of this program and reach a record > number > > of teenagers this year! Read more on today’s blog post. > > > > If you have any questions about Google Code-in please contact us at > > [email protected] > > > > Best, > > > > Stephanie and Mary > > > > -- > > 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 [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
