After almost 4 months of work on Google Summer of Code 2017, finally I'm completing my proposal. Every widget migration and every commit/PR/issue/discussion with my mentors about Cricket , Toga and Rubicon-ObjC were detailed on the Issue 58.
With Google Summer of Code 2017 program nearing its end, it is time to summarize what I got done during the summer working on Batavia.
Google Summer of Code 2017 is coming to an end. After three month of working on the BeeWare project, I would like to summarize my work and share my experiences.
Testing is a skill that is a vital part of every programmer's training. Learning how to write good tests helps you write more robust code, and ensures that when you've written code that works, it keeps working long into the future. It can also help you write better code in the first place. It turns out that well architected code, with high cohesion and low coupling, is also easy to test - so writing code that is easy to test will almost always result in better overall code quality.
Around 4 years ago, I made the first commit to Cricket - the first tool that would eventually become part of the BeeWare suite. Since then, the BeeWare project has grown to encompass support for mobile platforms, two alternate Python implementations, and a cross-platform widget set - as well as the developer tools that started the project originally.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
Want to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give away. Email contact@beeware.org and tell us why you want to bee there!
— PyBee (@PyBeeWare) January 30, 2017
PyCon US 2017 is running in Portland, Oregon from May 17 - 25, and it's bound to be another amazing conference.
At PyCon AU 2015, and again at DjangoCon US 2015, I gave a talk entitled
Welcome to the BeeWare project's new website!
The original BeeWare website was written a couple of years ago, when BeeWare was still a highly experimental project. The old website was a single page affair, with individual projects maintaining their own web identity. Over time, the number of contributors has grown, the number of subprojects has grown, and the number of core team members has tripled.
At PyCon US 2016, Philip James became a Core Contributor to BeeWare!
He wrote up some of his thoughts about the process in his article Tips for Becoming a Core Contributor.
Katie McLaughlin, who got her commit bit at DjangoCon Europe 2016, followed up with a post of her own, describing her path to becoming a core contributor.
For those who aspire to become contributors to open source projects, it's helpful to hear how others got there.