kdiagram in calligra project component?

[Jaroslaw Staniek]

On 5 September 2016 at 02:47, Friedrich W. H. Kossebau <kossebau at kde.org> wrote:
>
> Hi Jarosław,
>
> Am Montag, 5. September 2016, 01:03:32 CEST schrieb Jaroslaw Staniek:
> > Hi,
> > Background: The kde:sysadmin/repo-metadata git repo now replaces the
> > project.kde.org stuff.
> > I am moving kdb, kreport and kproperty repo metadata to projects/calligra
> > from playground/libs as I see them more fit to the new location and they
> > are, well, developed within our master project Calligra anyway, regardless
> > of repo fragmentation.
> >
> > That's not my play, the kde:releaseme tool which I'd be trying to use for
> > preparing releases depends on the projects metadata so it's good to have
> > the metadata as correct as possible.
> >
> > Now, that's mostly a question to Friedrich:
> >
> > There is projects/extragear/graphics/kdiagram. It describes "Powerful
> > libraries (KChart, KGantt) for creating business diagrams". Do you think
> > that kdiagram better fits to calligra/ and not so much to graphics/?
> > KChart clearly implements office-oriented objects: data charts and Gantt
> > charts.
>
> For one, those paths in the repo hierachy are just legacy and long-term will
> be dropped, for a flat list of repos.

That changes some of what I wrote but not the directory hierarchy, right?

> Then, that description is copied unchanged from marketing-buzzword loaded
> origin :)
>
> I had put kdiagram into projects/extragear/graphics after discussion as
> diagrams can be used for lots of things. There is a (business) world outside
> offices :)
> Current users known to me of either KChart or KGantt are Massif-Visualizer,
> something in KDEPIM, KMyMoney, Plan, a Calligra shape plugin and a KReport
> plugin.
> So KDiagram is a project shared by many KDE projects, nothing Calligra-centric
> there. So I do not see a reason to move this.

There's a graph for project organization, there's graph related to
what purposes are supported.
We won't simplify that in other way than tagging.
On thing sure is that the two libs from KDiagram form a framework. So
is the place within frameworks/ too? See my question below.

> More, as long as that legacy adressing hierarchy of repos exists, I would
> rather recommend to move non-Calligra-only stuff like KDb, KReport & KProperty
> somewhere into the generic extragear namespace, as those libs target
> developers, unlike the "apps" which make up what currently is known as
> Calligra and what is about end user products. By being in the generic
> extragear namespace this might help stressing the libs general usability
> outside of the existing set of Calligra apps.

I'd like to be consistent with what we said about extragear. You
didn't like it in the "State of Proposal to improving KDE Software
Repository Organization" thread and also Ben "would like to see the
Extragear moniker dropped." I agree.

I have to admit that I had to run deep-search to find kdiagram dir in
sysadmin/repo-metadata.git. I can imagine people may need the same for
kdb, etc.

Question: Based on what we say here ideally I'd like the
KDb/KProperty/KReport to be seen as projects/frameworks/. Is it right
place? At many levels there's no connection for these projects with
KF5.

Please review the current draft https://phabricator.kde.org/D2659 -
from what already not very right solution.

> My 2 cents on that :)

Thanks.

-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek