zkaoudi opened a new pull request, #135: URL: https://github.com/apache/wayang-website/pull/135
## Summary Cleans up the community section of the website: removes leftovers from the incubator period and from the Apache Spark guides these pages were adapted from, replaces Jira with GitHub issues, and makes clear that non-code contributions count, both for contributing and for becoming a committer. ## Changes **How to contribute** - Replace Jira with GitHub issues throughout (reporting bugs, triage, linking PRs with `Fixes #123`, draft PRs instead of `[WIP]` titles). - New section **Contributing by spreading the word**: talks, blog posts, social media, teaching, sharing use cases. - Remove Spark leftovers (SQL/Catalyst, R style guide, `wayang-packages.org`, the non-existent user@ list and StackOverflow) and the "Contributing user libraries" section. - Fix factual errors: Java code style is the Google Java Style Guide (the build runs Checkstyle with `google_checks.xml`), not Oracle's; drop the inherited Python line-length exception; resolve the contradiction about ML algorithms vs. ML4ALL. - Use `main` and post-graduation repository URLs, add the build command, note `--force-with-lease` after rebasing, link the AI tooling policy, fix a broken list/code block and heading levels. - State the review policy: one committer approval for small changes, two recommended for larger ones. **Becoming a committer** - Emphasise that committership is about commitment and sustained engagement with the project, not only code, and list the kinds of contributions the PMC considers. - Add "What is expected of a committer" and a separate "Becoming a PMC member" section. - Replace "(P)PMC" with "PMC", remove Spark references, use `main`, fix typos and formatting. - Align the review policy with the contribution guide (one approval for small changes, two recommended for larger ones). **Repositories** - Point to `apache/wayang` and `apache/wayang-website` instead of the incubator repositories. - Report issues on GitHub instead of Jira. - Restructure the page as a table with GitHub and GitBox links, a clone command, and links to the build and contribution guides. **Navigation** - Remove the Community Resources page (it had a single external link and outdated references). - Turn the **Community** navbar dropdown into a direct link to the community docs, since only one entry would remain. - Move **Blog** into the community sidebar, after Repositories. - Reorder the sidebar: How to contribute before Becoming a committer; Maturity Model right before Wayang Security. ## Testing - `npm run build` succeeds with `onBrokenLinks: 'throw'`, so all internal links resolve. - Checked the affected pages locally. - Also verified that this branch merges cleanly with the Join the Community PR and that the combined site builds. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
