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... we
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 le
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 wh
On Monday, November 11, 2013 12:16:38 Peter Grasch wrote:
> These people can not expected to know that deviating in case of special
> considerations is standard practice within the KDE community.
not at all. the key phrase is "established practices”. so, the established
practice of, say, respecti
On Sunday 10 November 2013 16:47:43 Carl Symons wrote:
> "The project stays true to established practices common to similar KDE
> projects."
Could be a solution indeed. Anybody against it apart from Peter?[*]
Cheers.
[*] @Peter, I read your points. I understand the worries and I think they got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2013 06:35 PM, Aaron J. Seigo wrote:
> On Monday, November 11, 2013 12:16:38 Peter Grasch wrote:
>> These people can not expected to know that deviating in case of
>> special considerations is standard practice within the KDE
>> community.
>
On Tuesday, November 12, 2013 10:52:45 Peter Grasch wrote:
> On 11/11/2013 06:35 PM, Aaron J. Seigo wrote:
> > On Monday, November 11, 2013 12:16:38 Peter Grasch wrote:
> >> These people can not expected to know that deviating in case of
> >> special considerations is standard practice within the K
On 11/12/2013 06:35 PM, Aaron J. Seigo wrote:
> 1) where exceptions are appropriate, they are encoded into the individual
> descriptions of “established practices”. we have a commit policy, for
> instance; it probably has exceptions to its guidelines. those exceptions
> belong in the commit poli
On Tuesday, November 12, 2013 21:45:40 Peter Grasch wrote:
> On 11/12/2013 06:35 PM, Aaron J. Seigo wrote:
> > 3) if there are undefined escape clauses in the “what it means to be a KDE
> > Project”, even if we don’t intend them to be used in that manner, people
> > will use them to justify behavio
Hi all,
Sorry to top-post, but this is getting wordier and wordier and I have
long lost trace of what is said. Could we have a tl::dr wrap-up,
please?
On Tue, Nov 12, 2013 at 2:54 PM, Aaron J. Seigo wrote:
> On Tuesday, November 12, 2013 21:45:40 Peter Grasch wrote:
>> On 11/12/2013 06:35 PM, Aa
On Tuesday 12 November 2013 18:38:24 Myriam Schweingruber wrote:
> Hi all,
>
> Sorry to top-post, but this is getting wordier and wordier and I have
> long lost trace of what is said. Could we have a tl::dr wrap-up,
> please?
>
> On Tue, Nov 12, 2013 at 2:54 PM, Aaron J. Seigo wrote:
> > On Tuesda
On Tuesday, November 12, 2013 18:38:24 Myriam Schweingruber wrote:
> Sorry to top-post, but this is getting wordier and wordier and I have
> long lost trace of what is said. Could we have a tl::dr wrap-up,
> please?
my position:
* “special considerations” is ill defined and can be applied to near
On Tuesday 12 November 2013 21:45:40 Peter Grasch wrote:
> On 11/12/2013 06:35 PM, Aaron J. Seigo wrote:
> > which established practices did Necessitas not follow?
>
> I would argue that "Use kdelibs" would be an "established practice" in
> KDE but I recognize that there was/is some disagreement as
Am Mittwoch, 13. November 2013, 20:32:26 schrieb Kevin Ottens:
> On Tuesday 12 November 2013 21:45:40 Peter Grasch wrote:
> > On 11/12/2013 06:35 PM, Aaron J. Seigo wrote:
> > > which established practices did Necessitas not follow?
> >
> > I would argue that "Use kdelibs" would be an "established
On Wednesday 13 November 2013 20:57:51 Olaf Schmidt-Wischhöfer wrote:
> Am Mittwoch, 13. November 2013, 20:32:26 schrieb Kevin Ottens:
> > On Tuesday 12 November 2013 21:45:40 Peter Grasch wrote:
> > > On 11/12/2013 06:35 PM, Aaron J. Seigo wrote:
> > > > which established practices did Necessitas
Hey guys,
sorry for not replying sooner, I just got back from some travel.
I completely agree that the old language was essentially meaningless
when it comes to "enforcement" but I thought that this was more or less
on purpose: Lax language allows us to convey the idea (do, how we do)
without nee
On Monday, November 18, 2013 23:41:04 Peter Grasch wrote:
> three of your use cases fail completely without a clear definition of
> what constitutes an "established practice".
The established practices are defined in individual documents. We have the
commit policy, the kdelibs coding style, the a
On 11/19/2013 12:20 AM, Aaron J. Seigo wrote:
>> a.) keep the language as is: "Legally" meaningless, just to convey intention
>
> It is worse than meaningless: it was formulated in a way that will eventually
> be abused.
Without a definition of "established practices", so could -
theoretically -
I have a more complete response to this email elsewhere, but this is important
enough to warrant its own short email:
On Tuesday, November 19, 2013 00:46:12 Peter Grasch wrote:
> Just for the record: I never said that the actual practices should be
> documented in the manifesto but that imo there
On 18.11.2013 17:31, Aaron J. Seigo wrote:
If people really feel the name, the “established practices” could link to:
http://techbase.kde.org/Policies
This would be much like how the CoC is linked to rather than included in the
Manifesto. The language on the Policies page would
On Monday 18 November 2013 17:40:36 Thomas Pfeiffer wrote:
> On 18.11.2013 17:31, Aaron J. Seigo wrote:
> > If people really feel the name, the “established practices” could link to:
> > http://techbase.kde.org/Policies
> >
> > This would be much like how the CoC is linked to rather than includ
On 11/19/2013 01:31 AM, Aaron J. Seigo wrote:
> On Tuesday, November 19, 2013 00:46:12 Peter Grasch wrote:
>> Just for the record: I never said that the actual practices should be
>> documented in the manifesto but that imo there should be references to
>> the full text of what people are committin
22 matches
Mail list logo
