[merb] The upside of merb's merge into rails...
1 view
Skip to first unread message
Ming
Apr 24, 2010, 1:57:24 PM4/24/10
to merb
One upside is that the support base should be greater. This is place
is a ghost town for support. Most merb users seem to be hackers or
developers. The average joe is SOL here. #merb useful if you're
lucky or persistent enough to get a sympathetic ear. I knew the
disparity in userbases going in but needed easy datamapper and
something else provided by merb.
--
You received this message because you are subscribed to the Google Groups "merb" group.
To post to this group, send email to me...@googlegroups.com.
To unsubscribe from this group, send email to merb+uns...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/merb?hl=en.
is a ghost town for support. Most merb users seem to be hackers or
developers. The average joe is SOL here. #merb useful if you're
lucky or persistent enough to get a sympathetic ear. I knew the
disparity in userbases going in but needed easy datamapper and
something else provided by merb.
--
You received this message because you are subscribed to the Google Groups "merb" group.
To post to this group, send email to me...@googlegroups.com.
To unsubscribe from this group, send email to merb+uns...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/merb?hl=en.
Ted Han
Apr 24, 2010, 2:04:29 PM4/24/10
to me...@googlegroups.com
Ming, i'm sorry you feel that way, though merb's future is certainly in limbo atm. You can find help for datamapper related problems in #datamapper. There's usually someone around answering questions (may even get help w/ merb related stuff).
I think raising awareness about the issue isn't a bad thing, but we need to come up with solutions to the problem, or at least describe what a solution would look like.
Do you have any suggestions? :(
from one merb user to another,
-knowtheory
Pavel Kunc
Apr 24, 2010, 5:28:46 PM4/24/10
to merb
Ming if you need something urgent best is to ping me in #merb. Usually
try to be responsive as possible. Have to say that I've been now 2
weeks off.
Pavel
try to be responsive as possible. Have to say that I've been now 2
weeks off.
Pavel
MarkMT
Apr 27, 2010, 8:02:56 AM4/27/10
to merb
It's been a bit quiet here lately - discussion seems a bit bursty, but
Pavel et al always seem very responsive to me. My bigger
disappointment is that the commitment from the original core team to
provide a series of incremental releases of merb that transition it to
Rails 3 no longer seems to be on their radar. At the moment, it isn't
clear to me what that transition is going to look like.
Pavel et al always seem very responsive to me. My bigger
disappointment is that the commitment from the original core team to
provide a series of incremental releases of merb that transition it to
Rails 3 no longer seems to be on their radar. At the moment, it isn't
clear to me what that transition is going to look like.
Yehuda Katz
Apr 27, 2010, 2:06:12 PM4/27/10
to merb
Mark,
I'd still be interested in that, but the new core team (Pavel, etc.) have expressed that they specifically do *not* want to go in that direction.
Pavel Kunc
Apr 27, 2010, 6:45:03 PM4/27/10
to merb
I'm willing to help anybody with my knowledge of Merb to contribute
changes needed for Rails3-ish version of Merb. However I don't
personally have any spare time to do the actual coding in this
direction.
Question would be what is needed to allow the easy transition. In my
opinion if someone wants to migrate to Rails3 from Merb than there
always be cost of the transition. If the transition is done in one go
or incremental IMHO doesn't change the cost of it much. If I'd like to
move I'd do it in one go rather than hanging in between the
frameworks.
What I can say is coming to Merb is:
- full support ActiveModel API which means you can use ActiveRecord 3
(merb_activerecord is outdated I think).
- probably ActiveSupport integration (there is still ongoing debate).
The dual extlib/AS3 can be expected.
- there will be changes to Rack integration which brings Merb closer
to Rails 3
This two changes will allow you to use some of the Rails 3 features,
for more stuff Jacuqes wanted to do something about this and there is
an idea shaping to provide merb_rails3 gem. The problem I currently
have is my limited knowledge of Rails 3 to be honest.
There are people doing the guide which helps with Merb -> Rails3
transition. I'll hopefully find the links/tweets which is yet another
way how to help people with the transition. I'd love to create wiki
page on the github.com/merb with information and resources about the
Merb -> Rails 3 transition.
Yehuda and Carl are super busy with delivering Rails 3 and Bundler
project and I totally understand that it's near to impossible to work
on the Merb->Rails3 transition. And honestly, I don't feel they
obliged to.
I think people who're about to switch should drive the contributions.
And as I've mentioned people are working on it.
I'll support/help/accept contributions if it doesn't cause current
Merb users to suffer.
Pavel
> > merb+uns...@googlegroups.com <merb%2Bunsu...@googlegroups.com>.
changes needed for Rails3-ish version of Merb. However I don't
personally have any spare time to do the actual coding in this
direction.
Question would be what is needed to allow the easy transition. In my
opinion if someone wants to migrate to Rails3 from Merb than there
always be cost of the transition. If the transition is done in one go
or incremental IMHO doesn't change the cost of it much. If I'd like to
move I'd do it in one go rather than hanging in between the
frameworks.
What I can say is coming to Merb is:
- full support ActiveModel API which means you can use ActiveRecord 3
(merb_activerecord is outdated I think).
- probably ActiveSupport integration (there is still ongoing debate).
The dual extlib/AS3 can be expected.
- there will be changes to Rack integration which brings Merb closer
to Rails 3
This two changes will allow you to use some of the Rails 3 features,
for more stuff Jacuqes wanted to do something about this and there is
an idea shaping to provide merb_rails3 gem. The problem I currently
have is my limited knowledge of Rails 3 to be honest.
There are people doing the guide which helps with Merb -> Rails3
transition. I'll hopefully find the links/tweets which is yet another
way how to help people with the transition. I'd love to create wiki
page on the github.com/merb with information and resources about the
Merb -> Rails 3 transition.
Yehuda and Carl are super busy with delivering Rails 3 and Bundler
project and I totally understand that it's near to impossible to work
on the Merb->Rails3 transition. And honestly, I don't feel they
obliged to.
I think people who're about to switch should drive the contributions.
And as I've mentioned people are working on it.
I'll support/help/accept contributions if it doesn't cause current
Merb users to suffer.
Pavel
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "merb" group.
> > > To post to this group, send email to me...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > merb+uns...@googlegroups.com <merb%2Bunsu...@googlegroups.com>.
> > > You received this message because you are subscribed to the Google Groups
> > "merb" group.
> > > To post to this group, send email to me...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > --
> > You received this message because you are subscribed to the Google Groups
> > "merb" group.
> > To post to this group, send email to me...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > merb+uns...@googlegroups.com <merb%2Bunsu...@googlegroups.com>.
> > You received this message because you are subscribed to the Google Groups
> > "merb" group.
> > To post to this group, send email to me...@googlegroups.com.
> > To unsubscribe from this group, send email to
MarkMT
Apr 28, 2010, 8:39:28 AM4/28/10
to merb
Thanks Pavel and Yehuda. I think wiki documentation on how to move a
merb app to Rails 3 would be tremendously helpful. There have been
numerous blog articles on how Rails 3 differs from Rails 2.x, but I've
seen nothing on how it differs from merb 1.1. Whether a transition
strategy is single shot or incremental, I think providing whatever
guidance is required to make the transition would be in the spirit of
the comments made when the merge was originally announced.
Mark.
merb app to Rails 3 would be tremendously helpful. There have been
numerous blog articles on how Rails 3 differs from Rails 2.x, but I've
seen nothing on how it differs from merb 1.1. Whether a transition
strategy is single shot or incremental, I think providing whatever
guidance is required to make the transition would be in the spirit of
the comments made when the merge was originally announced.
Mark.
Ian Eyberg
Apr 28, 2010, 11:42:06 AM4/28/10
to me...@googlegroups.com
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
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
Jonathan Stott
Apr 28, 2010, 12:16:03 PM4/28/10
to me...@googlegroups.com
On Wed, 28 Apr 2010 10:42:06 -0500
Ian Eyberg <i...@telematter.com> 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.
Ian Eyberg <i...@telematter.com> 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 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
Pavel Kunc
Apr 28, 2010, 5:04:03 PM4/28/10
to merb
Seems that the official wiki would be really good so:
http://wiki.github.com/merb/merb/howto-switch-to-rails-3 (sorry I
couldn't resist)
I count on the community to create best resource for the Merb -> Rails
3 transition.
Pavel
http://wiki.github.com/merb/merb/howto-switch-to-rails-3 (sorry I
couldn't resist)
I count on the community to create best resource for the Merb -> Rails
3 transition.
Pavel
MarkMT
Apr 28, 2010, 8:09:00 PM4/28/10
to merb
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 <pavel.k...@gmail.com> wrote:
> Seems that the official wiki would be really good so:
>
> http://wiki.github.com/merb/merb/howto-switch-to-rails-3(sorry I
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 <pavel.k...@gmail.com> wrote:
> Seems that the official wiki would be really good so:
>
Michishige Kaito
Apr 29, 2010, 11:18:00 AM4/29/10
to me...@googlegroups.com
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 <mark.t...@ieee.org>
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 <mark.t...@ieee.org>
pedro mg
May 12, 2010, 6:19:29 PM5/12/10
to me...@googlegroups.com
On Apr 27, 2010, at 11:45 PM, Pavel Kunc wrote:
>
> I think people who're about to switch should drive the contributions.
> And as I've mentioned people are working on it.
>
> I'll support/help/accept contributions if it doesn't cause current
> Merb users to suffer.
>
As for the original message, from Ming, with some patience he can get high level support from core devs/maintainers.
:message => "Long Live Merb"
--
pedro mg
http://blog.tquadrado.com
pedro mg
May 12, 2010, 6:30:06 PM5/12/10
to me...@googlegroups.com
Hi,
On Apr 28, 2010, at 5:16 PM, Jonathan Stott wrote:
> On Wed, 28 Apr 2010 10:42:06 -0500
> Ian Eyberg <i...@telematter.com> wrote:
>
>> as the maintainer of a larger merb stack in production use
>> I fully agree with this statement...
My team is working on 2 new web apps using Merb and plan to continue using it after that. I came from _why's Camping. Studied severall frameworks and moved into Merb.
I don't see frameworks like t-shirts, but understand Merb won't fit in every project, obviously.
>>
>> 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.
Agree.
>
> 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.
>
:merb => ["Good Principles", "Good code", "Stability", "Fun"]
> Regards
> Jon
>
pedro mg
http://blog.tquadrado.com
On Apr 28, 2010, at 5:16 PM, Jonathan Stott wrote:
> On Wed, 28 Apr 2010 10:42:06 -0500
> Ian Eyberg <i...@telematter.com> wrote:
>
>> as the maintainer of a larger merb stack in production use
>> I fully agree with this statement...
I don't see frameworks like t-shirts, but understand Merb won't fit in every project, obviously.
>>
>> 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
>
pedro mg
http://blog.tquadrado.com
Reply all
Reply to author
Forward
0 new messages