<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>Hi,</div><div><br></div><div>> WARNING! This post is a rant, expresses only my own opinion and feelings <br>> might be harmed during the course of this reading. <br><br>> *<RANT>* <br><br>> This post is a reaction to a thread on the dev list where Bogdan was <br>> lamenting on the lack of commitment to the project. <br>> I found it both laughable and pathetic in the sense that NOTHING is done to <br>> make it a project you can be committed to, and I'll expose, IMHO, why. <br><br>Until now I find your remarks very insulting ... <br><br>> 1) *This is a one man (and a half, sorry Ray), "benevolent despot" kind of <br>> project.* <br><br>I'm not going to accept you to insult Ray ! Ray's contribution is not <br>half ! <br>Because
Ray dedicate his free time to this project, now 4000+ users <br>can use this <br>project on windows and mac ! What have you done for this project ? <br><br>> Bogdan IS the project. Every single decision is made by him without <br>> discussions nor appeal. He has his vision for the project (that I didn't <br>> find, but it could be hidden in one of the zillions places the project is <br>> scattered into. More on this later) and I don't feel like he is open to <br>> discuss/challenge this vision. <br><br>I'm confused ! First you say that "He has his vision for the project <br>that I didn't <br>find .. " then you say "I don't feel like he is open to discuss/ <br>challenge this vision." ! <br>If you don't know my vision, how can you say that I'm not open to <br>discuss it, <br>did we ever discuss it ? <br><br>Anyway, my expectations for this project are
here: <br><a target="_blank" href="http://community.kde.org/index.php?title=Necessitas">http://community.kde.org/index.php?title=Necessitas</a><br><br>We (you and me) had a few discussions before, but I don't remember I <br>have been that close... <br>We talk about menus and about look&feel plugin, I remember that we <br>had different approaches on this topic, you wanted add android <br>look&feel only to <br>your QML, I didn't agreed, because I still want to support class <br>widgets. <br>It means that I'm not open to discuss? Please give me more hints on <br>this matter ! <br>BTW Android 9patch is more complex than the standard, so, you can't <br>use <br>QML BorderImage (qDrawBorderPixmap) to draw the images ! <br><br>> This is human. AFAIK Bogdan created the project and feels he has all rights <br>> on it (which he has), but that prevents real involvement from
others. <br>> Fact is, if Bogdan is unavailable, the project just plain stops. <br><br>Every community project, is based on meritocracy: <br>You code/contribute, then you have the right to make decisions ! <br><br>> 2) *NOTHING is done to make it a community project.* <br><br>> I already ranted about this, but the scattering of the project resources is <br>> just plain ridiculous, laughable and a HOWTO not to make a coherent project. <br>> Wiki on sourceforge, 1 mailing list on kde and 1 on google groups, 1 bug <br>> tracker on sourceforge and 1 on google code, unclear/hidden master <br>> repository, unclear contribution process, which leads me to: <br><br>If you search this mailing list you'll find all the informations you <br>need: <br>- regarding HOWTO and other information: The sf.net pages was written <br>by Damine Treg, <br>sadly he didn't had time to
continue, so I asked may times for peoples <br>help ! <br>Nobody wanted to do it! I can't do everything by myself ! <br>- 1 on google groups - this is a high traffic general mailing list <br>used by everybody. <br>- 1 mailing list on kde - this one is a low traffic mailing list <br>used only by developers, I don't have time to read all posts on <br>google. <br>- 1 bug tracker on sourceforge and 1 on google code - it was discuss <br>many times before, ONLY bug tracker on sourceforge should be used. <br>- unclear/hidden master repository: check <a target="_blank" href="http://community.kde.org/Necessitas/Repositories">http://community.kde.org/Necessitas/Repositories</a><br>- unclear contribution process, as I already said to you before is not <br>may fault ! <br><br>> 3) *What the f... does necessitas has to do with KDE?* <br><br>> I only assume Bogdan and Ray
are KDE devs and that it is easy for them to <br>> host necessitas's master git and "contribution process" on KDE, but this is <br>> VERY wrong from a necessitas perspective. KDE might have its own <br>> contribution process but it is irrelevant to us and ridiculous for a <br>> necessitas contributor to have to register a kde account to be able to use <br>> reviewboard, itself, IMHO, a very obscure and complicated system for code <br>> contribution vs. what is existing in github or gitorious. <br>> Obviously, all merge requests in the gitorious clone are ignored. <br>> Pretty please, make gitorious the main repository, use gitorious merge <br>> request system and do whatever KDE stuff you fancy do in your own KDE <br>> corner. <br><br>It has everything to do with KDE! Necessitas *IS* a KDE project ! <br>Again, searching this list will give you enough
informations. <br>I'll try to summarize: When I released first alpha I had to put <br>Ministro libs somewhere, <br>I used some free servers to put the libs, but it was not a good <br>solution. I dedicated my <br>free time to this project and I didn't wanted to give also my money, <br>so I had to find <br>a reliable solution, back then Nokia just joined Microsoft, to fight <br>against android, <br>so, I had to join somebody, KDE was the natural choice, we share the <br>same goal: <br>To keep QT free and powerful. <br><br>Regarding contributions: We want to upstream everything, the problems <br>are: <br> - Nokia doesn't accept contributions without accepting and sign their <br>contributors agreement, <br> - I can't move the project to qt-project.org (they don't want it yet <br>because is not finished) <br> so you can't accept their agreement,
when you publish your patch. <br> - The ONLY solution was to "force" contributors to release their code <br>under BSD or public domain. <br><br>> 4) *Accept contribution, reject them, discuss them or ask for update, DON'T <br>> rewrite them*. <br><br>> Crying for contribution, then taking some parts of a patch to rewrite it <br>> you way, mostly incompatible with the original patch, is NOT the way to go <br>> to motivate contributors. <br><br> Again I find some of your remarks very insulting, I'm not "crying" <br>for contribution ! <br> I'm happy to have more contributor, but i'm not crying ! <br><br> Some time is easier/faster to rewrite them, then to reject a patch <br>or to <br>ask for updates ! e.g. the menus patch that you sent [1], it didn't <br>work at all, <br>but I've seen a lot potential, so I decide to make it work [2] ! <br>I
*CREDIT YOU FOR YOUR WORK* and I push a working version, so, <br>what was wrong in that ? <br><br> Probably you are frustrated because I had to revert your last <br>patch, <br>because it was a fiasco, it made the applications almost unusable, is <br>that my fault ? <br>Probably it is, because I trust your patch and I didn't run and check <br>all the tests before push it ! <br>The problem is to run and check all the tests it takes too much (1-3 <br>days). <br><br>> 5) *The project is sloooooowwwwww*. <br><br>> Due to 1), 2) and Bogdan's limited availability, necessitas is slow to <br>> progress in its own right. I kind of made my own necessitas fork to move <br>> on, and due to 4) it has diverged so much from the main trunk that I'm not <br>> sure I'll bother rebasing. <br><br>> 6) *Maybe related to 3), I don't know if it is necessitas or KDE, but
one <br>> should definitely learn about the "git rebase" command*. <br><br>> All the merges coming from I don't know which branches makes the git <br>> repository unreadable. The proper way to merge upstream is to rebase and <br>> resolve conflicts. Merging upstream is pure lazyness. <br><br>WOW you are so good! We didn't know about "git rebase" command !!! <br>Of course you forgot to learn that you can't use "git rebase" command <br>when more than one people is using that branch ! <br>Check <a target="_blank" href="http://lwn.net/Articles/328438/">http://lwn.net/Articles/328438/</a> for more info on this topic. <br><br>Merging with upstream is NOT lazyness, is responsibility ! <br><br>> *Bottom line*: <br><br>> *Necessitas is NOT a community project*. <br><br>> Unless the issues outlined are addressed, It is pointless to whine about <br>> necessitas' lack
of contribution. <br>> I suspect many of the more knowledgeable potential contributors will just <br>> take the trunk and adapt it to their needs, without bothering trying to <br>> contribute it back. Unless the project becomes more community friendly, I'm <br>> open to contribute to a potential fork. <br><br>> *</RANT>* <br><br>I'm open to discuss what is wrong with my vision ! <br>I'm open to know other people vision, so, please share your vision <br>with us! <br><br>Don't forget that this project is based on meritocracy! Even if you <br>have a vision, remember that you must to code it, not only to discuss <br>it ! <br><br>To be clear: I'm open to discuss, but I'm not going to "cry" for <br>contributors or to accept contributions with insults in the same <br>box ! <br><br>> Best Regards <br>> - Chris - <br><br>[1] <a target="_blank"
href="https://git.reviewboard.kde.org/r/103934/diff/#index_header">https://git.reviewboard.kde.org/r/103934/diff/#index_header</a><br>[2] <br><a target="_blank" href="https://projects.kde.org/projects/playground/mobile/necessitas/androi">https://projects.kde.org/projects/playground/mobile/necessitas/androi</a>... <br><br>Cheers, <br>BogDan. <br></div> </div></body></html>