yet another trinity bashing blog post: http://blog.martin-graesslin.com/blog/2012/10/maintaining-history-done-wrong...
werner
Le 14/10/2012 11:41, Werner Joss a écrit :
yet another trinity bashing blog post: http://blog.martin-graesslin.com/blog/2012/10/maintaining-history-done-wrong...
werner
It looks more like a kwin3 bashing article than a trinity bashing article to me ...
On Sunday 14 of October 2012 13:44:12 Francois Andriot wrote:
It looks more like a kwin3 bashing article than a trinity bashing article to me
Sure - Martin is obviously well-known fighter for it us to start throwing away Trinity from basic parts. ...and add into Trinity bases (unwanted) dependence on QT4.
Slavek --
On Sunday 14 of October 2012 11:41:14 Werner Joss wrote:
yet another trinity bashing blog post: http://blog.martin-graesslin.com/blog/2012/10/maintaining-history-done- wrong/
werner
It's very funny that Martin pointed out an bug that in KDE 4.x is still poorly repaired. And for that is quite clear to see that from our side was exemplary cooperation.
But this time Martin can really help (perhaps unwittingly) - from its list of bugs could be something useful for Trinity.
Slavek --
yet another trinity bashing blog post:
http://blog.martin-graesslin.com/blog/2012/10/maintaining-history-done-wrong...
There are two points worth noting.
We should avoid depicting a public image that we are a large group of people. Yes, we have "international" participation but that is all. Believe in what we we do, but be humble about our size. We are what we are. Nothing more, nothing less.
This is the second time we've seen this statement that we make this claim. Does anybody know where we provide that image? Web site? Wiki? Source code?
The "tq" conversion did raise hell for us for a few months and we paid dearly for that, even losing some good developers. As I wrote previously, we should be ready to admit that period was a rough time. We have fixed most of those bugs --- but not all, as they still appear. Yesterday I posted a patch for libtqt-perl because the package was not building correctly due to inadvertent "tq" changes. No software project escapes occasional SNAFUs, regardless of how skilled the participants might be. Therefore we should be humble about that episode in project history and move onward.
All we can do is release stable products and believe in ourselves. Mind our own business and be content with what we are doing. Our concern is not what others are doing or saying.
I believe 3.5.13.1 is a good release that yes, fixed many of the "tq" bugs. I believe R14 will be better.
In the end, with each temper tantrum he posts, all Martin does is tarnish his own reputation, not Trinity.
I recommend (highly) that we do not participate in such debates. Just keep our heads pointed toward the row we are furrowing.
Darrell
On Sunday 14 of October 2012 20:27:54 Darrell Anderson wrote:
In the end, with each temper tantrum he posts, all Martin does is tarnish his own reputation, not Trinity.
Incidentally, it is also interesting to see the difference in our and their community of programmers. When discussing with them now on patch funny mentioned by Martin, now on me requires to have a patch prepared for their current GIT tree.
When I imagine, how Martin still flaunts the fact that he offered to help, that we will demanded patches prepared for our GIT tree ;)
Slavek --
Incidentally, it is also interesting to see the difference in our and their community of programmers. When discussing with them now on patch funny mentioned by Martin, now on me requires to have a patch prepared for their current GIT tree.
When I imagine, how Martin still flaunts the fact that he offered to help, that we will demanded patches prepared for our GIT tree ;)
Well, technically, he "offered" to help --- but only if we adopted kwin4. ;)
As I wrote, let's just ignore the noise and mind our own business. :)
Darrell
http://blog.martin-graesslin.com/blog/2012/10/maintaining-history-done-wrong...
"The problem is that we don’t handle patches through bug reports, for that we have to many reports." .. LOL