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

List:       kde-community
Subject:    Re: [kde-community] Proposal: KDE Manifesto wording revision
From:       Eike Hein <hein () kde ! org>
Date:       2013-11-11 6:31:15
Message-ID: 1433058.LqxpXfRu6D () ehw1 ! ehn
[Download RAW message or body]


> -  * Software assets access model
> -    * Direct write access to the software assets is granted only to KDE 
contributor accounts
> -    * Direct write access to the software assets is granted to all KDE 
contributor accounts
> +  * All KDE contributor accounts get direct (and universal) write access to 
the software assets

Wow - I struggle to put into words how much I am opposed
to this change. I just jumped up from the breakfast table
with breakfast uneaten in order to get to a keyboard as
fast as I could.

In my mind - based on experience as contributor, main-
tainer and for a period, sysadmin working on the contri-
butor account system - codifying the two halves that make
up our access model was the single most important accom-
plishment of the Manifesto process.

The access model is the basis for the trust dynamics,
shared ownership, shared responsibility and generally
contributor equality in our community. I believe it's
the key to why KDE, unlike many other FOSS communities,
has managed to become multi-generational, and I'd like
it to continue. Quite a lot on the first page of the
Manifesto flows from those two lines.

I urge everyone who can to go back to the original Mani-
festo discussions, where this was discussed at length.

What's the motivation for this change? Unwieldy lang-
uage? Then let's make it more elegant. But let's not
lose the meaning in the process, because _this stuff be
important_.


Cheers,
Eike
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[prev in list] [next in list] [prev in thread] [next in thread]