<commit_before># Contributing to Vimium

## Reporting a bug

File the issue [here](https://github.com/philc/vimium/issues).

## Contributing code

You'd like to fix a bug or implement a feature? Great! Before getting started, understand Vimium's design
principles and the goals of the maintainers.

### Vimium design principles

When people first start using Vimium, it provides an incredibly powerful workflow improvement and it makes
them feel awesome. Surprisingly, Vimium is applicable to a huge, broad population of people, not just users of
Vim.

In addition to power, a secondary goal of Vimium is approachability: minimizing the barriers which prevent a
new user from feeling awesome. Many of Vimium's users haven't used Vim before -- about 1 in 5 Chrome Store
reviews say this -- and most people have strong web browsing habits forged from years of browsing. Given that,
it's a great experience when Vimium feels like a natural addition to Chrome which augments, but doesn't break,
the user's current browsing habits.

**Principles:**

1. **Easy to understand**. Even if you're not very familiar with Vim. The Vimium video shows you all you need
   to know to start using Vimium and feel awesome.
2. **Reliable**. The core feature set works on most sites on the web.
3. **Immediately useful**. Vimium doesn't require any configuration or doc-reading before it's useful. Just
   watch the video or hit `?`. You can transition into using Vimium piecemeal; you don't need to jump in
   whole-hog from the start.
4. **Feels native**. Vimium doesn't drastically change the way Chrome looks or behaves.
5. **Simple**. The core feature set isn't overwhelming. This principle is particularly vulnerable as we add to
   Vimium, so it requires our active effort to maintain this simplicity.
6. **Code simplicity**. Developers find the Vimium codebase relatively simple and easy to jump into. This
   provides us an active dev community.

### Which pull requests get merged?

**Goals of the maintainers**

The maintainers of Vimium are @smblott-github and @philc. We have limited bandwidth, which influences which
PRs we can review and merge.

Our goals are generally to keep Vimium small, maintainable, and really nail the broad appeal use cases. This
is in contrast to adding and maintaining an increasing number of complex or niche features. We recommend those
live in forked repos rather than the mainline Vimium repo.

PRs we'll likely merge:

* Reflect all of the Vimium design principles.
* Are useful for lots of Vimium users.
* Have simple implementations (straightforward code, few lines of code).

PRs we likely won't:

* Violate one or more of our design principles.
* Are niche.
* Have complex implementations -- more code than they're worth.
<commit_msg>Update maintainer list<commit_after># Contributing to Vimium

## Reporting a bug

File the issue [here](https://github.com/philc/vimium/issues).

## Contributing code

You'd like to fix a bug or implement a feature? Great! Before getting started, understand Vimium's design
principles and the goals of the maintainers.

### Vimium design principles

When people first start using Vimium, it provides an incredibly powerful workflow improvement and it makes
them feel awesome. Surprisingly, Vimium is applicable to a huge, broad population of people, not just users of
Vim.

In addition to power, a secondary goal of Vimium is approachability: minimizing the barriers which prevent a
new user from feeling awesome. Many of Vimium's users haven't used Vim before -- about 1 in 5 Chrome Store
reviews say this -- and most people have strong web browsing habits forged from years of browsing. Given that,
it's a great experience when Vimium feels like a natural addition to Chrome which augments, but doesn't break,
the user's current browsing habits.

**Principles:**

1. **Easy to understand**. Even if you're not very familiar with Vim. The Vimium video shows you all you need
   to know to start using Vimium and feel awesome.
2. **Reliable**. The core feature set works on most sites on the web.
3. **Immediately useful**. Vimium doesn't require any configuration or doc-reading before it's useful. Just
   watch the video or hit `?`. You can transition into using Vimium piecemeal; you don't need to jump in
   whole-hog from the start.
4. **Feels native**. Vimium doesn't drastically change the way Chrome looks or behaves.
5. **Simple**. The core feature set isn't overwhelming. This principle is particularly vulnerable as we add to
   Vimium, so it requires our active effort to maintain this simplicity.
6. **Code simplicity**. Developers find the Vimium codebase relatively simple and easy to jump into. This
   provides us an active dev community.

### Which pull requests get merged?

**Goals of the maintainers**

The maintainers of Vimium have limited bandwidth, which influences which PRs we can review and merge.

Our goals are generally to keep Vimium small, maintainable, and really nail the broad appeal use cases. This
is in contrast to adding and maintaining an increasing number of complex or niche features. We recommend those
live in forked repos rather than the mainline Vimium repo.

PRs we'll likely merge:

* Reflect all of the Vimium design principles.
* Are useful for lots of Vimium users.
* Have simple implementations (straightforward code, few lines of code).

PRs we likely won't:

* Violate one or more of our design principles.
* Are niche.
* Have complex implementations -- more code than they're worth.

{'fraction_non_alphanumeric': 0.056665455866327645, 'fraction_numerical': 0.002905920813657828, 'mean_word_length': 4.305394990366088, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4176273', 'n_tokens_mistral': 1465, 'n_tokens_neox': 1380, 'n_words': 835}