'Re: one more bit of unasked-for input on the forking of the KOffice'

[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: Sven Langkamp <sven.langkamp () gmail ! com>
Date: 2010-10-30 1:12:08
Message-ID: AANLkTimaxpCJdMZKG6ARyWdfsYEi+qBgWQ-q3f9rxcF+ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On Fri, Oct 29, 2010 at 8:22 PM, Aaron J. Seigo <aseigo@kde.org> wrote:

> hi everyone...
>
> i hope you won't mind one more bit of unsolicited input on the recent fork
> in
> this community. feel free to ignore any or all of it, of course :)
>
> ======
>
> personally, i find it unfortunate and sad that it has come to this, simply
> because it is never nice to see splits in any community, especially ones
> that
> we are a part of. sometimes things get to the point where it is the only
> workable solution left, and after discussing various relevant issues with a
> few different people in koffice over the last year i can understand how
> that
> may be the case here. still, it's unfortunate.
>
> such circumstances do present an opportunity to grow and strengthen,
> however.
> i am hopeful that is what will happen here.
>
> koffice iteslf is not a strategically significant component for KDE. that
> may
> sound harsh, but i believe it to be true today. the user base is small,
> years
> of releases did not culminate into a (market-)significant product over the
> same time span in which 2.0-4.0 of the KDE SC was develped and released,
> etc.
>
> it has provided some great value for KDE, however: it has helped strengthen
> kdelibs, it has brought KDE some very positive light and recognition via
> key
> involvement with ODF and some apps like Krita and Kexi have had their well
> deserved moments of shining in the press. and of course those of us who use
> KOffice applications are deeply grateful for it.
>
> however, the truth is that without KOffice, KDE itself would continue on
> without a huge shift in direction or even a huge hit on brand values. ergo,
> it
> isn't (today) strategically significant. but it could be.
>
> many of you here are working directly towards that and making immense
> strides
> to making KOffice applications very signficant, be it Kexi's continue
> movement
> forward (and the communication around that movement! so key!) or the office
> document veiwer for mobile or various other efforts underway. there is a
> huge
> amount of work being done on KOffice these days, as evidenced by the commit
> logs and the review requests that appear on the list. i do believe that one
> day KOffice can be a very signficant technology group for KDE from a
> strategic
> POV.
>
> being in this "in between" state means that KOffice has the space to make
> significant shifts without risking too much value in the process. if this
> had
> to happen, now is a "good" time.
>
> it probably also means that as this happens, a significant effort will be
> required to turn KOffice into what it could be. this can't be news to
> anyone
> involved with KOffice :) this isn't a technical challenge, though, but a
> predominantly social one.
>
> those of you most intimately involved with KOffice have the challenging
> task
> of gelling a recently fractous group oriented in a useful direction. there
> are
> issues of tone and quality of communication on the mailing list, commitment
> to
> certain kinds of ettiquette and shared expectations in goals, marrying the
> needs of disinterested commercial contributors (e.g. 3rd party contractors)
> with interested commercial participants (e.g. those building companies
> and/or
> products around KOffice software) with community contribution.
>
> having met many (most? all?) of you in person over the years, i truly
> believe
> that each and every one of you are decent people with good hearts and great
> commitment. the technical abilities in this group also speak for themselves
> and are not to be a source of concern. without these things, it's unlikely
> that KOffice could succeed, but fortunately it has this solid foundation to
> build upon.
>
> however, i am greatly concerned about the future of KOffice due to one
> outstanding issue:
>
> KOffice has not had a track record of consistent, productive leadership.
> imho,
> this continues to this day.
>
> leadership is a skill, separate from other social skills and certainly
> separate from technical ones. leadership brings people together, helps
> enforce
> social contracts and norms and protects that community from outside poison
> when necessary. it is proactive when it can be, humble when it needs to be
> and
> thinks about the overall system of people involved when making decisions.
> leadership searches for consensus and makes hard decisions when called for
> that reflect the values inherent to that community. leadership is not
> forced
> on others, it is made available and attracts people to it.
>
> this is why it takes effort and deterination to develop leadership as a
> skill.
> it's also why it is the kind of asset that makes or breaks many projects,
> communities and human endeavours.
>
> i've been trying to become a marginally proficient leader for much of my
> adult
> life, and i still have so far to go .. it's not a trivial skill, but even
> in
> small amounts it can have profound effect.
>
> so while KOffice has many great people involved with it and a lot of very
> exciting activity, i'm not sure that there is a demonstrated level of
> profound
> leadership within the community here. and without that, KOffice will imho
> remain at risk of these kinds of problems festering and being created.
>
> if the "natural leaders" in KOffice have not already, i would very much
> encourage you to get books on the topic, find literature on leadership on
> line, maybe even find and enroll in leadership training courses.
>
> knowing that some of you are already investing significantly in KOffice in
> other ways, this would be another kind of investment to consider making to
> protect your existing and future monetary and effort based investments.
>
> just my 0.02. :)
>

