Hi Alan, thanks for your response. Sorry that I took that personally, although I was not targeted. I just have a few problems here. Among other things - like every day - with a certain problem in the SPARC-Xorg ws.
Also I see from the window, that today my car outside got the 3rd police ticket in 2 days. Also I type this via a small laptop keyboard, because all other kbds are connected to SB100, SB1500, SB2000, T2000 and SB2500 ... Let us please defer this. I respond later, some day. Too many things are (literally) in the air right now .... regards, %martin On Thu, Apr 15, 2010 at 8:52 PM, Alan Coopersmith <alan.coopersm...@oracle.com> wrote: > Martin Bochnig wrote: >>>> For the benefit of everyone else who might want to use them? (Unless you >>>> believe they're less deserving than Sun, of course.) >>> sure. But this is my position: If Sun doesnt want them (upstream into >>> ON), >> >> >> Err: ON for libpciaccess. >> xwin for the rest. > > libpciaccess itself is in the X gate, though it calls libraries like > libdevinfo > in ON. I don't remember seeing any open requests from you to have code > integrated into either gate, though I've been busy with many other things > and may have missed or forgotten them. Ideally though, changes to things > like > libpciaccess would be submitted by you to the upstream projects, and we'd just > pull them in automatically in the next resync, so we don't have to maintain a > patch, especially not a patch we can't really test or maintain. > >> But we discussed this long ago, 1000 times. >> Sun doesnt want. EOF > > Yes, as we've discussed many times before, the management of Sun's SPARC > workstations & graphics groups, back when Sun sold such things and thus still > had a group, decided that they were not going to invest in a lot of work to > support hardware that would not be generating any revenue, since it was no > longer sold and would be past the end of its support life by the time > customers > started buying support contracts for the next enterprise release of Solaris. > Now that those product lines and product teams are long gone, it will be even > harder to convince new management to spend any resources there. > > I'm not doing anything to block you from being able to provide drivers, and > the FOX project is still open to host code you wish to share with users or > other distro builders, but we're not planning to pull any of those drivers > into Oracle's releases. Unfortunately, the SPARC support for source juicer > has been delayed, so you can't yet submit them via there for hosting in the > pkg.opensolaris.org/contrib repo, but you can provide them directly to users > in a variety of other ways. > >> This was accepted from my side. >> But blaming users for writing more emails, than they contribute code ... ? >> At least in case of some individuals that is a bad joke! >> >> Shouldnt one be careful with too general allegations? > > I'm sorry you took offense to my joke - I really wasn't thinking about you at > all, but the people who post many of the complaints, but have never written a > line of code, have never helped another user on IRC or mailing lists, have > never gone to their local user groups, have never filed a bug or helped track > down an issue, have never participated in design or code review discussions, > and have never contributed to the community in any other way. Even if not > much of your code has been contributed back to the main OpenSolaris project > gates, you've contributed in many other ways. > > -- > -Alan Coopersmith- alan.coopersm...@oracle.com > Oracle Solaris Platform Engineering: X Window System > > _______________________________________________ website-discuss mailing list website-discuss@opensolaris.org
