Great news Edwin ! You'll want to read this http://www.apache.org/licenses/ , fill out http://www.apache.org/licenses/icla.txt , and your employer will need to complete http://www.apache.org/licenses/cla-corporate.txt . This can take many weeks to finish .
Make sure there are no third party dependencies that conflict w/ the apache license. In the meantime you'll also want to refactor the component for the myFaces sandbox after you get a hold of the source http://myfaces.apache.org/source-repository.html and submit a patch in the issue tracker http://myfaces.apache.org/issue-tracking.html . When the dev team feels the component has matured ( people use it, people ask for features/fixes, features/fixes are being taken care of ), it will be moved to tomahawk. I'd suggest getting some real good documentation in order to generate interest in the component. Start w/ the wiki. Also, use [email protected] for contribution related stuff. Good luck and looking forward :) Dennis Byrne >-----Original Message----- >From: Edwin Goei [mailto:[EMAIL PROTECTED] >Sent: Friday, March 10, 2006 07:22 PM >To: 'MyFaces Discussion' >Subject: Yet another calendar (also works in Java Studio Creator) > >I recently developed a prototype JSF popup calendar component to >accompany some documentation for third-party component developers for >the product I work on. Surveying other calendars on the web and fixing >problems in the currently shipping calendar, I think I have chosen the >functionality that 80% of users would want. One thing that is different >is that this calendar has design-time support for Java Studio Creator. >I'd like it to be the basis for a real product quality component. If >there's interest, I might be able to convice my employer to donate the >code to apache. For screenshots and links to docs, you can look at >http://blogs.sun.com/roller/page/edwingo?entry=component_authoring_for_creator. > >BTW, I originally tried to adapt the myfaces inputDate component, but >found it would require runtime changes to the code. It's still possible >to do this but when I started to write the sample, I decided to start >from a clean slate. > >-Edwin >
