Re: KDE Licensing Policy Updates

[Riccardo Iaconelli]

On 23 September 2016 at 18:52, Luigi Toscano  wrote:
> Still, as I mentioned, it would introduced problems if we move documentation
> forth and back from wikis to other formats, and also with mixing content from
> older documentation. I still don't buy the "cumbersome" argument, I don't
> think we use it the controversial parts like invariant section etc - do we?
> Trying to to relicense the existing documentation from FDL to FDL+CC as a
> start would be the best thing, but I think it would be complicated.

So yeah, FDL is impractical as it requires the full copy of the
license to be printed alongside with every printed copy of the
material covered by it.
...and doesn't really offer any more benefits I am aware of...

Bye,
-Riccardo
-- 
Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平
Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini Peoch שלום
Shanti Vrede Baris Rój Mír Taika Rongo Sulh Mir Py'guapy 평화

Re: KDE Licensing Policy Updates

[Luigi Toscano]

On Friday, 23 September 2016 16:46:22 CEST Jonathan Riddell wrote:
> On Fri, Sep 23, 2016 at 06:41:57PM +0200, Riccardo Iaconelli wrote:
> > Hi all,
> > 
> > On 20 September 2016 at 19:04, Jonathan Riddell  wrote:
> > > Added:
> > > "Content on collaborative edited websites such as wikis must be
> > > licensed under the Creative Commons Attribution-Sharealike 4.0
> > > International."
> > > Rationale: we have no policy for wikis but they are very important to
> > > us especially with wikitoLearn so we should add one.  Our wikis are
> > > currently CC 3.0+FDL but we should consider moving to CC 4.0 (CC
> > > includes an or later so there's no difficultly in doing this).  FDL is
> > > unmaintained and not much used so we can drop this.
> > 
> > WikiToLearn is currently dual licensing CC-BY-SA 3.0 / GNU FDL and
> > we're considering just dropping FDL as it is quite cumbersome and we
> > don't really use it anyways.
> 
> Right, that's why I suggest dropping FDL usage across all wikis and new
> docs.

Still, as I mentioned, it would introduced problems if we move documentation 
forth and back from wikis to other formats, and also with mixing content from 
older documentation. I still don't buy the "cumbersome" argument, I don't 
think we use it the controversial parts like invariant section etc - do we?
Trying to to relicense the existing documentation from FDL to FDL+CC as a 
start would be the best thing, but I think it would be complicated.

-- 
Luigi

Re: KDE Licensing Policy Updates

[Jonathan Riddell]

On Fri, Sep 23, 2016 at 06:41:57PM +0200, Riccardo Iaconelli wrote:
> Hi all,
> 
> On 20 September 2016 at 19:04, Jonathan Riddell  wrote:
> > Added:
> > "Content on collaborative edited websites such as wikis must be
> > licensed under the Creative Commons Attribution-Sharealike 4.0
> > International."
> > Rationale: we have no policy for wikis but they are very important to
> > us especially with wikitoLearn so we should add one.  Our wikis are
> > currently CC 3.0+FDL but we should consider moving to CC 4.0 (CC
> > includes an or later so there's no difficultly in doing this).  FDL is
> > unmaintained and not much used so we can drop this.
> 
> WikiToLearn is currently dual licensing CC-BY-SA 3.0 / GNU FDL and
> we're considering just dropping FDL as it is quite cumbersome and we
> don't really use it anyways.

Right, that's why I suggest dropping FDL usage across all wikis and new docs.

> We would need to keep BY-SA, but I am unaware of any particular
> difference between 3.0 and 4.0. We can of course evaluate only
> backward compatible changes, and we need to be backward compatible
> with 3.0 for a long time due to the usage of Wikimedia Commons content
> (still mostly 3.0).

4.0 just clarifies some bits and makes it more international.  It has
the additional advantage that content can be relicenced as LGPL 3,
usful for code examples.  CC 3 has an "or later" clause so content
from wikimedia commons can be moved to a CC 4 licenced wiki/

Jonathan

Re: Creating a map of KDE contributors?

[Nicolás Alvarez]

> El 23 sept 2016, a las 12:12, Thomas Pfeiffer  
> escribió:
> 
>> On 20.09.2016 14:06, Luigi Toscano wrote:
>>> On Tuesday, 20 September 2016 13:42:35 CEST Thomas Pfeiffer wrote:
>>> Hi everyone,
>>> I recently realized that unless you ask fellow KDE contributors personally
>>> where they live, you don't really know where over the world (or even in
>>> your home country) KDE is spread.
>>> 
>>> [...]
>>> 
>>> So, two questions:
>>> 1. Does that make sense to you?
>> 
>> We had a "heat-map" of committers in the old commit-digest:
>> https://commit-digest.kde.org/issues/2014-11-16/
>> So yes, it makes sense.
>> 
>> Also, for example:
>> https://www.debian.org/devel/developers.loc
>> 
>>> 2. If yes: Does anyone know of a piece of code that allows people to enter
>>> their city of residence and then show people on a map (ideally as an OSM
>>> overlay), or could otherwise maybe create it?
>> 
>> If it's not for the fact that sysadmin want to replace identity, a custom
>> field there with the city and/or coordinates and some script to grab them,
>> convert into geojson, and it's really easy (read: few lines of code) to setup
>> a map with leaflet.
>> 
>> http://leafletjs.com/examples/geojson.html
> 
> If I read the documentation [1] correctly, Phabricator (which would replace 
> Identity) allows custom fields in user profiles, so we could still do that.

Note it's not yet decided if we'll replace Identity with Phabricator or if 
we'll use something else.

(I was going to throw my opinion of such a replacement here, but I realized it 
would make this thread quickly go off topic)

-- 
Nicolás

Re: Creating a map of KDE contributors?

[Thomas Pfeiffer]

On 20.09.2016 14:06, Luigi Toscano wrote:

On Tuesday, 20 September 2016 13:42:35 CEST Thomas Pfeiffer wrote:

Hi everyone,
I recently realized that unless you ask fellow KDE contributors personally
where they live, you don't really know where over the world (or even in
your home country) KDE is spread.

[...]

So, two questions:
1. Does that make sense to you?


We had a "heat-map" of committers in the old commit-digest:
https://commit-digest.kde.org/issues/2014-11-16/
So yes, it makes sense.

Also, for example:
https://www.debian.org/devel/developers.loc


2. If yes: Does anyone know of a piece of code that allows people to enter
their city of residence and then show people on a map (ideally as an OSM
overlay), or could otherwise maybe create it?


If it's not for the fact that sysadmin want to replace identity, a custom
field there with the city and/or coordinates and some script to grab them,
convert into geojson, and it's really easy (read: few lines of code) to setup
a map with leaflet.

http://leafletjs.com/examples/geojson.html


If I read the documentation [1] correctly, Phabricator (which would replace 
Identity) allows custom fields in user profiles, so we could still do that.



[1] https://secure.phabricator.com/book/phabricator/article/custom_fields/