The Changelog: Software Development, Open Source - Trending up GitHub's developer charts (Interview)

Episode Date: December 14, 2019

In this episode we’re shining our maintainer spotlight on Ovilia. Hailing from Shanghai, China, Ovilia is an up-and-coming developer who contributes to Apache ECharts, maintains Polyvia, which does very cool low-poly image and video processing, and has a sweet personal website, too. This episode with Ovilia continues our maintainer spotlight series where we dig deep into the life of an open source software maintainer. We’re producing this series in partnership with Tidelift. Huge thanks to Tidelift for making this series possible.

Bandwidth for Changelog is provided by Fastly. Learn more at Fastly.com. We move fast and fix things here at Changelog because of Rollbar. Check them out at Rollbar.com. And we're hosted on Linode cloud servers. Head to Linode.com slash Changelog. Welcome back, everyone. This is the Changelog, a podcast featuring the hackers, the leaders,

and the innovators of software development. I'm Jared Santo, managing editor here at changelog. In this episode, we are shining our maintainer spotlight on Ovilia. Hailing from Shanghai, she's an up and coming developer who contributes to Apache Echarts, created Bolivia, which does very cool low poly image and video processing and has a sweet personal website to boot. This episode with Ovilia continues our Maintainer Spotlight series where we dig deep into the life of an open-source maintainer. We're producing this series in partnership with Tidelift. Huge thanks to them for making this series possible. Tidelift is the first managed open-source

subscription that pays the maintainers of the exact projects that you're using while giving you the commercial support you've been looking for. Learn at tidelift.com okay let's do it enjoy ovelia we've been paying closer attention to github's training developer charts and in october your name popped up and you're from shanghai china you're doing some really cool stuff in open source you're a committed to ap. Yes, I am a committer of the Apache Echarts incubating project and I do a lot of personal open source projects on GitHub. What is it that draws you to open source and the things you're doing today? Before we kind of get into the details of things, what is it that draws you to the community of open source and what you're doing? I think it's cool to get people to know what you are doing and how you do it.

And I think this is the spirit of the open source, that people can see how you do it along with what you are doing. And I think it's very cool to make interesting things and projects that is really useful on the GitHub. Maybe what specifically you yourself, what's sort of your developer path? Give us some background on you. I've been studying for software developing at school and after graduation I think I'm passionate on the

data visualization field so I joined the Apache group Apache eTrust group and on the other side I have been using github for many years and as a start there are not many followers but as i doing many open source projects and after some time i get some followers and the comments from them and i think this feedback really makes me goes on to do more interesting stuff on github yeah speaking of followers, 9.6, or otherwise known as 9,600 followers or 9.6 thousand followers on GitHub. So you said it started slow. What do you think began an attraction to you

as a software developer? Was it your work here on eCharts? What was sort of the proverbial hockey stick for you? I think it all started from a CV project that I did before graduation. At that time, I was looking for a job after graduation. So I think instead of looking for jobs everywhere, why don't I put my resume online and let the companies to know about me?

So I made an online CV, and this project promoted very well, and it has maybe hundreds of thousands of people to get to know me. And from that time, I get some followers on the GitHub. Maybe speak to that. I don't know if we've ever really talked much about the fact that obviously many people know that GitHub is a social network for software developers, but we don't often talk about

the following that someone cultivates on GitHub. How have you seen that affect your developer life? The fact that you have 9.6 thousand people following on GitHub, how does that permeate into your everyday life as a developer? I think definitely it makes me more devoted and want to make more projects and interesting cool stuffs on github but I think the difference is not very large between having 9,000 followers or 9 followers maybe the most difference here is that when I create a new project, more people will get noticed to it, maybe put a star on it also. But most important thing is to continuously create cool stuff on GitHub.

Let's get into that then. So cool stuff on GitHub, cool projects. As we talked about, you're involved with Apache Echart, which is a JavaScript visualizer. How did you end up as part of that incubator project? Yeah, I was looking for a job after graduation. So as I said, when I made this online resume and my current boss found my resume and asked me if I got interested in this project. And at that time, eTrust was quite famous. But I said, no, I haven't heard about it. But luckily, I passed the interview, partly because my research domain was about computer graphics and image processing. So it's quite related to the project. And I'm very passionate about quantified self and data visualization.

