On 25 February 2011 12:47, Sean W. Liu <[email protected]> wrote: > Hi fellows, > > I'm starting a small company developing a SNS website and we are using > RoR. The concern we have right now is that we don't want each of our > developers get the entire Rails code base of our project. > > To my knowledge, there might be three pieces of ideas of potential > technical solutions for us. But since I don't really have any so > called industrial experience on web development, I'm looking forward > to some advices. > > 1. Encode/encrypt our Rails souce code somehow; > > 2. Distribute the minimum amount of code to an individual developer as > needed; > > 3.Construct some sepcial architecture for our SNS like Drupal that > people can develop "plug-in" or "module" for such system that one > developer only needs to know the corresponding APIs for working on his/ > her specific "plug-in"/"module". > > Or, is there any other better way? Or, what mechenism is actually > being used by big commercial companies using Rails like Twitter?
Employ reputable contractors (I presume it is contractors that you are talking about) and get them to sign non-disclosure agreements. Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
