On Saturday, November 19, 2011 21:03:50 Thomas Friedrichsmeier wrote:
> I don't want to play the blame-game. But I'm really worried about this
> tendency to take essential discussions to side-channels. So I'm sorry to
it worries me, too. we need to realize that it was our behaviour here on k-c-d
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103188/
---
Review request for kdelibs and Richard J. Moore.
Description
---
This
Hi,
I don't want to play the blame-game. But I'm really worried about this
tendency to take essential discussions to side-channels. So I'm sorry to
continue on one of those another lengthy meta discussions.
On Saturday 19 November 2011, Aaron J. Seigo wrote:
> On Thursday, November 17, 2011 18:
On Saturday, November 19, 2011 12:22:33 Alexander Neundorf wrote:
> How about doing something similar for the frameworks stuff ?
> Use k-c-d, but prefix the subject with "KF5" or something.
that does not prevent people from derailing the discussions by sending off-
topic emails. noise is, unfortun
On Thursday, November 17, 2011 18:17:30 Alexander Neundorf wrote:
> If the signal to noise ratio here is considered too low, then having the KF5
> discussions here
> * would have increased the signal, and thereby increased the SNR
this assumes that the tendency to noise on this list would not prev
On Saturday 19 November 2011, Aaron J. Seigo wrote:
> On Thursday, November 17, 2011 16:21:55 Steven Sroka wrote:
> > True, but then shouldnn't those interested in reviewboard patches go
> > read what's on the reviewboard?
>
> the point of having them CC'd here is so that discussion of patches are
On Thursday, November 17, 2011 16:21:55 Steven Sroka wrote:
> True, but then shouldnn't those interested in reviewboard patches go
> read what's on the reviewboard?
the point of having them CC'd here is so that discussion of patches are
visible to everyone involved in kdelibs development. with th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks, last month a team of three young developers and one
non-devel were sponsored by Google to Google's first documentation
sprint, along with 3 other teams: OpenMRS, OpenStreetMaps, and Sahana
Eden. Each team wrote a book that week which was publ