So I chose eTrust to be my first career and hope it to be the last one. What do you know about the background of the project itself for becoming an Apache incubator project? Do you know the backstory there? Yeah, I know some of it. Can you share that with us? Yeah. It was back in the year 2012 when an engineer of our company was doing a chart-related task with his job. And he found that it could also help many others

with similar requirements. So he made this project open source on GitHub under the organization of the company. And that's the beginning of the eTrust project. And in recent years, more and more companies in China, especially the big ones, perhaps have come to realize that by donating projects to open source organizations like Apache Software Web Foundation, it is a good opportunity to let the project used and maintained by more people who would otherwise be hesitated about the license or other issues when choosing a project owned by a company. And of course, it helped the company in reputation and more. So in the year 2018, we donated the e-charts to the Apache Software Foundation, and now

it's under incubation there. That's interesting. What does it offer? What do they offer to an incubator project that made you want to do that? Why was it compelling for the eCharts team to donate this project to Apache? Basically, by incubation, it means to learn the Apache way, which is how we do certain things when maintaining a project under Apache. For example, when we are going to release a version, we will do a series of things to

build the release and run a vote, both inside the project's committee and outside with other Apache members. Frankly speaking, this process could be quite complicated, but it ensures the project is under license protection, so the inconvenience is well paid. And being incubationist to learn such rules and make sure that we have everything down without the help of mentors. And that will be the time then we can go out of incubation. So back to the question, I think a very important value

that Apache offers is the opportunity to learn from such a mature community how to operate such an open source project. Because being open source is not just about making your project public on the GitHub, which is the first step, but a very small one. In order to make it used by many others, there is plenty of work to be done. For example, we need to provide complete and detailed documents and tutorials to help others understand how to use it.

But a more challenging job for us is to build a healthy community, where people with different levels of knowledge can all get help from it. That's one of the most primary considerations when we decided to join Apache. Because at that time, we only have less than 5 people maintaining the project as day job, and most of us are not doing it full time. Well, on the other hand, we have 200,000 of downloads on MCN weekly. I think we could be proud of this ratio, but potentially it is a very dangerous signal. This means that if one or two of us don't maintain the project because of personal reasons or job changes, that will probably be the end of the project.

So by joining Apache, we wish to learn more about how to encourage the community to contribute and make it healthier. And I can't say that we've done well enough, but we are having progress on this. After joining Apache, we have voted and accepted about six new committers and definitely have more pull requests from the community after we turn to be more open and provide more proper ways to guide the community to help. Very great answer. You said that you've been involved in Apache eCharts for more than three years now. Refresh my memory, how long ago was the incubation process?

That was beginning from January 2018. 2018, so just a little over maybe two years now. Just approaching two years. Yes. years yes and you mentioned i think it's uh wise of you to mention the you know the difficulty i would say i or i to paraphrase what you've said you know how hard it is to become an incubator project what's involved in it but the the payback is to learn the apache way and it's not just simply putting your source code onto github or onto the internet anywhere and saying, hey, we're here.

It's more of a how to build an open source project. That's really interesting the way that you've spoken about that because not everybody has that perspective. What is it that gave you that perspective? How did you investigate the Apache way or the way of Apache to, I guess, decide to incubate with them versus someone else or somewhere else yeah because we tend to realize that by maintaining the projects by only our few people is not enough and previously we have poor requests from the community, but for projects like Etrus, that is, the code base is large and not easy to understand.

So we often get the pull requests that seem to eliminate the kind of PRs and fix it by ourselves, because it takes more time for us to teach them how to fix than to fix it by ourselves. But this could be a problem because we have so many users and the product is rather complicated in order to meet the requirement of so many people. And before joining Apache, we realized this problem and we think we should have a way to solve it. And Apache helped us a lot by providing us ways to fix this. You seem very well versed in the behind the scenes of this project, more so than I expected. What role do you play for the project?

And what are the things you do for it? I am a committer of it, and I do fix bugs and do feature requests for it, along with do community buildings. Like I will ask the community to vote for the new committers and to see how we can help more people contribute to the project. And for the code part, I've doing some tools like SimEditor, which helps the user set the chart themes in GUI and export it to be used in eCharts. And I've made a cheat sheet to help users understand the terminology of components. Because in the documents, components are named like legend or access pointer or visual map.

