Addition to the existing framework in Community Server 2.1

We are curretnly looking for a long term relationship with a software development company. Therefore we have a few jobs open at the moment. Anyone proving themselves to us in one of these jobs, will be chosen as our regular partner. We need to add a group module to the existing framework in community server ([login to view URL]) You must make it possible to create a group with the following properties: - groupname - password - short-code (max 7 letters. The shortcode must be unique across all groups) - description - news It needs to be possible to invite other users of the site to join the group. When you invite them you use their mobile phone number as described above. The invited user must be informed of this invitation by email. Part of the email is a link to a web-page with a list of the user’s invitations and the option to say yes or no to these invitations. If the user answers yes, he or she is added to the members of the group. This webpage should also include a list of the groups the user is a member of. The user needs to have the option to leave these groups if he or she wants to. Instead of using the user-id in Community Server you should use the ProviderUserKey from the membershipUser from the asp.net membership store. Each group needs to aggregate it’s members’ blog-entries concerning that group. You must therefore extend the existing blog-component in communityserver so that each blog-entry contains a “concerns group??-property. This property maybe empty if it doesn’t concern a specific group. You cannot use the tagging structure of community server for this. Only users who know the password can invite new users and change the description and news of the group. Of course this ‘module’ needs to integrate perfectly with the rest of Community Server. You shouldn’t worry about the design of the webpage, a web-designer will handle it. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Thursday Aug 10, 2006 12:38:38 PM: We have decided to cancel this project and move away from Community Server, since we didn't get the number of bids we expected. - we are afraid that sticking with CS will be to expensive in the long run. We have decided to build the site ourselves (through RAC). We welcome you all to bid on these tasks when we publish them. Regards Crowdcatcher Inc. ## Platform asp.net,c#, community server