This article does make it sound like an arduous task of tracking down the maintainer on irc and asking him questions. seriously?
The thing is yes wayland could be documented better, would it have helped the Canonical developers avoid creating a replacement?
Tracking down someone like krh on irc isn't exactly burdensome, sending a mail to a mailing list saying we think wayland works like this, are we correct? could it work like this? this is open source 101.
If the only interface to wayland was a bunch of developer docs like MSDN then yes not talking to wayland would actually be more valid!
(also Chase no longer works for Canonical, hence why he stopped following up).
Ubuntu unveils its next-generation shell and display server
Posted Mar 7, 2013 3:32 UTC (Thu) by n8willis (editor, #43041)
[Link]
Well, I don't think I was saying it was arduous; but rather observing that incidents of miscommunication often have multiple causes (which definitely includes docs; which as a public entry point, can do many things - mitigate, or exacerbate, or entangle them). The level of detail provided on all sides appears to be a contributing factor; it did certainly appear that both sides came away from the IRC discussion with a better position on where the differences were; I'd certainly hope that that continues if (or when) there is subsequent discussion.
Nate
Ubuntu unveils its next-generation shell and display server
Posted Mar 7, 2013 13:47 UTC (Thu) by dbnichol (subscriber, #39622)
[Link]
I thought the same thing. The only way you get involved in a project, figure out the direction, and eventually try to guide the direction is to show up. I can't think of any open source project where you could have no contact with anyone on the project and feel you had a strong understanding of the its direction.
It seems like if the alternative is writing your own graphics stack from scratch, then you probably want to make sure you've got a full understanding of the project you're discarding.