| Community Comments |
| Give the contributors access and feedback about their contribution otherwise it will not take off. I, for example, did stop contributing because I did not want to waste my time if my first contribution is stalled for over 3 months with nearly no feedback or updates without insisting on java.net blogs and Sun employess. |
| tutorial guides (with source code) that makes java learning easy translated into french for eg. |
| Ship more and better examples with the JDK. Replace the outdated demos. |
| Embrace the open source runtimes. Work together with them on test suites & specifications. Share code where your business reasons don't prevent you from doing so. |
| Translated pages is key to build a larger community |
| open source |
| Split the JDK in two parts, the RI and the Sun specific implementations. Find legal ways to opensource (OSI recognized) the RI and keep the suns specific parts under usual license.I do realy thing that having something like dual license for RI is possible (for instance GPL and usual sun JDK license). RI |
| open source the JDK. Clearer and freer licensing. No "pay us to use your fixes that you contributed that will go in a JDK 2 years from now" silly games. |
| There are tons of samples on 'java.net', but the GUI is absolutely not easy to follow.I return there from time to time, want to download source code of a project and I have problems to find it!It surely is there but hidden.It's easy to find it on 'sf.net' but definitely not here. |
| Host national 'subcommunities' on site. |
| JAVADOC SHOULD HAVE MORE USAGE SAMPLE CODE WITH LESS USED & NEW FEATURE CLASSES. iF THERE WAS SOME WAY TO BLOG OR DISCUSS WHICH CAN MAKE SOME CLASSES MORE EASY TO USE. OR MORE PRODUCTIVE FROM DEVELOPERS PROSPECTIVE ON JAVADOC. |
| I think opening up Java even more would be good. I very much hope that SUN will support GNU classpath and related free and open projects even more. SUN's recent change to more open processes (e.g. with Mustang) is important and I like it (even though I personally nearly never do download weekly snapshots but that the possibility exists for me and for others is very important). Taking further steps into an even more open futurewould be even better! |
| Work as a true open source development community, mimicing the success of Netbeans, Apache and Eclipse, instead of just "looking like" open source |
| more transparent issue - bug tracking mechanisms , more inside information of the JDK developers. online JDK code browsing (use Grok from Sun!) |
| Open Java |
| In short, the community could become much larger if easily deployable desktop application could be developed with Java. Currently the lack of the MVM, limited desktop integration, JRE lack of modularity and thus huge download footprint make it very hard to develop small to medium sized desktop tools in Java - be it either with Swing or JFace/SWT.With the release of Longhorn, desktop GUI might come again in the center of attention and will find Java unsuitable for robust multi-platform GUI development. Focus in this area, and the user base will grow considerably. Ignore it and Java will be synonymous with server side and mobile development.Once this accomplished, as a next step could come the unification of JFace with Swing. This could be achieved with the implementation of a SWT layer on top of Swing and vice-versa, a Swing layer on top of SWT. Desktop developers want responsive GUIs and proper application frameworks. |
| Open source Java |
| -- |
| Let community go most thing. Just manage it in opem manner. My dream is 1 000 000 developers do fixes, 200 sun engineers just approve them and wrote additional tests. |
| 1. Change JRE licensing to allow Linux distributions like Debian to ship under their existing acceptance policy2. Change source licensing to allow developers on open-source JVM projects to contribute both to those projects (kaffe, harmony, classpath) and the Sun JDK/JVM3. Possibly collaborate with these projects, or make code capable of being shared with GPL projects4. Create a Sun-specific java trademark to differentiate 'a java implemenetation' from 'sun's java implementation' for purposes of developer support.5. Be more open to core language/library changes (such as replacement of Calendar and the rest of the date system, ACT asynchronous IO library, stack-based objects, strong versioning, deployment improvements) |
| Again obiously: Take a closer look to open source projects. |
| Open source the JDK under a recognized open source license like Apache, BSD, or (L)GPL. The current license is off-putting and has caused people to leave the Java community. After years of strong Java advocacy, we are moving away from Java in favor of Mono and .NET. |
| more communication with the developers who are interested in the commnunity!for example, collect the view of developers on the design,implements and so on. |
| Open-Source J2SE! |
| Many OS initiatives produce great software. Learn from each other. |
| Charge for Java SDK and JEE (but desktop JRE is free). |
| The ultimate goal: release the source under an OS aproved license.In the mean time: Change the binary license for allow to the Linux distributions to include the JRE/JDK in thier distribution |
| easier participation, faster response cycles etc. |
| I have the hardest time with the multiple registration IDs. If you could have a single name, with a home and office email, and preferably use one or other email to login, I would connect more often. I'm sure I have many historical IDs, that would be best dropped. |
| web pages with local contents |
| The Sun Site to me is a huge Ocean...I get lost very easily...There are so many things to look at and read but I usually end up with anything flashy.I think separate SITES for each technology offering could help....so that browsing is restricted and usually target search oriented.Its an opinion ! |
| Focus on a "built with Java" camaign, where the development od applications such as media players/encoders, content development environments and playback engines, etc. are promoted. I.e. add more focus bringing Java technology to the "non-programmer" who simply wants to build content that can be deployed on Linux, MacOS, Windows, etc. (Technologies to compete with Flash/Shockwave for example.) |
| Make it easier to participate in contributing bug fixes. Signing up was such a hassle that I gave up part way through the process. |
| don't "fool" open source java implementations.They are not well for sun for licensing reasons I understand that, but well community does work differeent ;) |
| * Make sure java is still up to date : Pickup some tricks from the Ruby scripting language and C# 3.0.* Be more responsive to bug reports and change requests. |
