Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Should the Code of Conduct be updated? (v1.4 to v3.0)

Aberta
#2,619 0 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
20/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Domínio
documentation

Direção de pesquisa

The file in question is CODE_OF_CONDUCT.md at the repository root, and the issue links the Contributor Covenant v3.0 text to replace the current v1.4 wording. Before editing, confirm with maintainers that the team agrees, since the issue asks for a team decision at a meeting and no comments show one. Done means the file carries the agreed text, which the maintainers must approve first.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Is your feature request related to a problem? Please describe.
I have the bad habit of writing wall of texts, as you already know. I'd like to be more concise by having numbered lists of items to link to in the Code of Conduct.

Current version is v1.4
Latest version is v3.0

Describe the solution you'd like
To update it, see https://www.contributor-covenant.org/version/3/0/code_of_conduct/.

Describe alternatives you've considered
Not to update it and bear with it (who knows for how long?!).

Additional context
Current version: https://www.contributor-covenant.org/version/1/4/code-of-conduct/
File in question: https://github.com/pvlib/pvlib-python/blob/main/CODE_OF_CONDUCT.md

Since it has new clauses, I think it deserves both discussion and ensuring all the team agrees on it. Deferring to a bi-monthly meeting is encouraged. Prior discussion on specifics can be done here. Feel free to weight in.

Linguagem predominante
Python
Estrelas
1.7k
Forks
1.2k
Merge médio
3d 18h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pvlib/pvlib-python

Todas as issues de pvlib/pvlib-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.