I recently had to beef up the continuous deployment of Jupyter Book, and used
it as an opportunity to learn a bit more about CircleCI’s features. It turns out,
they’re pretty cool! Here are a few of the things that I learned this time around.
tl;dr: you can automatically mirror the contents of one repository to another by
using CI/CD services like CircleCI. This post shows you one way to do it using
secrets that let you push to a GitHub repository from a CircleCI process.
In the last couple of years, we’ve seen an increasing number of organizations start to
spawn products that take a largely open stack (e.g., the SciPy ecosystem) and wrap
it in a thin layer of proprietary/custom interface + infrastructure.
On the face of it, this isn’t a problem - I really want people to be able to
make money using the open source stack - however, there is a big caveat. When you look
at the work that those organizations have done over time, you often see a pretty thin trail
of contributions back to those open source projects.
I’ve had a bunch of conversations with friends who were interested in how to
keep track of the various projects they’re working on, and to prioritize their
time over the course of a week. I thought it might be helpful to post my own
approach to planning time throughout the week in case it’s useful for others to
riff off of.
How do open projects signal their “openness” to the outside community? This is
a really hard question, particularly because nowadays “open” has become a buzzword
that doesn’t just signal a project’s position to the community, but is also used
as a marketing term to increase support, users, or resources.
Recently I’ve been reading up on governance models for several large-ish open
source projects. This is partially because I’m involved in a bunch of
these projects myself, and partially because it’s fascinating to see distributed groups
of people organizing themselves in effective (or not) ways on the internet.