https://s3-us-west-2.amazonaws.com/secure.notion-static.com/9f5b8539-09b2-4ed8-8b0f-412164f59e1e/Untitled_presentation_(2).png

Hey everyone, after being selected for GSoC 2020, there's a great summer full of open source development. This is the fifth weekly check-in and we're into the coding period. Here's what I've been up to this week

This week is pretty amazing and there's quite a good variety of things going on. Being the first week of the Coding period, it brings awesome pieces of work to you and gives you a chance to actually experiment, enhance and upgrade your work strategy.

What I'm up to this week ?

This week is mostly focused on bringing the things that we were working on earlier to an end. The two big tasks are to have S3 support in Gutenberg, and multi zim creation in TED. We're also working on addressing the issues with youtube throttling for some videos in TED and managing both of them.

The Gutenberg S3 based optimization cache is the longest, both in terms of lines and in terms of time.

As of now, the TED multi-zim support is almost ready to merge and the Gutenberg S3 support is awaiting a review. Currently, I'm working on the sotoki bug in zimfarm and some small TED fixes and zimfarm support for the multi-zim scripts.

What's ahead now?

We do have got the very first TED zims in zimfarm this week and are on our way to complete everything we started last week. Coming to the near future, we do have seen the very first release of python-libzim and we may have a shift in priorities if that gets a stable release anytime soon. Anyways, currently we look forward tosome enhancements in the openedx scraper and youtube videos support in TED.

Challenges I faced

This week had some challenges and one of them being the S3 support in Gutenberg. Actually, all the steps in Gutenberg are exploded and are sometimes meant to be run independently. So, I had to deal with that in the S3 support implementation. However, since it's done now, that doesn't seem to be much of a problem now. Also, the sotoki bug is a bit challenging as there are many error candidates, but theoretically I can rule out all of them. This one's very interesting BTW.

Verdict

Okay, I know I'm a few hours late with this post, but it's actually due to the fact that I was trying to fix the sotoki bug last night. Overall, I can say that the work that you get to do during GSoC is super interesting and keeps you involved and makes you forget things. And that gives GSoC the awesomeness that it's known for.