I agree that leadership is part problem. I think the recent development of
the Krita community shows the way out. Since the 2.0 the Krita developer
team has tripled in size, there is a growing community of non-developer
community members and Krita is reaching for user-readyness in 2.3.

I think there are several things:

Most important is that the Krita team trusts the work of every team member.
Development is very open. People are allowed to make mistakes and these will
resolved collaborative. That's something I'm missing in the a part of the
KOffice community. Too often peoples work is blocked, trashed in endless
dicussions and reverts.

Vision. Last year we developed a vision for Krita. It's just three
sentences, but is provides a guide for the further Krita development. I
think the Krita vision lead to a much better working application as it
allowed us to focus on the important things. For the other applications we
don't have a formal vision. That leads to a situation where team members
have different opinions about features that are important or not e.g. about
the importance of MS Office compatibility.

The Leadership thing. There is the big goal of user-readyness that we want
to reach, but my impression is that we are not really getting closer to it.
After more than four year of development in 2.x the core applications are
still not ready, which is just bad. Krita development did suffer from times
where we did open too many construction sites and I see the same happening
in KOffice too. There were some advanced features done before the basic
functionality was working good. The users don't use KOffice because it's too
unstable and not because it's missing features.

These are the things that a fork (and the other suite) need to solve to
become successful.

[Attachment #5 (text/html)]

<div class="gmail_quote">On Fri, Oct 29, 2010 at 8:22 PM, Aaron J. Seigo &lt;<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>&gt; \
wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; \
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> hi everyone... 
 
i hope you won&#39;t mind one more bit of unsolicited input on the recent fork in 
this community. feel free to ignore any or all of it, of course :) 
 
====== 
 
personally, i find it unfortunate and sad that it has come to this, simply 
because it is never nice to see splits in any community, especially ones that 
we are a part of. sometimes things get to the point where it is the only 
workable solution left, and after discussing various relevant issues with a 
few different people in koffice over the last year i can understand how that 
may be the case here. still, it&#39;s unfortunate. 
 
such circumstances do present an opportunity to grow and strengthen, however. 
i am hopeful that is what will happen here. 
 
koffice iteslf is not a strategically significant component for KDE. that may 
sound harsh, but i believe it to be true today. the user base is small, years 
of releases did not culminate into a (market-)significant product over the 
same time span in which 2.0-4.0 of the KDE SC was develped and released, etc. 
 
it has provided some great value for KDE, however: it has helped strengthen 
kdelibs, it has brought KDE some very positive light and recognition via key 
involvement with ODF and some apps like Krita and Kexi have had their well 
deserved moments of shining in the press. and of course those of us who use 
KOffice applications are deeply grateful for it. 
 
however, the truth is that without KOffice, KDE itself would continue on 
without a huge shift in direction or even a huge hit on brand values. ergo, it 
isn&#39;t (today) strategically significant. but it could be. 
 
many of you here are working directly towards that and making immense strides 
to making KOffice applications very signficant, be it Kexi&#39;s continue \
movement forward (and the communication around that movement! so key!) or the \
office document veiwer for mobile or various other efforts underway. there is a \
huge amount of work being done on KOffice these days, as evidenced by the \
commit logs and the review requests that appear on the list. i do believe that \
one day KOffice can be a very signficant technology group for KDE from a \
strategic POV. 
 
