Re: Releasing a non-KF5 library under MIT License

[Alexander Potashev]

On Wed, Mar 31, 2021 at 12:54 AM Luigi Toscano  wrote:
>
> Alexander Potashev ha scritto:
> > The https://community.kde.org/Policies/Licensing_Policy says I can't
> > do this because (according to this policy) the MIT License is only
> > allowed for parts of the "KDE Platform".
>
> Does it? I see:
>
> 4. Source files that are part of a library with a public API which is part of
> the KDE Platform (kdelibs, kdepimlibs, kde-runtime and KDE Frameworks) must be
> licensed under:
> [... licenses, including: ...]
>  * MIT: MIT license as listed below.
> [...]
>
> 5. Any other source files must be licensed under one of the terms listed under
> 4) or:
> [ other licenses]

Makes sense. Thanks for pointing this out!

(IOW the licensing policy "KDE Platform" is even tighter and for the
other projects, and this is great for me!)

-- 
Alexander Potashev

Re: On the reappointment of Richard Stallman as a director of the FSF

[Philippe Cloutier]

Thank you Alexander, I must agree with your general idea.

Before starting to give lessons about transparency and participation to 
independent organizations, we should start by being exemplary. While 
being clear about the community's adhesion to the message would indeed 
be a great start, I would go further and request consultation. The board 
is IMO empowered to release such statements unilaterally, but a call for 
participation is weakened if we ourselves fail to allow participation in 
such a high-profile case.


Consulting the community obviously delays reaction, but the level of 
urgency doesn't prevent it in this case. Input from the community would 
not only allow to validate that the message reflects the community's 
position, but it would ensure optimal communication of that position.


Le 2021-03-25 à 00:33, Alexander Potashev a écrit :

Thanks for the effort Aleix!

It would be nice to clarify whose opinions this linked message 
represents. If this is something that the KDE e.V. Board voted for, 
then probably a signature "KDE e.V. Board of Directors" on the bottom 
of the page would make sense.


--
Alexander Potashev


On Wed, Mar 24, 2021, 23:27 Aleix Pol > wrote:


Dear community,
From the KDE e.V. we followed closely the discussions on the last few
days regarding this recent decision within the Free Software
Foundation's leadership.

We have tried to sum up our thoughts in the following announcement
with the hope to foster collectively the Free Software leadership we
need.
https://ev.kde.org/2021/03/24/on-the-reappointment-of-rms-fsf/


Looking forward to a more inclusive discussion that will shape the
Free Software movement of tomorrow.

Best regards,
Aleix Pol with the KDE e.V. Board of Directors


--
Philippe Cloutier
http://www.philippecloutier.com

Re: Releasing a non-KF5 library under MIT License

[Luigi Toscano]

Alexander Potashev ha scritto:
> Hi,
> 
> I would like to release a Go library under the terms of the MIT
> License and host it at invent.kde.org. The library definitely won't
> fit in KF5 because it has nothing to do with Qt.
> 
> The https://community.kde.org/Policies/Licensing_Policy says I can't
> do this because (according to this policy) the MIT License is only
> allowed for parts of the "KDE Platform". 

Does it? I see:

4. Source files that are part of a library with a public API which is part of
the KDE Platform (kdelibs, kdepimlibs, kde-runtime and KDE Frameworks) must be
licensed under:
[... licenses, including: ...]
 * MIT: MIT license as listed below.
[...]

5. Any other source files must be licensed under one of the terms listed under
4) or:
[ other licenses]


-- 
Luigi

Re: Releasing a non-KF5 library under MIT License

[Jonah Brüchert]

Hi Alexander,

To clarify, the MIT licensed files in Kaidan are third party files which 
are not available as libraries and needed to be copied into the Kaidan 
repository, with the exception of the generate-license.py script.


All the actual code of Kaidan is GPL licensed.

Of course this does not mean anything about whether it is generally 
wanted to host MIT-licensed code on KDE Infrastructure.



Am 31.03.21 um 00:16 schrieb Alexander Potashev:

Hi,

I would like to release a Go library under the terms of the MIT
License and host it at invent.kde.org. The library definitely won't
fit in KF5 because it has nothing to do with Qt.

The https://community.kde.org/Policies/Licensing_Policy says I can't
do this because (according to this policy) the MIT License is only
allowed for parts of the "KDE Platform". Can we please review the
policy and stop this discrimination against projects that don't happen
to be part of the "KDE Platform"?


P.S.  It seems like MIT is already used outside of the "KDE Platform":
  - https://invent.kde.org/network/kaidan (at least two files are under 

MIT)

  - http://invent.kde.org/sdk/cutehmi (dual-licensed, including MIT)



OpenPGP_0xA81E075ABEC80A7E.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Releasing a non-KF5 library under MIT License

[Alexander Potashev]

Hi,

I would like to release a Go library under the terms of the MIT
License and host it at invent.kde.org. The library definitely won't
fit in KF5 because it has nothing to do with Qt.

The https://community.kde.org/Policies/Licensing_Policy says I can't
do this because (according to this policy) the MIT License is only
allowed for parts of the "KDE Platform". Can we please review the
policy and stop this discrimination against projects that don't happen
to be part of the "KDE Platform"?


P.S.  It seems like MIT is already used outside of the "KDE Platform":
 - https://invent.kde.org/network/kaidan (at least two files are under MIT)
 - http://invent.kde.org/sdk/cutehmi (dual-licensed, including MIT)

-- 
Alexander Potashev

Another take on planning for the journey ahead

[Valorie Zimmerman]

Found on Twitter: Audrey Eschright @ameschright

With the FSF imploding, I’m thinking again about the idea of a 3rd wave of
> FLOSS and what we really want from it (I gave this talk three years ago!)
> http://lifeofaudrey.com/essays/history_and_future_floss.html


Short essay, really excellent and thought-provoking, although I miss KDE's
part in the story.

Valorie

-- 
http://about.me/valoriez - pronouns: she/her

MBition is hiring Linux desktop/Wayland expertize

[Eike Hein]

Hi everyone,



At MBition GmbH in Berlin, we're currently looking for senior
software engineers with a strong background in the Linux desktop
technology stack and open source development to join our Video/HMI
team. In particular, we're looking for your experience with Linux
display servers, window managers and Wayland. Experience with KDE's
Plasma technology is considered a very strong plus.

MBition is tasked with developing the infotainment operating system
for Mercedes-Benz cars. We're are adopting many technologies you
are excited by, and some you may have already contributed to and
want to keep contributing to.

Our developer machines run Plasma by default, and we strongly share
your appreciation for the color blue:

https://api.media.mercedes-benz.com/v2/storage/v1/public/7b07ed5e-6bf5-4bb3-86f0-807dde19722a


If this sounds interesting, please have a look at the job listing
on our website:

https://mbition.io/wp-admin/admin-ajax.php?action=full_job_ad_page=9575277


If you have any questions about the position or the company,
please feel free to get in touch.


Cheers,
Eike Hein
-
Principal System Architect, MBition GmbH


PS.: I'm also very happy to be able to announce that MBition will
sponsor Akademy 2021 for the third year in a row, and, for the
first time, also Linux App Summit 2021. See you there!