Earning points through community work
This page is for partners who want to grow their level by helping the community, not only by selling. The program names "Knowledge Sharing" and "Program Activities" as point sources next to revenue (https://exponential.earth/partner/requirements, read 18 October 2026):
- "Write technical articles, tutorials, wiki article documentation or documentation."
- "Participate in forums or community support."
- "Speak at conferences or contribute to open-source extensions."
- "Join campaigns, feedback sessions, or events."
- "Help test marketing materials or participate in bug hunts."
- "New ideas or impactful activities not listed? Let us know—we'll evaluate and reward on a case-by-case basis."
Activities, points and a quality bar
| Activity | Published points | Quality bar | Where |
|---|---|---|---|
| Bug report | 50 | Reproducible steps, version, expected and actual result | Filing bugs well |
| Forum post | 10 | Answers a real question; no advertising | https://share.exponential.earth/forums |
| Tutorial (1,500+ words) | 500 | Tested on a current 6.0.x install; screenshots; FLOSS license | Contributing documentation and translations |
| Article (500–1,500 words, FLOSS-licensed) | 500 | Sources named; no invented figures | Writing a case study |
| Conference presentation | 500 | Slides published under a free license | Press releases and announcements |
| Contribution to open source extensions | Case by case | Merged pull request | Contributing extensions back upstream |
| Translations | Not listed; ask ("case-by-case") | Complete catalogue sections, reviewed | Contributing documentation and translations |
| Code to the kernel | Not listed; ask | Pull request that passes CI | Contributing code back |
Why community work matters more than its points
A forum answer is worth 10 points, but it may save a hundred people an hour each. The program's values are Open, Sharing and Innovative (https://exponential.earth/partner/program); community work is where a partner shows them in public. It also builds your reputation where future customers and employees look: in the forums, in the Git history and in the documentation.
A quarterly plan
Quarter: ______ Owner: ______________
Bug reports (aim 3) ............ links: ______________________
Forum answers (aim 15) ......... links: ______________________
One tutorial or article ........ title: ______________________
One contribution (code/docs/translation) ... PR: _____________
Event or talk (optional) ....... name: _______________________
Reported to the partner team on: ____/____/______Rules of thumb
- Publish under a free license. The program asks for FLOSS-licensed articles; the project's documentation is GFDL 1.3 or later and its code GPL v2 or later (Licensing for partners).
- Write as yourself or your company, never as 7x or the Foundation.
- Link to the help and the official sources instead of copying them without attribution (Free documentation).
- Report the activity in the same month (Logging your partner activity).
Related pages
- The points system
- Open source values in daily partner work
- Supporters: start here
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.