So new users may find it hard to locate the document. And I created a chart with frequently used components. And when the mouse focus on the component, it will show the name of that component and the link to the document. And I've also created some new types of charts like liquid field chart for percentage data and some burst chart for data in tree structure. But our regular work is about fixing bugs and producing new features for all parts of the code. Very cool. Well, I guess it's kind of hard to bypass the fact

that you're from China. And my guess, I didn't ask you this, but my assumption is that Chinese is your first language. Is that correct? Yes. And English is your second, I would say, maybe third or fourth, who knows, potentially. And I guess one question that gets asked often is about language barriers. Can you speak to a language barrier in general? Is that a major

problem for you when you are involved in open source? I know that a lot of software and documentation and whatnot is primarily written in English. Is that a problem for you when you commit to open source or is it only annoyance? I think when contributing to the open source, the language is not

a very big problem for me because luckily making comments on GitHub or writing emails to discuss about technical problems don't require one to have a degree in english literature and even i make grammar mistakes like i may did many times today i guess usually others can also understand what i mean and i don't think it's an annoyance because only with the help of having a common language can we people all over the world communicate and together build a better tomorrow. Isolation and arrogance can only take one backward. As a famous Chinese slang goes,

move forward or you will fall behind. Very, very well spoken, very well spoken. I like that. There's another one in the Bible that basically says to plow a straight row, you can't look back. So if you're trying to go to a certain point, the analogy essentially is, and obviously using a plow, somebody who would be gardening or developing their farm, they're going to be using a plow somebody who would uh would be gardening or developing their farm

they're going to be using a plow to make straight rows for their planting for their their process and so in order to make that row straight you have to have a vantage point far enough in front of you that you're fixated on it because that's how you keep the plow straight and if you're constantly looking back well you're not going to plow a straight row. Yeah, exactly. Thank you. Python, Java, PHP, Ruby,.NET, and more. Subscriptions include security updates, licensing verification and indemnification, maintenance and code improvement, package selection and version guidance,

roadmap input, and more. The bottom line is this. You get all the capabilities you expect from commercial software, but for all of the key open source software that you're already using and depending on. Tidelift works with GitHub, GitLab, Bitbucket, and more. They support every cloud platform out there. And of course, you can try it absolutely free. Start your free let's talk about uh polyvia is that how we pronounce it polyvia yeah i would call it

polyvia but that's okay because you you don't have to pronounce it as i thought it so well sorry about that polyvia low poly image and video processing let's talk about this this is a project you started tell me about the background of this project yes this was originally my graduation project which takes an image as input and generates stylized image with triangles of different colors and sizes. Naive method would be to choose some random points in the image and form triangles from that. But it loses edge information so the result is not recognizable that much. And my method is to first find out the edge information and then put a higher possibility on

random points to lay on the edge. In this way, the edge can be preserved and the overall result is better. After we have some random points, dilineation triangulation is used to form points into triangles. The main idea of this algorithm is to avoid obtuse angles in triangles so that the result is more pleasing. And finally use the color at the gravity center of the triangles and we have the result there. How long did this project take for you then? So you said it was a graduate project, is that right? Yeah. What was the, I guess, behind the scenes of the aha moment? So you mentioned a naive approach

would be just to simply find the edges and instead you took a different route to not just find the edges but then also to sort of find the defining edges there. How did you get to that point? Tell me about the iteration process. Because the naive way lose the edge information. So my first point was how to preserve that information. So from the image processing lesson, I learned that I can use some operators to get that information. And once I get the edge information, I can put more random points on that edge so that the triangles will be formed on that edge. I haven't dug into every single project you've done on GitHub, but considering what you've been involved with, with eCharts and this graduate project, it seems like you've got a pretty, let's just say, creative mind. What are some of your favorite projects that you have on GitHub?

What are some ones that really, whether they're popular or not, it doesn't matter. It's just more like, which ones were the ones that were most fun for you? That's definitely my personal website. Ah, yes. What was the style behind this? This is a really interesting website. I love it. I redesign my website every year because I always have new ideas for the new design or

new technical details. So this year I made an old school pixel art style because last year the design was like a robot which you can communicate with it. She will ask you about how do you feel about this website also and you can pick an answer to communicate with it. And in this form, I want to make conversational app to the user. So this year, I think of that

instead of making a communication robot, why don't I make a mobile phone? And in this mobile, you can see apps of my projects for example the album is about my photos and the apps are the apps I made and there are apps that I made on iOS app store and in this way this website can hold the projects I did and the things about myself I think this could be an interesting personal website idea I definitely think it's interesting and I think it's frankly I think it's awesome thank you one thing I love is just how yeah I'm digging through your album as you you mentioned, and how it's based on

real photos, but when you first look at it. So for the listeners, when you're checking this out, you can go to z-h-a-n-g-w-e-n-l-i.com and you'll be presented with the latest iteration of her website. And it's super cool. So when when you go here you can see your images and it it sort of it goes from this pixelated version to the actual real photo what was that is that a separate project what's the thinking behind that how does that work yeah this is a separatist project that i made for my new design of personal website. The main idea is to use image processing to make the photos into old school palette. So I made a command line Node.js service to do the job.

And after that, I made this separate MPM package and open sourced it. The main idea is to give a palette of colors. For example, for old school, I may give some different scales of gray colors and then it will find the nearest color of each pixel and turn it into an old school palette image. You mentioned that's for Node.js. Is that open source as well as most things you work on? Yes, it's open source to a separate project.

And I created an MPM package of it. So clearly you have a plethora of open source this website is a testament to that that's also open source on github so if you want to dig into this software and the code behind it the the website you can check out our show notes but i'm curious when you find time to do all this like how do you design your life to to be able to work on so much open source and I guess maybe a side note to that is is why open source everything that you've done I think for the time part if you really want to do something you will have the time rather than excuses. We all have limited time nowadays, but what we do with our limited times

pretty much forms who we are. So I think it is a cool thing to make those things open source to public and let others to see who I am from the projects I made. Let's talk about maybe the reasoning why open source then. Why do you open source so much? I can't think of a straight answer, but the first idea come to me is that why not? Okay, I like that. Okay. So then why not then, right?

Let's speak to that then versus the opposite side of that. So then why not? What's your reasoning behind that? I think my idea was that at first, if I open source a project, I have nothing to lose, right? And then I certainly get more reputation from the community, and I don't think there is instant revenue from that, but I think pretty much like the, enjoy the experience of open source, yeah.

So you spoke to time, you spoke to the why. Maybe what do you like most? You kind of mentioned it's not about revenue or i would assume some sort of income or some sort of personal gain but what is it that you like most about being an open source software maintainer i think it's really encouraging to see that the project i participate in can help so many people like e-charts And this is one of the Apache values called earned merit, which means you contribute to a project

and gain reputation and respect from the community. And I think this is pretty much the most inspiring thing for me to maintain such projects. These values of the Apache way, are they well known? It's well known in Apache community, but I don't think so outside. Because that seems like some wisdom. What other wisdom is behind the Apache values? Can you share some of your favorite Apache values? Yes, one of them is that you contribute to the project personally rather than representing from a company or organization. For example, eTrust was originally donated from a company to Apache.

And we committers are speaking our minds personally but not representing the companies. In this way, we all have the equal right to have a conversation or discussion and no one has the authority in deciding everything. Yeah, I like that because the merit, I suppose, would even be the case. It comes back to you versus the company you represent. It's a personal value versus a corporate value

that you get to inherit. Yes. Interesting. I love that. Earn the merit is such a nice thing to say. It's a phenomenal response to why open source because you get to earn the merit. You get to make the world a better place.

Obviously, on the flip side of that, there's always some sort of least favorite thing. So as an open source software maintainer, what is it that makes you want to pull your hair out? What's the least thing you like about being an open source software maintainer? I sometimes feel regret to see that some of the users from the open source community take it for granted that their requirements should be answered and fulfilled as soon as possible. Not only for eTrust, but this is rather a common problem for the open source world. Of course, we can understand that from the user's view, they always have urgent requirements and think it's the responsibility of the open source project's maintainers to fix the problems with the highest priority. But it's not how the open source works, and this may make some of the users frustrated or even angry about it.

