Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/boomerang-io/community

The Boomerang community, roadmap, planning, and architecture repository. The central place for information on joining, contributing, and governance.
https://github.com/boomerang-io/community

automation boomerang community no-code planning roadmap

Last synced: 1 day ago
JSON representation

The Boomerang community, roadmap, planning, and architecture repository. The central place for information on joining, contributing, and governance.

Awesome Lists containing this project

README 

        
# :wave: Welcome to the Boomerang community



Boomerang is a collection of open source, cloud-native projects for CI/CD and automation. You can learn more [here](https://useboomerang.io)



This is the community, roadmap, planning, and architecture repository. Where you can find information on:



- joining and contributing to the community

- governance

- roadmap and releases.

- architecture (including decisions)



## Roadmap and Planning



Take a look at our high-level [roadmap](ROADMAP.md)



We use [GitHub Issues Projects](https://github.com/features/issues) for our release management, if you want to take a look at the active release or the roadmap:



- [Boomerang Flow GitHub Issues Project](https://github.com/orgs/boomerang-io/projects/4/views/1)

- [Boomerang Bosun GitHub Issues Project](https://github.com/orgs/boomerang-io/projects/5)



## Governance



The following documentation will help guide us all as we strive to create a community working together to build open source tools.



- [Maintainers](https://github.com/boomerang-io/roadmap/blob/main/MAINTAINERS.md)

- [Code of Conduct](https://github.com/boomerang-io/roadmap/blob/main/CODE_OF_CONDUCT.md)



### Community Meeting



A community meeting will be held every four weeks on Wednesday at 3:30pm US Central Timezone for 30 minutes.



- [Agenda](https://docs.google.com/document/d/1298K1t36f5jl9VwEipp3KHgmdj-vRHHA5YlnMaS2n0A/edit?usp=sharing)

- [Google Meet](https://meet.google.com/thh-dpwr-ynv)

- [Add to Calendar](https://calendar.google.com/event?action=TEMPLATE&tmeid=NHNzZmVpaDRxdGh0MTM5MjQ1aGUzdDhoY3ZfMjAyMTA3MTNUMjAwMDAwWiB0eXNvbkBsYXdyaWUuY29tLmF1&tmsrc=tyson%40lawrie.com.au&scp=ALL)



> To get access to this meeting and the agenda, please [join the Boomerang IO google group](https://groups.google.com/g/boomerang-io)



## Documentation & Presentations



- [Docs](https://www.useboomerang.io/docs/boomerang-flow/introduction/overview)

- [Presentation](https://docs.google.com/presentation/d/1id1qePshOm3YRbLay47Ny6WvkrbxIOHEJtVXsM8PmGI/edit?usp=sharing)

- [YouTube](https://youtu.be/erBEQdBHFJU)



## Want to get involved?



We welcome all contributions to the project and you can reach out to us via [slack](https://join.slack.com/t/boomerang-io/shared_invite/zt-pxo2yw2o-c3~6YvWkKNrKIwhIBAKhaw) or through GitHub.



### How to Contribute



Like any good development project, we use Pull Requests (PRs) to track code changes. We recommend that if you want to contrubute and implement a fix, change, or enhancement, you do so by linking the PR with an Issue.



Typically this is achieved by forking the repository and create a PR to be able to link this to the parent repository and request a merge.



### GitHub Issue Types



There are 5 types of issues that we have added to the issue templates. Epic and Task are generally reserved for the active development team and related to implementing a Change or Enhancemnet



| Type                     | Purpose                                                                    |

| ------------------------ | -------------------------------------------------------------------------- |

| 🐛 Bug Report            | Create a report to help us improve if something isn't working as expected. |

| ✨ Change or Enhancement | A change or improvement suggestion.                                        |

| 💬 Support or Inquiry    | When help is needed or to track questions.                                 |

| 🚀 Epic                  | A theme of work that is required to complete the larger goal               |

| 🔨 Task                  | Steps to implement a feature                                               |



### Commit Messages



The commit message should state the change in 72 characters or less. Additionally we recommend, and require in some repositories, the usage of a commit lint and conventional commit so that we can map these to Release Notes.