Change the scope of the CiviCRM Extensions Directory so that it is no longer limited to Extension projects, can include Drupal Modules, Joomla Extensions, WordPress plugins, Mobile Apps, Integration Projects etc. which are not CiviCRM Extensions
Change the scope of the CiviCRM Extensions Directory so that it is no longer limited to Extension projects, can include Drupal Modules, Joomla Extensions, WordPress plugins, Mobile Apps, Integration Projects etc. which are not CiviCRM Extensions.
Two examples we worked on recently are the Outlook 365 integration which is Office 365 plugin and the CiviContact Mobile App. There are a growing number of WordPress plugins and some Drupal modules too that could be listed. None of these are "extensions".
Related to this change is then the requirement to "be smarter" about checking for the existence of the info.xml file and trying to publish a release on civicrm.org. Since this only applies to CiviCRM extensions, the release process should not apply to non-CiviCRM extensions.