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

List:       koffice-devel
Subject:    Re: Tasks for newcomers,
From:       Yue Liu <opuspace () gmail ! com>
Date:       2010-12-19 11:24:23
Message-ID: AANLkTikS49FzEoZMBRrUQHX8vC=0rb3DLeXFnLnDFsKk () mail ! gmail ! com
[Download RAW message or body]

Hello Brian,

I'm the maintainer of Calligra Flow (used to be Kivio). If you are
interested in flow charting tool you can join us on
calligra-devel@kde.org . Flow is thirsty for developers now, I planned
to blog about that but currently busy with my college affairs. I've
come up with a lot of ideas and hope that Flow will be released in
Calligra 2.4 and capable for basic uses. In KOffice trunk the code of
Kivio is two years old (I just started coding for Kivio recently and
in a long time Kivio had no maintainers), so it would be a better
choice to join Flow if you want to see a usable flow charting tool as
soon as possible.

Yue Liu

On Sun, Dec 19, 2010 at 12:34 PM,  <brian@amason.net> wrote:
>
>> coinstallable. The problem would be between calligra 2.4, and a potential
>> 2.4
>
> I can see the point of a upgrade from 2.3 to 2.4, but my point is since
> there is a fork, I'd assumed the parts on both sides of the fork will use
> different names. Hence their own sets of code, and my confusion on why
> they are conflicting going forward. It's not analogous to KDE 4.4 and 4.5,
> but more like XFree86 and X.Org. Right? Or is this an EOL event for
> KOffice? I mean, from what I've been able to piece together, it seems to
> be an end to KOffice, as it seems all of the KOffice maintainers are going
> to Calligra, except for KWord. So KWord remains and all the other KOffice
> apps now have no maintainers. Then someone is taking up the fork of KWord
> to Calligra. At least that's the understanding I've taken from lurking
> here.
>
>> As to why it is not worth the effort, in the event something get released
>> from
>> koffice/trunk, I find it unlikely that a user would want to have both
>
> Again, should someone take up maintaining the KOffice apps, they would
> have to rename them, correct? So you would not have two conflicting Kexi
> 2.4 apps? But potentially two Kexi-based apps using potentially the same
> libraries. But it is not a given that they are going to be conflicting.
>
>
>> so .. a fair amount of work indeed, but it's all CMakeLists.txt workso not
>> particularly hard and not particularly risky either. it can even happen in
>> a
>> git branch while everyone else continues to work on the code.
>>
>> you also have people here like Brian who are just looking for some way to
>> get
>> involved. to quote his email:
>>
> ...
>>
>> now, assuming Brian is actually telling it like it is, maybe he would like
>> to
>> take this CMakeLists.txt work on so that Calligra becomes fully
>> self-contained
>> on install. as a new contributor, he'll need some help and will certainly
>> have
>> questions as he goes .. but it's perfect "first time contributor" work
>> because
>> it isn't deeply technical _and_ Brian will get an awesome overview of the
>> entire codebase.
> Hmmm, huge chance at global destruction, small chance of success? I love it.
>
> Guaranteed to nullify time with my family... Priceless?
>
>>> I'm new here, and have been holding back on contributing, mostly because
>>> I
>>> don't know which project I'm supposed to help with; Project A, B or 6 of
>>> 9.
>>> All this drama doesn't help either.
>> I can't help you to choose (I am obviously biased ;) ) What I can suggest
>> to
>> you is to come and irc (on both channel #koffice and #calligra) and talk
>> to
>> people and see with who you get along. Also, right now code base are still
>
> Well, being a old coder, I don't generally play well with others. ;')
> Kind of like writing my own code, my own way. Not that, I was able to do
> that for most of my career. I have participated in many teams and led a
> few, and conformed to company standards. More or less. But then I've been
> running my own company for almost 6 years now. It will be interesting to
> be part of a team again.
>
> I came here, because I was interested mostly in a helping to make a better
> flow charting system for Linux. Kivio had the best interface, imo. Hence
> the reason for joining the list. I need a professional flowcharting tool
> in Linux. If that means writing it so be it.
>
> Brian
>
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
_______________________________________________
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]