Known labels topics
Clarification: these are "topics" set on repository settings, not issue labels.
However, as of 2023, we are not actively using them, instead continuing to rely on the civicrm.org extension directory
- actionprovider
- activities
- cart
- cases
- civirules
- contributions
- dedupe
- emails
- events
- imports
- interface
- locations
- logs
- mobile
- paymentprocessors
- scheduledreminders
- search
- sms
- sync
- translation
- tokens
Partners:
- agileware
- agiliway
- civicoop
- coopsymbiotic
- ixiam
- jmaconsulting
- joineryhq
- megaphonetech
- mjwconsulting
- tadpole
- vedaconsulting
Suggestions:
- forms
- reports
- calendar (eventcalendar, calendar, activityscheduler)
- thirdpartyintegration (mailchimp, mautic, eventbrite)
- remotesiteintegration (formprocessor, dataprocessor, remoteform, inlay)'
- security (civiproxy, civihoneypot)
CMS-specific:
Label structure suggestions
These are somewhat arbitrary suggestions by @bgm. Feel free to discuss in the extensions channel.
- If it is related a components (events, memberships, cases, etc), use the plural form when it is something that is usually pluralized (many events, but only one cart).
- Always lowercase
- Avoid spaces (ex: scheduledreminders)
- Avoid tags very specific to one extension. Obviously this is very subjective, but say there is only one extension for "Jupiter Address Formatting", and it's the only extension for Jupiter, then the Jupiter tag might not be relevant. 'geolocation' would be a good tag. 'address'? hard to say, since people are unlikely to search by "address extensions", but more likely to search for "address formatting".
- Avoid combining tags into one, ex: avoid "mailingcleanup", use "mailings" and "cleanup" (or something more generic?)