Not to mention the extra work created for localizers if they have to
maintain two forks... it would be like the OpenOffice / LibreOffice mess.
I must admit I understand very little about the technical arguments put
forth in this debate but from the localizer (and to a certain extent
end-user) perspective, forking should be a very very very very last
resort if a project is dead in the water but somehow under someone's
deathgrip. Most 'normal' end users glaze over when I try to explain the
difference between OpenO and LibreO... I wouldn't want to have to do
that with Gimp too.
Michael
05/11/2014 12:00, sgrìobh gimp-developer-list-request@xxxxxxxxx:
Another advantage to forking babl and GEGL for GIMP is that GIMP's fork
of babl and GEGL could be GPLed, thus freeing the GIMP devs to add FFTW
(Fourier transforms,http://www.fftw.org/) and other new functionality
to GIMP. FFTW is GPLed. At present, GIMP is somewhat hobbled as to what
GPL code can be used for new editing functions because the babl/GEGL
code is LGPLed.
With kindest regards,
Elle Stone
--
*Akerbeltz <http://www.faclair.com/>*
Goireasan Gàidhlig air an lìon
Fòn: +44-141-946 4437
Facs: +44-141-945 2701
*Tha Gàidhlig aig a' choimpiutair agad, siuthad, feuch e!*
Iomadh rud eadar prògraman oifis, brabhsairean, predictive texting,
geamannan is mòran a bharrachd. Tadhail oirnn aig www.iGàidhlig.net
<http://www.iGaidhlig.net/>
_______________________________________________
gimp-developer-list mailing list
List address: gimp-developer-list@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
