>>> Il s'agit de détacher la suite bureautique de KDE SC pour mieux s'attaquer à d'autres plate-formes.
Non ça c'est du blabla marketing. Il s'agit en vérité d'arracher KWord des griffes de son mainteneur associal qui emmerde tout le monde. Pour ça il a fallu en passer par ce fork et ce renommage de KOffice en Calligra.
Quelques liens :
http://aseigo.blogspot.com/2010/12/rose-by-any-other-name.ht(...) : "KOffice has experienced an internal fork and in the process has been renamed "Calligra". The fork itself came about through unresolved differences between a member of the KOffice team and the rest of the members over how to manage both long term targets and day-to-day development. This eventually resulted in people coming to the conclusion that those differences were not only unresolved but also unresolvable. "
http://lists.kde.org/?l=koffice-devel&m=128782551919625&(...) : "As you might be aware, after months of discussions, it has been concluded that the best solution is to split the community (...) 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.
# Fork
Posté par patrick_g (site web personnel) . En réponse au journal aptitude install calligra. Évalué à 10.
Non ça c'est du blabla marketing. Il s'agit en vérité d'arracher KWord des griffes de son mainteneur associal qui emmerde tout le monde. Pour ça il a fallu en passer par ce fork et ce renommage de KOffice en Calligra.
Quelques liens :
http://aseigo.blogspot.com/2010/12/rose-by-any-other-name.ht(...) : "KOffice has experienced an internal fork and in the process has been renamed "Calligra". The fork itself came about through unresolved differences between a member of the KOffice team and the rest of the members over how to manage both long term targets and day-to-day development. This eventually resulted in people coming to the conclusion that those differences were not only unresolved but also unresolvable. "
http://lists.kde.org/?l=koffice-devel&m=128782551919625&(...) : "As you might be aware, after months of discussions, it has been concluded that the best solution is to split the community (...) 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.