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

List:       koffice-devel
Subject:    Tasks for newcomers,
From:       brian () amason ! net
Date:       2010-12-19 4:34:45
Message-ID: 15a4ae37bc7f971c3ed3d4b4ebcbca14.squirrel () www ! amason ! net
[Download RAW message or body]


> 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
[prev in list] [next in list] [prev in thread] [next in thread]