One of the interesting conversations I had at last night's inagural Bay Area OpenSolaris User's Group meeting was with Ben Rockwood who asked about our plans to contribute code from Sun's X code pool to X.Org. This is something we've been doing since the Xorg CVS tree opened on freedesktop.org a little over a year ago and plan to do more of as we can. Our primary limiting factor right now is mainly the time it takes to port the code into the CVS head, build it, test it, and commit it. There's a lot more things we can contribute and hope to get to than we have time to do while still working on improving the X software in Solaris. So the question arises, how do we prioritize the bits to give back? It's been pretty random so far, with code putbacks done because we needed to get extensions like Xevie out there for our joint projects with the GNOME Accessibility Project, or because we found issues in Xorg on Solaris we needed to fix for our release and it was easy to give back to Xorg at the same time, or because it simply was interesting or useful to someone at a certain time.
For instance, right now, I've got a couple of CVS trees with bits I'm getting ready to check into Xorg CVS "HEAD" in various states of preparation, including:
But we can also decide to work on things in a different order, if there's something we have in the X Window System in Solaris that would be useful to others to have. It's hard for us to know what that is in many cases though - so if there's something you know we have in X in Solaris, drop me an e-mail or comment here, and we can look at pushing that up on the list.
I should probably warn ahead of time that there are limits - our group can only do this for the code in our source trees, and can't control the decisions of other groups over what to give back or not. So if you're asking for something, it may help to understand how our trees are broken up internally:
So while I'd love to release the source to our SPARC frame buffer modules, and let the community help port them to Xorg, it's out of my hands. There is still a bit of stuff we could contribute from the rest though, so if there's some feature we have that you'ld like to see us give to Xorg, let me know. I can't promise that we'll do anything more than listen and think about it, but we'll do that.