Rainbow Portal

In order for any new module, theme or core code change to be considered for inclusion in a future Rainbow release:

1. Describe the work you are doing on Rainbow Confluence under "Current Work".  Access to this area requires a special Confluence account which you may recieve by emailing hr@rainbowportal.net with a brief description of why you want to join the team.  
2. Your post on Confluence should include:
   • Your name and contact information
   • A description of the new feature
   • Optional:  a description of possible future enhancements you are considering for this feature (this will help us find links between your work and current open issues in jira as well as the work of other recruits who may be able to help you.)
   • If you consider yourself active on the support areas for Rainbow - for example the Rainbow Forums,  the Yahoo Support Group or any other means you may be providing support to those in need... maybe you want to make your self known as a Member of the support team. Anyone on this team will be have the chance to be a moderator in the forums as well as be the guides for what content get's into the FAQ's and UserGuides.
     
3. Send a note to the rainbow developers mailing list which includes the URL to your posting in Confluence.

Some things to consider, Since Rainbow has now moved to a more manageable system with SVN source control and multiple solutions we are begin to integrate certain policies. Information on all the SVN solutions can be read about here http://support.rainbowportal.net/confluence/x/swU. The main point here is policies, in which everyone should know that Anyone is able to contribute to the project. Anyone is able to commit code to the DEV solution and see how it mingles with the rainbow solution. Then, there is a stepladder to get the code into the core and release versions of Rainbow. If you are a new member of the team, who has completed some code and would like to see this code make its way into the test, beta and finally release solutions, you should contact rbAdmins@RainbowBeta.com with a message containing details of the code you finished developing and want to integrate into the test solution for it's first rounds of Quality Assurance with the team. This way all code working its way into releases is known and documented. NO code will work it's way past test and into beta without having at least passed certain levels of test to assure proper documentation of the feature, install process and compatibility.

The Rainbow Team is growing every month with contributors from around the world. We have an ongoing need for people experienced in, or interested in, ASP.NET development (both C# and VB), technical writing, graphic design, language translation, testing, and marketing.

Contributions can be at any level, from a core infrastructure developer, to an add-on module writer, to someone that volunteers just a few hours over one weekend to improve or create a piece of documentation, a new theme, report some bugs, or create a small graphical design element.

Why Join?

Additional benefits for team members include:

• a private mailing list
• private content areas on this web site
• participation in setting Rainbows future requirements
• friendships with a global community
• satisfaction from making a significant contribution to a project where everyone is appreciated

How to join

1. Read about our organization on the Team Org Chart page
2. Pick the topic areas that interest you most
3. Send us an email with the following info:
   • your name and email address
   • topic areas you would like to contribute
   • a few sentences about your experience in the topic areas of interest
   • join the sourceforge developers mailing list