I know not to use the "gegl" name space for plugin development - but can you please not make things difficult for me.
I am fully aware about Jehan's new rule to not use name spaces (gegl, gimp, svg) and how one day Gimp may reject those name spaces and plugins using them. So far I have taken action and all new and simple plugins of mine were converted to a new name space. However, large plugins of mine that do advance text styles still use the GEGL name space, Not because I am being rebellious but because I don't want presets to break for my users. My most important plugins like GEGL Effects, Custom Bevel, Rock Text 2, are very complex plugins with many options and have been around for over a year or at least several months. Users converting to my new name spaces will lose all their presets unless they edit the preset file in config (something most don't know how to do and isn't user friendly). This would lead to scenarios where my users lose all their presets.
To resolve this, As of today I am planning to make a new branch of all my GEGL plugins for Gimp 3/2.99 exclusively, with a warning about presets breaking with the new name space for Gimp 2.99/3 only. So if you ever implement the name space blockage for GEGL/GIMP/SVG please consider the following to be friendly towards my user base.
1. Please only apply the name space blockage to Gimp 2.99/3 and not Gimp 2.10 (as most non-technical people won't be effected) and 2.10 is near its final days anyway.
2. Give it several months so I have a grace period for users to catch up. Maybe it would be best it initiated launch of Gimp 3 and never back ported to Gimp 2.10.
I ultimately wish you didn't do this. It gives me work. Though it was my fault from the start to use the GEGL name space.