--===============1567417227075765511== Content-Type: multipart/alternative; boundary=001a11c37920917d1e04ecb0bf61 --001a11c37920917d1e04ecb0bf61 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Dec 4, 2013 at 3:33 AM, Kevin Kofler wrote: > Alex Turbov wrote: > > +1 for GHNS! (for Python plugins) > > I don't think hiding the non-free plugins behind GHNS is that great a > solution, also considering that GHNS is notoriously bad at displaying > license information. > > I've talked about GHNS mostly in context: "it would be nice to allow users to write/publish/exchange/download their plugins using GHNS as a platform, to stimulate kate/python plugins development (and unlocking from kate's twice-a-year-new-releases as the only source of that plugins)"... and at last in context of mentioned license problem... --001a11c37920917d1e04ecb0bf61 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On W= ed, Dec 4, 2013 at 3:33 AM, Kevin Kofler <kevin.kofler@chello.at&= gt; wrote:
Alex Turbov wrote:
> +1 for GHNS! (for Python plugins)

I don't think hiding the non-free plugins behind GHNS is that great a solution, also considering that GHNS is notoriously bad at displaying
license information.


I've talked about GHNS mostly in c= ontext: "it would be nice to allow users to write/publish/exchange/dow= nload their plugins using GHNS as a platform, to stimulate kate/python plug= ins development (and unlocking from kate's twice-a-year-new-releases as= the only source of that plugins)"... and at last in context of mentio= ned license problem...
=A0


--001a11c37920917d1e04ecb0bf61-- --===============1567417227075765511== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KWrite-Devel mailing list KWrite-Devel@kde.org https://mail.kde.org/mailman/listinfo/kwrite-devel --===============1567417227075765511==--