[Kmymoney-devel] I really apologize.

Alvaro Soliverez asoliverez at kde.org
Tue Sep 7 20:12:59 CEST 2010


Apologies accepted.

I am touchy about certain topics. Censorship or disregarding
non-contributor messages are examples. I have a thick skin, but I also
do believe that certain comments cannot go unanswered, not to answer
you (you are entitled to your opinion),but to make my position clear
to others.

Myself, I have stopped reading your emails, save for a very light
reading, long time ago. We don't get along and I can live with it.
There are other developers in this project and they can handle your
requests. Keep contributing as you see fit, and I'm sure they'll
answer.

I'm just the one who helps triage bugs on the tracker and the mailing
lists, ie. I help clarify the problem so other people can solve them.
My expertise is limited to reports and forecast and I try to stay away
from the rest for as far as I can.

You may want to use more neutral words in the future. Censorship is a
strong word by any definition. Next time, just write asking whether
people got your message or not. It happens all the time. Mails get
sucked away into hyperspace, servers hiccup. No one thinks of
ill-faith when that happens.

Regards,
Alvaro


2010/9/7 Χρήστος Σιουλής <CSioulis at dsa.gr>:
> Alvaro,
>
> I REALLY appreciate your enormous contribution on this wonderful
> project, and I REALLY want to apologize for some 'extreme' expressions
> on these lists.
>
> It is long time now, that there is a 'bad mood' in our conversations,
> and I REALLY don't like it.
>
> As I have tried to tell you in another thread, I believe that the
> biggest part for this is emanated from misunderstandings in my
> expressions -given that many of my used words come directly for
> greek-english dictionaries.
>
> ON the other hand, I also believe that you are very 'touchy' and a lot
> of times you stick at the finger and not at the point that this finger
> shows.
>
> I am not a developer and I can't  (I really don't have the time/skills
> to understand C++, object oriented programming, 'classes', 'voids',
> 'cmakes', and all these, to) contribute directly to the code of
> KMyMoney, BUT I have also spent a lot of hours to debug and comment
> (even using dictionaries!) this project - I hope constructively- and I
> am really proud for this (small) contribution.
>
> I use KMyMoney basically for complex business transactions (I Know that
> it is mainly a "personal accounting program") by using many tricks (i.e.
> duplicating special preformed transactions), and I don't conceal my
> interesting in enriching KMyMoney with more Business features and my
> willing to assist on such direction.
>
> If all these consist an 'undesired participation' in the project by the
> main developer's group, I really would like to know it and abandon any
> more efforts.
>
> Thank's
>
> Christos Sioulis
> (S. Chris)
>
>
> On 07-09-2010, 11:47 -0300, Alvaro Soliverez wrote:
>> You mention censorship. That is unwarranted. There is not a single
>> event in our history where we censored someone.
>> I take that kind of accusations very seriously, and I think it's
>> undeserving. Not only did you not apologize, you up the stakes.
>> Thank you very much.
>>
>> And you bring up contribution again, which is not what we are talking
>> about here. You must have an issue with that, I don't.
>>
>>
>>
>> 2010/9/7 Χρήστος Σιουλής <CSioulis at dsa.gr>:
>> > Sorry about my doubts, but my message at the "original" KDE maillist
>> > archives in
>> > http://mail.kde.org/pipermail/kmymoney-devel/2010-September/003361.html
>> > it is shown in my PC exactly as in the attached screenshot! (only one
>> > paragraph!)
>> >
>> > Given this (which I can't explain and for this I ask if there is any
>> > kind of inconsistency at KDE track system), I thing that it is a little
>> > undeserved to me to be accused for "baseless accusations".
>> >
>> > For me, 1+1 in a compatible system MUST ALWAYS make 2, not 3.
>> > And no reason such as "I contribute, YOU not" may change this! Period.
>> >
>> > S.Chris
>> >
>> > (PS: this message DOES need approval from you ! -due the size of the
>> > attached screenshot!) :-)
>> >
>> >
>> > On 07-09-2010, 07:16 -0300, Alvaro Soliverez wrote:
>> >> Is this the message you are referring to? I think we had the privilege
>> >> to receive it completely.
>> >>
>> >> Your comments are your own. Please stop throwing baseless accusations.
>> >>
>> >>
>> >>
>> >> On Mon, Sep 6, 2010 at 4:25 PM, csioulis <csioulis at dsa.gr> wrote:
>> >> > https://bugs.kde.org/show_bug.cgi?id=249844
>> >> >
>> >> >
>> >> > csioulis <csioulis at dsa.gr> changed:
>> >> >
>> >> >           What    |Removed                     |Added
>> >> > ----------------------------------------------------------------------------
>> >> >                 CC|                            |csioulis at dsa.gr
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --- Comment #9 from csioulis <csioulis dsa gr>  2010-09-06 21:25:39 ---
>> >> > Dear Stefan,
>> >> > I totally disagree with the expression "The payee should be definitely per
>> >> > transaction, not per split", especially when the transaction is a "transfer"
>> >> > (as it is in your report) where two -or more- accounts (=not one account and
>> >> > some categories, like in deposits and at withdraws) are involved.
>> >> > Both Memo, Payee (and 'No') fields SHOULD BE 'per split' in this occasion, and
>> >> > it SHOULD BE easy to entry, see and edit any of them per split.
>> >> >
>> >> > From my point of view, there are much more situations where you would like to
>> >> > be able to assign different Payee, Memo and No values at the two (or more)
>> >> > splits of a transfer transactions to avoid some inconsistencies in KMyMoney!
>> >> > For example, if you credit your supplier when you receive goods and, then, in a
>> >> > next day, you pay him, you need to assign in "Payee" field: a) his name in your
>> >> > asset account (cash or checking) from where you pay him, and b) your name (or
>> >> > even your partner's name -if you are a company) as a "payer" to his (liability)
>> >> > account (where you debit the amount of the transfer), to have the right balance
>> >> > in his payee view. (see the 'WONTFIX" Bug No 141364 for details).
>> >> > My way to overcome this is to change/modify the payee at the "half-part" of the
>> >> > transfer transaction  (in supplier liability ledger) for the first time and
>> >> > then, for every next payment to this supplier I duplicate this "half-corrected"
>> >> > (with the different Payees in each split) transaction editing only the date and
>> >> > the amount (and maybe the memo) fields!
>> >> >
>> >> > So, the problem that you describes exists, but IMHO it is problem of the
>> >> > data-entry GUI especially in transfer transactions, not of the data structure.
>> >> > If only you had in front of you both of "Pay From" and "Pay to" payees fields
>> >> > to fill in in the data entry form, you should resolve a lot of issues - such as
>> >> > this in the current bug report.
>> >> >
>> >> > It is more than 1 year that I insist that there are a lot of problems about
>> >> > transfers in KMyMoney -see post http://forum.kde.org/viewtopic.php?f=69&t=29110
>> >> > "Transfer need DUAL Payee, Memo and No fields in form to entry" for some argues
>> >> > on it.
>> >> >
>> >> > Another useful thread on this issue (with many links to similar discussions)
>> >> > you can see at:
>> >> > http://sourceforge.net/mailarchive/forum.php?thread_name=w2p64e15f8f1004281745xfa74a637m912461f8d45e3b4d%40mail.gmail.com&forum_name=kmymoney2-developer
>> >> > (started at 25/4/10 by Charles Merriam)
>> >> >
>> >> > I hope that I will find soon the time to write analytic bug reports and
>> >> > proposes about the "transfer issue".
>> >> > S. Chris
>> >> >
>> >> > --
>> >> > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
>> >> > ------- You are receiving this mail because: -------
>> >> > You are the assignee for the bug.
>> >> > _______________________________________________
>> >> > KMyMoney-devel mailing list
>> >> > KMyMoney-devel at kde.org
>> >> > https://mail.kde.org/mailman/listinfo/kmymoney-devel
>> >> >
>> >
>> >
>
>
>


More information about the KMyMoney-devel mailing list