In fact, the whole point of being open source is to provide the source code so that everyone can help improve it. We don't expect everyone to debug and find the problems by themselves, but some users just don't know how to raise a question informatively and politely. And that could be frustrating for the maintainers tell me about i guess this concept that has become more popularized in the last several years and maybe especially this year with the inception of github sponsors for independent open source software maintainers to essentially find paths to fund themselves. There's words like sustainability, funding, sponsorship, etc. But what is your position on

receiving financial benefit from your efforts in open source? What's your stance on that? Yeah, I think it's a nice way to start an experiment to see if this could work for the open source world. But I've not personally tried with it because they are only for the better stage. And I think if it can go to a healthy community like the patron goes, I think it's a good way for the maintainers to put more effort on it because some of them can be a full-time open source maintainer

to put more efforts on the project. But on the other hand, I do have concerns about whether these benefits could let the open source go another way to consider the benefits too much so that it will have some potential bad effects from that. So your concern is that a focus on sustainability or a focus on funding could skew the focus essentially i can't say for sure but i think it's worth experimenting yeah because one thing i'm noticing the reason why i ask you that is because i'm not seeing on your super awesome personal website any sort of mention of patreon or anything like that when i visit your github profile i don't see the option to sponsor you i know that they're still rolling out some of these benefits especially on github i know that they recently just announced coming out of beta

to 30 different countries and i would assume that china might be one of them maybe not can you speak to that as is gith GitHub sponsors an option for you personally in China? I don't know the current stage, but I do know that GitHub is trying to build more relationship with the developers in China. In fact, I was heading for Shenzhen to a GitHub meetup to hold by GitHub so that they want to get more Chinese developers focused on GitHub. So I think this is a good signal to see. So if you had some, I guess what I'm driving at is

I haven't seen you make an effort to try to fund yourself through sponsorships, donations, patrons patrons however you want to frame it are you personally interested in that are you just sort of like waiting and kind of figuring out what how it's gonna play out what what's your your personal stance on it for you and and uh finding some sort of way to be kind of financially supported through your open source? I think if it's open to me, I will have a try. But I don't think this is a very long term good way for me to get supported financially. Because I think a really healthy way is to provide real values to the users. And if the users can use the products I create and benefit from it, they will donate to me. That's a good thing. Like if I contribute to

the eTrust project and help many other people and then they donate me. I think this is a good thing to see. But for my personal projects, I usually do the projects that is not used by many people or I can say they are just toy projects. And I don't think that I can gain benefits from them or even if I can get some benefits from it, it's not enough to support me to do it full time. So I think what I wish to do is to create apps or other services that really help people

to create their own values. So since you don't have a way right now for someone to donate to you, what options are available to you in China? What options are available to you personally to take that first step? When might you consider doing that? I have put two of my apps on the App Store so they can buy my apps if they think it's helpful to them. And in China, we have other donate services pretty much like Patreon and they are open to Chinese people. But I think my reputation outside of Chinese is not very much. So I didn't provide an extra way for people outside of China to sponsor me. I see. I see.

Well, that's what we're trying to drive to with this particular show is a peek into not only the projects that we speak to on this show around open source, but also the maintainers behind those open source projects, their lifestyle, what they're involved in, their values, as you've talked about, the reasonings why they do what they do, and maybe what you like most and what you don't like as much. But then also as we sort of try to find ways to sustain, that being an open source software maintainer, as you've said, one of the things you said you liked least about it was that people feel as if they can ask you

or ask of the project maintainers something and expect the answer today. And that's a skewed expectation from a user standpoint, but it doesn't help you be able to show up every day. It doesn't help you to, to cover rent or to, for lack of better terms, to make being an open source software maintainer, your, your thing, what you do. And the reason why I say that is because when we spoke with Devin Zugal on a recent episode of The Change, when we talked about GitHub sponsors, near the end of the show, we asked her, what's success for you for GitHub sponsors? And I was quite surprised by her answer.

And her answer was, just like someone would say they want to be a firefighter or a lawyer or a doctor, I want someone who's young, who's aspiring to their future to say, I want to be an open source software maintainer. And so one of our reasonings for doing this show, this maintainer spotlight series is to sort of kind of get an understanding of everyone's thought around that particular subject because it's becoming so much more of a concern to figure out how to sustain

