Hello Stefan,
First, thanks for a better balanced response.
Your welcome.
1. we contributed with code, a function necessary for BIG applications with
characteristics we and others might have = a solution to the problem
A function you think its necessary and we don't. Lets keep the facts.
Normal behaviour is:
1. thank you, as one of you did on the bug list
I did. As you might have noticed, usually I am the one scheduling the bugs.
2. second evaluate the contribution
We did, well T did.
3. come up with facts, discussion and questions, no imaginations, attacks and
theoretical ideasirregularities like T was doing
He came up with some questions and and the discussion went well enough but it
was never about either is is useful if you have your use case or not. The
question what it was about was, if its general enough to put it into the
framework or not. Thats what I said in the last mail.
4. why not ask the community about new additions?
Do you really think we should ask the community about every enhancement we
implement? No, we sure don't because the community in general trusts us that we
are doing a great job on such decisions.
5. then decide if you want to take it in or just keep it as available code
Sure, thats what we haven't but I (personally) still think that this use case
is not general enough to put it into the framework.
Frankly, we do not care if it is taken into the qooxdoo code or not. It is not
our goal by sharing our solutions.
The best point here is, that you will understand what problems developers out
there have and you will get ideas, new ideas.
Thats why we are maintaining that mailing list. Don't forget that this is a
free service where you usually get help within 24 hours. Someone, to be
specific, 1&1 is paying us for maintaining this list, just as a little reminder
that we sure do know why we are having the project open source and not closed.
This point T has totally forgotten and shadowed by arrogance instead of
patience and calm.
He has not shadowed that but he has simply another opinion that you have when
it comes to the question if that is general or not. And by the way, we want to
keep it on a professional level so please don't call other here on the list
arrogant.
>You wrote "checked in" and as this is a term usually used for repositories,
>that was a simple clarification.
Checked in or not... It is a game of words. You know very well what was meant.
Clarifications can be done in many ways.... This one was not a good one.
Sure, we did know what it was about. But not every subscriber reads every mail
on that list and i would guess that most of them only read the headlines which
said... i don't need to explain it again. Still, he just cleared something out
and you call him arrogant, how to compare that?
BIG difference between assume and know! It was a rhetorical question and that
means that, we hope this was not the opinion of the core team. We didn't say
that we know anything!!!
Thats good to know. But just to let you know, usually everyone of core team
reads the mails on the list and if someone would totally disagree with T.
opinion, he would have talked to him. So if someone of the core developers is
answering, its in the most cases, the whole teams opinion. In doubt, ask the
technical responsible for the framework.
>We would appreciate a more professional attitude! Thanks!
>As we would too. ;)
We contributed and get attacked.... that is all!!!
Which is an excuse for attacking back? No, I don't think so.
But, Martin, we have never claimed to put it into the framework! Read the
correspondence again!
Ah, why did you then open an enhancement bug report for that? Ok, you want to
contribute but I don't get why you are so passionate about it and start an
discussion on the mailing list?
1. You say so. We have never seen. Show us those apps! How big are they etc....
That would be useful for new users to know.
We have everything documented on out homepage, as you can see:
http://qooxdoo.org/community/real_life_examples#gmx_webmaillarge-scale_qooxdoo_app
2. image-combine and many other functions are also "a single precompilation
step" and can also be done by a command line tool...and you have no control of
the developers images!!!! Different? No, it is not!
As I said, I'm not willing to discuss technical details with you. I understand
you technical details but thats not the point.
Your arguments are weak both technically as well as structurally in this case.
Just a little hint here. Thats attacking me in person which is, usually, not a
good idea if you want someone do something. I don't know if english is your
natural language or not but here in germany, that would be considered as rude
and not professional.
You are stuck in stone!
So as you. To be honest, I don't think you think that we have experience in
building big applications, building a framework and know whats important and
what not. Am I right with that?
Martin, why don't you instead say: THanks for the contribution and we will look
at it and see if it might be a function we would like to implement or not.
I did in the bug. You mentioned it some lines above yourself.
That is all...we contribute with NO demands at all... we don't care if you use
it or not....we just would like to make it easier to someone else who might get
the
same problem as we did, and that is all.
Thats honorable for sure. But you still have to accept the decision we make
here in the core team if thats worth including with all the side effects for
us. Have you ever thought of that what side effects that could have?
Regards,
Martin
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
