Since I endured the data-loss yesterday while running the tests, I have run into another issue. What can I say? Curiosity kills the cat. Or, in this case, the build that’s vital to logging my usage and activity for the program.
I am honored to be part of the Foxfooding program, by Mozilla. This is a program that allows employees and contributors to test drive a Firefox OS device. The catch is that you have to use the device daily. Now, it doesn’t say you have to use it as your primary device with SIM card and the works, but I decided to be adventurous, and given I wanted to work closely with the Firefox OS team next summer, I decided why not.
It is with much pleasure that I announce the release of Terml.io today as now an open source tool that will help students not only study definitions, but now expose them to real-life industry standard code.
Open sourcing Terml.io has always been something I wanted to do, however with the payment system and premium feature integration, I opted to keep it closed to encourage use of our own platform. From this point onward, I will be taking mostly a hands-off approach. My colleague, Jeffrey Wang, will be in control of all aspects from this point onward, and I will be a contributor should I decide to make updates.
At this point in time, Terml.io is stable, with a clean design and good functionality. There is no better circumstance to step back from this project, although I hope it continues to grow from here. Thanks again, to all who supported the product since its beginning. Keep rocking.
You may view the new GitHub repository here.
It’s been two weeks since my summer ended with Mozilla, and I can’t say it’s been easy to take a break. I’ve spent so much time with the team, from attending the work week in Whistler, to chatting with them on IRC. I had a blast working with Dave Hunt on my project, and learned a lot more about test automation, QA, and web development.
Last Friday marked the end of Mozilla’s 2015 mid-year work week and I have to say, it was one of the best one’s I’ve ever attended. I’ve only attended one other workweek (Portland, December 2014), but it’s been awesome. Before I go into the details, I want to applaud Mozilla on their exceptional effort to involve community in events like this. Never in a million years would I have imagined myself sitting in meetings and attending sessions with a team at such an amazing company, and the fact that I, a 17-year-old contributor, am able to attend such events. I would also like to thank everyone involved in organizing and planning this event. It ran so smoothly, and was very enjoyable, for me at least.
I am a core contributor for the Web QA team. According to the Mozilla wiki, this means that I “have made major contributions to support the mission through their contributions of time and skill. They give Mozilla reach in terms of scope, geography and influence far beyond what could be achieved through directly staffing an organization.” I work on everything, from automation to manual testing, and this summer will be spending my time on switching our test framework from Selenium to Marionette.
This is a blog post that appeared a while back on quality.mozilla.org, which was the main page of Mozilla’s QA efforts. I wrote this during the summer when I was considered a “sponsored intern,” working 15-30 hours a week on Web QA related work with Mozilla, in exchange for my parents to pay for my car insurance and gas. I thought it would make a nice first post, as a view into the past of who I was, and where I am today, as a core contributor to various projects including Mozillians, Webmaker, and learning the ropes of Firefox OS QA. So without further delay, my first blog post ever written…