Originally posted by LinuxGamer
View Post
Announcement
Collapse
No announcement yet.
Mir Support Not Merged For Mesa 9.2
Collapse
X
-
Originally posted by blackout23 View PostI also don't get it why they wait for NVIDA and AMD to make new drivers. Why don't they write their own drivers? Just fork nouveau.
Originally posted by dh04000 View PostProject A: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project X, so if we don't its their fault not us.
Project B: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project A, so if we don't its their fault not us.
Project C: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project B, so if we don't its their fault not us.
Project D: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project C, so if we don't its their fault not us.
Rince, Wash, Repeat.
If you don't collaborate with others, you have no one to blame but yourself. Selectve collaboration is the death of FOSS. Looking down GPL code to your selected few poisions GPL code and makes it no better than non-GPL code.
Originally posted by DanL View PostWhere do you people get this stuff? All the article says is that Mir will not be ready for the Mesa 9.2 release. Most likely, Canonical will use Mesa 9.2 + their Mir patches for Ubuntu 13.10. By the next Mesa release point, the API should be stable and the code will be well-tested and ready for merging.
This "news" is not newsworthy IMO (just gets the Canoncial haters worked up).
However, everything you say is stated on the article, and points the problems: they are on their own, and most likely they don't know in depth the mesa code base.
About the haters, not everyone are Canonical haters. Some of us just have personal opinions about different things. If I'd hate Canonical, I wouldn't use any of their products, nor would I test their alphas and betas. This said, I think Mir is an awful choice. They didn't share their needs, and then they started blaming other projects for not fulfilling them, for a start. Then, this needs were actually fulfilled by the time they did their announcement. An open company that takes such a huge decision inside close doors is not really that open. I could keep all day. Then, they throw the testing on the end users. You see why I don't think this is going well? These are all bad choices, and I don't see how pointing this out turns me into a hater. I'm a user, and I will most likely be affected by their choices in one way or another.
Leave a comment:
-
Originally posted by dh04000 View PostProject A: Look Canonical doesn't collaborate with anyone. They submitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project X, so if we don't its their fault not us.
As an old-school basketball fan, I'm reminded of Dennis Rodman and his "reputation" fouls (he never got the benefit of the doubt on close calls)
Leave a comment:
-
Originally posted by entropy View PostI'm pretty sure Canonical will start pointing fingers at upstream soon, accusing them of not collaborating.
It's their own fault, playing foul is not easily forgiven.
Mesa is being Developed for Wayland and for them wanting for it to be developed for Mir is Funny this is one of the Biggest Fails i seen in a long time "If you build it, they will come"
Leave a comment:
-
Originally posted by blackout23 View PostSo they want everyone (DE's etc.) to embrace Mir without having any real upstream support? lol
This "news" is not newsworthy IMO (just gets the Canoncial haters worked up).
Leave a comment:
-
Originally posted by entropy View PostI'm pretty sure Canonical will start pointing fingers at upstream soon, accusing them of not collaborating.
It's their own fault, playing foul is not easily forgiven.
Project A: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project X, so if we don't its their fault not us.
Project B: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project A, so if we don't its their fault not us.
Project C: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project B, so if we don't its their fault not us.
Project D: Look Canonical doesn't collaborate with anyone. They sumbitted collaborative code to us?!? I'm not going to collaborate with them, they didn't play well with Project C, so if we don't its their fault not us.
Rince, Wash, Repeat.
If you don't collaborate with others, you have no one to blame but yourself. Selectve collaboration is the death of FOSS. Looking down GPL code to your selected few poisions GPL code and makes it no better than non-GPL code.Last edited by dh04000; 11 July 2013, 11:12 AM.
Leave a comment:
-
I think Canoncial should drop 13.10. They should fully focus to give a good experience on Ubuntu 14.04 and for that improve Mir and the driver situations.
Leave a comment:
-
Originally posted by gufide View PostThey obviously should fork mesa! With this fork, they will have more control!
A fork of the kernel should be a good idea too!
Leave a comment:
-
They obviously should fork mesa! With this fork, they will have more control!
A fork of the kernel should be a good idea too!
Leave a comment:
-
Originally posted by blackout23 View PostSo they want everyone (DEs etc.) to embrace Mir without having any real upstream support? lol
It's their own fault, playing foul is not easily forgiven.
Leave a comment:
Leave a comment: