Jean-Marc Lasgouttes wrote:
"Bo" == Bo Peng <[EMAIL PROTECTED]> writes:

We are supposed to manage a project, not just write code.
Bo> For this particular problem, I have declared WONT FIX for qt <
Bo> 4.2.2. There are a lot more severer bugs there and it would be a
Bo> waste of time to work on a fixed bug. People who believe
Bo> saveState/restoreState can magically solve all problems are
Bo> welcome to do so.

It is not necessarily this particular problem that worries me. I was
worried to see how little concerned some of us can be about these
problems.

Let's just concentrate on the remaining bugs. If there would be some packaging problems, we will resolve them; it will take the time it will take, that's it. Nothing to be afraid of, really.

[Beware, personal opinion below]

And mine below :-)

> More generally, our problem is that we do not have a maintainer right
> now. Lars was very good for this job, especially because he can be
> rude when needed. Unfortunately, his presence is virtual currently and
> even his recent come-back was not really convincing (Lars, come back!
> We love you!). We need someone who says "no!" or "stop that!". I am
> not very good at this game myself, and this is definitely not
> something that I enjoy doing.

I think on the contrary, that the greater liberty in the project has resulted in much more good things than bad things. OK, some commits are sometimes stupid (some of my last ones being examples) but we are responsible enough to recognize the problem, if any, and act upon it. I was vocal last time because it was friday, I thought that it was clear. We should probably stop this tradition because it has some bad side effects apparently.

I think something weird happened to the team. We were in real need of
new blood, because many of us did not have enough time. The new blood
came, but the new developers have been too active and too numerous
(which was not difficult actually) to be incorporated smoothly.

I find on the contrary that, generally, a very good spirit is planning on the list. I think there is a lot of cooperation between the developers and that a particular feature is now being done by two or three people at the same time. This is a very good sign, and not a sign of useless competition at all. This shows that a greater and greater number of people now _knows_ and _understands_ the code.

There
is a real need to have everybody join at some meeting and find
a better common ground than the one we have currently. I know that
some of us are fond of competition,

I am not personally and I think that most of us are not. Give me the names so I can shoot them ;-)

but if the result is that either
the oldtimers or the newtimers lose interest, I am not sure LyX will
be able to continue in an useful form. I guess all projects have this
kind of problems, but it is not very enjoyable.

Repeat after me: there is no problem! I don't understand why you are so scared of potential break down or something...


Some probably find it weird that I have such a dark view of the
situation at the time where we are going to unleash a very good
release. I find that weird too. It is probably all the tension leaving
scars on me.

I think that there is too much drama over every little point right now. I don't see the situation as dramatic at _all_. Come on, at Christmas last year would you have bet that a faster, cleaner, prettier, LyX-1.5 would be released in about a year after 1.4? Why don't you all rejoice instead of being fearful of what might turn bad.

Abdel.

Reply via email to