https://github.com/vlingo/vlingo-community
Guidelines and useful documentation about internal vlingo development
https://github.com/vlingo/vlingo-community
community guidelines vlingo
Last synced: 8 months ago
JSON representation
Guidelines and useful documentation about internal vlingo development
- Host: GitHub
- URL: https://github.com/vlingo/vlingo-community
- Owner: vlingo
- Created: 2019-01-06T22:21:12.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2019-11-15T10:41:00.000Z (almost 6 years ago)
- Last Synced: 2025-01-18T12:21:30.871Z (10 months ago)
- Topics: community, guidelines, vlingo
- Homepage: https://vlingo.io
- Size: 11.7 KB
- Stars: 6
- Watchers: 10
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# vlingo-community
[](https://gitter.im/vlingo-platform-java/)
:warning: __Work in progress__ :warning:
## Vision
The vlingo/platform is the Domain-Driven Design friendly open source distributed computing platform simplifying reactive, event-driven, microservices architectures.
We aggressively advance software developer DDD and Reactive capabilities to help deliver excellent software solutions. We are committed to balancing the right technology choices with your essential and unique business vision. We champion simplicity, which requires special discipline and determination.
## Governance
The vlingo/platform is an inclusive open source project lead by [Vaughn Vernon][vernon-gh], who provides long-term vision, architecture, and development. Each component has at least one _responsible champion_. The component champion is responsible for:
- Mentoring newcomers
- Ensuring that new features match the project vision
- Takeing into account what the team is capable of delivering
- Reviewing Pull Requests and checking whether or not new contributions meet the _Definition of Done_
We recognize and value everyone's contribution and time spent. We want our shared development efforts to be pleasant and productive. The following information will help you do that.
### How to become a contributor
We want you the add value, and know you have value to contribute. Share what you are interest in by implement a new feature or fixing one or more bugs.
[Check the contributor resources](#contributor-resources)
### How to become a maintainer
A maintainer is someone who has shown commitment over a long period of time. A maintainer is granted such as a merit of her/his contributions.
### Reasons to remove a contributor/maintainer
1. Break the [Code of Conduct][coc]
TLDR: __Be kind with everybody__ :smile:
## Contributor resources
- [Development][development]: Code guidelines, developing new feature requirements, Pull Request guidelines.
- [Documentation][documentation]: Helping others find the knowledge. Create guides, source code examples, tutorials, or writing component documentation [docs.vlingo.io][official-docs] and making knowledge more accessible.
- [Automation / CI][automation]: Documenting the CI process. How to release vlingo/platform components.
- [Meetups/Workshops][meetups]: Resources to spread the vlingo/platform joy! :loudspeaker:
## Communication
We aim to keep most of our communication in the public GitHub threads.
[development]: development/README.md
[documentation]: documentation/README.md
[automation]: automation/README.md
[meetups]: meetups/README.md
[official-docs]: https://docs.vlingo.io
[vernon-gh]: https://github.com/VaughnVernon
[coc]: CODE_OF_CONDUCT.md