2008-05-26, 21:54
@Equusz, you do not have the full picture so please refrain from making assumptions, (and please do not insult other community members, no matter what they say to you). I highly recommend that you (and everyone else here) read this:
http://www.catb.org/~esr/faqs/smart-ques...l#keepcool
and this:
http://www.catb.org/~esr/faqs/smart-ques...not_losing
In the end it was Elan choice to leave Team-XBMC, (we did not force him no matter what you might hear elsewhere), and I honestly do not think there is anything that we on Team-XBMC or you the users can do to make him come back right now. I do not believe that Team-XBMC put too much pressure on Elan, to summarize it we really only requested for the source code to be released before or at the same time as any binaries (as per the GPL), and that the source code was not committed to the main SVN branch in huge chunks but rather smaller per feature commits. Nor is it my belief that Team-XBMC have too much bureaucracy, you have to understand that as a more than a one man project we need to have some common rules and guidelines (these rules and guidelines are of course open to discussion internally in the team but one single person does not have right to simply refuse to follow the rules and guidelines set before him just because he does not agree with them, try to change them to an acceptable compromise or go with the majority is the correct solution, not let one individual set his own rules).
It is true that both the people on Team-XBMC and the people behind osxbmc.org could have handled the whole situation differently, but what's been done has been done and what's been said has been said. Team-XBMC have learned from the experience and I very much doubt that we will make the same mistakes again.
http://www.catb.org/~esr/faqs/smart-ques...l#keepcool
and this:
http://www.catb.org/~esr/faqs/smart-ques...not_losing
In the end it was Elan choice to leave Team-XBMC, (we did not force him no matter what you might hear elsewhere), and I honestly do not think there is anything that we on Team-XBMC or you the users can do to make him come back right now. I do not believe that Team-XBMC put too much pressure on Elan, to summarize it we really only requested for the source code to be released before or at the same time as any binaries (as per the GPL), and that the source code was not committed to the main SVN branch in huge chunks but rather smaller per feature commits. Nor is it my belief that Team-XBMC have too much bureaucracy, you have to understand that as a more than a one man project we need to have some common rules and guidelines (these rules and guidelines are of course open to discussion internally in the team but one single person does not have right to simply refuse to follow the rules and guidelines set before him just because he does not agree with them, try to change them to an acceptable compromise or go with the majority is the correct solution, not let one individual set his own rules).
It is true that both the people on Team-XBMC and the people behind osxbmc.org could have handled the whole situation differently, but what's been done has been done and what's been said has been said. Team-XBMC have learned from the experience and I very much doubt that we will make the same mistakes again.
