Problem/Motivation
A new significant development in the Drupal community are apps for specific functionality, easy to install on sites and distributions even by non-technical end users. That is, in some way, a not very different concept from, for example, Android or iPhone apps, etc. As Drupal derivatives, they are GPL; however, while app servers and app stores are being built, Drupal apps do not have a home on drupal.org yet.
For background info, some related resources:
- Apps - Project page.
- App Server - Project page.
- Open App Standard - Group.
- Apps: Making Drupal distributions work - Article.
- Apps for distributions: Ready to get started? - Article.
- App Sprint Austin - Success - Article.
- OpenPublic Documentation: Apps - Docs.
- Apps for Drupal distributions: A start to finish guide - Video.
- Taking inventory of Drupal products and app stores - Video.
- Drupal Licensing FAQ - GPL.
- GNU Philosophy - GPL.
Proposed resolution
The proposal of this issue is to add an "Apps Package" term to the module categories vocabulary on drupal.org, similar to the already available "Features Package" term for features. For the initial work, there is no need of app server functionality, etc., just a place where the community can start developing apps on drupal.org. Simply like this:

Remaining tasks
Later, a possible follow-up issue to this one could be to consider whether features and apps should continue to be part of the modules section, or should have their separate listings. Something like this:

That future possibility would be a different issue with more implications (#1348458: Drupal Feature Server, #322626: META: Package and version non-modules for download, etc.) than the simple current one (just a term for modules, not separate listings).
A couple of years ago, similar proposals were discussed for features, without reaching a consensus, apart from the term "Features Package", which was accepted:
- #711912: Should features be allowed as projects on drupal.org?
- #760878: Add a "Features" term to the taxonomy vocab for modules on d.o
- #907964: Distinguish between features and non-feature modules
Perhaps this could be different soon, when distributions -which use features and apps more and more intensively- keep increasing their importance for the Drupal community.
In any case, other improvements such as #1314124: [META] Improve installation profile listing on Drupal.org have more priority now, and just a module term similar to the current one for features -even when hidden among many others- seems enough, at least for now.
User interface changes
With the proposal of this issue -just adding the new term- everything would work like for the rest of projects. No additional changes needed.
API changes
No API changes. It's a new term, a one-minute fix, nothing more at this moment.
| Comment | File | Size | Author |
|---|---|---|---|
| Introducing-features,-apps.jpg | 42.72 KB | juan_g | |
| Apps-Package.jpg | 76.28 KB | juan_g |
Comments
Comment #0.0
juan_g commentedAdded a resource on apps (video).
Comment #0.1
juan_g commentedAdded reference to OpenPublic Documentation: Apps.
Comment #1
Bojhan commentedPlease list projects that would currently fit this category.
Comment #2
juan_g commentedThat's the problem. On Drupal.org, without the proposed app tag/term, apps are few and not easy to find. At this time they are developed (for distributions, clouds, and SaaS services) mainly on other Drupal sites such as Acquia, Open Enterprise, OpenPublic, SubHub...
Some examples, including links to the Drupal.org project pages that I could find:
Acquia (cloud):
Open Enterprise (distribution):
OpenPublic (distribution):
SubHub (SaaS):
Apps are a very promising technology, especially for Drupal distributions. I think it would be important that developers could more easily choose to have them available for the community also on Drupal.org, not only on external app servers and app stores...
Comment #2.0
juan_g commentedMinor edit (typo).
Comment #3
mlhess commentedI am closing some old issues,these feel like distributions.