| Transparency Comments |
| I provided a bug fix for bug #6212146 at the end of November last year and even I complaint about it with the help of Sun employees still I did not get an insights on where the contribution stands in the bug fixing process except that I got an email in February that finally someone is looking into it. |
| Full specifications as they are developed, rather than dumping snapshots. That's a pretty poor excuse for not developping the specifications in the open. |
| Improve "Bug Parade" interface. |
| online and active resource (irc, netbeans collab channels, stuff like that) |
| open source |
| Apply to the JDK team the same practices that Glassfish team is doing : active issue tracking, quick analysing of fix submission, interractive discussions |
| OPEN SOURCE THE JDK. The JRL "you can pay us to use your fixes" is NOT acceptable. |
| Best practices, tips and tricks. While the quality of java API documentation is one of the best out there, there still isn't enough done to educate the 'masses' about the benefits of MVC, (concerning swing). More real life examples with JTree, JList and JTable, those are the three most important components. |
| I'd like to have the information, code and binaries released under less restrictive licenses. At least without the NDAs that prevent me from collaorating with other open source software projects |
| For me personally, it would most useful it there would be a mailing list where Java compiler and tool writers are subscribed to: at least Sun's javac team, Eclipse JDT Core, and GCJ.Too many issues that compiler writers encounter are not communicated clearly and there is no forum where you are sure that you will get answers from real experts (such as Bracha, Gafter, Ahe, Mulet) if you have questions about details of the Java sematics. An experts mailing list would be good for this (invitation only). Except for the generics forum there is not an obvious place for discussing these things.If there is already such a list, then I would love to know about this (martin.bravenboer@gmail.com). |
| get rid of the old bugs in the bug tracker. There are a number of bugs that are pointless or will never be fixed. Also there is a 500 bug limit that you can search for which makes it hard to find them.The turn around time for community supplied bug fixes is terrible. I have a fix that is outstanding since, I think, October. I recently received an update about it but 5 months for a comment?! |
| It's not an addition, just more articles/docs/tutorials ... |
| Sun have lots of JDK tests. If it possible, somehow open them to use. Like you publish JDK source code, publish tests and test results as well.Based on that, you can automate patch approval. For example, I did a patch, run locally against tests (take 40 hours fo example), get some encrypted string and sent to you both the string and the patch. On your side, you look at the encrypted string and get - hey, he fix bug and no tests fail. Approve. Or something like that. Most of developers not submit patches now, because nobody want to wait years need to small group of engineers to check every patch. |
| Make a better site, one that looks better (more modern) and doesn't look like it's 15 years old. For instance one can't even have threded posts in the bug database, and it looks so very old. It's hardly works either since one have to use html in some sections. It just looks very abbandoned. |
| GPL compatible licensing |
| MacOSX Mustang JDK. |
| Compare other libaries against those hosted by java.net. |
| More RIA tutorials. |
| Make the JDK available under a true open source license. Until then, there is no point for users to contribute bug fixes or enhancements to Sun, and the limitations of Java and the JDK show this. |
| it has been enough for me! |
| Just like this one, as I am providing mty feedback to Sun ( a developer). Sun must now first care for the developers and than users and than Companies. In last so many years I have seen Sun has mostly cared for the companies only like EJB specification & other few things are too, too complex. If you had cared for developers first this couldn't have happened. Honestly asying, New energy(freshers) is today avoiding Java because of too many things involved. As much time a fresher need to spend on learning it, they can even learn, develop and deploy code in .NET. If u find my feedback usefull please contact me at hemantmalhotra@gmail.com, than I'll send you detailed description of a developer thoughts about trends in Java. |
| Technical articles |
| Open-Sourcing!!! |
| build mustang on latest visual studio without all the crap and especialy without cygwin. |
| deciding what new projects should be (ex: thin down jre) and what the desired resources should be allocated (ex: more desktop, less jee) |
| Make the whole JCP work faster - over one Year for "Expert Group Formation" ???? |
| easier (and I mean much easier) code contribution, esp those smaller + trivial ones. |
| Overall, you are doing a wonderful job. Sun has always seemed to be serving my interests as a developer and my employer's as well. My usual problem is not having the time to read everything. I am usually torn between researching problems and learning new concepts and contexts. |
| new features and code samples about new features. |
| How other forums and non-SUN Communities are doing.A news letter from them could be helpful, that is categorized under packages of Java....say ME,SE,EE versions of Java. |
| A brief description of the change when a bug fix is made. |
| Long term plans, strategy for java platform. F.x. how to compete with .NET, hopefully cooperate with eclipse and bring in new stuff from Ruby etc. |
| Materials and Online Books on Java and Java certifications.... |
