Skip to main content

Get involved

Contribute code, docs, ideas, and feedback to Apache StreamPipes

A practical path from first contact to first contribution

Contributing

StreamPipes grows through community contributions. You do not need to start with a large feature or a major architectural change. Bug reports, documentation improvements, testing, UI refinements, example updates, and small code fixes all help move the project forward.

Start with a discussion

If you want feedback on an idea, need product context, or want to understand whether work is already in progress, start with the community channels before opening a larger pull request.

The best places are the mailing lists and GitHub Discussions.

Pick an issue or report one

Contributions often begin with an issue. You can report bugs, propose improvements, or look for an existing task that matches your area of interest.

Browse the issue tracker at github.com/apache/streampipes/issues.

Open a pull request

Once you have a concrete change, open a pull request against the relevant repository and describe the motivation, scope, and any follow-up work clearly.

Smaller, focused pull requests are usually easier to review and integrate than broad, multi-topic changes.

Typical contribution flow

A good default workflow is to discuss the change briefly, align on scope, implement the update in the correct repository, and then open a focused pull request with enough context for reviewers. This keeps review cycles short and makes it easier for the community to help you quickly.

Choose the right place depending on the type of contribution

Community Channels

Mailing lists

Use the project mailing lists for design discussions, contributor questions, and community-visible decisions that should be easy to reference later.

Open mailing lists

GitHub Discussions

GitHub Discussions are a good entry point for questions, ideas, and early feedback when you want a lower-friction conversation around a possible contribution.

Open discussions

GitHub Issues

Use issues for actionable bugs, feature requests, and work items that should be tracked explicitly in the project backlog.

Browse issues
The main repositories for code, documentation, and examples

Source Code

RepositoryWhat it containsLink
streampipesCore platform, extension services, backend components, and the main UI application.Open repository
streampipes-websiteWebsite, product pages, and user and developer documentation.Open repository
streampipes-examplesExample projects, sample extensions, and reference material for contributors.Open repository