On Thursday 01 February 2007 07:49 am, Shawn Walker wrote: > I think what's most frustrating about the closed_bins is that we don't know > *why* in some cases. It would be helpful if there were a status list for > the closed_bins that indicated what items would never be available (due to > 3rd party or something generic like that as reason), which have a chance of > being available at some unknown date (under review), and which items will > be available at some unknown date (in process).
Why would you need to know *why*? They have gone through legal and have been reviewed numerous times, and they can not be released. The only thing anyone needs to know is the list of closed pieces that need to be re-written. You want to know why? It's because they're encumbered. > That would go a long way to silencing critics. If we *knew* that you > actually couldn't release an item ever because it was completely out of > "SUN's hands" so to speak; that might be a motivation for people to start > working on something. At the moment, we have some vague notion that some > things are "out of our control" but we don't know who the group of people > the comprise "our" is, and we don't know if that means *forever*. I disagree with this, in fact, why would critics care about closed sources that are out of Sun's control? > Thankfully though, we finally *know* that libc_i18n is completely out of > "SUN's hands" so to speak. It indeed sounds like a great opportunity for a > community project. Yes, and it doesn't even matter why, all that matters is that we know it's un-usable, and we would have to re-write it. I think it would make a great project, and would support such an effort (support in the sense that I am for it, I am not offering to work on the project specific). -- Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group Advocate of Insourcing at Sun, hire people that care about our company! _______________________________________________ opensolaris-discuss mailing list [email protected]
