| Participation Comments |
| Allow contributors to participate in the bug management process so that he/she indicate that he/she is working on that bug (bug tracking) as well as given a contributor a contact person the contributor can contact to raise issues or request update on the bug fix status even though that I think Sun should handle this without that. |
| Improve the java.net forums to offer threaded views of the messages. |
| Fix your licensing. It's no good for neither research, nor sharing contributions with other projects. I'd love to see some of the work done on GNU Classpath, Kaffe and other projects find its way into the JDK, but currently you're making it impossible for people to work on both. Create a patent covenenant around J2SE implementations, that protects anyone implementing it, like you did for open office. Try to be a part of the Java runtime community, instead of just dropping random binaries over the wall. |
| open source |
| Provide the JDK RI under a dual license (one of those license should be GPL friendly). |
| The licensing it primarly. An open source monitorable repository is secondary. (aka public anon cvs/svn) |
| General transparency |
| Open up the JDK. Probably provide the spec to OASIS or another standardization group. SUN alreday has chosen this way for the OpenDocument Format, why not specify Java accordingly and provide an open imlementation? |
| Remove license restrictions, that is, using an OSI-approved license at least for the TCK but ideally for the JDK as well |
| Better bug database. Some way to have better co-ordination beteen people fixing bugs (both in and outside of Sun). |
| I know I am repeating myself, but Open Java;) |
| The JavaOne event in USA is nice, but do not expect many developers to come from Europe. It does not worth that much. I would personally like to have a similar event in Eastern Europe, since there are lots of Java developers around. |
| Open source Java |
| -- |
| Better, faster and cooler interface into the process. |
| Repeated with last one: Take a closer look at open source projects. |
| I can only repeat again: make the JDK available under a true open source license like Apache, BSD, and/or (L)GPL and you will encourage participation. Under the current set of licenses, you are merely asking people to work for free for Sun. |
| no temporarily |
| Open-Source Java! |
| make build easyer.why not have visual studio solution file just to use it and build with it.now you need one week setup everything and then another 3 days to find anything in code....try to document what is in which folders... |
| Help developers market their applications. Like Swing sighting s, but help them market it. |
| Better license for involve the Open Source community. |
| Allow me to vote for as many bug fixes or enhancements as I wish. I will surely not have time to read them all, mostly the ones closely related to active problems or development... |
| provide more technical articles |
| Have more Seminars. Assign event managers to each city.Regularly meet up. You might think of contribution and membership recognitions that could entice developers to take pride in being part of a Community/Group.Like a certificate to a bonafide developer that identifies him of being a Community member. |
| The ability to build the Windows version of the JDK with free tools. Currently we need Visual Studio .NET, which not everyone has. Microsoft releases some tools for free without the Visual Studio GUI (I forget the name), so if we could build it with just those tools I would be able to build the JDK and therefore possibly contribute more. |
| Make it simpler to become a contributor. |
| More cooperation and less bashing of eclipse. |
| Provide easy-to-find details on how to contribute code, including examples and guidance on what might be needed and what not. I've not sought this actively but if I thought of submitting code, I'm not sure where or how to submit it, for example. Of course, I might just be blind ;-) |