Report

Rewards and Recognition

How community members should be best recognized and/or rewarded for leadership, contributions, feedback and general participation in the community.

List contributor names in prominent places

	Frequency
Very Important	22 20%
Important	36 33%
Nice to Have	38 35%
Not Important	9 8%
Don't Know	3 3%
Total	108 100%

n=108

Rewards: prizes, give-aways, T-Shirts, etc.

	Frequency
Very Important	10 9%
Important	22 20%
Nice to Have	44 41%
Not Important	28 26%
Don't Know	4 4%
Total	108 100%

n=108

Personal acknowledgements at JavaOne and other events

	Frequency
Very Important	10 9%
Important	25 23%
Nice to Have	51 47%
Not Important	18 17%
Don't Know	3 3%
Not Answered	1 1%
Total	108 100%

n=108

Closer (personal) access to JDK engineering

	Frequency
Very Important	18 17%
Important	53 49%
Nice to Have	24 22%
Not Important	10 9%
Don't Know	3 3%
Total	108 100%

n=108

Public listing/ranking based on significance and frequency of participation

	Frequency
Very Important	10 9%
Important	29 27%
Nice to Have	29 27%
Not Important	36 33%
Don't Know	3 3%
Not Answered	1 1%
Total	108 100%

n=108

Provide community site privileges to top participants

	Frequency
Very Important	19 18%
Important	33 31%
Nice to Have	36 33%
Not Important	12 11%
Don't Know	8 7%
Total	108 100%

n=108

In your opinion, how is Sun currently doing in recognizing JDK community participation?

	Frequency
Excellent	3 3%
Good	34 31%
Fair	42 39%
Poor	13 12%
Don't Know	16 15%
Total	108 100%

n=108

What other means should Sun consider to recognize significant achievements and community leadership?

Recognition Comments

Not everyone has the chance and time to contribute a lot but still if they provide a important or difficult fix should be recognized for but that also needs a better integration and cooperation with the contributors by Sun.

Listen to those who have helped you in the past. But from my perspective this already happens.

Let them open up their code.

A bounty system, perhaps?

involvmnet in providing users answers to basic or complex questions on forum or newsgroup

Let the community and active contributors make desicion and commit code to the JDK, like they can in Jakarta, OpenOffice or Mozilla.

money :)

More of a comment on the above. My original thought was that community members would be able to "graduate" to more complex fixes... but out of the 4 or 5 (I forget now) simple bug fixes I have supplied the time spent waiting (5 months now for one of them I think) it is "impossible" to advance to anything more important than trivial fixes. Basically I had some momentum that has been totally lost because of the the delays from Sun. I do recognize that the process is new and engineering resource may be scarce... but why have the program if it isn't going to be properly run?

I think you have summed it up pretty well above.

Obiously, with more community leadership.

Stop playing around with gimmicks; developers aren't lapdogs that can be rewarded with little treats, they want to be sure that their contributions remain open and free. You can accomplish that by open sourcing the JDK under a license like BSD, Apache, or (L)GPL.

no temporaryly

Just contineously have feedback from especially developers on regular basis, just like this. I hope this would boost Java a lot.

Open-Sourcing J2SE!

Keep on moving, you're heading in the right direction. Nominate maintainers for the relevant JDK packages.

People help Sun to scratch their own itch. So if there's a bug that is a problem for me, I'd fix it and give it to Sun.

let them participate easier, for the more contributions that they have made.

I am hampereed by an employer that prohibits participation in open source, and who even claims ownership of code I might develop in my spare time. The most important thing anyone can provide is optimal, usable examples, which are clearly in the public domain. (see Core java, for example)

support Java courses to colleges

Give Royalty, everytime anyone uses the persons contribution, give Royalty !

Another license - a contributor more or less gives all rights away to SUN. Thats the reason why I e.g. never looked into Mustangs source - just because its license.Many free java projects don't allow to put ones hands on if you've ever had a look at SUN's source, just because SUNs licenses are that complex and brutal.

Money