Jürgen Spitzmüller wrote:

> Well, Georg, on the other hand, please realize that Uwe is currently
> the only person actively working on tex2lyx, and he really tries hard
> to get things on par. Not everyone has the same coding skills (I
> certainly count myself to the lower rank of the scale), and this can
> be frustrating for others. But we should be glad that people do care
> for the rather neglected and uncool parts of the code. Uwe is putting
> much effort in many of these areas (tex2lyx, installer,
> documentation), and I do not think he deserves this kind of bashing.

I definitely appreciate his work. I also did not complain about coding 
skills. I have lerned myself a lot from LyX developers, and if somebody has 
questions how to handle a particular problem he always gets help. In fact, 
this is something that works extremely well in LyX (as compared to some 
other projects).

However, this needs some prerequisites: Developers need to ask for comments 
if they are unsure, or if they do controversal changes. As an example, I 
still have a pending patch for the footmisc package. You and Jean-Marc 
raised concerns, and therefore it is not yet in (although it would 
technically work). This is perfectly OK with me: The discussion uncovered 
some issues I was not aware of, so I need to find a better solution. Uwe, 
please try hard in the future to work in a similar way: Ask for comments 
before committing for all changes that are either complicated or that might 
be controversal. Of course this slows the initial development down, but IMO 
this is no problem at all. If you sum up over all developers it will cost 
less time than committing first and discussing afterwards. It will also make 
it less likely that broken changes go into the stable branch

I wrote the message cited by Jürgen when I was really frustrated: I got a 
lot of trac emails, started to investigate, others did so as well and 
finally discovered the problems, and my work was wasted. To me it looked 
like the problematic changes went in quickly without testing. As we 
understand now this was caused by an unlucky combination of reasons, so it 
hopefully does not happen again, and I hope that all is OK now.


Georg

Reply via email to