Hmmm, I think maybe there might be a mix-up between treating the products as separate and not-maintaining plugins.
In the discussion in the referenced thread, I mentioned that the plugins should be a separate product as in having their own separate build system and release strategy. This does not mean they are not supported or do not get the same attention, it just means they are separate. So elaborating on this, if you commit something in the framework and it breaks something in plugins then my suggestion is that it should not be fixed in one single commit but rather as two separate unrelated commits. In other words, the two products should be very loosely coupled which is the main advantage of separating the project into two products. I hope this clarifies it better. On Wed, Apr 12, 2017 at 12:49 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Actually it's only about a policy to support plugins with a clear how-to > documentation. > > We can start that right now. We need to clarify that plugins deserve the > same attention than the framework and committers need to be aware of it. > > Jacques > > > > Le 12/04/2017 à 08:59, Taher Alkhateeb a écrit : > >> I think starting any vote right now might be a little premature. >> > >