Posts: 99
Joined: May 2008
Reputation:
0
As a new community member, I'm sorry to see this happen. I run both Linux and OS X (all on Apple hardware) and have enjoyed being able to use the same database no matter what OS I happened to be running.
Posts: 146
Joined: Feb 2008
Reputation:
0
My concern is for the users. If something is team driven and team members come and go the project can hopefully stay fairly on track.
If some if more focused or driven by one individual and that person decides to leave is hard for the reaming people to keep things going.
Elan took on a load by starting this up and getting it going. And many people have come on board since, and some have left. But now that it's forked if Elan were to have no part in it (at a point in the future) where does that leave the rest of the OSXBMC team and the users. Hopefully not not up the creak without a paddle.
I'd like to know there are some solid legs to stand on long.
You can't get someone hooked and then leave them feeling like their supplier might get out of the business without some clean plan.
=)
Posts: 323
Joined: Feb 2008
Reputation:
0
Jeremeymc, we're committed, we won't leave you high and dry, the XBMC-team is welcome to access our code and implement it in their products as they wish, as jmarshall noted there will be compatibility between both versions that will remain.
Posts: 5
Joined: May 2008
Reputation:
0
I am glad that you are going along with the product on a different road!
It's a very important project for the mac in my opinion. I like to help the team in any way I can (Graphics, testing, function suggestions, some money etc.)
Posts: 341
Joined: May 2008
Reputation:
1
It must be difficult for those developers who got close and now find themselves in an uncomfortable situation socially. A bit like an amicable divorce.
That being said, perhaps from a user's point of view getting OSX information and discussions will now be easier. Half the replies here would end with: "oh, I didn't realize you were using the OSX version". There is a big cultural difference between OSX, Windows and Linux. To have things in sync across this divide is very difficult and probably ends up in compromises and discussions that don't serve anyone. There's a reason why people prefer certain platforms. I doubt the solution is to aim for the least common factor.
As long as there are enough developers to form a vibrant OSX group then that sounds ideal to me. I don't particularly care for situations where OSX is an afterthought of some Windows or Linux project. I guess the one worry is that not only does a media app on the Mac have to worry about other platforms but it's not as though Front Row will be standing still forever.
pmcd
Posts: 420
Joined: May 2004
Reputation:
0
yuvalt
Retired Team-Kodi Member
Posts: 420
My personal note on this:
About a year ago I started the linux port (on which the OSX heavily relies). When I started this project I was part of TeamXBMC in all senses: I did not start my own personal web site (without even linking to xbmc.org!!??), I did not re-brand the product, I made sure the code is still compatible with the XBOX code (as much as I could), I did not release binaries on my own, I consulted with other members on design considerations etc. Being a team member means working with the team and for the goal of the team.
When happened with the OSX port is far from being like that.
I think elan is a great developer but he was not a TEAM PLAYER. This makes all the difference in the world. I'm not talking about cullman since I never understood his role (XBMC already has two great project managers, why need more?? what is his added value?? who assigned him to be a project manager??).
I think that when new people join a project that has been going on successfully for a few years, they should have some respect to the team and how it works. They either accept the rules (and possibly try to change them later through discussion) or leave. I accept the fact that they wanted to fork, but playing dirty in blog posts is not the proper way leave.
I have a strong feeling that team OSXBMC have a hidden agenda in this whole play which goes far beyond of "I'm used to commit stuff only after I release". Only time will tell. Just everyone needs to remember that the XBMC code is GPL and I'm willing to defend this, no matter the cost.
-Yuval
Posts: 158
Joined: Dec 2003
Reputation:
0
hazeh
Senior Member
Posts: 158
My spidey senses are telling me there are some more "give us credit for actually making this...?" arguments along the line.
Massive potential and clueless(ly) loyal users is a good combo, well done for spotting it.
obviously this is a joke post
Posts: 43
Joined: Apr 2008
Reputation:
0
Equusz
Junior Member
Posts: 43
2008-05-26, 20:00
(This post was last modified: 2008-05-26, 21:55 by Gamester17.)
[MODERATOR EDIT]: Deleted insult of other member(s).
Posts: 43
Joined: Apr 2008
Reputation:
0
Equusz
Junior Member
Posts: 43
Gamester17: And I think you and Team XBMC should recognize that you will never have a better OS X product than you do with Elan and his group on your team, kill the bureaucratic B.S. and do whatever it takes to get them back as part of Team XBMC.
When bureaucracy and red tape stifle creativity you end up with second rate products ala Micro$oft.
I feel that the pressure your team brought on Elan's group which forced them to leave is reminiscent of the pressure brought on Linux developers by the Windows community in the early days.
Of course, I only have the posts here and Elan's blog from which to form an opinion, but based on the responses I've seen by people such as Jezz-X and others on TeamXBMC, I don't think I'm far off the mark here.
Make up, make it right, and get back on the same team!