I'm on the same boat. Never liked Rails, and I really doubt I'm gonna like it any more at version 3, no matter how much Merb you inject. I'll do whatever I can to keep Merb alive, since it's what I like to use, and would find it really sad to see it die.
I'm a ruby user, far from a ruby guru, probably not good enough to hack around at Merb internals. Documentation, however, might be something I can contribute to. I'll look into it. Beside the documentation on Rails migration, does anyone have topics in mind that are not currently documented, or poorly documented? 2010/4/29 MarkMT <[email protected]> > Just to be clear - I'm in no hurry to leave merb - I love it, and hope > I can contribute in some way to its continued well-being for as long > as possible. But I just feel that prudent risk management requires > that I be prepared to make a switch if and when the environment makes > it necessary. > > On Apr 28, 4:04 pm, Pavel Kunc <[email protected]> wrote: > > Seems that the official wiki would be really good so: > > > > http://wiki.github.com/merb/merb/howto-switch-to-rails-3(sorry<http://wiki.github.com/merb/merb/howto-switch-to-rails-3%28sorry>I > > couldn't resist) > > > > I count on the community to create best resource for the Merb -> Rails > > 3 transition. > > > > Pavel > > > > On Apr 28, 5:16 pm, Jonathan Stott <[email protected]> wrote: > > > > > > > > > On Wed, 28 Apr 2010 10:42:06 -0500 > > > > > Ian Eyberg <[email protected]> wrote: > > > > as the maintainer of a larger merb stack in production use > > > > I fully agree with this statement... > > > > > > now on to reality ... this is open source software so we > > > > are all in it together -- use what you want to use and > > > > contribute what you can contribute -- I know a lot of people > > > > are probably in my situation -- we use the software but > > > > we don't necessarily have the time to be submitting patches > > > > every day to maintain it -- having to manage all the other > > > > components and working on other software eats my time > > > > hardcore -- so people in my situation can do the next best > > > > thing -- documentation, howtos, etc.. > > > > > > I have personally not been so helpful in this regard and have > > > > done a lot of bitching on this front which is not helpful > > > > so in an effort to reconcile this, I'll try to write > > > > some more howtos and fill in any necessary documentation > > > > that I had trouble figuring out -- I suggest others that > > > > are in my shoes to do the same > > > > > > - Ian > > > > > That would be greatly appreciated, both by Pavel and myself, and I'm > sure by the community in general. I don't see Rails3 as the future of merb, > because I don't see much value in what would be Rails3, but with an 'odd' > syntax. This feeling is, I think, shared by Pavel. > > > > > That having been said, the last thing we want to do is make things more > difficult and inconvenient for users wanting to make the transition than it > has to be. Whether aiding the transition is writing docs, or writing a > rails plugin which makes rails behave like merb, it's something I'd like to > offer help and advice to the authors for, but don't have the time to work on > myself. There are things I want to work on for merb itself, as well as all > the other things which take up time. > > > > > Regards > > > Jon > > > > > -- > > > 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] <merb%[email protected]>. > > > For more options, visit this group athttp:// > groups.google.com/group/merb?hl=en. > > > > -- > > 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] <merb%[email protected]>. > > For more options, visit this group athttp:// > groups.google.com/group/merb?hl=en. > > -- > 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] <merb%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/merb?hl=en. > > -- 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.
