plg wrote:

Just like for branch 2.0, I've removed AMM. It exists in piwigo.org/ext and in piwigo.org/svn/extensions.

Let's go?

Ok

Why don't we remove all plugins from core ? I mean remove from trunk/branches/tags. If we want to deliver plugins with core and use it in developement we can use svn:externals. I think it's a better way. When we prepare a new release we just have one file to modify.

nicolas wrote:

Why don't we remove all plugins from core ? I

Why not!
But it's necessary to present a list of useful plugin. A linked list from PEM? A list by branch version?

We can also propose a list with more used plugins?

The aim is to easiness installation and used of firt plugin.

Remark, if c13y_upgrade plugin is removed, it's necessary to include this code on core code. It's the only plugin embedded with core of piwigo.

VDigital wrote:

plg, could you move it in extensions (I don't care about its log of changes).

Job's done :-)

as of plugins delivered with the install package, you can do whatever you want (delete all from trunk, add all from extensions .... whatever).

I would like to transfer a part of the event_tracer in the admin multi view (logging the calls to trigger_event). Otherwise I'm ok with deleting the others

rub wrote:

plg wrote:

I would also like to remove some plugins from core:

* add_index
* admin_advices
* event_tracer

and have them in piwigo.org/ext + piwigo.org/svn/extensions

Let's go?

ASAP I move add_index to extensions.

But at moment [extension by rub] add_index is not a plugin but a MOD... I will change this plugin...

[extension by Piwigo Team] Add Index

admin_advices was moved, VDigital, can you create an extension in the extension manager? (to have your name in front of the extension)
event_tracer was moved, rvelices, can you create an extension in the extension manager? (to have your name in front of the extension)

Tell me if you prefer I create the extensions.