DevHeads.net

KF5: Let's get KDEUI down

Hello all,

I didn't make noise about KDE Frameworks for a while now, and to the outside
it could look like it wasn't making progress. Let me assure you: this is not
the truth. Admittedly, I decided to take a risk a few months ago... I stopped
communicating or reaching toward people to get more contributors.

Why would I take such a risk? Well, we hit a major road block in the form of
KDEUI. The complexity was so high there, that as soon as someone was trying to
split something out they were daunted by the task. That's why I stopped trying
to bring more people in... what's the use if they then walk away in disgust?
I'd rather have them do stuff they take pride in.

And so I took the risk, went into a sort of retreat to focus all my energy on
trying to find a way to slay the beast. I can tell you it has been months of
work to remove the difficult parts of KDEUI in order to make it more inviting
to people. It's not all solved of course, but we're at a point where the beast
is about to die... we have to collectively strike it once more to put it to
rest before moving to other fun areas.

That's why, today, I am glad to announce that the battle plan to split
KDEUI[3] is finally published. I am able to concentrate on other people again,
and so expect more communication and help from me (it even picked up a bit
already).

All people wanting to push KDE Frameworks forward are invited to pick tasks
either to split KDEUI or push our contributions to Qt forward [2]. Both are
surely needed and most of the tasks there should have a similar size.

Note however that the requirements are not the same between contributing to
Qt5 or contributing to the "KDEUI Crumble".
For Qt5, having a clone of qtbase is enough to get you started, you then have
to follow the Qt processes[4] and pick a task on the Qt5 contribution page[2]
by putting your name in the relevant column.
For the KDEUI Crumble, you will need to build kdelibs-frameworks[1]. Then pick
a task on the crumble page[3] by putting your name in the relevant column.

If you are interested, please contact us by email on kde-frameworks-devel, or
on IRC at #kde-devel. If you are not sure what to pick we can help you get
started and select something matching your skills. If you have issues with
your task and are unsure what to do we can help you.

We also plan to hold regular meetings to share efforts and progress. They
will happen on #kde-devel every Tuesday at 4pm.

Hoping to see you there! Let's bring KDEUI down.

Regards.

[1]: <a href="http://community.kde.org/Frameworks/Building" title="http://community.kde.org/Frameworks/Building">http://community.kde.org/Frameworks/Building</a>
[2]: <a href="http://community.kde.org/Frameworks/Epics/Contributions_to_Qt5" title="http://community.kde.org/Frameworks/Epics/Contributions_to_Qt5">http://community.kde.org/Frameworks/Epics/Contributions_to_Qt5</a>
[3]: <a href="http://community.kde.org/Frameworks/Epics/KDEUI_Crumble" title="http://community.kde.org/Frameworks/Epics/KDEUI_Crumble">http://community.kde.org/Frameworks/Epics/KDEUI_Crumble</a>
[4]: <a href="http://qt-project.org/contribute" title="http://qt-project.org/contribute">http://qt-project.org/contribute</a>

Comments

Re: KF5: Let's get KDEUI down

By Kevin Ottens at 05/07/2013 - 12:26

On Tuesday 07 May 2013 19:13:03 Kevin Ottens wrote:
Since I got the question already, the timezone will be UTC+1 AKA "the timezone
I live in". :-)

Regards.

Re: KF5: Let's get KDEUI down

By Kevin Ottens at 05/07/2013 - 13:17

On Tuesday 07 May 2013 19:26:01 Kevin Ottens wrote:
OK... second try, the current weather is confusing me apparently... Soooo...
"the timezone I live in" is currently using summer time... So that would be
UTC+2 and NOT UTC+1.

Sorry about the noise. I hate timezones. :-)

Regards.

Fwd: KF5: Let's get KDEUI down

By Patrick Spendrin at 05/07/2013 - 15:57

Maybe interesting for us as well...

regards,
Patrick

-------- Original-Nachricht --------
Betreff: KF5: Let's get KDEUI down
Datum: Tue, 07 May 2013 19:13:03 +0200
Von: Kevin Ottens < ... at kde dot org>
Organisation: KDAB
An: <a href="mailto:kde-core- ... at kde dot org">kde-core- ... at kde dot org</a>
Kopie (CC): <a href="mailto:kde-frameworks- ... at kde dot org">kde-frameworks- ... at kde dot org</a>

Hello all,

I didn't make noise about KDE Frameworks for a while now, and to the outside
it could look like it wasn't making progress. Let me assure you: this is not
the truth. Admittedly, I decided to take a risk a few months ago... I
stopped
communicating or reaching toward people to get more contributors.

Why would I take such a risk? Well, we hit a major road block in the form of
KDEUI. The complexity was so high there, that as soon as someone was
trying to
split something out they were daunted by the task. That's why I stopped
trying
to bring more people in... what's the use if they then walk away in disgust?
I'd rather have them do stuff they take pride in.

And so I took the risk, went into a sort of retreat to focus all my
energy on
trying to find a way to slay the beast. I can tell you it has been months of
work to remove the difficult parts of KDEUI in order to make it more
inviting
to people. It's not all solved of course, but we're at a point where the
beast
is about to die... we have to collectively strike it once more to put it to
rest before moving to other fun areas.

That's why, today, I am glad to announce that the battle plan to split
KDEUI[3] is finally published. I am able to concentrate on other people
again,
and so expect more communication and help from me (it even picked up a bit
already).

All people wanting to push KDE Frameworks forward are invited to pick tasks
either to split KDEUI or push our contributions to Qt forward [2]. Both are
surely needed and most of the tasks there should have a similar size.

Note however that the requirements are not the same between contributing to
Qt5 or contributing to the "KDEUI Crumble".
For Qt5, having a clone of qtbase is enough to get you started, you then
have
to follow the Qt processes[4] and pick a task on the Qt5 contribution
page[2]
by putting your name in the relevant column.
For the KDEUI Crumble, you will need to build kdelibs-frameworks[1].
Then pick
a task on the crumble page[3] by putting your name in the relevant column.

If you are interested, please contact us by email on
kde-frameworks-devel, or
on IRC at #kde-devel. If you are not sure what to pick we can help you get
started and select something matching your skills. If you have issues with
your task and are unsure what to do we can help you.

We also plan to hold regular meetings to share efforts and progress. They
will happen on #kde-devel every Tuesday at 4pm.

Hoping to see you there! Let's bring KDEUI down.

Regards.

[1]: <a href="http://community.kde.org/Frameworks/Building" title="http://community.kde.org/Frameworks/Building">http://community.kde.org/Frameworks/Building</a>
[2]: <a href="http://community.kde.org/Frameworks/Epics/Contributions_to_Qt5" title="http://community.kde.org/Frameworks/Epics/Contributions_to_Qt5">http://community.kde.org/Frameworks/Epics/Contributions_to_Qt5</a>
[3]: <a href="http://community.kde.org/Frameworks/Epics/KDEUI_Crumble" title="http://community.kde.org/Frameworks/Epics/KDEUI_Crumble">http://community.kde.org/Frameworks/Epics/KDEUI_Crumble</a>
[4]: <a href="http://qt-project.org/contribute" title="http://qt-project.org/contribute">http://qt-project.org/contribute</a>