Bundle plugins to packages and fewer repos.

[draftkraft]

I suggest to merge multiple plugins into one or more repositories: eg: packages common with ''format,highlighteditables,link,list,table,abbr,paste,undo'' media with ''image,dragdropfiles,upload'' extra with ''hints,product,ribbon,vie,toc,googletranslate,linkchecker'' collaboration with ''comments''

This reduces current pain with:

• branching and linking submodules
• version numbers of plugins
• defining a maintainer of a package
• handling overhead for tiny pieces of code

[Jotschi]

Sounds good. I guess this would mean we need to change the plugin folder structure as well since we would have something like /src/plugin/common/, /src/plugin/media/ ...

[draftkraft]

That should not be the case. It could all remain the same. You would load plugins with common/format,common/list instead of format,list. I think that's still reasonable...

[npomaroli]

I think this is a good idea.

[draftkraft]

bundles are made (with plugins as submodules - they will be merged once bundles work with stable)

common

• abbr
• align
• block
• format
• highlighteditables
• link
• list
• paste
• table
• undo

extra

• gmaps
• googletranslate
• hints
• linkchecker
• metaview
• ribbon
• toc
• vie
• wai-lang

media

• draganddropfiles
• image

collaboration

• comments

What should happen with the following plugins?

• save
• product
• cropnresize
• markdown
• annotations
• initeditablecontents
• collator
• autotagging

[scribu]

Shouldn't cropnresize go under media?

[Jotschi]

I think cropnresize was merged into "image"

[nka11]

The plugin list is huge, that's great !!! what does actually means your question about what should happend with plugins ? I may ask, what happends now ? How high are those plugins maintained ? who uses them ? maybe an unmaintained category for some of them like cropnresize, cause image handles its features (with canvas support).

I propose a semantic category for vie and autotagging

The save plugin contains valuable example, we should maintain it well commented as it is a good starting point for cms adopters to integrate aloha, so it brings up an example category. initeditablecontents may apply too.

[Jotschi]

I suggest putting markdown into extra

[Jotschi]

Perhaps we should even create a demo/plugin-examples bundle where we could place plugins that are used to show how to write dummy implementations. They would need also a documentation that describes them of course. The product plugin would be a good example for that.

[draftkraft]

For the 0.10 release plugins are linked. Merge will be done for 0.11