Hi Cyrille, Am Freitag, 22. März 2013, 14:46:18 schrieb Cyrille Berger: > Hi, > > On 2013-03-21 22:51, Friedrich W. H. Kossebau wrote: > > Hi Cyrille, > > > > at the Calligra Sprint two weeks ago Braindump was found to be > > actually > > unmaintained, at least the last commit to braindump from you seems to > > be from > > june last year, while there are still a few bugs open (even from > > yourself :) > > )* > > > > Would you agree to this finding? > > No I don't, I object to them :)
Okay, fine to see you still overlooking (and using?) Braindump :) > > Or is it just feature complete for you, > > It is definitely basic features complete. There are a couple of > possible improvements, there are a couple of features that are > desirable, but it has everything it needs to function properly. But it > is true that most of the improvement to braindump are being done by you > guys right now... in shapes plugins :) And there is still an outstanding > feature, that I had like to tackle one of these days, having an always > visible text tool (a bit like in Krita, but without dragging around, and > supporting only the regular text box). But that is more a usability > improvement than a really big required feature. > > > and the few bugs are not in your way? > > Yeah, I would classify the bugs, as: > > need more info: > https://bugs.kde.org/show_bug.cgi?id=266377 > > can't reproduce: > https://bugs.kde.org/show_bug.cgi?id=285873 > https://bugs.kde.org/show_bug.cgi?id=291178 Possibly time to ask the reporters to reproduce their problems with the latest Braindump, then close these bugs? > don't know how to fix, except by throwing XMLGui to the trashbin: > https://bugs.kde.org/show_bug.cgi?id=299161 Seems a bug in XMLGUI with default menus being dumped if not filled on initial creation, have found two workarounds, soon coming up with a review request :) > most likely not a braindump bug: > https://bugs.kde.org/show_bug.cgi?id=298145 > > and finaly, a bit annoying, but really mostly a problem for other > applications that use the webshape: > https://bugs.kde.org/show_bug.cgi?id=304368 > > > Can we officially declare that we are looking for a new maintainer > > for > > braindump, e.g. by a blog entry? > > Lets say it like this, I would not mind having someone come and take > over maintainership and develop new features, and bring braindump to the > next level :) > I would say it is current status is low maintenance, ie, reproducible > bugs fixing, but no new features development. Okay. So it would be better you who blog about this then :) And you might need to recall the word being out of maintainership for Braindump being searched, as spread by http://slangkamp.wordpress.com/2013/03/16/calligra-sprint-2013/ and http://blogs.kde.org/2013/03/10/fruits-css2013 > > If so, would you blog about this yourself? Or could you give some > > cite which I > > could use in a blog post of mine? Perhaps some additional ideas (or > > inspiring > > mockups) you have, to help people get the idea of Braindump and what > > they > > would like to use/develop it for? > > Now the question is if this blog is specifically about getting > maintainer or about attracting contributors to underdeveloped area of > calligra that might interest some people. > > > PS: I personally would like to take over and e.g. add features I like > > from > > DeepaMehta (http://deepamehta.de/en). But my TODO list has lots of > > higher > > priority stuff... ;) > > Feel free :) Thanks. Next year (tm). Perhaps... ;) Cheers Friedrich _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel