[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu
Subject:    Re: Having KDE-Edu on the frontpage of api.kde.org
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2016-09-29 22:39:31
Message-ID: CACcA1Rq1VS9nN66XFsWeQMSCzZv5TWX05gWuPr4WU-qsTddPdQ () mail ! gmail ! com
[Download RAW message or body]

On Thu, Sep 29, 2016 at 11:43 PM, Albert Astals Cid <aacid@kde.org> wrote:
> El dijous, 29 de setembre de 2016, a les 0:32:03 CEST, Aleix Pol va escriure:
>> On Wed, Sep 28, 2016 at 8:19 PM, Olivier Churlaud <olivier@churlaud.com>
> wrote:
>> > IF YOU WANT TO ANSWER: I'm not on the mailinglist, so please put me in
>> > copy :)
>> >
>> > Hello,
>> >
>> > I write you because we had some issues with kstar today which is not
>> > correctly generated. I wasn't able to find why because it is generated by
>> > very old scripts.
>> >
>> > I'm therefore in the process of moving the generation to kapidox.
>> >
>> > I ran ./kdesrc-build kdeedu --src-only  to get all your projects.
>> >
>> > # What I've done
>> > (not commited yet, I'm waiting for a "go" from you, guys)
>> >
>> > 1. I put the group definition in kdeedu-data.
>> > 2. For each lib I created a metainfo.yaml file which is generic but let
>> > the app being generated
>> >
>> > # Issues you will have:
>> > 1. No fancynames, descriptions, maintainers, test/example/docs/source
>> > folders are defined, but "." so it fills with 'None' the missing fields
>> > and generates the documentation for tests and examples as well.
>> > 2. The rule is that only documented class are generated. I saw that some
>> > of
>> > your classes were not, so they won't appear.
>> >
>> > # My questions:
>> > Do I push this as it is and let you fix it later?
>> > or Do you want to take care of it and I help you if needed?
>> >
>> > How do we proceed?
>> >
>> > Cheers
>> > Olivier
>>
>> Hi Olivier,
>> I wouldn't put KDE Edu on api.kde.org. KDE Edu is not for developers.
>
> Why not? there's libs on kde edu people can use, so why is it not for
> developers?

If we wanted to focus some components for developers, we'll make these
a framework. With proper schedule, documentation and support. What we
have it's mostly by-products of the end-user software we're providing.

Which is free software and properly licensed to facilitate adoption,
but I would not put it at the same level as KF5 or even actively
advertise it.

Aleix
[prev in list] [next in list] [prev in thread] [next in thread]