Clicking the action will not publish your project instantly, you need to fill in the wizard first. So I don't think it
can happen accidentally. However, the wizard should make it very clear that you are sending your project sources to a
public space where anybody can see it.

Also... how many times in a project's lifetime will this button be clicked?

Makes you wonder if it should still be in the context-click for every project, doesn't it? ;-) Honestly, there is no reason for it to be there... even if I wanted to 
share a project on Kenai, I'd first look in the Team -> Kenai menu entry. I think having the button where it is, is redundant, clutter and non-intuitive.

Once the project is version-controlled, the Share on Kenai action should not appear in the context menu. I'd say it is a
bug if it is there. For a local project I'd say it is a good fit. I saw a few cases when people asked to put their
project on Kenai went exactly to the project context menu. They are used to go there for version control actions, and
this one is rather similar.

Tomas is right. Share on Kenai should not be on version controlled projects.

Having a context-click menu entry that has a lifetime of one click seems a little extravagant to me. It irks me enough to want to remove the Kenai support 
from Team. Please consider removing the context-click button.

*** Issue 165535 has been marked as a duplicate of this issue. ***

*** Issue 161681 has been marked as a duplicate of this issue. ***

Context-menu entry with a lifetime of one click is not extravagant at all .. consider delete :-). 

Now seriously .. what is the real problem? The fact that people who run the wizard will make their code public and are
not aware of it, right? Hiding the wizard from the contextual menu will not solve the problem, it will make it less
visible (less people will run the wizard, but they will still publish their sources public and not be aware of it).

The real solution to this problem really is making sure that the user knows they're uploading their sources to a public
space. Adding a text: "Your project will be available to anyone on Kenai.com, please specify the source licence:" above
the licence combo-box should do the job.

Actually, all you've done is made me think "yes, Delete should be removed from that list as well".

IMHO, the context-click should only contain useful entries. If it contains buttons that have a lifetime of one click, then it is cluttered to hell and the human 
interface folk should be on your case ;-)

I'm sorry, but whether items are in menus is driven by how useful in given context they are (this one is, even though
just once during a project lifespan, similarly to other actions) and also sometimes by marketing requirements. Kenai is
top-priority feature so it also plays some role here. 

FYI, we recently tested this usecase (sharing project on Kenai.com) in a usability study and majority of participants
actually did use this contextual menu item rather then the top-level menu entry. 

This issue is valid and we need to solve the problem with people being unconscious about sharing the project with the
whole world, but not by removing the item from the menu (which would not solve the problem anyway, as previously explained)

You bet the HI folks (me) are following on ;-).

I added label:
"Your project will be available to anyone on Kenai.com, please specify the source licence:" 
to both Share on Kenai wizard and New Kenai Project Wizard.

58a92a7f51c5

Actually, the message is not quite clear/correct.

If they add their project they are sharing the sources and any other project information with everyone, not just people
"on kenai".

you do not have to be registered with kenai to get the sources and view issues, wikis, etc

So it is a little late for a UI suggestion, but I would personally suggest adding an extra confirmation dialog after
they click Finish asking if they want to really continue to give them that one extra warning. The dialog could have
wording such as:

"You are about to make your project available to the public with a XXXX license. Are you sure you would like to continue?

If you are going to just add a message to the wizard

"By creating a project on Kenai.com your project will be available to the public. Please specify a source license."

It would also be good to provide a link to kenai.com.

"You can view the Terms of Use at Kenai.com"  

Integrated into 'main-golden', will be available in build *200905220201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/58a92a7f51c5
User: Jan Becicka <jbecicka@netbeans.org>
Log: #165344: "Share on Kenai" button is dangerous
explanatory text added

I am not convinced that the message in the wizard is sufficient. I barely saw it and i was looking for it

Ok. Let's add 3rd page (summary page) of the wizard saying what is going to happen. Ondro, or anyone, please improve
wording.

-----------
Project xxx will be shared on kenai.com 
* Bugtracking will be created
* JavaProject1, JavaProject2 will be committed into new public subversion/mercurial repository under GPL/Whstever license
* Chatroom will be created

I'd highlight that it is going to public and also show the URLs (was one of observation of usability study that people 
still were not sure where the sources are going to end up). My attempt:

Ready to start sharing sources on Kenai.com
* Project xxx will be created under GPL/Whstever license
  <project url>
* JavaProject1, JavaProject2 will be committed into new *public repository*
  <repository url>
* Issue tracking will be set up
  <issue repository url>
* Project chatroom will be created

Bullet #2 should be different if there is no local project initially chosen to share - possibly:
* A new *public repository* will be created for sources
  <repository url>

already fixed