Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readme: add PyPA CoC #11

Merged
merged 1 commit into from
Jun 20, 2020
Merged

readme: add PyPA CoC #11

merged 1 commit into from
Jun 20, 2020

Conversation

FFY00
Copy link
Member

@FFY00 FFY00 commented Jun 10, 2020

Signed-off-by: Filipe Laíns lains@archlinux.org

@FFY00 FFY00 mentioned this pull request Jun 10, 2020
@codecov
Copy link

codecov bot commented Jun 10, 2020

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines          228       228           
=========================================
  Hits           228       228           

@gaborbernat
Copy link
Contributor

IMHO merge this.

@FFY00
Copy link
Member Author

FFY00 commented Jun 15, 2020

I wanted to wait for confirmation the repo is gonna be moved to PyPA.

Signed-off-by: Filipe Laíns <lains@archlinux.org>
Copy link
Contributor

@gaborbernat gaborbernat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adopting a code of conduct is acceptable even before moving it under PyPa. So I'll go ahead with this, we can always alter it if things change, though I'm not expecting that to happen. IMHO the only reason why we are not under pypa, for now, is that the project needs some improvements.

@FFY00
Copy link
Member Author

FFY00 commented Jun 20, 2020

@gaborbernat next time please get the opinion of at least one other maintainer when merging a change someone is arguing against.

In this case, there is no problem. Your argument makes sense, and I did not have strong feelings anyway. But that could not be the case.

Over my other open source work, I found this helps avoiding conflict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants