🐝 Let's make it easier for contributors!





Subscribe to our newsletter

By subscribing, you agree with Revue’s Terms of Service and Privacy Policy and understand that Adrien Joly will receive your email address.


Adrien Joly

June 22 · Issue #32 · View online

Every week, I share a side-project I made in 1 day.

This week I spent a lot of time communicating about my product for teachers, but that’s not the topic I want to talk about today.
It’s also been a week of transition. A transition from a “let me handle this” posture, towards a “you can do it, it’s easy!” posture. In other words, I’m learning how to let go and delegate tasks.
But, in order to maintain a consistent level of quality, I need to explain how I do things, why I do them, and provide tools or examples to help people contribute with ease and confidence!
So far, I’ve been applying this transition on two topics:

1. Communication of Openwhyd
I’m very happy to get help from Claire and Constance, for Openwhyd’s external communication! In fact, Claire just wrote a first article that is going to be relayed by OpenCollective, about our mission to crowdfund the future of our platform, and she did a great job! More about that soon.
As I told Claire, it’s important that Openwhyd’s communication is not only tied to my name. Openwhyd is a community project, so I want to empower volunteers to have their say, and to put their face on it. My hope is that coordinating efforts becomes my only duty. And, of course, making sure that Openwhyd keeps going in the right direction.
If you want to be involved, please let me know!
By the way, I’m looking for some legal advice, if you know anyone who would like to help.
2. Code contributions to Openwhyd
Today, I spent some time trying to standardise the automated tests that I wrote for the multi-platform track player at the core of Openwhyd: PlayemJS.
My goal is to increase the sustainability of Openwhyd, by making sure that tracks from all supported platforms (Youtube, Soundcloud, Deezer, Bandcamp, Vimeo…) keep working as expected. Therefore, it must be easy for volunteers to fix bugs. And, most importantly, to not add new bugs accidentally, when contributing to its codebase. (Hence the tests.)
So I played a few hours with Webdriver.io, to see how I could integrate it with PlayemJS’ custom test driver. If you have any advice on this topic, I’d be really interested to chat!
That’s it for today!
Tomorrow I’m leaving for a 4-day break with friends, so talk to you soon!
Have a great week end!
Did you enjoy this issue?
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue