[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-12 17:08:08
Message-ID: 1862436.QfATBVO4I7 () ehw1 ! ehn
[Download RAW message or body]

On Tuesday 12 November 2013 18:00:34 Aaron J. Seigo wrote:
> my concern is that if it says that all KDE contributors can write to it, it
> can be interpreted as being enough to simply be able to open an account
> there.
> 
> iow, this makes github a valid place to put your code (well, if we ignore
> their odd push-request driven workflow). any KDE contributor can get an
> account there after all.
> 
> imho the purpose of this particular requirement is so that anyone with a KDE
> membership in hand can immediately trot over to project X and start
> contributing. it is about keeping the contribution barrier low and the
> shared ownership high.

I agree. Basically, summing things up: We want KDE sysadmin
to be the entity extending the reach of KDE contributors in
a centralized fashion, rather than having it be enough for,
say, an individual GitHub repo owner to grant access. The
Gitorious.org scheme which we do continue to want to be open
for in principle wouldn't actually have worked if sysadmin
hadn't performed that function.

Thus, the correct reading of "accounts" isn't to think
"identity.kde.org" but more "KDE sysadmin". Then it also
doesn't strictly preclude other authentication mechanisms.

Given that, I agree we should keep "accounts" after all.


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]