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

[RFC] adopt contributor covenant v2 #4802

Merged
merged 1 commit into from
Sep 10, 2020

Conversation

achrinza
Copy link
Member

@achrinza achrinza commented Mar 6, 2020

This PR consists of 1 commit:

  • Adopt Contributor Covenant v2

    This is to steer the project to be more in-line with the expectations from the FOSS community, thereby increasing ease of adoption and contribution.

    Electron, AMP, nvm, Node-RED are examples of Node.js projects that adopt the Contributor Covenant.

Signed-off-by: Rifa Achrinza [email protected]

Checklist

👉 Read and sign the CLA (Contributor License Agreement) 👈

  • npm test passes on your machine
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • API Documentation in code was updated
  • Documentation in /docs/site was updated
  • Affected artifact templates in packages/cli were updated
  • Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

@achrinza achrinza added community-contribution Contributing Things making it easier and more pleasant to contribute to LoopBack labels Mar 6, 2020
@achrinza achrinza self-assigned this Mar 6, 2020
@achrinza achrinza mentioned this pull request Mar 6, 2020
2 tasks
@achrinza achrinza removed the 2019Q2 label Mar 6, 2020
@achrinza achrinza mentioned this pull request Mar 6, 2020
7 tasks
@bajtos
Copy link
Member

bajtos commented Mar 6, 2020

Thank you @achrinza for the pull request. I don't have strong opinions on details about which form of code of conduct to adopt. @dhmlau @raymondfeng what's your take? Are we ok to adopt "Contributor Covenant v2"? Do we need to get any IBM-internal approvals for this change?

@bajtos bajtos requested review from raymondfeng and dhmlau March 6, 2020 16:10
docs/CODE_OF_CONDUCT.md Outdated Show resolved Hide resolved
@@ -17,6 +17,9 @@ defer to the owners of each individual module; the powers of the individual
owner are kept in check by the ability of the community to fork and replace
dependencies on the individual module and maintainer.

The LoopBack project adopts the
[Contributor Covenant version 2](CODE_OF_CONDUCT.md).
Copy link
Member

Choose a reason for hiding this comment

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

I think we will need to update the documentation in http://loopback.io/doc/en/contrib/index.html too.

@bajtos bajtos added the Docs label Mar 6, 2020
achrinza added a commit to achrinzafork/loopback-next that referenced this pull request Mar 13, 2020
This is to steer the project to be more in-line with the expectations from the FOSS community, thereby increasing ease of adoption and contribution.

Signed-off-by: Rifa Achrinza <[email protected]>

chore: apply @bajtos' feedback

replace naked email with a `mailto` link.

see loopbackio#4802 (comment)

Signed-off-by: Rifa Achrinza <[email protected]>
@emonddr
Copy link
Contributor

emonddr commented Mar 26, 2020

@raymondfeng , @dhmlau , your opinion on this? thanks. :)

@dhmlau
Copy link
Member

dhmlau commented Mar 29, 2020

I need to find out what's the implications and recommendation from the IBM open source side. Will circle back.

@dhmlau
Copy link
Member

dhmlau commented Aug 19, 2020

We just switch the contribution method from CLA to DCO, making your contribution easier in the future. Please sign the commits with DCO by amending your commit messages with -s flag and push the changes again. If you're using the command line, you can:

git commit --amend -s
git push --force-with-lease

Please refer to this docs page for details. Thanks!

@achrinza
Copy link
Member Author

@dhmlau Any updates on your front? This PR is ready to go, just needs approval 😀

Copy link
Member

@bajtos bajtos left a comment

Choose a reason for hiding this comment

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

LGTM as far as I am concerned. Please wait for an approval from @dhmlau and @raymondfeng before landing.

Thank you @achrinza for initiating this change!

@achrinza achrinza marked this pull request as ready for review September 8, 2020 17:46
achrinza added a commit to achrinzafork/loopback-next that referenced this pull request Sep 9, 2020
This is to steer the project to be more in-line with the expectations from the FOSS community, thereby increasing ease of adoption and contribution.

Signed-off-by: Rifa Achrinza <[email protected]>

chore: apply @bajtos' feedback

replace naked email with a `mailto` link.

see loopbackio#4802 (comment)

Signed-off-by: Rifa Achrinza <[email protected]>
@dhmlau
Copy link
Member

dhmlau commented Sep 10, 2020

@achrinza, could you please take a look at the commit linter issue? Thanks.

✖   body's lines must not be longer than 100 characters [body-max-line-length]

This is to steer the project to be more in-line with the expectations
from the FOSS community, thereby increasing ease of adoption and
contribution.

Signed-off-by: Rifa Achrinza <[email protected]>
@bajtos bajtos merged commit 70eceb6 into loopbackio:master Sep 10, 2020
@bajtos
Copy link
Member

bajtos commented Sep 10, 2020

Landed, thank you @achrinza again!

Can you please take a look at the contrib docs on loopback.io (start with http://loopback.io/doc/en/contrib/index.html) and check what needs to be updated too?

I think we should add a link to CODE OF CONDUCT to Governance Principles - see https://loopback.io/doc/en/contrib/Governance.html#principles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contributing Things making it easier and more pleasant to contribute to LoopBack Docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants