Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-22 Thread Jos Poortvliet
On Thursday 20 February 2014 09:27:05 Jaroslaw Staniek wrote:
 In searching of a business model...
 I understand that in case of GCompris content is king. Since it's
 getting rewritten (minus the resources), at least scripts can be
 published under any license suits the author, if you ask me, for
 example *GPL-incompatble linux-only license. This separation is easier
 to understand for the consumers than the story about source code.
 
 /me looking at bodega-based distribution channels to enable that
 because OS packaging is not a the best place for the multimedia
 market.
 
 Technically, it would be good if lessons are separated from the
 core/engine. I understand this is largely the case especially after
 upgrading to Qt Quick.

I think this could be a brilliant solution - the app free, payment for content 
through the Bodega store...

But I also agree with Thomas and others that this isn't a barrier to joining 
our community in any way.

___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-21 Thread Aaron J. Seigo
On Wednesday, February 19, 2014 21:18:25 Thomas Zander wrote:
 The beliefs of freedom are not at all hurt by someone taking that FLOSS and
 packaging it for a fee. There is no incompatibility there.

Agreed, and this could be an opportunity to explore what is possible there.

Perhaps the way we’ve been distributing KDE applications on platforms such as 
Windows and Mac is not the best. KDE Connect already goes through an 
application store on Android, though it is made available at no cost. People 
can always get the sources and build for themselves, but for these other 
platforms it could make sense to offer binaries via app stores and even charge 
a small fee.

I know that I would happily pay a couple euros (or whatever) for KDE Connect 
on Android ...

I do think we should keep the discussions of monetization separate from 
community hosting, however. They are not related, as can be seen by all the 
Linux distros who take the source code we write and monetize it. Some give 
back (some do so significantly, in fact), others don’t .. we don’t seem to be 
bothered by it.

So definitely a topic for further discussion, and one that is sure to have a 
variety of points of view within KDE ... but perhaps we should separate it 
from issues of hosting projects. Our manifesto says nothing about 
monetization, probably because that isn’t part of the core values that defines 
KDE’s identity: freedom and community do.

-- 
Aaron J. Seigo
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-20 Thread Bruno Coudoin

Le 19/02/2014 21:24, David Edmundson a écrit :


What I see as a problem is that this has an implicit attached request
to our current KDE Windows releasing team saying they shouldn't
package and release GCompris.

It would be unfair on Bruno for our KDE Windows team to do so. Legally
they absolutely can, but it would still be more than a little bit
rude. It's also equally unfair on our KDE Windows team to ever prevent
them from doing so.

I think it does open up some very interesting questions, not just here
but for other cases where our Android/iOS porting becomes popular on
how to do this in a manner that is fair to everyone. Money can easily
cause a lot of tension and arguments.

I'd like a discussion on it and maybe some guidelines.



Hi,

Yes I confirm that this is an important question and we must think about 
it before going further.


Distributing 2 different binary versions of GCompris, one on 
gcompris.net with an activation code and one on kde.org without would be 
unfair and confusing for the users. Like you mention it would be much 
more confusing on Android/iOS.


Even if you take out the activation issue, it is very confusing to have 
different application with the same name being build and distributed by 
several organization. It is the rule on GNU/Linux and we are used to 
work that way but on the other platforms it is not practical.


Bruno.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-20 Thread Bruno Coudoin

Le 20/02/2014 09:37, Martin Gräßlin a écrit :

On Thursday 20 February 2014 09:03:04 Bruno Coudoin wrote:

Le 19/02/2014 21:24, David Edmundson a écrit :

What I see as a problem is that this has an implicit attached request
to our current KDE Windows releasing team saying they shouldn't
package and release GCompris.

It would be unfair on Bruno for our KDE Windows team to do so. Legally
they absolutely can, but it would still be more than a little bit
rude. It's also equally unfair on our KDE Windows team to ever prevent
them from doing so.

I think it does open up some very interesting questions, not just here
but for other cases where our Android/iOS porting becomes popular on
how to do this in a manner that is fair to everyone. Money can easily
cause a lot of tension and arguments.

I'd like a discussion on it and maybe some guidelines.

Hi,

Yes I confirm that this is an important question and we must think about
it before going further.

Distributing 2 different binary versions of GCompris, one on
gcompris.net with an activation code and one on kde.org without would be
unfair and confusing for the users. Like you mention it would be much
more confusing on Android/iOS.

Even if you take out the activation issue, it is very confusing to have
different application with the same name being build and distributed by
several organization. It is the rule on GNU/Linux and we are used to
work that way but on the other platforms it is not practical.

But you cannot prevent it. If for example I don't like that you distribute it
with an activation code I can take the source and distribute it without the
activation code.

Hi,

It is true and this is not specific to free software or to GCompris. The 
software industry at large learned to live with people distributing 
unauthorized version. The difference with free software is that it is 
legal to do so. What happens in this case is that the original author 
request the unauthorized distributor to change the name of the software. 
It is what happened with RedHat versus CentOS or Firefox versus Iceweasel.


In our case the situation is different because it would be legitimate to 
have a build on gcompris.net and one on kde.org thus both parties have 
to define the rules.


Given that I don't think it really matters at the moment. You have to be
prepared that others will provide binaries (whether it's friendly (e.g. KDE)
or unfriendly (someone just going for the money)).
I am prepared to that and this issue is already present for the Gtk+ 
version. I have been somewhat protected by the complexity of doing a 
build on Windows and MacOSX.



  Maybe this could be split
of into a new thread to brainstorm ideas around that and how to fairly
distribute the income as that can raise conflicts.



I am open do discussion on this matter.

Bruno.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-19 Thread Agustin benito bethencourt
Hi Bruno,

I am Agustín Benito Bethencourt, KDE e.V. Treasurer.

 It is important to mention that the Windows and MacOSX version are
 distributed as demo ware. These binaries have only a limited number of
 activities and the users are invited to buy an activation code through
 paypal. The activation system is very simplistic, it does not require a
 network connection and is included normally in our code. An average
 developer can understand the activation system and create valid codes. I
 have no way to know if a buyer use the code on one or more computer and
 I don't care. Even if the money I get through this is encouraging, it is
 not enough to work full time on it so I also have a day job. All the
 money is officially declared and I pay taxes to the French government (I
 live in Toulouse in France).
 
 This is an unusual practice for a free software, I took this decision to
 make sure schools, teachers, parents who choose the GNU/Linux path get
 an advantage over the ones staying on a proprietary platform. To my
 surprise, it has been very well received by users and by the free
 software developers. More than this, the duality of the project,
 commercial and community allows it to benefit from the best of both
 worlds. I won't explain you the advantage of a community behind a
 project. For the commercial part, to my surprise, I have numerous
 examples where GCompris was selected in a school _because_ they could
 buy it.

I do not have any decision power in this area and we do not have any specific 
policy about what business models are ideal/desired/allowed to become part of 
KDE. From this point of view I do not see any problem with your model.

I agree with you that this model is unusual. I think I understand your 
reasoning behind it and I am glad to see that, from your point of view, it 
works.

I must confess though that I am worry about the association between:
* proprietary platforms = commercial
* free platforms = non commercial

that might be implied from this model.

But the business models is a discussion that we need to solve within KDE.

Your example will help us (enrich) to find good practices/solutions where we 
all feel comfortable and, at the same time, we can provide ways for 
contributors to be successful also in the financial area.

With this in mind, I am very happy to see your request.

Saludos
-- 
Agustin Benito Bethencourt
KDE eV Treasurer
aben...@kde.org
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-19 Thread Agustin
Hi Bruno,

I am Agustin Benito, KDE eV Treasurer.

Thanks for providing us the information around the income that GConpris 
generates. We do not have a clear policy about this topic. I do not see a 
major problem in this area.

We have a wide variety of different business models used by KDE developers to 
generate income. Your experience will help us to provide better answers to KDE 
developers in the future in this area.


 
 As a community project, it was part of the Gnome community, and the Gtk+
 version will still be there until the Qt version is on par. We got
 numerous contributors coming from Gnome, especially the translation team
 who does an excellent job. We also managed individual contributors all
 over the years. Many come, create an activity and leave when their
 children does not use GCompris anymore. I usually integrate the
 contributions and handle the maintenance of this code. At some point in
 time there as been other commiters and it was working fine.
 
 I am also a GSoC mentor since 2011 under the Gnome umbrella. I really
 appreciated doing that. It helps the project, the community, the student
 and myself as I like to share my knowledge. For this year I registered
 GCompris as an independent organization since I expect to get students
 working on the new Qt Quick version. Of course, if we work together, I
 will propose next year GCompris under the Kde umbrella.
 
 Enough history, lets talk about our future.
 
 Nowadays, more and more users are requiring us a tablet version. By far,
 Gtk+ is not ready in this area . After reviewing different
 possibilities, I had HTML5 and Qt Quick on my short list. I made a test
 and ported a GCompris activity in HTML5 and a few one in Qt Quick to be
 sure to make a wise decision.
 
 I am happy to tell you that I have been more than surprised by the ease
 of development and the quality of the code I wrote in Qt Quick. Yes it
 does not run on the web but for GCompris there are many reasons to stay
 off the web anyway.
 
 So I have now published a beta version in Qt Quick and used it to
 announce the world that I bet the future of GCompris on it. It has been
 well received in the GCompris community. Of course it deceived the Gnome
 team and I am sad for them but I had to take this drastic decision to
 make sure GCompris stay relevant in the years to come.
 
 On the development side, after looking at creating a compatibility layer
 to run old GCompris activities on a new Qt Quick framework. It proved to
 be difficult and the the result would be ugly in term of code and in
 term of user experience. I decided to go the hard way and to make a full
 rewrite. We will reuse the graphic, sound, voices, data and of course
 the concept of each activity of the Gtk+ version to create the new one.
 I expect the port to last one or two years.
 
 So this is a brain new project with just a demonstrator of only 4
 activities on 140. I think it is a good time frame for GCompris to join
 the Kde community for different reasons:
 
 - We need the best skills to create a solid framework
 - This is easier to jump on a new project and more interesting for a new
 contributor
 - Wehave no on line development tools to migrate
 
 I hope my request did raise your interest and I'll be please to answer
 your questions.
 
 Regards,
 
 Bruno.
 
 
 ___
 kde-community mailing list
 kde-community@kde.org
 https://mail.kde.org/mailman/listinfo/kde-community

-- 
Agustin
tosca...@gmail.com
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-19 Thread Sune Vuorela
On 2014-02-19, Agustin benito bethencourt aben...@kde.org wrote:
 I must confess though that I am worry about the association between:
 * proprietary platforms = commercial
 * free platforms = non commercial

 that might be implied from this model.

I understood it that it was 'source code is free software and it is
available over there = link'  'My binaries available from over there
= otherlink costs money to be fully used'.

I agree that I might worry about what Augustin is writing. But I have no
issue with people charging for their binary builds of free software,
and I'm pretty sure that others, including RMS, Redhat and others would
be okay for such a business model. (I of course assume that you still
live up to the license)

You can probably also hire half of the people on this list to build
windows installers for you - for a fee.

/Sune

___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-19 Thread Alvaro Soliverez
There were (and probably still are) KDE apps available in the N9 app
store for a fee. So, it's not new, and I don't see any problem with
it.

On Wed, Feb 19, 2014 at 10:56 AM, Sune Vuorela nos...@vuorela.dk wrote:
 On 2014-02-19, Agustin benito bethencourt aben...@kde.org wrote:
 I must confess though that I am worry about the association between:
 * proprietary platforms = commercial
 * free platforms = non commercial

 that might be implied from this model.

 I understood it that it was 'source code is free software and it is
 available over there = link'  'My binaries available from over there
 = otherlink costs money to be fully used'.

 I agree that I might worry about what Augustin is writing. But I have no
 issue with people charging for their binary builds of free software,
 and I'm pretty sure that others, including RMS, Redhat and others would
 be okay for such a business model. (I of course assume that you still
 live up to the license)

 You can probably also hire half of the people on this list to build
 windows installers for you - for a fee.

 /Sune

 ___
 kde-community mailing list
 kde-community@kde.org
 https://mail.kde.org/mailman/listinfo/kde-community
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-19 Thread Thomas Zander
On Wednesday 19. February 2014 12.58.57 Agustin benito bethencourt wrote:
 I must confess though that I am worry about the association between:
 * proprietary platforms = commercial
 * free platforms = non commercial
 
 that might be implied from this model.
 
 But the business models is a discussion that we need to solve within KDE.

To be frank, I could not disagree more.

The open source as well as the free-software movements are about freedom, and 
I believe KDE supports that as well.
The beliefs of freedom are not at all hurt by someone taking that FLOSS and 
packaging it for a fee. There is no incompatibility there.

Or, specifically, any commercial activity people do with free software, 
provided they honor the licenses, should never be a problem.
KDE is not about socialism. Commercial actions are specifically allowed by our 
licenses and I feel its a bridge too far to even imply that its KDE that can 
have a say about how a person asks for compensation of his/her time.

Practically speaking, the concept of filling the void of good Windows packages 
is something that is open to economic markets (i.e. Capitalism). With a severe 
shortage of people doing the work, there is an opportunity for those that want 
to do it for a price.
Its economy 101, everyone benefits when this is allowed by default. Forbid 
commercial activity and certain things just won't get done.

I believe even hinting that KDE should manage business models or commercial 
incentives on using Free Software is bound to kill that.
-- 
Thomas
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-19 Thread Bruno Coudoin

Le 19/02/2014 13:43, Agustin a écrit :

Hi Bruno,

I am Agustin Benito, KDE eV Treasurer.

Thanks for providing us the information around the income that GConpris
generates. We do not have a clear policy about this topic. I do not see a
major problem in this area.


Hi, I have no problem sharing this information but not on a public list. 
As you are interested I'll give you some details in private.




We have a wide variety of different business models used by KDE developers to
generate income. Your experience will help us to provide better answers to KDE
developers in the future in this area.


Sure, I have an long lasting experience and I am always pleased to share 
it. Each project is different and what worked for GCompris maybe 
inappropriate for another software. I already proposed to make a 
conference on that topic during a meeting in a Toulouse Lug Kde event.


Bruno.

___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-19 Thread Thomas Zander
On Wednesday 19. February 2014 21.24.22 David Edmundson wrote:
  The open source as well as the free-software movements are about freedom,
  and I believe KDE supports that as well.
  The beliefs of freedom are not at all hurt by someone taking that FLOSS
  and
  packaging it for a fee. There is no incompatibility there.
 
 What I see as a problem is that this has an implicit attached request
 to our current KDE Windows releasing team saying they shouldn't
 package and release GCompris.
 
 It would be unfair on Bruno for our KDE Windows team to do so. Legally
 they absolutely can, but it would still be more than a little bit
 rude. It's also equally unfair on our KDE Windows team to ever prevent
 them from doing so.

It doesn't have to be the case, the kde-on-windows effort still is making baby 
steps and there are plenty of problems I have personally seen when trying
to run kde on windows that could a turn-off for an educational app like 
GCompris.

There certainly is place in this huge Windows market for competition and 
market support allowing for a stand-alone, well-packaged setup app that has no 
direct ties to the KDE installer.

Such competition will only be good for the end-users.
-- 
Thomas
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-16 Thread Kevin Ottens
Hello,

On Thursday 13 February 2014 04:48:00 Bruno Coudoin wrote:
 [...]
 So this is a brain new project with just a demonstrator of only 4
 activities on 140. I think it is a good time frame for GCompris to join
 the Kde community for different reasons: [...]
 
 I hope my request did raise your interest and I'll be please to answer
 your questions.

Since a project going through the incubator should have a sponsor who oversees 
the integration and provide guidance to a community willing to join, let me 
say that I volunteer to be GCompris' sponsor.

I think it especially makes sense as I live in Toulouse too and I've known 
Bruno for years now. Hopefully it'll make the process easier.

I just need to know if we're willing to start that process, or is there anyone 
with concerns of having GCompris in our community? Finding issues and 
resolving them is obviously part of the process, so I'm thinking about 
anything radical (on the value level), personally I don't think there's any.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com



signature.asc
Description: This is a digitally signed message part.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-16 Thread Lydia Pintscher
On Fri, Feb 14, 2014 at 9:05 AM, Aaron J. Seigo ase...@kde.org wrote:
 decides to go for GPLv3+, and then leaves the project, it is possible
 that a rewrite would need to happen for the new people getting
 involved to avoid the limitation of GPLv3 which is not present in
 GPLv2. This would impose an additional overhead for the project.

 This is not limited to GPLv3, of course, but also GPL-LGPL (for instance).
 This is one of the reasons KDE e.V. introduced the FLA agreement, so that if
 people do go away we can continue to manage the licensing of the code within
 the boundaries set out (must be Free software, stick to the licenses in our
 policies, etc.) I hope that a large % of KDE community members have signed it
 by now as it resolves this exact issue.

Excellent point, Aaron! There's still a lot of developers who have not
signed an FLA. If you're one of them please do consider doing so. The
details are at http://ev.kde.org/rules/fla.php


Cheers
Lydia

-- 
Lydia Pintscher - http://about.me/lydia.pintscher
KDE e.V. Board of Directors / KDE Community Working Group
http://kde.org - http://open-advice.org
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community


Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-16 Thread Inge Wallin
On Saturday, February 15, 2014 00:03:15 Bruno Coudoin wrote:
 Le 14/02/2014 14:12, Inge Wallin a écrit :
  On Friday, February 14, 2014 00:28:38 Bruno Coudoin wrote:
   Le 13/02/2014 23:17, Aaron J. Seigo a écrit :
On Thursday, February 13, 2014 22:54:12 Bruno Coudoin wrote:
Anyway another approach is needed here for the new version.

Knights, a chess program written with KDE libraries, has an
  
  XBoardProtocol
  
class (GPLv2+ licensed) that speaks to gnuchess. It does this over

stdout/stderr which isn’t awesome as you note, but it exists and could

perhaps be shared.



It is part of a larger set of classes in the src/proto/ directory. The

classes in proto/ look fairly well self-contained (a single
  
  QObject class
  
hierarchy) so could be turned into a library with a little bit of
  
  effort.
  
Perhaps Knights and Gcompris could share this bit of code to at least

share the load of breakage?



The project page for Knights is here:

https://projects.kde.org/projects/extragear/games/knights
   
   Hi,
   
   
   
   Thanks for the information. Depending on an external binary proved to be
   
   a mess for the portability between the distro and annoying extra work on
   
   Windows and MacOSX. To see if GCompris works after a port all I do is
   
   check if the chess activity works because it is more than often broken.
   
   
   
   Now if we add the tablets into the mix, I am much more reluctant to rely
   
   on an external binary. An option would be to see if we cannot find and
   
   integrate a small chess engine. One important feature I also like to
   
   have is a weak chess engine that the children can beat (and myself).
  
  I am currently working on a board game AI library for kde games. The
  only thing you have to do to use it is to write a class representing a
  chess position, a move generator and an evaluation function and plug
  it in. (...and wait for me to finish, which should take a month or
  two) [1]
  
  Those classes should be pretty easy to get from another chess engine,
  especially if weakness is more important than strength. :)
 
 Hi, I just love this approach. We do not rely on external dependencies,
 we can use the same concept for other games beside chess and we can make
 it weak.
 
 I have not looked at it and this is perhaps another topic but will it be
 Android compatible?

My code will just be the brain of the chess AI so to speak, so definitely 
yes.  There is no UI there so you would have to create / port a UI that is 
compatible with Android.

  Btw, this is KDE and we love plugins. Do you have a plugin API for
  GCompris? If not, that would even make it possible for 3rd parties to
  create activites...
 
 Yes, the Gtk version of GCompris is plugin based. Each activity is a
 plugin. In the Qt Quick prototype I took a similar approach. You can see
 the list of current activities:
 https://github.com/bdoin/GCompris-qt/tree/master/src/activities
 
 Each one follow a similar structure, a file ActivityInfo.qml which
 describes the plugin and its QML entry point. At startup, the core loads
 the menu plugin first that itself display the list of activity plugins
 to the user.
 
 So yes in GCompris it is very important to make it easy to create a new
 activity, this is how we reached 140 activities while keeping the code
 easy to maintain. We have a core which exposes common features and
 ensure the coherency of the whole application.

That's great.  Qt has a very good plugin API too and KDE extends it in the kde 
libraries.  I don't know what the status of Qt 5 and the KDE Frameworks is but 
I guess it is the way to go for you.  It would make little sense to first port 
GCompris to Qt4 and then immediately to Qt5.

-Inge

 Bruno.___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-14 Thread Kevin Krammer
