reflecting on 4.10

Aaron J. Seigo aseigo at kde.org
Sat Jan 12 16:36:01 UTC 2013


On Saturday, January 12, 2013 16:00:10 Kevin Ottens wrote:
> As already pointed out, this should be a set of people not a single one.

a bus number greater than 1 is important, but i also think the realities of 
doing this job limits the number of people who can, will and even should be 
doing it.

a committee causes communication requirements, which decreases efficiency (time 
spent coordinating with each other rather than with the code base).

i'm also not entirely keen on trying to get each main maintainer to spend time 
on the integration points between different major components as that requires 
them to specialize less in their topic and spend less time on their component. 
if we go for a set of people, this is exactly what is likely to happen.

it is entirely a job that can be done by one person in a given release. having 
people that the responsibility can be rotated around from one release to 
another (and serve as a backup for when the person holding the "oversight 
token" is not available) would be a great thing.

the most important thing, whether we have 1 person or 5 doing this, is that we 
support that role unanimously as a set of teams working on the workspaces.

> FYI I plan to use master again[*] as my main setup sometime in 2013
...
> [*] Historical note no one will probably care about

actually, i care :) i rather suspected this was the case, given the number of 
developers i've heard this same kind of story from. the reason for moving to 
packages varies, but fewer KDE devs run master than probably ever before. it 
seems a recent phenomenon, just as with you.

i'm personally very excited that more people will be running master again. and 
i hope with an integration branch, that will extend even further.

-- 
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20130112/aee81387/attachment.sig>


More information about the Plasma-devel mailing list