Tools
Where the work happens. Everything below is public — you can read the code, the discussions, the build logs and the release votes without an account anywhere.
Code and issues
Everything is public. There is no private tracker and no internal fork.
GitHub
All source code lives in apache/hop, with the website in apache/hop-website. Contributions arrive as pull requests.
GitHub Issues
Bugs and feature requests. Read the GitHub guide first - a well-formed issue is much more likely to get picked up.
GitHub Discussions
Open-ended questions and ideas that are not yet a bug or a proposal, for people who would rather not use a mailing list.
Build and quality
Two systems, doing different jobs.
GitHub Actions
Runs on every pull request: it builds the code, builds the documentation, and handles the issue and milestone housekeeping.
Jenkins
ASF-hosted CI for the branch builds, the nightly build and the Hop Web Selenium suite. The website is published from here too.
SonarQube Cloud
Static analysis and coverage for the apache_hop project, tracked over time.
Talking to each other
Decisions are made on the mailing lists. Everything else is convenience.
Mailing lists
users@ for questions, dev@ for development and project decisions, commits@ for change notifications. The archives are public and searchable.
Slack
The #hop channel on the ASF Slack. An @apache.org address gets you in directly; otherwise ask for an invite on the users list.
LinkedIn
Release announcements, events and community news, and the easiest place to share Hop with colleagues.
Bluesky
Release announcements and project news from @hop.apache.org.
Documentation
Docs are code, and live beside the code.
The manuals
The user and developer manuals are AsciiDoc in the apache/hop repository, published once per release branch. A documentation change is an ordinary pull request.