Re: [kde-community] Proposal: KDE Manifesto wording revision
> - * 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
Re: [kde-community] Discussion: KDE Manifesto, "web services"
On Sun, Nov 10, 2013 at 10:12 AM, Kevin Ottens wrote: > Hello community, > > In the principles section of the manifesto, we have the following point: > "Projects that choose not to host their web services on KDE infrastructure > need to provide administrative access to the KDE sysadmin team; or, if such > access cannot be granted, a regular backup of all the code and data used by > the web services should be provided to the KDE sysadmins (except if the > service is not an integral part of the project's workflow, community > interactions and public image) to ensure continued availability" > > Don't know how you feel about that one, but it sticks out like a sore thumb > when you look at the other points in the manifesto. All the other points are > short and to the point... but that one is just monstrous. :-) > > It's kind of the pandora box though. The idea is basically we want to ensure > the continuity of online services outside of our infrastructure. I'm looking > for alternative wording for that one. > > I'd be tempted to go with: > "Projects that do not use KDE infrastructure for their online services must > work with the KDE sysadmin team on an agreement to ensure continuity." > > Opinions? > > Regards. > -- > Kévin Ottens, http://ervin.ipsquad.net Short, sweet, and more important: clearer. Valorie -- http://about.me/valoriez ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Discussion: KDE Manifesto, "established practices"
On 11/11/2013 09:47 AM, Carl Symons wrote: > "...unless special considerations force it to deviate" could be considered an > established practice. Dropping that clause retains the essence of this point. > > "The project stays true to established practices common to similar KDE > projects." I wholeheartedly disagree with this change. Keep in mind that teams of external projects will (and should) consult the manifesto as part of their consideration of potentially becoming a part of KDE. These people can not expected to know that deviating in case of special considerations is standard practice within the KDE community. Removing that clause changes the meaning quite substantially in that case. Best regards, Peter ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Discussion: KDE Manifesto, "established practices"
On Sunday, November 10, 2013 19:00 Kevin Ottens wrote: > Hello, > > In the principles, section of the manifesto we have the following point: > "The project stays true to established practices common to similar KDE > projects unless special considerations force it to deviate". > > I guess after lengthy discussions you end up with points like that which > says... well... nothing really. "Do it like anybody else except if you feel > you can't". :-) > > So, I'm looking for an alternate wording. I think that either we find a way > to make it stronger or we should just drop it. It's meaningless as it is. > > Regards. "...unless special considerations force it to deviate" could be considered an established practice. Dropping that clause retains the essence of this point. "The project stays true to established practices common to similar KDE projects." Carl ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Discussion: KDE Manifesto, "web services"
On Sunday, November 10, 2013 19:12 Kevin Ottens wrote: > Hello community, > > In the principles section of the manifesto, we have the following point: > "Projects that choose not to host their web services on KDE infrastructure > need to provide administrative access to the KDE sysadmin team; or, if such > access cannot be granted, a regular backup of all the code and data used by > the web services should be provided to the KDE sysadmins (except if the > service is not an integral part of the project's workflow, community > interactions and public image) to ensure continued availability" > > Don't know how you feel about that one, but it sticks out like a sore thumb > when you look at the other points in the manifesto. All the other points are > short and to the point... but that one is just monstrous. :-) > > It's kind of the pandora box though. The idea is basically we want to ensure > the continuity of online services outside of our infrastructure. I'm > looking for alternative wording for that one. > > I'd be tempted to go with: > "Projects that do not use KDE infrastructure for their online services must > work with the KDE sysadmin team on an agreement to ensure continuity." > > Opinions? > > Regards. Yes. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Proposal: KDE Manifesto wording revision
On Sunday 10 November 2013 18:28:58 Kevin Ottens wrote: > That's what this email is about, I'd like to apply the attached patch, > it's mostly about small scale changes. I don't see anything which > could be controversial in there. > > Any opinions on this? I'd like to collect feedback before proceeding > with a vote of the e.V. membership and then a push. It's really a minor point, but I don't understand the change of * Stand on the shoulders of giants to * To stand on the shoulders of giants Why does this phrase now begin with "To"+verb when all other phrases (still) start with a verb without leading "To"? IMHO the leading "To" makes the phrase sound less personal. When I read the other phrases I mentally add a "You" or a "You can", as in "You can make use of KDE infrastructure [...]", "You benefit from [...]", "You get support from [...]", etc. The leading "To" prevents this. Other than that the changes look good. Regards, Ingo signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Proposal: KDE Manifesto wording revision
On Sunday, November 10, 2013 18:51:06 Kevin Ottens wrote: > On Sunday 10 November 2013 18:45:42 Marta Rybczynska wrote: > > leadin -> leading > > Great, I managed to introduce a typo... Thanks for spotting it. It's fixed you just wanted to see if we were actually reading it ;) other than the typo, and including David E.’s input: +1 from me cheers ... -- Aaron J. Seigo ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Proposal: KDE Manifesto wording revision
On Sunday 10 November 2013 19:03:45 David Edmundson wrote: > There's a change from > > "_can_ be defended via the FLA" > to > "_will_ be protected defended via the FLA" > > (emphasis added by me) > > As I understand it the FLA is opt in (http://ev.kde.org/rules/fla.php) > and does not automatically cover all projects. Which makes it a "can" indeed. Changed back to "can", kept the rest of the change. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] Discussion: KDE Manifesto, "web services"
Hello community, In the principles section of the manifesto, we have the following point: "Projects that choose not to host their web services on KDE infrastructure need to provide administrative access to the KDE sysadmin team; or, if such access cannot be granted, a regular backup of all the code and data used by the web services should be provided to the KDE sysadmins (except if the service is not an integral part of the project's workflow, community interactions and public image) to ensure continued availability" Don't know how you feel about that one, but it sticks out like a sore thumb when you look at the other points in the manifesto. All the other points are short and to the point... but that one is just monstrous. :-) It's kind of the pandora box though. The idea is basically we want to ensure the continuity of online services outside of our infrastructure. I'm looking for alternative wording for that one. I'd be tempted to go with: "Projects that do not use KDE infrastructure for their online services must work with the KDE sysadmin team on an agreement to ensure continuity." Opinions? Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Proposal: KDE Manifesto wording revision
On Sunday, November 10, 2013 18:28 Kevin Ottens wrote: > Hello community, > > After the publication of the initial version of the manifesto, I said I'd > act as curator for the time being and that it should be a living document > which would get updated from time to time. > > I didn't really live up to it so far as no revision has been done. But > somehow I found a small chunk of time today and decided to use it to > prepare a new revision. > > As a matter of fact, I got some feedback from people. Some of the items are > rather large (and I'll send separate emails for those), but there was a > collection of nice wording simplifications. > > That's what this email is about, I'd like to apply the attached patch, it's > mostly about small scale changes. I don't see anything which could be > controversial in there. > > Any opinions on this? I'd like to collect feedback before proceeding with a > vote of the e.V. membership and then a push. > > Regards. I support the changes. Carl ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Proposal: KDE Manifesto wording revision
There's a change from "_can_ be defended via the FLA" to "_will_ be protected defended via the FLA" (emphasis added by me) As I understand it the FLA is opt in (http://ev.kde.org/rules/fla.php) and does not automatically cover all projects. David ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] Discussion: KDE Manifesto, "established practices"
Hello, In the principles, section of the manifesto we have the following point: "The project stays true to established practices common to similar KDE projects unless special considerations force it to deviate". I guess after lengthy discussions you end up with points like that which says... well... nothing really. "Do it like anybody else except if you feel you can't". :-) So, I'm looking for an alternate wording. I think that either we find a way to make it stronger or we should just drop it. It's meaningless as it is. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Proposal: KDE Manifesto wording revision
On Sunday 10 November 2013 18:45:42 Marta Rybczynska wrote: > leadin -> leading Great, I managed to introduce a typo... Thanks for spotting it. It's fixed on my side. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part. ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
Re: [kde-community] Proposal: KDE Manifesto wording revision
leadin -> leading Otherwise I like it. Cheers, Marta On Sun, Nov 10, 2013 at 6:28 PM, Kevin Ottens wrote: > Hello community, > > After the publication of the initial version of the manifesto, I said I'd > act > as curator for the time being and that it should be a living document which > would get updated from time to time. > > I didn't really live up to it so far as no revision has been done. But > somehow > I found a small chunk of time today and decided to use it to prepare a new > revision. > > As a matter of fact, I got some feedback from people. Some of the items are > rather large (and I'll send separate emails for those), but there was a > collection of nice wording simplifications. > > That's what this email is about, I'd like to apply the attached patch, it's > mostly about small scale changes. I don't see anything which could be > controversial in there. > > Any opinions on this? I'd like to collect feedback before proceeding with a > vote of the e.V. membership and then a push. > > Regards. > -- > Kévin Ottens, http://ervin.ipsquad.net > > KDAB - proud supporter of KDE, http://www.kdab.com > > > ___ > kde-community mailing list > kde-community@kde.org > https://mail.kde.org/mailman/listinfo/kde-community > ___ kde-community mailing list kde-community@kde.org https://mail.kde.org/mailman/listinfo/kde-community
[kde-community] Proposal: KDE Manifesto wording revision
Hello community, After the publication of the initial version of the manifesto, I said I'd act as curator for the time being and that it should be a living document which would get updated from time to time. I didn't really live up to it so far as no revision has been done. But somehow I found a small chunk of time today and decided to use it to prepare a new revision. As a matter of fact, I got some feedback from people. Some of the items are rather large (and I'll send separate emails for those), but there was a collection of nice wording simplifications. That's what this email is about, I'd like to apply the attached patch, it's mostly about small scale changes. I don't see anything which could be controversial in there. Any opinions on this? I'd like to collect feedback before proceeding with a vote of the e.V. membership and then a push. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com diff --git a/benefits.markdown b/benefits.markdown index 0cdad69..78ec683 100644 --- a/benefits.markdown +++ b/benefits.markdown @@ -2,19 +2,19 @@ layout: page title: Benefits of a KDE Project --- -Being part of the international KDE community conveys certain benefits and rights. These include: +Being part of the international KDE community conveys certain benefits: -* Stand on the shoulders of giants +* To stand on the shoulders of giants * Make use of KDE infrastructure for project hosting * Benefit from the experience of the KDE sysadmins * Get support from the larger community with development, documentation, translation, testing, bug handling, etc. * Use opportunities to integrate with a large ecosystem of end-user products - * Create cross-pollination of ideas and innovation through interaction with teams sharing common values + * Interact with teams that have common values, leadin to the cross-pollination of ideas and innovations * Enjoy representation and support by KDE e.V. * Participate in Akademy and other KDE events - * Be considered for financial and organizational support - * Know that your trademark can be secured - * Know that your project's license can be defended via the [Fiduciary Licensing Agreement](http://ev.kde.org/rules/fla.php) + * Receive financial and organizational support + * Know that your trademarks can be secured + * Know that your licensing wishes will be protected via the [Fiduciary Licensing Agreement](http://ev.kde.org/rules/fla.php) * Increase your market visibility through the reputation of the KDE community and KDE promotion tools such as: * pushing project announcements to the Dot and employing other KDE promotion channels @@ -24,7 +24,7 @@ Being part of the international KDE community conveys certain benefits and right for communication on web sites and other channels -Principles of a KDE Project +Commitments of a KDE Project Back to the manifesto diff --git a/commitments.markdown b/commitments.markdown index b046224..7824919 100644 --- a/commitments.markdown +++ b/commitments.markdown @@ -1,27 +1,25 @@ --- layout: page -title: Principles of a KDE Project +title: Commitments of a KDE Project --- -The KDE Project designation carries certain principles and requirements: +The KDE Project designation carries with it certain commitments: * Support the [KDE Code of Conduct](http://www.kde.org/code-of-conduct/) * There is no mandatory Contributor License Agreement * Technical requirements * The project stays true to established practices common to similar KDE projects unless special considerations force it to deviate - * 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 * Projects that choose not to host their web services on KDE infrastructure need to provide administrative access to the KDE sysadmin team; or, if such access cannot be granted, a regular backup of all the code and data used by the web services should be provided to the KDE sysadmins (except if the service is not an integral part of the project's workflow, community interactions and public image) to ensure continued availability * Copyrights, trademarks and patents - * [KDE licensing policy](http://techbase.kde.org/Policies/Licensing_Policy) should be respected - * KDE branding guidelines should be respected - * Trademark continuity – if the authors of the software abandon it or disappear, they agree to transfer the trademark to the next maintainer - * Patent License - If the code is covered by patents registered by the project itself, those patents must be licensed freely + * [KDE licensing policy](http://techbase.kde.org/Policies/Licensing_Policy) must be respected + * KDE branding guidelines are