On Friday, 2014-02-14, 13:02:31, Shlomi Fish wrote:
 Hi Aaron,
 
 On Fri, 14 Feb 2014 09:17:05 +0100
 
 Aaron J. Seigo ase...@kde.org wrote:
  On Friday, February 14, 2014 04:24:12 Shlomi Fish wrote:

   The VideoLAN / VLC project took the opposite approach and after being
   unhappy with the GPLv3, decided to convert all their GPLv2 code into
   LGPLv2.
  
  I can name two likely reasons: DRM and tivoization clauses.
  
  Indeed, there is no one-size-fits-all license.
 
 Yes.
 
 BTW, regarding the so-called Tivoisation, from what I recall reading on
 http://zgp.org/pipermail/linux-elitists/ , the whole story was that Tivo
 contacted the https://en.wikipedia.org/wiki/Free_Software_Foundation (FSF)
 asking whether the practise of signing the kernel was allowed by the GPLv2.
 After consulting their lawyers, the FSF replied Yes , it's OK, thanks for
 asking.. Then after Tivo became popular, this practice was deemed
 non-desireable and Richard Stallman nicknamed it Tiovization after Tivo
 despite the fact that earlier the FSF told Tivo that it was acceptable.

I doubt that the FSF has any problem with cryptography being used to protect 
users from software from untrusted sources so I doubt that they do not 
consider signing acceptable.

The problem with Tivo, as far as I understand, is not them signing their 
binaries and checking that signature before execution.
The problem is that Tivo does not provide an adequate mechanism to register 
new keys. Which of course denies the user at least one of the four core 
principles of Free Software.

I doubt that Tivo asked the FSF whether withholding one of the Four Freedoms 
would be OK and the FSF said yes. I doubt they would even need to ask their 
legal counsels.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


signature.asc
Description: This is a digitally signed message part.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-14 Thread Inge Wallin
On Friday, February 14, 2014 00:28:38 Bruno Coudoin wrote:
 Le 13/02/2014 23:17, Aaron J. Seigo a écrit :
  On Thursday, February 13, 2014 22:54:12 Bruno Coudoin wrote:
  Anyway another approach is needed here for the new version.
  
  Knights, a chess program written with KDE libraries, has an XBoardProtocol
  class (GPLv2+ licensed) that speaks to gnuchess. It does this over
  stdout/stderr which isn’t awesome as you note, but it exists and could
  perhaps be shared.
  
  It is part of a larger set of classes in the src/proto/ directory. The
  classes in proto/ look fairly well self-contained (a single QObject class
  hierarchy) so could be turned into a library with a little bit of effort.
  Perhaps Knights and Gcompris could share this bit of code to at least
  share the load of breakage?
  
  The project page for Knights is here:
  https://projects.kde.org/projects/extragear/games/knights
 
 Hi,
 
 Thanks for the information. Depending on an external binary proved to be
 a mess for the portability between the distro and annoying extra work on
 Windows and MacOSX. To see if GCompris works after a port all I do is
 check if the chess activity works because it is more than often broken.
 
 Now if we add the tablets into the mix, I am much more reluctant to rely
 on an external binary. An option would be to see if we cannot find and
 integrate a small chess engine. One important feature I also like to
 have is a weak chess engine that the children can beat (and myself).

I am currently working on a board game AI library for kde games. The only 
thing you have to do to use it is to write a class representing a chess 
position, a move generator and an evaluation function and plug it in.  (...and 
wait for me to finish, which should take a month or two) [1]

Those classes should be pretty easy to get from another chess engine, 
especially if weakness is more important than strength. :)

Btw, this is KDE and we love plugins.  Do you have a plugin API for GCompris?  
If not, that would even make it possible for 3rd parties to create 
activites...

-Inge

[1] http://quickgit.kde.org/?p=scratch%2Fingwa%2Flibkdeai.git

 We have the same issue with the electricity activity which relies on
 gnucap but it proved more stable over time.
 
 Bruno.
 
 ___
 kde-community mailing list
 kde-community@kde.org
 https://mail.kde.org/mailman/listinfo/kde-community___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-14 Thread Jonathan Riddell
On Thu, Feb 13, 2014 at 11:28:08PM +0100, ivan.cu...@gmail.com wrote:
 ‎+1 for adding gpl3 to the licensing policy 

Please review the proposals I have made and posted in the thread licence 
policy updates

Jonathan

___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Re: [kde-community] Request to join the Kde incubator for GCompris

2014-02-13 Thread Bruno Coudoin

Le 13/02/2014 22:15, Albert Astals Cid a écrit :

Wait, does GCompris require for copyright assignment to the FSF?
No it does not. I know that it is a FSF recommendation but we never 
followed it.


In GCompris all the copyright are assigned to their authors.

Bruno.

___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community