Skip to main content

Join the Community

Apache Wayang is built in the open by researchers, engineers, and students from universities and companies around the world. Whether you want to ask a question, report a bug, share how you use Wayang, or write code, you are welcome here, and no contribution is too small.

You don't need to write code to contribute. Improving documentation, spreading the word on social media, giving talks, answering questions, and testing releases are all real contributions to Wayang, and they count just as much in the Apache way.

Join the dev@ mailing listWays to contributeBrowse open issuesContribution guide

Talk with us​

The dev@ mailing list is where the project lives: design discussions, release votes, and questions all happen there, in public and archived. The other channels are great for following the project and sharing news.

dev@ mailing list

Ask questions, propose ideas, introduce yourself, and take part in project decisions. To subscribe, send an empty email and reply to the confirmation.

Subscribe →Archive →

GitHub issues

Report a bug, request a feature, or find something to work on. Please search existing issues first.

Open issues →New issue →

Slack

Chat in real time in #wayang on the ASF Slack. Anyone with an @apache.org address can join directly; everyone else, send a short email to dev@ asking for an invitation.

Request an invitation →ASF Slack →

commits@ mailing list

Follow every commit, pull request, and issue update as it happens.

Subscribe →Archive →

Blog

Release announcements, technical deep dives, and stories from contributors and students.

Read the blog →

YouTube

Talks, demos, and tutorials about Wayang and cross-platform data processing.

@apachewayang →

LinkedIn

Project news, events, and updates from the community.

Apache Wayang →

Reddit

Informal discussion, links, and questions from users.

r/ApacheWayang →

X (Twitter)

Short announcements about releases, talks, and papers.

@apachewayang →

Every contribution counts, not just code​

Open source projects need much more than code to thrive. Pick whatever matches your skills and interests; most of these don't involve the codebase at all.

Documentation

Fix a typo, clarify a confusing guide, write a tutorial, or add an example. Good docs are often the most impactful contribution, and this website is open source too.

Website repo →

Social media

Share releases, blog posts, and your own Wayang experiments on LinkedIn, X, Reddit, or wherever your audience is. Helping others discover Wayang grows the community.

LinkedIn →X →

Talks and events

Present Wayang at a meetup, conference, lecture, or company tech talk. Let us know on dev@ so we can help spread the word.

Talks on YouTube →

Blog posts and articles

Write about how you use Wayang, a benchmark you ran, or a lesson learned. We are happy to publish posts on the Wayang blog or link to yours.

Our blog →Propose a post →

Help other users

Answer questions on the mailing list or in issues. Sharing what you know is one of the most valued contributions.

Mailing list guide →

Test and report

Try release candidates on your workloads, vote on dev@, and file clear bug reports or feature requests.

Downloads →New issue →

Students

Wayang takes part in programmes like Google Summer of Code and welcomes thesis projects. Read about past projects on the blog.

Student projects →

Code

Fix bugs, add operators, or support new platforms. The steps below walk you through your first pull request.

Add an operator →Optimizer →

Your first pull request​

If you want to change code or documentation, most contributors follow roughly these steps. You don't need permission to start, but saying hello first helps us point you in the right direction.

  1. 1

    Introduce yourself

    Send a short email to dev@wayang.apache.org saying who you are and what you are interested in. For larger changes, describe your plan there before you start coding so others can give early feedback.

  2. 2

    Set up your environment

    Fork apache/wayang, build it locally with the installation guide, and get familiar with the codebase through Developing in Wayang.

  3. 3

    Pick something to work on

    Choose an open issue, fix a bug you ran into, or improve the documentation. Comment on the issue so others know you are on it.

  4. 4

    Open a pull request

    Make sure the build and tests pass, then open a PR against main. Read the contribution guide and, if you use AI tools, our AI tooling policy.

  5. 5

    Iterate with reviewers

    A committer will review your PR. Address the comments, and once it is approved it gets merged. Welcome aboard!

Grow with the project​

Apache projects run on merit: people who contribute steadily earn more responsibility.

Become a committer

Committers have write access to the repositories. The PMC invites people with sustained contributions of any kind, including documentation, community building, and advocacy, not only code.

What we look for →

Join the PMC

The Project Management Committee oversees releases, votes on new committers, and keeps the project healthy. Active committers are invited over time.

Meet the team →ASF guidance →

Code of conduct

We follow the Apache Code of Conduct and expect respectful, inclusive behaviour in every channel.

Read it →Report a vulnerability →

Still have questions?​

Write to dev@wayang.apache.org. Messages from non-subscribers are held for moderation, so subscribing first gets your email through faster and makes sure you see the replies. For quick chats you can also ask on dev@ for an invitation to #wayang on the ASF Slack. If you aren't sure where something belongs, the mailing list is always the right place to ask.