https://github.com/loopbackio/loopback-governance

A place for discussing "meta" topics around LoopBack project governance and team management
https://github.com/loopbackio/loopback-governance

Last synced: 4 months ago
JSON representation

A place for discussing "meta" topics around LoopBack project governance and team management

• Host: GitHub
• URL: https://github.com/loopbackio/loopback-governance
• Owner: loopbackio
• License: other
• Created: 2020-02-25T15:35:53.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2023-12-15T02:51:48.000Z (about 2 years ago)
• Last Synced: 2025-01-03T22:30:28.456Z (about 1 year ago)
• Size: 43 KB
• Stars: 0
• Watchers: 23
• Forks: 0
• Open Issues: 23
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md
  • Codeowners: CODEOWNERS

Awesome Lists containing this project

README

          
# loopback-governance

A place for discussing "meta" topics around LoopBack project governance and team

management.

There are [Technical Steering Committee](https://github.com/loopbackio/loopback-next#technical-steering-committee) and [project maintainers](https://github.com/loopbackio/loopback-next#other-project-maintainers) maintaining this project.

## How to work in this repo

1. Check the existing open issues for discussions in progress.

   Post a comment to join.

2. Open a new issue to start a new discussion.

3. Open a pull request to capture outcome of a discussion in a markdown file.

   Allow at least 3 business days for other maintainers to review the proposal

   before landing.

## Code of conduct

See LoopBack's [Governance

Principles](https://loopback.io/doc/en/contrib/Governance.html#principles):

> LoopBack is an open, inclusive, and tolerant community of people working

> together to build a world-class Node framework and tools. We value diversity

> of individuals and opinions, and seek to operate on consensus whenever

> possible. We strive to maintain a welcoming, inclusive, and harassment-free

> environment, regardless of the form of communication. When consensus is not

> achievable, we 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.