'Re: KOffice split'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: KOffice split
From:       Johannes Simon <johannes.simon () gmail ! com>
Date:       2010-10-29 12:09:21
Message-ID: C11AB478-F96E-4823-B863-F4799AD42F87 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

FYI, KChart will go with group B, as decided by its contributors.

Johannes.

Am 23.10.2010 um 11:16 schrieb Cyrille Berger Skott:

> Dear fellow members of the community,
> As you might be aware, after months of discussions, it has been concluded that the \
> best solution is to split the community. However, the split is going to happen at \
> application level. The maintainer of each application will be asked to consult his \
> fellow developers to decide in which group, A or B, the application will lived. The \
> other group is free to fork the application under a different name. It is also \
> possible for the developers to change the application name and ask that the current \
> name is not used by any of the group. This can be used as an opportunity for a \
> fresh start. Currently, to the best of my knowledge the groups are composed of the \
> following applications: Group A: KWord
> Group B: KPresenter, Krita, Karbon, Kexi
> Since the license give the right for a fork, I can already mention that Group B \
> will come with a fork of KWord, under a name that has yet to be decided. Group A is \
> free to fork any application of Group B under a different name. Maintainers have \
> until Sunday October 31th to decide with which group to go. Applications that have \
> not choosen a group will have to be renamed by each group. The KDE e.V. board will \
> be asked to decide what happen to the KOffice name, the KOffice website, the \
> KOffice mailing list, KOffice.org, KOffice wiki and the KOffice bugzilla product. \
> The recommendation from members of the CWG is to retire the name KOffice \
> altogether, which will allow both side to start on a fresh start and leave the past \
> behind. Then the application maintainers and developers of each group will have one \
> week to find a new name for their suite, and move to another place in the KDE \
> subversion tree and to rename or remove the applications that are in the other \
> group. In the meantime, I am suspending the KOffice release process, meaning that I \
> will release Beta 3, but that the date for the following release is undefined. The \
> reason is that I do not feel confident that the splitting will happen in time \
> before the RC1, and I do not think it is a good idea to ship a RC release that will \
> get different applications than the final release. If the splitting takes more \
> time, I will proceed with one more beta. I also advise each group to ensure that \
> they have a release coordinator. I will urge readers of this letter to:
> 1) refrain discussion around the splitting outside the mailing list, or to do so in \
> private conversation 2) acknowledge, that at this point there is no sense in trying \
> to place the blame anywhere, we just have to accept the fact 3) remain civilised \
>                 and polite in this difficult moment
> -- 
> Cyrille Berger Skott
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel

[Attachment #5 (unknown)]

<html><head><base href="x-msg://35/"></head><body style="word-wrap: break-word; \
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">FYI, KChart will \
go with group B, as decided by its \
contributors.<div><br></div><div>Johannes.<br><div><br><div><div>Am 23.10.2010 um \
11:16 schrieb Cyrille Berger Skott:</div><br \
class="Apple-interchange-newline"><blockquote type="cite"><span \
class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; \
font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: \
normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; \
white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: \
0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; \
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; \
"><div style="font-family: 'DejaVu Sans Mono'; font-size: 9pt; font-weight: 400; \
font-style: normal; "><div style="white-space: pre-wrap; margin-top: 0px; \
margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">Dear \
fellow members of the community,</div><p style="white-space: pre-wrap; margin-top: \
0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; \
"></p><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; \
margin-left: 0px; margin-right: 0px; text-indent: 0px; ">As you might be aware, after \
months of discussions, it has been concluded that the best solution is to split the \
community.</div><p style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; \
margin-left: 0px; margin-right: 0px; text-indent: 0px; "></p><div style="white-space: \
pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; \
text-indent: 0px; ">However, the split is going to happen at application level. The \
maintainer of each application will be asked to consult his fellow developers to \
decide in which group, A or B, the application will lived. The other group is free to \
fork the application under a different name. It is also possible for the developers \
to change the application name and ask that the current name is not used by any of \
the group. This can be used as an opportunity for a fresh start.</div><p \
style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; \
margin-right: 0px; text-indent: 0px; "></p><div style="white-space: pre-wrap; \
margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; \
text-indent: 0px; ">Currently, to the best of my knowledge the groups are composed of \
the following applications:</div><p style="white-space: pre-wrap; margin-top: 0px; \
margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "></p><div \
style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; \
margin-right: 0px; text-indent: 0px; ">Group A: KWord</div><div style="white-space: \
pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; \
text-indent: 0px; ">Group B: KPresenter, Krita, Karbon, Kexi</div><p \
style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; \
margin-right: 0px; text-indent: 0px; "></p><div style="white-space: pre-wrap; \
margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; \
text-indent: 0px; ">Since the license give the right for a fork, I can already \
mention that Group B will come with a fork of KWord, under a name that has yet to be \
decided. Group A is free to fork any application of Group B under a different \
name.</div><p style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; \
margin-left: 0px; margin-right: 0px; text-indent: 0px; "></p><div style="white-space: \
pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; \
text-indent: 0px; ">Maintainers have until Sunday October 31th to decide with which \
group to go. Applications that have not choosen a group will have to be renamed by \
each group.</div><p style="white-space: pre-wrap; margin-top: 0px; margin-bottom: \
0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "></p><div \
style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; \
margin-right: 0px; text-indent: 0px; ">The KDE e.V. board will be asked to decide \
what happen to the KOffice name, the KOffice website, the KOffice mailing list, <a \
href="http://KOffice.org">KOffice.org</a>, KOffice wiki and the KOffice bugzilla \
product. The recommendation from members of the CWG is to retire the name KOffice \
altogether, which will allow both side to start on a fresh start and leave the past \
behind. Then the application maintainers and developers of each group will have one \
week to find a new name for their suite, and move to another place in the KDE \
subversion tree and to rename or remove the applications that are in the other \
group.</div><p style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; \
margin-left: 0px; margin-right: 0px; text-indent: 0px; "></p><div style="white-space: \
pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; \
text-indent: 0px; ">In the meantime, I am suspending the KOffice release process, \
meaning that I will release Beta 3, but that the date for the following release is \
undefined. The reason is that I do not feel confident that the splitting will happen \
in time before the RC1, and I do not think it is a good idea to ship a RC release \
that will get different applications than the final release. If the splitting takes \
more time, I will proceed with one more beta. I also advise each group to ensure that \
they have a release coordinator.</div><p style="white-space: pre-wrap; margin-top: \
0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; \
"></p><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; \
margin-left: 0px; margin-right: 0px; text-indent: 0px; ">I will urge readers of this \
letter to:</div><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: \
0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">1) refrain discussion \
around the splitting outside the mailing list, or to do so in private \
conversation</div><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: \
0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">2) acknowledge, that at \
this point there is no sense in trying to place the blame anywhere, we just have to \
accept the fact</div><div style="white-space: pre-wrap; margin-top: 0px; \
margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">3) \
remain civilised and polite in this difficult moment</div><p style="white-space: \
pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; \
text-indent: 0px; "></p><div style="white-space: pre-wrap; margin-top: 0px; \
margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">-- \
</div><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; \
margin-left: 0px; margin-right: 0px; text-indent: 0px; ">Cyrille Berger \
Skott</div>_______________________________________________<br>koffice-devel mailing \
list<br><a href="mailto:koffice-devel@kde.org">koffice-devel@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/koffice-devel">https://mail.kde.org/mailma \
n/listinfo/koffice-devel</a><br></div></span></blockquote></div><br></div></div></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] 