[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: one more bit of unasked-for input on the forking of the KOffice
From: Cyrille Berger Skott <cberger () cberger ! net>
Date: 2010-10-29 22:03:47
Message-ID: 201010300003.47334.cberger () cberger ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Aaron,
I thank you for your input. I am sure it will be useful in the future to avoid
mistakes of the past.
However, I will make two notes:
1) I understand that the split came as a surprise to many people out of the
inner circle of KOffice. But as it has been pointed out, the difficulties in
the community are not a recent issue, also over the years many attempt to
solve those issues has been tried. Many more solutions could be tried.
Someday, you have to ask the question whether the problems can be solved,
whether trying does not have a higher cost to the project than a radical
approach. What has happened is that a group of developers thinks that now
enough is enough, the cost of trying is not worth the cost the project is
paying.
2) No one thinks the split is a good solution. And I mean *no* *one*. I do not
even think it could be qualify of "best", at most you can say "less worse".
Lets face it, at the end of the day, the project, or what is going to survive
after the split, is going to lose one of its main contributor. This is a net
loss. It is also having a direct negative impact on the image of the project.
Thus, this is not a decision that was taken lightly, it is the result of a
long process and several months of discussions.
--
Cyrille Berger Skott
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" \
content="1" /><style type="text/css"> p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'DejaVu Sans Mono'; font-size:9pt; \
font-weight:400; font-style:normal;"> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">Hi Aaron,</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">I thank you for your input. I am sure it will be \
useful in the future to avoid mistakes of the past.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">However, I will make two \
notes:</p> <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">1) I understand that the split came as a surprise to many people \
out of the inner circle of KOffice. But as it has been pointed out, the difficulties \
in the community are not a recent issue, also over the years many attempt to solve \
those issues has been tried. Many more solutions could be tried. Someday, you have to \
ask the question whether the problems can be solved, whether trying does not have a \
higher cost to the project than a radical approach. What has happened is that a group \
of developers thinks that now enough is enough, the cost of trying is not worth the \
cost the project is paying.</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">2) No one thinks the split is a good solution. \
And I mean *no* *one*. I do not even think it could be qualify of "best", \
at most you can say "less worse". Lets face it, at the end of the day, the \
project, or what is going to survive after the split, is going to lose one of its \
main contributor. This is a net loss. It is also having a direct negative impact on \
the image of the project. Thus, this is not a decision that was taken lightly, it is \
the result of a long process and several months of discussions.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">-- </p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Cyrille Berger \
Skott</p></body></html>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic