Skip to content
Snippets Groups Projects

docs/customize/extensions.md - Copy-edits re: available extensions

Merged totten requested to merge totten/sysadmin:master-exts into master
4 unresolved threads

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
21 civicrm.org/extensions](https://civicrm.org/extensions) This is the main directory for extensions. We encourage all people publishing extensions to do so here. The extensions can be at any state of development including experimental, and they may be for a particular CMS. There will be a link to download the latest version, and to the source code (repository).
22 - Elsewhere. Of course people are free to put their own code wherever they like.
23 - CiviCRM's GitLab at <https://lab.civicrm.org/extensions> This is the
24 preferred home for extensions, and if developers create extension on civicrm.org, the extension will be added to the public extensions directory and a repository will be set up on lab.civicrm.org/extensions automatically. Generally, extensions here will probably be on the main directory already.
25 - GitHub, Codeberg, GitLab and other such open source software hosts.
8 !!! note "More information about CiviCRM extensions"
9 To find out about **developing** CiviCRM extensions, see [Developer Guide: Writing Extensions](https://docs.civicrm.org/dev/en/latest/extensions/).
10
11 ## Where do extensions come from?
12
13 Extensions come from various sources:
14
15 - __CiviCRM Core__: The official release of CiviCRM includes several "core extensions". These are always available.
16 - __[CiviCRM Extension Directory](https://civicrm.org/extensions)__: Members of the CiviCRM community may list
17 extensions on the public directory. After a [general peer review](https://docs.civicrm.org/dev/en/latest/extensions/lifecycle/),
18 these become available for in-app download.
  • Comment on lines +16 to +18

    I think it's confusing to link to the public c.o/ext page here where you talk about in-app download because the latter is a subset of the former.

    I think this bullet would be clearer saying something like: Other extensions available in-app from the Administer » System Settings » Extensions screen. The extensions on this screen are a subset of community-provided extensions listed on civicrm.org that have been peer reviewed and are compatible with your particular CiviCRM and CMS.

  • I don't think we should remove 'in-app' from the list the sources. That feels like a more logical flow of where users would look for extensions.

  • Please register or sign in to reply
  • Rich
    Rich @artfulrobot started a thread on the diff
  • 23 - CiviCRM's GitLab at <https://lab.civicrm.org/extensions> This is the
    24 preferred home for extensions, and if developers create extension on civicrm.org, the extension will be added to the public extensions directory and a repository will be set up on lab.civicrm.org/extensions automatically. Generally, extensions here will probably be on the main directory already.
    25 - GitHub, Codeberg, GitLab and other such open source software hosts.
    8 !!! note "More information about CiviCRM extensions"
    9 To find out about **developing** CiviCRM extensions, see [Developer Guide: Writing Extensions](https://docs.civicrm.org/dev/en/latest/extensions/).
    10
    11 ## Where do extensions come from?
    12
    13 Extensions come from various sources:
    14
    15 - __CiviCRM Core__: The official release of CiviCRM includes several "core extensions". These are always available.
    16 - __[CiviCRM Extension Directory](https://civicrm.org/extensions)__: Members of the CiviCRM community may list
    17 extensions on the public directory. After a [general peer review](https://docs.civicrm.org/dev/en/latest/extensions/lifecycle/),
    18 these become available for in-app download.
    19 - __Other Sources__: Administrators may manually add extensions from other sources. This may include:
    20 - New (*un-reviewed or un-released*) items from the [Extension Directory](https://civicrm.org/extensions).
    • New is a misnomer. I have dozens (?) of extensions listed there that are years old that are un-reviewed.

    • Author Owner

      "Other Sources: ... This may include..." ==> The list doesn't need to be exhaustive -- merely demonstrative/representative.

    • Please register or sign in to reply
  • Rich
    Rich @artfulrobot started a thread on the diff
  • 25 - GitHub, Codeberg, GitLab and other such open source software hosts.
    8 !!! note "More information about CiviCRM extensions"
    9 To find out about **developing** CiviCRM extensions, see [Developer Guide: Writing Extensions](https://docs.civicrm.org/dev/en/latest/extensions/).
    10
    11 ## Where do extensions come from?
    12
    13 Extensions come from various sources:
    14
    15 - __CiviCRM Core__: The official release of CiviCRM includes several "core extensions". These are always available.
    16 - __[CiviCRM Extension Directory](https://civicrm.org/extensions)__: Members of the CiviCRM community may list
    17 extensions on the public directory. After a [general peer review](https://docs.civicrm.org/dev/en/latest/extensions/lifecycle/),
    18 these become available for in-app download.
    19 - __Other Sources__: Administrators may manually add extensions from other sources. This may include:
    20 - New (*un-reviewed or un-released*) items from the [Extension Directory](https://civicrm.org/extensions).
    21 - Extensions from <https://lab.civicrm.org/extensions>
    22 - Extensions from `github.com`, `gitlab.com`, `codeberg.org`, or similar third-party system
    • Comment on lines +21 to +22

      There's also lab.civi/myuser/...

      I don't think it's worth separating these two without a note about why lab.civi/ext are in any way separate.

    • Please register or sign in to reply
  • Please register or sign in to reply
    Loading