Review Request: remove unmaintained plugins from Calligra

Boudewijn Rempt boud at valdyas.org
Fri Apr 20 07:29:02 BST 2012


On Friday 20 April 2012 Apr, Cyrille Berger wrote:
> On Thu, 19 Apr 2012 16:35:27 +0200, Jaroslaw Staniek <staniek at kde.org>
> wrote:
> > On 19 April 2012 14:18, Inge Wallin <inge at lysator.liu.se> wrote:
> >>
> >>
> >> I see this comment a lot, but in practice it's not true. I have never
> >> seen anybody ask "did you once have a good implementation of what I am
> >> about to do but remove it?" before starting any effort. It just doesn't
> >> happen.  If you go ahead and remove all of the modules in the list,
> could
> >> you at least create a page (say Calligra/Deletions)  on
> community.kde.org
> >> that clearly lists what is removed, and how to get it back. At least we
> >> will have a trail that we can point people to.
> > 
> > 
> > How about keeping the directories empty  with only README that
> > explains what the plugin is supposed to do and where to look for
> > archived code?
> > Or if this still looks like a pollution of the filesystem, maybe we
> > can keep obsolete/ directory with such empty dirs?
> 
> I think a single OBSOLETE file at the root of calligra source directory
> is more than enough. And that file would contains a link to the wiki and
> the branch that contains the obsolete stuff.
> 
> 

Okay. I will add that. Another question: should we retain the googledocs plugin? It's currently not usable, and we're getting bugs reports about. Mani -- are you still working on it?

-- 
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl



More information about the calligra-devel mailing list