There are two aspects to this merge: Technical and Cultural. 1) Technical - the upgrade path for mebists; how much of 'rails 3' will be merb; what each project gains from the other; community support for current Merb users.
2) Cultural - 'good ruby code' as Matt tweeted (e.g less metaprogramming); less fandom and more geekiness (merb); good communication with framework users (as in merb); specifying a clear protocol for contribution. - highandwild On Thu, Dec 25, 2008 at 8:08 AM, Matt Aimonetti <[email protected]>wrote: > > I hear some sarcasm in this comment ;) However, adding more people > with different tasks will def. help a lot. We are bringing our > expertise and we will work on separate parts of the framework. I'm > positive that will help. > > - Matt > > On Wed, Dec 24, 2008 at 7:53 PM, Brian LeRoux <[email protected]> > wrote: > > > > Yeah adding more people should really speed things up and help > > innovation. Makes sense right? > > > > > > On Wed, Dec 24, 2008 at 7:36 PM, Ryan Bigg <[email protected]> > wrote: > >> > >>> > >>> Is there really a point to asking specific questions about technical > >>> details right now? > >> > >> No one knows. Things change. Wait for it to mature and then see what > >> comes out. I wouldn't be too worried about the technical details > >> anyway since there's a bunch of competent people from the merb camp > >> and a bunch of competent people from the rails camp working on the > >> same project together. Generally (in a logical world) the sum of two > >> positives is positive. > >> > >> > > >> > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