being in this &quot;in between&quot; state means that KOffice has the space to \
make significant shifts without risking too much value in the process. if this \
had to happen, now is a &quot;good&quot; time. 
 
it probably also means that as this happens, a significant effort will be 
required to turn KOffice into what it could be. this can&#39;t be news to anyone 
involved with KOffice :) this isn&#39;t a technical challenge, though, but a 
predominantly social one. 
 
those of you most intimately involved with KOffice have the challenging task 
of gelling a recently fractous group oriented in a useful direction. there are 
issues of tone and quality of communication on the mailing list, commitment to 
certain kinds of ettiquette and shared expectations in goals, marrying the 
needs of disinterested commercial contributors (e.g. 3rd party contractors) 
with interested commercial participants (e.g. those building companies and/or 
products around KOffice software) with community contribution. 
 
having met many (most? all?) of you in person over the years, i truly believe 
that each and every one of you are decent people with good hearts and great 
commitment. the technical abilities in this group also speak for themselves 
and are not to be a source of concern. without these things, it&#39;s unlikely 
that KOffice could succeed, but fortunately it has this solid foundation to 
build upon. 
 
however, i am greatly concerned about the future of KOffice due to one 
outstanding issue: 
 
KOffice has not had a track record of consistent, productive leadership. imho, 
this continues to this day. 
 
leadership is a skill, separate from other social skills and certainly 
separate from technical ones. leadership brings people together, helps enforce 
social contracts and norms and protects that community from outside poison 
when necessary. it is proactive when it can be, humble when it needs to be and 
thinks about the overall system of people involved when making decisions. 
leadership searches for consensus and makes hard decisions when called for 
that reflect the values inherent to that community. leadership is not forced 
on others, it is made available and attracts people to it. 
 
this is why it takes effort and deterination to develop leadership as a skill. 
it&#39;s also why it is the kind of asset that makes or breaks many projects, 
communities and human endeavours. 
 
i&#39;ve been trying to become a marginally proficient leader for much of my \
adult life, and i still have so far to go .. it&#39;s not a trivial skill, but \
even in small amounts it can have profound effect. 
 
so while KOffice has many great people involved with it and a lot of very 
exciting activity, i&#39;m not sure that there is a demonstrated level of \
profound leadership within the community here. and without that, KOffice will \
imho remain at risk of these kinds of problems festering and being created. 
 
if the &quot;natural leaders&quot; in KOffice have not already, i would very much 
encourage you to get books on the topic, find literature on leadership on 
line, maybe even find and enroll in leadership training courses. 
 
knowing that some of you are already investing significantly in KOffice in 
other ways, this would be another kind of investment to consider making to 
protect your existing and future monetary and effort based investments. 
 
just my 0.02. :) </blockquote></div> I agree that leadership is part problem. I \
think the recent development of the Krita community shows the way out. Since the 2.0 \
the Krita developer team has tripled in size, there is a growing community of \
non-developer community members and Krita is reaching for user-readyness in 2.3. \
 I think there are several things: Most important is that the Krita team \
trusts the work of every team member. Development is very open. People are allowed to \
make mistakes and these will resolved collaborative. That&#39;s something I&#39;m \
missing in the a part of the KOffice community. Too often peoples work is blocked, \
trashed in endless dicussions and reverts. Vision. Last year we developed a \
vision for Krita. It&#39;s just three sentences, but is provides a guide for the \
further Krita development. I think the Krita vision lead to a much better working \
application as it allowed us to focus on the important things. For the other \
applications we don&#39;t have a formal vision. That leads to a situation where team \
members have different opinions about features that are important or not e.g. about \
the importance of MS Office compatibility. The Leadership thing. There is the \
big goal of user-readyness that we want to reach, but my impression is that we are \
not really getting closer to it. After more than four year of development in 2.x the \
core applications are still not ready, which is just bad. Krita development did \
suffer from times where we did open too many construction sites and I see the same \
happening in KOffice too. There were some advanced features done before the basic \
functionality was working good. The users don&#39;t use KOffice because it&#39;s too \
unstable and not because it&#39;s missing features. These are the things that \
a fork (and the other suite) need to solve to become successful.

_______________________________________________
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] 