Community checklists
Copy the one you need into your notes.
Contents
- Before posting a question
- Before filing a bug
- Before opening a pull request
- Before answering someone
- Before publishing an extension or theme
- Before running an event
Before posting a question
[ ] I searched the help, the documentation, eZpedia and the forums
[ ] I describe the goal, not only the error
[ ] Steps, expected and actual result, exact message
[ ] Environment from exp:info --plain or Copy report as text
[ ] No passwords, keys, server addresses or personal data
[ ] It is not a security problem (those go to [email protected])Page: Asking a good question.
Before filing a bug
[ ] It is reproducible on a current release or main
[ ] I searched the tracker; no existing issue
[ ] Right tracker: software / Velocity / extension / community
[ ] Title names the problem
[ ] Steps, expected, actual, environment, cleaned log lines
[ ] Nothing private in text or screenshotsPage: Filing a bug.
Before opening a pull request
[ ] One change only
[ ] make hooks installed; hooks pass
[ ] Commit message starts with Added: / Updated: / Fixed: / Removed: / Renamed:
[ ] share/filelist.md5 updated (make manifest-fix)
[ ] Tests added that fail without the change
[ ] Coding standards and naming prefixes followed; no inline styles in admin templates
[ ] Documentation updated if behavior changed
[ ] AI-assisted parts checked and mentioned
[ ] Signed CLA on file (kernel); checkbox tickedPage: Contributing code.
Before answering someone
[ ] I understand their goal
[ ] I know the answer, or I say that I am not sure
[ ] I link the source
[ ] I say which version I checked
[ ] No sales pitch
[ ] Security problem? Point to the private channel insteadPage: Answering questions.
Before publishing an extension or theme
[ ] No secrets, customer data or site-specific settings
[ ] LICENSE file (GPL 2 or later recommended)
[ ] ezinfo.php and extension.xml carry the same version
[ ] composer.json; Packagist package; webhook
[ ] README: what it does, supported versions, how to install
[ ] Tag chosen from what is published, sorted by version; never moved later
[ ] Listed on Projects; announced in the forumsPage: Sharing extensions and themes.
Before running an event
[ ] Announced as community-run, not "official"
[ ] Code of conduct linked; contact person named
[ ] Accessibility checked
[ ] Demo on a test installation with invented data
[ ] Consent for photos, recordings and published names
[ ] Only the attendee data needed; deleted afterwardsPage: Community safety and privacy.
Related pages
- Community: start here
- Advocate checklists
- Event checklists
- The release checklist
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.