84 lines
		
	
	
		
			3.4 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			84 lines
		
	
	
		
			3.4 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
Code of Conduct
 | 
						||
 | 
						||
This Code of Conduct is derived from the 10 Pāramitās of Theravadin Buddhism.
 | 
						||
You can read more about them in Ṭhānissaro Bhikkhu’s Ten Perfections: A Study
 | 
						||
Guide [0].
 | 
						||
 | 
						||
1. Generosity (Dāna)
 | 
						||
 | 
						||
Give contributions freely and willingly under the terms of the GNU Affero
 | 
						||
General Public License, version 3 or later, or a compatible license.
 | 
						||
 | 
						||
2. Ethics (Sīla)
 | 
						||
 | 
						||
Do not use nonfree code or uncredited code in contributions. Do not contribute
 | 
						||
code of dubious origins, such as code generated by large language models or
 | 
						||
unlicensed snippets found online [1]. Do not take credit for others’
 | 
						||
contributions. Make sure to utilize the copyright header and license notice on
 | 
						||
source files to credit yourself and others for their work.
 | 
						||
 | 
						||
3. Renunciation (Nekkhamma)
 | 
						||
 | 
						||
Stay committed to the principles of simplicity and interoperability embodied by
 | 
						||
the project. Keep your personal will and desire out of the project, for it can
 | 
						||
only prove harmful to its success.
 | 
						||
 | 
						||
4. Wisdom (Pañña)
 | 
						||
 | 
						||
Look to established sources for standards, best practices, and important
 | 
						||
implementation details when setting new precedence. Follow the existing
 | 
						||
precedence where it applies.
 | 
						||
 | 
						||
5. Energy (Viriya)
 | 
						||
 | 
						||
Focus on the currently-open, currently-assigned, and currently-in-progress
 | 
						||
issues, pull requests, and other endeavors in order to keep yourself and others
 | 
						||
from being overwhelmed with responsibility, either from your zeal or your
 | 
						||
negligence.
 | 
						||
 | 
						||
If you notice an issue, open an issue as soon as you can. If you see a neglected
 | 
						||
branch, open a pull request or comment on an existing one, if applicable. Be
 | 
						||
diligent in your commitment to making this project work.
 | 
						||
 | 
						||
6. Patience (Khanti)
 | 
						||
 | 
						||
Be patient with maintainers and other contributors. We all have our own lives
 | 
						||
going on and may need significant time to get to things.
 | 
						||
 | 
						||
7. Truthfulness (Sacca)
 | 
						||
 | 
						||
Communicate honestly and openly. Do not embellish facts to get your way. Make
 | 
						||
sure to let maintainers know about any issues along the way and keep ample
 | 
						||
communication channels open.
 | 
						||
 | 
						||
8. Determination (Adhiṭṭhāna)
 | 
						||
 | 
						||
Stay focused on long-term objectives and cultivate attainment to that
 | 
						||
achievement by utilizing to the fullest extent possible the tools available to
 | 
						||
you for managing the workload.
 | 
						||
 | 
						||
9. Loving-Kindness (Mettā)
 | 
						||
 | 
						||
Treat everyone with respect, even if they treat you poorly. This does not mean
 | 
						||
you have to put up with abuse, but make sure to respond with kindness and with
 | 
						||
love in your heart. Support and uplift maintainers and other contributors with
 | 
						||
your words and actions.
 | 
						||
 | 
						||
Do not use angry or hateful language toward contributors, such as demeaning
 | 
						||
phrases and slurs. Make sure that if you do not know the pronouns of a
 | 
						||
contributor to ask for them and, in the meantime, use gender-neutral they/them
 | 
						||
or equivalent pronouns.
 | 
						||
 | 
						||
10. Equanimity (Upekkhā)
 | 
						||
 | 
						||
Keep a balanced perspective on all suggestions and contributions and make
 | 
						||
judgements not from a place of ego and personal preference but on their
 | 
						||
usefulness and suitability to the project. Make sure to keep an eye on the
 | 
						||
bigger picture as implementing individual features may seem intuitive at first
 | 
						||
but scale poorly in practical use. Keep a level head about your own work: it is
 | 
						||
not shameful to make a mistake in this vein, and fixing it usually leads to
 | 
						||
more insight.
 | 
						||
 | 
						||
[0] <https://www.dhammatalks.org/books/#/books/TenPerfections/Section0001.html>
 | 
						||
[1] <https://www.fsf.org/news/publication-of-the-fsf-funded-white-papers-on-questions-around-copilot>
 |