When this issue cropped up on the mailing list, I went and reviewed the archive. You link to Michael finally "snapping", and even then he wasn't rude or out of place at all; I agree with Michael that the emails in the archives speak for themselves.
Michael seems extremely patient and completely professional - traits that I find productive in any environment. He's given you multiple chances to drop it, and even offered to welcome you back if you changed your communication methods. You're clearly extremely talented - which is absolutely useless without the soft skills to get your changes considered effectively. Perhaps brushing up on interpersonal communication would be beneficial. In any event, I think if everyone just said, "Gee, I got heated, I am sorry, we can all learn from this", we could all move on and FPC would be better for it. A split in a community that is already small is detrimental for new users and is unprofessional from a business perspective - how would we expect a business to use tools from a community that can't even agree enough to produce canonical items, or work to resolve technical issues without serious fracture? On Fri, Dec 21, 2018 at 11:48 AM Maciej Izak via lazarus < [email protected]> wrote: > pt., 21 gru 2018 o 19:28 Travis Ayres via lazarus < > [email protected]> napisał(a): > >> There needs to be provisions for making people full time to work on >> FPC/Lazarus as well - >> "Foundation makes provision {document or processes} for administrative >> costs, in order to make their application transparent and in consideration >> of the valuable time of contributors, with Foundation approval and as >> documented in {Living document Y}". >> > > This would be good. I think that clear rules are always fine. Also the > very important is to not concentrate all power in the hand of one person > without any control (for example in much smaller project like NewPascal I > don't have exclusive control). Some time ago I was involved in many parts > of work in FPC compiler (generics.collections, management operators other > fixes for compiler and new features in progress) but in the case of > personal conflict, project has no instance of appeal or regulations or any > code of conduct. So instead of coding I need to waste time to shows what > happened. Sadly... > > It looks like David's fight with Goliath. Anyway the truth is important. > > All is fine when someone has the same opinion like Michael Van Canneyt. > The style of communication with Michael is visible in this thread, when he > know he is not right he is just ignoring messages, but he is first to throw > the rock. He is using power - not arguments. No one can do anything because > he has full control on all infrastructure. > > Admin, lead of project, programmer and foundation ruler in one person? Too > much power always corrupts. > > -- > Best regards, > Maciej Izak > -- > _______________________________________________ > lazarus mailing list > [email protected] > https://lists.lazarus-ide.org/listinfo/lazarus >
-- _______________________________________________ lazarus mailing list [email protected] https://lists.lazarus-ide.org/listinfo/lazarus