not just the projects, but the people behind them. What are your thoughts on that? Yes, that's exactly why I can't answer your question about why I do open source. I think the idea is I just love it. You just love it. That's, in all honesty, that's the best answer i love that thank you let's talk about maybe other maintainers out there you might admire or appreciate you'd mentioned that a lot of your popularity and potentially even a lot of your social network that you know

is in china who out there may have you learned from over the years? Who's somebody you look up to? Somebody that we can share with our audience? I would recommend two developers. One of them is our eTrust committer whose GitHub ID is P-I-S-S-A-N-G. He is specialized in WebGL and created many interesting and useful visualization tools. One of which is called paper cooling art,

which generates artistic image processing results simulating the effect of paper cooling art. It's quite hard to describe, but I think you will be impressed if you check it out. He can answer almost all of my technical questions, as much as I can remember remember because he is my mentor. But one more valuable thing I learned from him is that to persist in what you think worth doing and put in continuous effort before achieving a result good enough. This has always been inspiring me when I feel not so confident about what I

could or should do something. Yeah, absolutely. We can obviously get quite paralyzed. And unless we think something's worth doing, I think that's fantastic advice to persist in something worth doing. That's awesome. And another one is a designer, but not related to the eTrust project. He is a designer, but his web programming skill is good enough to make his excellent designs into code.

And he's also very active on GitHub. His ID is jjying. I most admire his taste of design and he's also producing a podcast called Anyway.fm, but it's in Chinese. Well, my point is, it's really inspiring to have some people around me doing excellent jobs in their own fields. And that can make me myself to be more devoted and create more interesting works from my side. Maybe let's talk about the necessity of a mentor. That often gets glossed over, I would think, to some degree. We've spoken about it on GS Party, another podcast we have here

at Change Law, but can you speak to this idea of mentorship to you and maybe even some helpful tips on how to find a mentor? It's actually from my day job mentor. So I can't tell you how to find one, but I think I'm really lucky to have one. Well, let's go from the angle then if if you didn't have a mentor today and you have the open source prowess and followership that you have and the impact that you're already involved in obviously you're involved in a uh a high profile project with apache you know with with each arts if you had to seek out a mentor today how would you do it i think the first question would be why would you do it? I think the first question would be why would you need a mentor? For me,

maybe this is for technical problems or to have someone that you admire so that you can be more devoted and be as good as you think he is. So if it is the later one, I think we can find many mentors on GitHub. I think that's pretty much the reason why so many people follow me. Because they find me doing those cool things and always have interesting new ideas. So maybe they think that by following me, this can help them to be more devoted and do cool things by themselves. Well, let's laser in on that then. What's the next step for you to become a mentor?

Or are you already a mentor? You mean in my day job? I mean, in open source, you seem to be very well you know, very well spoken for one, very well capable of producing awesome software and leading great communities and being a leader. What's the next step for Ovilia to be a mentor of someone else? Oh, I write blogs in Chinese, sorry. I write blogs about those non-technical ideas. For example, I posted a blog about how I did two iOS projects in two years.

And I wish to use these kind of posts to inspire more people to have faith in themselves and to do those cool things by themselves. I'd love to help you do that. That would be awesome. One of the positions also for us doing this is to help people like you to reach more people. And in many cases, like you'd mentioned, that's probably the reason why people are following you is because they want to find some inspiration. They want to find a path forward. And you're providing that path in many ways. Avelia, thank you so much for your time.

It was awesome to hear about your background and your involvement with Apache eCharts and your thoughts on mentorship, your thoughts on why to even be an open source software maintainer. So thank you so much for your time. It was awesome. Thank you, Adam. All right. Thank you for tuning into this episode of The Change Law. Guess what? We have comments on every single podcast episode. Head to changelaw.com, find this episode, and you can discuss it with the community.

Huge thanks to Tidelift for their support of our Maintainer Spotlight series. And of course, thanks to Fastly, Rollbar, and Leno for making everything we do possible. Our music is produced by the one and only Breakmaster Cylinder. If you want to hear more episodes like this, subscribe to our master feed at changelog.com slash master or go into your podcast app

and search for Changelog Master. You'll find it. Subscribe, get all of our shows, as well as some extras. Only hit the master feed. It's one feed to rule them all. Again, changelog.com slash master. Thanks for tuning in. We'll see you next week. Thank you.