Rainbow Portal

RainbowPortal.NET coordinator

FAQ Coordinator

• Develops a list of common questions and answers by browsing the forums to see what rpoblems are most frequently encountered by new users. 
• Verifies that links to the one offical FAQ on Rainbow portal.net are maintained on other various support sites like confluence, demo sites, community sites.
• Periodically checks the FAQ and cleans up the language or clarity of recent posts by other contributors.

Forum Coordinator

• Moderates forum postings from new users
• Maintains the list of active Forums and makes sure we have the right topiocs covered.  Not too many, not too few.
• Moves posts to the proper forum area when they are possted in the wrong place
• Goal is to get all support (non-development) questions answered within one business day
• Daily browses the forums searching for unanswered questions, especially in support dept.
• Either answer question or pose the question to the dev mailing list asking for some to answer the question directly in the forum
• Encourages users who are posting bugs instead of questions to submit them to Jira by provided the Jira Issue Tracker url directly in his topic replay.  i,e, : Please post this a bug on Jira at http://...
• questions that seem like they should not be issues but are, should be brought up here in the dev list. because these are probably things in the application that should work better

QA coordinators:

• Seeks volunteers for testing from the dev mail list and from the forums
• Acts as Forum coordintaor for the QA forum
• Works with QA volunteers to make sure the QA web site is vistied regularly and tested
• Looks inside the forums to find bug reports and asks submitter to please coipy them to Jira. If submitter won't post in Jira then QA coordintaor will move the bug to Jira.
• Helps with testing new code/modules.

Think that any feature could potentially be used as a demo feature. Features should be easy to understand, so just by looking at them and playing for 5 minutes, you might catch easy usability problems that could be squashed in development before it gets close to cvs and is released to hundreds of people. People who are willing to dedicate more time, get into deeper levels of checking the betas and all that, including testing different data, dangerous data, heavy data, take time to test big loads, not just 2 or three item loads. The people with the most time make themselves available when a new module installation or core feature must be tested, meaning they download the whole package as ig they where downloaded a release, do a clean install and play with things the way they should be tested.

Module Coordinator:

• First and foremost the module coordinator is a project project manager, not a developers
• Own all of the open Module issues in Jira and should insure that requirements are clearly stated, prioritized, assigned, executed, and tested.
• Get contributing programmers to follow Rb standards. This easy way is point out code that adheres to Rb standards that can reused.
• Helps with testing new code/modules.
• Points out people in the Rb coummunity with particular skills/knowledgde. When somebody want to modify existing Rb code the coor should try to make the original programmer involved.
• Adds code to CVS for Rb programmers that does not have CVS-edit rights.
• Answers questions like this: Is there a module that can... When will it come... Why is ...
• Introduce new modules/features in http://forums.rainbowportal.net
• Keeping in touch with Rb programmers that more rarely contributes to Rb
• The team lead is an entry point for new programmers in the Rainbow community. The coor gets newbies started by answering typical Rb programming questions. The coordinator points to existing code that are similar to code the newcommer are working with.