Community Features
MarketHub includes an integrated community hub where tenants discuss packages, publishers answer questions, and admins post announcements. Community participation is part of the reputation system — publishers earn points for accepted answers, creating a direct incentive for genuine engagement.
What the Community Hub Provides
Discussion Forums
Open, threaded discussions about packages and the marketplace ecosystem. Any logged-in user can post. Structured into sections so relevant conversation is easy to find.
Q&A System
Dedicated Q&A threads where the question author (or package publisher) can mark one reply as the accepted answer. Publishers earn +5 reputation points for accepted answers.
Announcements
Pinned, read-only posts from admins and publishers. Used for release notes, policy updates, and marketplace news. Subscribers are notified when new announcements are posted.
Moderation
A three-strike system with admin review queues ensures community quality. Users can report content; admins can warn, temporarily ban, or permanently ban offending accounts.
Access Model
| Action | Login Required? |
|---|---|
| Browse and read all threads | No — public read access without login |
| Post new threads | Yes — must be logged in |
| Reply to threads | Yes — must be logged in |
| Upvote posts | Yes — must be logged in |
| Mark accepted answer | Yes — question author or package publisher only |
| Post announcements | Yes — admins or the package publisher only |
| Report content | Yes — must be logged in |
| Subscribe to thread notifications | Yes — must be logged in |
Community and Reputation
The community hub is directly integrated with the reputation system. Publishers who actively participate and demonstrate helpfulness earn reputation points through the Q&A accepted answer mechanic (+5 pts per accepted answer). This creates a genuine incentive for publishers to stay engaged with their package's user community — not just as a support obligation, but as a reputation-building activity.
Every package has its own forum section. The publisher is the designated moderator of their package's forum — they can pin posts, remove off-topic content, and mark accepted answers on questions about their package. This gives publishers direct stewardship over the community conversation about their software.