Open Source

I do a lot of work in the open, and you'll be able to find most of the code I write in my GitHub account (I've got more than 200 repositories at this point!).

However, I don't pay the same level of attention to all the repositories. Some of them are throwaway projects, and some are libraries I've been working on for years. You should be able to guess which is which by reading the README file and looking at the commit count/history. However, as a rule of thumb, if a repository is listed in my projects page without the "experimental" or "archived" tags, you can count on it being maintained.

Issues/PRs

If you find something that could be improved, or need help, please open an issue! Even if the repository doesn't look maintained, I'll be happy to at least give you an update on the status.

However, keep in mind that most of the work I do is opinionated. Which means that I'm not going to implement all the feature requests. Many times, I'll just add an "enhancement" badge and keep it open in case someone else wants to work on it. But unless something is a bug, I don't guarantee I'll tackle the request.

Still, feel free to open an issue and share your ideas! I should reply within a couple of weeks at most; but if I don't please ping me again. I've been known to miss github notifications before 😅. At the moment, the activity in my repositories is not too overwhelming, so you can expect to get a reply if you take the time to write an issue :).

You're also welcome to open PRs, but if you do please read the following section first.

Contributions

If you're thinking about contributing to one of my repositories, thank you!

Here's some guidelines you should keep in mind:

Open an issue before opening a PR

For any substantial feature, I strongly suggest that you open an issue validating your idea before you spend any time working on it. As I mentioned, most of my projects are opinionated, so I won't be accepting any feature even if it's technically correct.

We can use the issue to discuss the problem and the solution, and once we have agreed on the general direction of your contribution, you can go ahead and start working on the code.

Of course, for small fixes or typos you can go ahead and open a PR directly. But keep in mind that I may reject anything that I haven't approved previously.

AI contributions

In general, I'm ok with AI contributions, though I'd prefer it if you write the PR description yourself (AIs tend to be too verbose). Or if you include an AI summary of the task, please make it clear because I'll probably just skim it.

The code itself can also be AI-generated, as long as you're not infringing any copyright or stealing someone else's code (which can be hard to prove, I know). Ideally, you should include a Co-Authored-By line in your AI-assisted commits. In any case, your job when opening a PR is to contribute code that you have proven to work. If you're happy with the PR, and you're confident that it's good code that solves the problem you're trying to address, I don't mind if it was hand-written or AI-generated. Just avoid vibe-coded solutions where you haven't even looked at the code.

CONTRIBUTING.md

These are general rules for most of my projects, but some of them may have particular exceptions or things to note. If you're going to contribute to a repository, make sure to see if there is a CONTRIBUTING.md file with some additional comments.