jscheffl commented on code in PR #60744:
URL: https://github.com/apache/airflow/pull/60744#discussion_r2702530010


##########
COMMITTERS.rst:
##########
@@ -55,33 +55,43 @@ repositories, i.e., they can modify the code, 
documentation, and website by them
 accept other contributions. There is no strict protocol for becoming a 
committer. Candidates for new
 committers are typically people that are active contributors and community 
members.
 
-Some people might be active in several of those areas and while they might 
have not enough 'achievements' in any
+Some people might be active in several of those areas and while they might not 
have enough 'achievements' in any
 single one of those, their combined contributions in several areas all count.
 
 As a community, we appreciate contributions to the Airflow codebase, but we 
also place equal value
 on those who help Airflow by improving the community in some way. It is 
entirely possible to become
-a committer (and eventually a PMC member) without ever having to change a 
single line of code.
+a committer (and eventually a PMC member) without ever having to change a 
single line of code,
+though that requires visibility and presence in the regular community channels 
- slack, devlist, social
+media - this is important for the PMC to be aware of such activities. If PMC 
is not aware of those, they
+have no chance to spot and discuss such candidates.
+
+Guidelines from ASF are listed at ASF:
+`New Candidates for Committership 
<http://community.apache.org/newcommitter.html#guidelines-for-assessing-new-candidates-for-committership>`_
 
 
 Prerequisites
-^^^^^^^^^^^^^^
+^^^^^^^^^^^^^
 
 General prerequisites that we look for in all candidates:
 
-1.  Consistent contribution over last few months
+1.  Consistent contribution over at least three months
 2.  Visibility on discussions on the dev mailing list, Slack channels or 
GitHub issues/discussions
-3.  Contributions to community health and project's sustainability for the 
long-term
-4.  Understands contributor/committer guidelines: `Contributors' Guide 
<contributing-docs/README.rst>`__
+    including casting non-binding votes and testing RCs
+3.  Helping other contributors and users - with sharing their code 
contributor's experience and reviewing other's code

Review Comment:
   It means that it is not solely intended to drop code to be a committer but 
that you also engage reviewing others contributions. And providing constructive 
feedback that others can learn.
   It means you bring-in your expertise to help others to benefit the project.
   
   Do you have a proposal for wording in this?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to