On 2017 M01 16, Mon 07:48:25 CET Martin Gräßlin wrote:
> Am 2017-01-15 22:58, schrieb Alexander Neundorf:
> > Hi Martin,
> >
> > just replying somewhere...
> >
> > On 2017 M01 15, Sun 14:52:30 CET Martin Gräßlin wrote:
> >> I think that is a reasonable suggestion. If distros patch our
> >> depend
Having been paid to maintain a system that was a maze of #ifdef I
disagree with your statement that a professional should have no problem
with adding them. Sometimes a professional will add them, but not if
there is another choice. Every ifdef adds to the cost of maintenance,
and that is a very un
New draft is up, all changes are to the last section:
* I changed the overall tone from law into strongly suggested
guidelines, with the central idea that sysadmin will only
promise to keep up its end for projects which keep up theirs,
i.e. a reasonable quid-pro-quo hrotocol witj properly c
On 01/16/2017 06:58 AM, Alexander Neundorf wrote:
> - OTOH, if you are maintaining kwin fulltime as paid job, I consider it
> reasonable to expect that the maintainer is able to maintain necessary
> #ifdefs, or apply pragmatic solutions, just to solve the problem for his
> users... but that is
I'll use this as a launching-off point to continue the debate:
Coming out of the weekend, after reflecting a little, I no longer
feel like the extremely hard approach I took in the current draft
is appropriate for the community at large, in line with ade's
concerns of over-democratizing. I don't
