RFR: Update committer description

[Alexey Ivanov]

On Fri, 3 Jun 2022 08:58:39 GMT, Jesper Wilhelmsson <jwilhelm at openjdk.org> wrote:

> Clarified that the number of commits in the project isn't everything that counts.

src/guide/introduction.md line 44:

> 42: ### Becoming a Committer
> 43: 
> 44: To become a [Committer](https://openjdk.java.net/bylaws#committer) you should show that you are a good citizen of the project and that you can produce non-trivial changes that are accepted for inclusion into the project code base. The number eight has been seen as a formal lower limit on the number of changes, but since the changes must be non-trivial, or "significant" as the [OpenJDK Project description](https://openjdk.java.net/projects/) says, and the definition of significant is subjective, the general recommendation is to wait with a Committer nomination until there's at least 10-12 changes pushed to have some margin for different interpretations of "significant". In practice though, we have seen several examples where the number of significant changes hasn't been the dominating factor in a Committer vote. A contributor's work in another OpenJDK project may also be relevant for the vote. What the vote should ultimately test is the committers commitment to the OpenJDK proje
 ct for which the vote applies - is it believed that the person is dedicated and willing to spend time and effort on the project? Is the person believed to be a good citizen of the project? It's always a good idea to seek the advice of a sponsor who can guide you through the process to becoming a Committer - you will need one to run the Committer vote anyway. They will probably also have a better idea of what constitutes a "significant" change.

…the _committer's commitment_ to the OpenJDK project…? With the apostrophe?

-------------

PR: https://git.openjdk.java.net/guide/pull/88