Frameworks Overview

Ben Cooksley bcooksley at kde.org
Fri Sep 27 09:50:42 UTC 2013


On Wed, Sep 25, 2013 at 8:22 AM, Alexander Neundorf <neundorf at kde.org> wrote:
> On Tuesday 24 September 2013, Ben Cooksley wrote:
>> On Sep 24, 2013 7:33 AM, "Alexander Neundorf" <neundorf at kde.org> wrote:
>> > On Monday 23 September 2013, Sebastian Kügler wrote:
>> > > Hey,
>> > >
>> > > On Monday, September 23, 2013 00:27:21 Cornelius Schumacher wrote:
>> > > > On Thursday 19 September 2013 Sebastian Kügler wrote:
>> > > > > http://community.kde.org/Frameworks/Overview
>> > > >
>> > > > I have put the data on Inqlude (see http://inqlude.org/edge.html).
>> > >
>> > > Thanks. One issue though, we're duplicating incomplete information that
>>
>> is
>>
>> > > in flux. (For example, I know of at least one framework that has been
>> > > added to tier2 (I think) since last week. The information will need
>> > > constant updating for a few more months. Having it in to places doesn't
>> > > make that easier.
>> > >
>> > > Can I update the info on inqlude.org somehow, so we can ditch the wiki
>> > > version?
>> > >
>> > > > It would be nice, if we could improve the presentation of the
>>
>> different
>>
>> > > > libraries along with the code. The goal of Inqlude is to make them
>>
>> easily
>>
>> > > > accessible not only to us, but also to Qt developers who don't
>> > > > necessarily know anything about KDE or might have (more or less
>>
>> founded)
>>
>> > > > objections against using KDE libraries. To reach this we'll need to
>> > > > present KF5 in a bit  more independent way, and make sure that each
>> > > > library can stand on its own.
>> > >
>> > > Technically, this is the current focus. We're splitting kdelibs.
>> > >
>> > > As to communication, it probably needs a bit of boilerplate. (Which the
>> > > bits I wrote don't contain purposefully.) Otherwise, you're right, we
>>
>> need
>>
>> > > to work on the presentation side here.
>> >
>> > IMO, if projects.kde.org would have the wiki enabled, the project pages
>>
>> there
>>
>> > could be an easy way to have simple homepages for all the frameworks:
>> > https://projects.kde.org/projects/kdesupport/attica
>>
>> Due to maintenance and performance concerns, sysadmin would like to move
>> away from Chiliproject.
>
> Oh, really ?
> What alternatives are you looking at ?
> Personally I like redmine/chili a lot.

Yep. At the moment there are no real contenders as such - which is why
it has not yet been replaced.
Phabricator is being monitored for progress on a blocking issue however.

The primary issues are those of performance (

>
>> Enabling the wiki would complicate this when a
>> replacement is found.
>>
>> It would also create competition with the main wikis.
>
> I don't think so.
> As Cornelius put it "To reach this we'll need to present KF5 in a bit
> more independent way, and make sure that each library can stand on its own."
> IMO a kind of separate home page for each library is part of that.

Would something similar to the Manifesto site fit this?

>
> Alex

Regards,
Ben

> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel


More information about the Kde-frameworks-devel mailing list