On Fri, Aug 19, 2011 at 12:24 AM, Frederick Cheung < frederick.che...@gmail.com> wrote:
> > > On Aug 19, 2:58 am, Rodrigo Ruiz <rodrigo.ru...@gmail.com> wrote: > > Thank you everyone, and that link helped me with git. > > > > Well, setting aside the code access concern, the other thing I wanted to > > know is how to work in a team with rails, and I mean, how should I split > my > > project? > > > > For example, one member will do the Controllers, other will do the > Models, > > other will do the Views, one for Mailers, and one for Tests. > > That sounds really wrong to me. Splitting along vertical slices of > functionality is normally how I do things > Definitely a recipe for disaster. Rodrigo, you might want to look at mountable engines here: http://railscasts.com/episodes/277-mountable-engines This is one way to partition application functionality, where you add specific models + controllers + views as one mountable engine into a gem, which can be developed independently. So you could have one for accounting, one for sales management, one for production planning or whatever your poison is. You might also want to look into SOD (service oriented design), there is a good book about it here: http://www.amazon.com/Service-Oriented-Design-Rails-Addison-Wesley-Professional/dp/0321659368 In any case, and please take don't take that in a negative way: I think you are over-complicating things unnecessarily. Adding security requirements in a workflow is necessary when you work for the DoD, but in 99.9% of the cases it is just a huge waste of time and makes your project a magnitude riskier. Don't worry about people stealing your code, worry about finding and making customers happy. It is much much harder than any coding you will ever encounter in your life. > > Fred > > > > That is probably a wrong example, so thats what I need to know, how to > > explicitly split parts of my project for each one to work on. It seems to > me > > that rails is like a one way straight coding, you can't work on one part > of > > the code without completing all the others that should come before. > > > > I don't know if I was very clear, so please give me some feedback if I > > wasn't. If I was, thought, please give me answers =) > > > > Thank you guys. > > > > Ps.: Ruby (or Rails) community is awesome, every single question I've > made > > was answered. > > > > On Thu, Aug 18, 2011 at 4:12 AM, Alexey Muranov <li...@ruby-forum.com > >wrote: > > > > > > > > > > > > > > > > > Rodrigo, > > > > > take a look at "Distributed Workflow" section in Git Community Book: > > >http://book.git-scm.com/3_distributed_workflows.html > > > > > It is assumed there however that everybody in your project has access > to > > > the > > > full code. > > > > > Alexey. > > > > > -- > > > Posted viahttp://www.ruby-forum.com/. > > > > > -- > > > 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 rubyonrails-talk@googlegroups.com > . > > > To unsubscribe from this group, send email to > > > rubyonrails-talk+unsubscr...@googlegroups.com. > > > For more options, visit this group at > > >http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- > 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 rubyonrails-talk@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
