Merb Reorg
1 view
Skip to first unread message
Jacques Crocker
Nov 11, 2009, 9:13:09 PM11/11/09
to me...@googlegroups.com
Merb is slowly resurrecting into an active development project again, and we're reorganizing things a bit so the project is easier to maintain via a small and distributed group of contributors. If you still use Merb and would like to make your impact, now's a great time to take ownership of your piece of the framework. We currently have about half a dozen or so people who are contributing to Merb on an active basis, and would love to have your help steering the project back to life with a stable 1.1 release and beyond.
Source Code:
The official Merb home on github has moved to http://github.com/merb. The core gems will now live at http://github.com/merb/merb. Merb's previous home (github.com/wycats/merb) has had code updated for the recent 1.0.15 release (the last of the 1.0.x). Any new releases, 1.1 and beyond, will be at github.com/merb/merb.
We've separated out some gems into top level github.com/merb repositories. merb_datamapper and merb-auth are now separate repositories. They are still included and built as part of the default stack, however they'll now be maintained as separate gems.
Other important gems in the Merb ecosystem have now been forked into github.com/merb. Examples include merb_sequel, merb_cucumber, merb_activerecord, and merb_parts. These gems can be considered "active and maintained". Other gems will eventually be added here as a way to highlight the most common and useful Merb plugins, and provide a better common destination for all the available forks of these plugins. Commit access can be easily obtained for any active contributors to these libraries.
Merb's Lighthouse (merb.lighthouseapp.com) will continue to be the main Merb bug tracking for github.com/merb/merb. All other top level projects however will just use github's built in issue tracker. This will allow the lighthouse tickets to stay focused on the common gems used by the majority of Merb developers, while specific issues on the other Merb gems can stay as close as possible to the source and maintainers.
Releases:
Merb will now use gemcutter.org to host all new release and prerelease Merb gems. If you have edge.merbivore.com on as a rubygem source path, we'd recommend removing it as soon as possible and replacing it with http://gemcutter.org
Documentation:
We'll be migrating the previous merbivore wiki system over to a github hosted, static site repository at http://merb.github.com. This is similar to how Sinatra organizes it's docs, and any documentation contributions can be made by forking and updating the site codebase. We'll also allow commit access here for anyone who would like to actively contribute to the main docs without the overhead of approving and merging commits.
For howto's and other notes, we'll use the built-in github wiki system (wiki.github.com/merb/merb). The main goal is to build up a stable documentation library within the site, so any useful content on the wiki will eventually be migrated over to the static documentation site's github repository.
The Merb internals book, written by Michael Klishin, has also been integrated into the root Merb repository and will be hosted via a generated github static site at merb.github.com/internals. This will be maintained as the main getting started documentation for people who want to start hacking on the Merb source code.
Matt's "Merb Book" project will also be resurrected and hosted as a github.com static site repository, hosted at merb.github.com/book. We'll probably drop the multilingual support and focus on just filling out the docs in English for now, unless someone wants to focus on translations and maintenance for any given language.
Team:
Pavel Kunc (github.com/pk), Martin Gamsjaeger (github.com/snusnu), Jonathon Stott (github.com/namelessjon), and Jacques Crocker (github.com/merbjedi) have been the primary drivers on this reorganization and have been actively contributing to Merb development. However, we are *not* looking to replace the old core team. What we are is Merb hackers who are looking to extend and revive the project that currently provides the absolute best tools for web development in Ruby.
Since Merb is now completely dependent on the user community for patches and development of new features, any person who contributes even a single commit will be mentioned, praised, and documented as a core Merb contributor. Our goal is to be much more responsive with pull requests, so please send them to us via github and we'll try to merge in any useful code contributions that we find.
The Future:
Merb 1.1.0pre release to gemcutter very soon (in the next few days). It has full bundler integration, and tons of bug fixes from lighthouse. We believe it's already quite stable, but we'll be fixing addition bugs on it for the next couple weeks, with a target Merb 1.1 release shortly after RubyConf.
Matt Aimonetti
Nov 11, 2009, 9:24:02 PM11/11/09
to me...@googlegroups.com
It's awesome guys!
Regarding the merb book, I would recommend to no through away the translations, I think they are very important and it's a way for a lot of people to contribute. There is also a lot of content from Matthew Ford's book that could be merged in.
Keep up the good work and see you at RubyConf.
- Matt
Regarding the merb book, I would recommend to no through away the translations, I think they are very important and it's a way for a lot of people to contribute. There is also a lot of content from Matthew Ford's book that could be merged in.
Keep up the good work and see you at RubyConf.
- Matt
Jacques Crocker
Nov 11, 2009, 9:28:56 PM11/11/09
to merb
> Regarding the merb book, I would recommend to no through away the
> translations, I think they are very important and it's a way for a lot of
> people to contribute. There is also a lot of content from Matthew Ford's
> book that could be merged in.
Yeah, that's a good point. We should keep the translations. I'm
> translations, I think they are very important and it's a way for a lot of
> people to contribute. There is also a lot of content from Matthew Ford's
> book that could be merged in.
updating the site to be html generated (webgen) so github to host it
so I'll go ahead and include the translations files in the html
generation scripts. Shouldn't be too hard.
On Nov 11, 6:24 pm, Matt Aimonetti <mattaimone...@gmail.com> wrote:
> It's awesome guys!
>
> Regarding the merb book, I would recommend to no through away the
> translations, I think they are very important and it's a way for a lot of
> people to contribute. There is also a lot of content from Matthew Ford's
> book that could be merged in.
>
> Keep up the good work and see you at RubyConf.
>
> - Matt
>
>
>
> On Wed, Nov 11, 2009 at 6:13 PM, Jacques Crocker <merbj...@gmail.com> wrote:
> > Merb is slowly resurrecting into an active development project again, and
> > we're reorganizing things a bit so the project is easier to maintain via a
> > small and distributed group of contributors. If you still use Merb and would
> > like to make your impact, now's a great time to take ownership of your piece
> > of the framework. We currently have about half a dozen or so people who are
> > contributing to Merb on an active basis, and would love to have your help
> > steering the project back to life with a stable 1.1 release and beyond.
>
> > The official Merb home on github has moved tohttp://github.com/merb. The
> > core gems will now live athttp://github.com/merb/merb. Merb's previous
> > home (github.com/wycats/merb) has had code updated for the recent 1.0.15
> > release (the last of the 1.0.x). Any new releases, 1.1 and beyond, will be
> > at github.com/merb/merb.
>
> > We've separated out some gems into top level github.com/merb repositories.
> > merb_datamapper and merb-auth are now separate repositories. They are still
> > included and built as part of the default stack, however they'll now be
> > maintained as separate gems.
>
> > Other important gems in the Merb ecosystem have now been forked into
> > github.com/merb. Examples include merb_sequel, merb_cucumber,
> > merb_activerecord, and merb_parts. These gems can be considered "active and
> > maintained". Other gems will eventually be added here as a way to highlight
> > the most common and useful Merb plugins, and provide a better common
> > destination for all the available forks of these plugins. Commit access can
> > be easily obtained for any active contributors to these libraries.
>
> > Merb's Lighthouse (merb.lighthouseapp.com) will continue to be the
> > main Merb bug tracking for github.com/merb/merb. All other top level
> > projects however will just use github's built in issue tracker. This will
> > allow the lighthouse tickets to stay focused on the common gems used by the
> > majority of Merb developers, while specific issues on the other Merb gems
> > can stay as close as possible to the source and maintainers.
>
> > *Releases:*
> > release (the last of the 1.0.x). Any new releases, 1.1 and beyond, will be
> > at github.com/merb/merb.
>
> > We've separated out some gems into top level github.com/merb repositories.
> > merb_datamapper and merb-auth are now separate repositories. They are still
> > included and built as part of the default stack, however they'll now be
> > maintained as separate gems.
>
> > Other important gems in the Merb ecosystem have now been forked into
> > github.com/merb. Examples include merb_sequel, merb_cucumber,
> > merb_activerecord, and merb_parts. These gems can be considered "active and
> > maintained". Other gems will eventually be added here as a way to highlight
> > the most common and useful Merb plugins, and provide a better common
> > destination for all the available forks of these plugins. Commit access can
> > be easily obtained for any active contributors to these libraries.
>
> > Merb's Lighthouse (merb.lighthouseapp.com) will continue to be the
> > main Merb bug tracking for github.com/merb/merb. All other top level
> > projects however will just use github's built in issue tracker. This will
> > allow the lighthouse tickets to stay focused on the common gems used by the
> > majority of Merb developers, while specific issues on the other Merb gems
> > can stay as close as possible to the source and maintainers.
>
> > Merb will now use gemcutter.org to host all new release and
> > prerelease Merb gems. If you have edge.merbivore.com on as a rubygem
> > source path, we'd recommend removing it as soon as possible and replacing it
> > withhttp://gemcutter.org
>
> > *Documentation:*
> > prerelease Merb gems. If you have edge.merbivore.com on as a rubygem
> > source path, we'd recommend removing it as soon as possible and replacing it
> > withhttp://gemcutter.org
>
> > We'll be migrating the previous merbivore wiki system over to a github
> > hosted, static site repository athttp://merb.github.com. This is similar
> > to how Sinatra organizes it's docs, and any documentation contributions can
> > be made by forking and updating the site codebase. We'll also allow commit
> > access here for anyone who would like to actively contribute to the main
> > docs without the overhead of approving and merging commits.
>
> > For howto's and other notes, we'll use the built-in github wiki system (
> > wiki.github.com/merb/merb). The main goal is to build up a stable
> > documentation library within the site, so any useful content on the wiki
> > will eventually be migrated over to the static documentation site's github
> > repository.
>
> > The Merb internals book, written by Michael Klishin, has also been
> > integrated into the root Merb repository and will be hosted via a generated
> > github static site at merb.github.com/internals. This will be maintained
> > as the main getting started documentation for people who want to start
> > hacking on the Merb source code.
>
> > Matt's "Merb Book" project will also be resurrected and hosted as a
> > github.com static site repository, hosted at merb.github.com/book. We'll
> > probably drop the multilingual support and focus on just filling out the
> > docs in English for now, unless someone wants to focus on translations and
> > maintenance for any given language.
>
> > *Team:*
> > be made by forking and updating the site codebase. We'll also allow commit
> > access here for anyone who would like to actively contribute to the main
> > docs without the overhead of approving and merging commits.
>
> > For howto's and other notes, we'll use the built-in github wiki system (
> > wiki.github.com/merb/merb). The main goal is to build up a stable
> > documentation library within the site, so any useful content on the wiki
> > will eventually be migrated over to the static documentation site's github
> > repository.
>
> > The Merb internals book, written by Michael Klishin, has also been
> > integrated into the root Merb repository and will be hosted via a generated
> > github static site at merb.github.com/internals. This will be maintained
> > as the main getting started documentation for people who want to start
> > hacking on the Merb source code.
>
> > Matt's "Merb Book" project will also be resurrected and hosted as a
> > github.com static site repository, hosted at merb.github.com/book. We'll
> > probably drop the multilingual support and focus on just filling out the
> > docs in English for now, unless someone wants to focus on translations and
> > maintenance for any given language.
>
> > Pavel Kunc (github.com/pk), Martin Gamsjaeger (github.com/snusnu),
> > Jonathon Stott (github.com/namelessjon), and Jacques Crocker (
> > github.com/merbjedi) have been the primary drivers on this reorganization
> > and have been actively contributing to Merb development. However, we are
> > *not* looking to replace the old core team. What we are is Merb hackers who
> > are looking to extend and revive the project that currently provides the
> > absolute best tools for web development in Ruby.
>
> > Since Merb is now completely dependent on the user community for patches
> > and development of new features, any person who contributes even a single
> > commit will be mentioned, praised, and documented as a core Merb
> > contributor. Our goal is to be much more responsive with pull requests, so
> > please send them to us via github and we'll try to merge in any useful code
> > contributions that we find.
> > **
> > Jonathon Stott (github.com/namelessjon), and Jacques Crocker (
> > github.com/merbjedi) have been the primary drivers on this reorganization
> > and have been actively contributing to Merb development. However, we are
> > *not* looking to replace the old core team. What we are is Merb hackers who
> > are looking to extend and revive the project that currently provides the
> > absolute best tools for web development in Ruby.
>
> > Since Merb is now completely dependent on the user community for patches
> > and development of new features, any person who contributes even a single
> > commit will be mentioned, praised, and documented as a core Merb
> > contributor. Our goal is to be much more responsive with pull requests, so
> > please send them to us via github and we'll try to merge in any useful code
> > contributions that we find.
> > *The Future:*
Matt Aimonetti
Nov 11, 2009, 9:31:57 PM11/11/09
to me...@googlegroups.com
On Wed, Nov 11, 2009 at 6:28 PM, Jacques Crocker <merb...@gmail.com> wrote:
Yeah, that's a good point. We should keep the translations. I'm
> Regarding the merb book, I would recommend to no through away the
> translations, I think they are very important and it's a way for a lot of
> people to contribute. There is also a lot of content from Matthew Ford's
> book that could be merged in.
updating the site to be html generated (webgen) so github to host it
so I'll go ahead and include the translations files in the html
generation scripts. Shouldn't be too hard.
Why not just putting it on heroku? it's a simple merb app that generates html, add a etag and heroku will cache the pages in varnish
http://book.merbist.com/
This way, you can keep the source files in markdown and let them get converted at runtime.
- Matt
MarkMT
Nov 11, 2009, 10:00:20 PM11/11/09
to merb
Very much appreciate the continuing efforts and the encouragement for
folks to get involved. I'm hoping I may be able to contribute
something by way of documentation, if not actual code. I started
working with merb largely because I was so impressed by the merbcamp
presentations last year. I've continued to work with it in the
expectation that it will eventually evolve into Rails 3, and have
enjoyed sometimes having to dive into the internals, and honing my
ruby knowledge in the process. I guess like others I've wondered
exactly how/when/whether the Rails transition will happen but I think
the renewal of active development that you've outlined provides some
reassurance that regardless of how that plays out, there will continue
to be a framework that truly reflects the vision and philosophy of
merb.
One thing I'm not clear on is the github issue tracking for gems not
in the main repository. I haven't used github for this before and I'm
having difficulty finding this feature. Can you maybe post a link to
this feature for one of the repos, say merb_cucumber?
Mark
On Nov 11, 8:13 pm, Jacques Crocker <merbj...@gmail.com> wrote:
> Merb is slowly resurrecting into an active development project again, and we're reorganizing things a bit so the project is easier to maintain via a small and distributed group of contributors. If you still use Merb and would like to make your impact, now's a great time to take ownership of your piece of the framework. We currently have about half a dozen or so people who are contributing to Merb on an active basis, and would love to have your help steering the project back to life with a stable 1.1 release and beyond.
>
> Source Code:
> The official Merb home on github has moved tohttp://github.com/merb. The core gems will now live athttp://github.com/merb/merb. Merb's previous home (github.com/wycats/merb) has had code updated for the recent 1.0.15 release (the last of the 1.0.x). Any new releases, 1.1 and beyond, will be at github.com/merb/merb.
>
> Documentation:
> We'll be migrating the previous merbivore wiki system over to a github hosted, static site repository athttp://merb.github.com. This is similar to how Sinatra organizes it's docs, and any documentation contributions can be made by forking and updating the site codebase. We'll also allow commit access here for anyone who would like to actively contribute to the main docs without the overhead of approving and merging commits.
folks to get involved. I'm hoping I may be able to contribute
something by way of documentation, if not actual code. I started
working with merb largely because I was so impressed by the merbcamp
presentations last year. I've continued to work with it in the
expectation that it will eventually evolve into Rails 3, and have
enjoyed sometimes having to dive into the internals, and honing my
ruby knowledge in the process. I guess like others I've wondered
exactly how/when/whether the Rails transition will happen but I think
the renewal of active development that you've outlined provides some
reassurance that regardless of how that plays out, there will continue
to be a framework that truly reflects the vision and philosophy of
merb.
One thing I'm not clear on is the github issue tracking for gems not
in the main repository. I haven't used github for this before and I'm
having difficulty finding this feature. Can you maybe post a link to
this feature for one of the repos, say merb_cucumber?
Mark
On Nov 11, 8:13 pm, Jacques Crocker <merbj...@gmail.com> wrote:
> Merb is slowly resurrecting into an active development project again, and we're reorganizing things a bit so the project is easier to maintain via a small and distributed group of contributors. If you still use Merb and would like to make your impact, now's a great time to take ownership of your piece of the framework. We currently have about half a dozen or so people who are contributing to Merb on an active basis, and would love to have your help steering the project back to life with a stable 1.1 release and beyond.
>
> Source Code:
>
> We've separated out some gems into top level github.com/merb repositories. merb_datamapper and merb-auth are now separate repositories. They are still included and built as part of the default stack, however they'll now be maintained as separate gems.
>
> Other important gems in the Merb ecosystem have now been forked into github.com/merb. Examples include merb_sequel, merb_cucumber, merb_activerecord, and merb_parts. These gems can be considered "active and maintained". Other gems will eventually be added here as a way to highlight the most common and useful Merb plugins, and provide a better common destination for all the available forks of these plugins. Commit access can be easily obtained for any active contributors to these libraries.
>
> Merb's Lighthouse (merb.lighthouseapp.com) will continue to be the main Merb bug tracking for github.com/merb/merb. All other top level projects however will just use github's built in issue tracker. This will allow the lighthouse tickets to stay focused on the common gems used by the majority of Merb developers, while specific issues on the other Merb gems can stay as close as possible to the source and maintainers.
>
> Releases:
> Merb will now use gemcutter.org to host all new release and prerelease Merb gems. If you have edge.merbivore.com on as a rubygem source path, we'd recommend removing it as soon as possible and replacing it withhttp://gemcutter.org
> We've separated out some gems into top level github.com/merb repositories. merb_datamapper and merb-auth are now separate repositories. They are still included and built as part of the default stack, however they'll now be maintained as separate gems.
>
> Other important gems in the Merb ecosystem have now been forked into github.com/merb. Examples include merb_sequel, merb_cucumber, merb_activerecord, and merb_parts. These gems can be considered "active and maintained". Other gems will eventually be added here as a way to highlight the most common and useful Merb plugins, and provide a better common destination for all the available forks of these plugins. Commit access can be easily obtained for any active contributors to these libraries.
>
> Merb's Lighthouse (merb.lighthouseapp.com) will continue to be the main Merb bug tracking for github.com/merb/merb. All other top level projects however will just use github's built in issue tracker. This will allow the lighthouse tickets to stay focused on the common gems used by the majority of Merb developers, while specific issues on the other Merb gems can stay as close as possible to the source and maintainers.
>
> Releases:
>
> Documentation:
> We'll be migrating the previous merbivore wiki system over to a github hosted, static site repository athttp://merb.github.com. This is similar to how Sinatra organizes it's docs, and any documentation contributions can be made by forking and updating the site codebase. We'll also allow commit access here for anyone who would like to actively contribute to the main docs without the overhead of approving and merging commits.
Jacques Crocker
Nov 11, 2009, 10:01:33 PM11/11/09
to me...@googlegroups.com, me...@googlegroups.com
Sounds like a good strategy, especially if we can trigger updates via a github hook. I'll check into it.
- Jacques
Jan
Nov 11, 2009, 10:24:22 PM11/11/09
to me...@googlegroups.com
It's so exciting that merb is resurrecting, we have one more reason not to rewrite our merb project in rails now. Good job :-)
Cheers.
Cheers.
Matt Aimonetti
Nov 12, 2009, 3:00:48 AM11/12/09
to me...@googlegroups.com
btw from GitHub:
Most Watched This Month
FooBarWidget / rubystein
javan / whenever
fudgestudios / bort
mattetti / merb-book
defunkt / cijoe
I guess the merb book is still popular, having new content will probably help.
- Matt
Most Watched This Month
FooBarWidget / rubystein
javan / whenever
fudgestudios / bort
mattetti / merb-book
defunkt / cijoe
I guess the merb book is still popular, having new content will probably help.
- Matt
Pavel Kunc
Nov 12, 2009, 8:09:12 AM11/12/09
to merb
Hi,
I also think we should keep the translations. Maintaining the
translations is going to be whole different story, but that is one
thing community should take care of. Migration of the wiki and
documentation is going to be big task as well. And wiki could use some
updates.
I've talked yesterday about Merb on LRUG (London Ruby UG) with good
results. One mentioned disadvantage of Merb (over rails) was
documentation. Also the silence project suffered was mentioned often,
hopefully we managed to change that.
There is an interest having Merb hacking event in Europe as well.
Which is really interesting for all us who can't make it to the
RubyConf (3/4 of the team :-)). I'll put together proposal and
circulate it here.
Pavel
On Nov 12, 8:00 am, Matt Aimonetti <mattaimone...@gmail.com> wrote:
> btw from GitHub:
>
> Most Watched This Month
>
> FooBarWidget / rubystein
> javan / whenever
> fudgestudios / bort
> mattetti / merb-book
> defunkt / cijoe
>
> I guess the merb book is still popular, having new content will probably
> help.
>
> - Matt
>
>
>
> On Wed, Nov 11, 2009 at 7:24 PM, Jan <jan.h....@gmail.com> wrote:
> > It's so exciting that merb is resurrecting, we have one more reason not to
> > rewrite our merb project in rails now. Good job :-)
>
> > Cheers.
>
> >> The official Merb home on github has moved tohttp://github.com/merb. The
> >> core gems will now live athttp://github.com/merb/merb. Merb's previous
> >> *The Future:*
I also think we should keep the translations. Maintaining the
translations is going to be whole different story, but that is one
thing community should take care of. Migration of the wiki and
documentation is going to be big task as well. And wiki could use some
updates.
I've talked yesterday about Merb on LRUG (London Ruby UG) with good
results. One mentioned disadvantage of Merb (over rails) was
documentation. Also the silence project suffered was mentioned often,
hopefully we managed to change that.
There is an interest having Merb hacking event in Europe as well.
Which is really interesting for all us who can't make it to the
RubyConf (3/4 of the team :-)). I'll put together proposal and
circulate it here.
Pavel
On Nov 12, 8:00 am, Matt Aimonetti <mattaimone...@gmail.com> wrote:
> btw from GitHub:
>
> Most Watched This Month
>
> FooBarWidget / rubystein
> javan / whenever
> fudgestudios / bort
> mattetti / merb-book
> defunkt / cijoe
>
> I guess the merb book is still popular, having new content will probably
> help.
>
> - Matt
>
>
>
> On Wed, Nov 11, 2009 at 7:24 PM, Jan <jan.h....@gmail.com> wrote:
> > It's so exciting that merb is resurrecting, we have one more reason not to
> > rewrite our merb project in rails now. Good job :-)
>
> > Cheers.
>
> > On Thu, Nov 12, 2009 at 10:13 AM, Jacques Crocker <merbj...@gmail.com>wrote:
>
> >> Merb is slowly resurrecting into an active development project again, and
> >> we're reorganizing things a bit so the project is easier to maintain via a
> >> small and distributed group of contributors. If you still use Merb and would
> >> like to make your impact, now's a great time to take ownership of your piece
> >> of the framework. We currently have about half a dozen or so people who are
> >> contributing to Merb on an active basis, and would love to have your help
> >> steering the project back to life with a stable 1.1 release and beyond.
>
> >> *Source Code:*
>
> >> Merb is slowly resurrecting into an active development project again, and
> >> we're reorganizing things a bit so the project is easier to maintain via a
> >> small and distributed group of contributors. If you still use Merb and would
> >> like to make your impact, now's a great time to take ownership of your piece
> >> of the framework. We currently have about half a dozen or so people who are
> >> contributing to Merb on an active basis, and would love to have your help
> >> steering the project back to life with a stable 1.1 release and beyond.
>
> >> The official Merb home on github has moved tohttp://github.com/merb. The
> >> core gems will now live athttp://github.com/merb/merb. Merb's previous
> >> home (github.com/wycats/merb) has had code updated for the recent 1.0.15
> >> release (the last of the 1.0.x). Any new releases, 1.1 and beyond, will be
> >> at github.com/merb/merb.
>
> >> We've separated out some gems into top level github.com/merbrepositories. merb_datamapper and merb-auth are now separate repositories.
> >> release (the last of the 1.0.x). Any new releases, 1.1 and beyond, will be
> >> at github.com/merb/merb.
>
> >> They are still included and built as part of the default stack, however
> >> they'll now be maintained as separate gems.
>
> >> Other important gems in the Merb ecosystem have now been forked into
> >> github.com/merb. Examples include merb_sequel, merb_cucumber,
> >> merb_activerecord, and merb_parts. These gems can be considered "active and
> >> maintained". Other gems will eventually be added here as a way to highlight
> >> the most common and useful Merb plugins, and provide a better common
> >> destination for all the available forks of these plugins. Commit access can
> >> be easily obtained for any active contributors to these libraries.
>
> >> Merb's Lighthouse (merb.lighthouseapp.com) will continue to be the
> >> main Merb bug tracking for github.com/merb/merb. All other top level
> >> projects however will just use github's built in issue tracker. This will
> >> allow the lighthouse tickets to stay focused on the common gems used by the
> >> majority of Merb developers, while specific issues on the other Merb gems
> >> can stay as close as possible to the source and maintainers.
>
> >> *Releases:*
> >> they'll now be maintained as separate gems.
>
> >> Other important gems in the Merb ecosystem have now been forked into
> >> github.com/merb. Examples include merb_sequel, merb_cucumber,
> >> merb_activerecord, and merb_parts. These gems can be considered "active and
> >> maintained". Other gems will eventually be added here as a way to highlight
> >> the most common and useful Merb plugins, and provide a better common
> >> destination for all the available forks of these plugins. Commit access can
> >> be easily obtained for any active contributors to these libraries.
>
> >> Merb's Lighthouse (merb.lighthouseapp.com) will continue to be the
> >> main Merb bug tracking for github.com/merb/merb. All other top level
> >> projects however will just use github's built in issue tracker. This will
> >> allow the lighthouse tickets to stay focused on the common gems used by the
> >> majority of Merb developers, while specific issues on the other Merb gems
> >> can stay as close as possible to the source and maintainers.
>
> >> Merb will now use gemcutter.org to host all new release and
> >> prerelease Merb gems. If you have edge.merbivore.com on as a rubygem
> >> source path, we'd recommend removing it as soon as possible and replacing it
> >> withhttp://gemcutter.org
>
> >> *Documentation:*
> >> prerelease Merb gems. If you have edge.merbivore.com on as a rubygem
> >> source path, we'd recommend removing it as soon as possible and replacing it
> >> withhttp://gemcutter.org
>
> >> We'll be migrating the previous merbivore wiki system over to a github
> >> hosted, static site repository athttp://merb.github.com. This is similar
> >> to how Sinatra organizes it's docs, and any documentation contributions can
> >> be made by forking and updating the site codebase. We'll also allow commit
> >> access here for anyone who would like to actively contribute to the main
> >> docs without the overhead of approving and merging commits.
>
> >> For howto's and other notes, we'll use the built-in github wiki system (
> >> wiki.github.com/merb/merb). The main goal is to build up a stable
> >> documentation library within the site, so any useful content on the wiki
> >> will eventually be migrated over to the static documentation site's github
> >> repository.
>
> >> The Merb internals book, written by Michael Klishin, has also been
> >> integrated into the root Merb repository and will be hosted via a generated
> >> github static site at merb.github.com/internals. This will be maintained
> >> as the main getting started documentation for people who want to start
> >> hacking on the Merb source code.
>
> >> Matt's "Merb Book" project will also be resurrected and hosted as a
> >> github.com static site repository, hosted at merb.github.com/book. We'll
> >> probably drop the multilingual support and focus on just filling out the
> >> docs in English for now, unless someone wants to focus on translations and
> >> maintenance for any given language.
>
> >> *Team:*
> >> be made by forking and updating the site codebase. We'll also allow commit
> >> access here for anyone who would like to actively contribute to the main
> >> docs without the overhead of approving and merging commits.
>
> >> For howto's and other notes, we'll use the built-in github wiki system (
> >> wiki.github.com/merb/merb). The main goal is to build up a stable
> >> documentation library within the site, so any useful content on the wiki
> >> will eventually be migrated over to the static documentation site's github
> >> repository.
>
> >> The Merb internals book, written by Michael Klishin, has also been
> >> integrated into the root Merb repository and will be hosted via a generated
> >> github static site at merb.github.com/internals. This will be maintained
> >> as the main getting started documentation for people who want to start
> >> hacking on the Merb source code.
>
> >> Matt's "Merb Book" project will also be resurrected and hosted as a
> >> github.com static site repository, hosted at merb.github.com/book. We'll
> >> probably drop the multilingual support and focus on just filling out the
> >> docs in English for now, unless someone wants to focus on translations and
> >> maintenance for any given language.
>
> >> Pavel Kunc (github.com/pk), Martin Gamsjaeger (github.com/snusnu),
> >> Jonathon Stott (github.com/namelessjon), and Jacques Crocker (
> >> github.com/merbjedi) have been the primary drivers on this reorganization
> >> and have been actively contributing to Merb development. However, we are
> >> *not* looking to replace the old core team. What we are is Merb hackers who
> >> are looking to extend and revive the project that currently provides the
> >> absolute best tools for web development in Ruby.
>
> >> Since Merb is now completely dependent on the user community for patches
> >> and development of new features, any person who contributes even a single
> >> commit will be mentioned, praised, and documented as a core Merb
> >> contributor. Our goal is to be much more responsive with pull requests, so
> >> please send them to us via github and we'll try to merge in any useful code
> >> contributions that we find.
> >> **
> >> Jonathon Stott (github.com/namelessjon), and Jacques Crocker (
> >> github.com/merbjedi) have been the primary drivers on this reorganization
> >> and have been actively contributing to Merb development. However, we are
> >> *not* looking to replace the old core team. What we are is Merb hackers who
> >> are looking to extend and revive the project that currently provides the
> >> absolute best tools for web development in Ruby.
>
> >> Since Merb is now completely dependent on the user community for patches
> >> and development of new features, any person who contributes even a single
> >> commit will be mentioned, praised, and documented as a core Merb
> >> contributor. Our goal is to be much more responsive with pull requests, so
> >> please send them to us via github and we'll try to merge in any useful code
> >> contributions that we find.
> >> *The Future:*
MarkMT
Nov 12, 2009, 9:17:03 AM11/12/09
to merb
MarkMT wrote:
> One thing I'm not clear on is the github issue tracking for gems not
> in the main repository. I haven't used github for this before and I'm
> having difficulty finding this feature. Can you maybe post a link to
> this feature for one of the repos, say merb_cucumber?
Ok I figured out why I couldn't find the issues feature... you need to
> One thing I'm not clear on is the github issue tracking for gems not
> in the main repository. I haven't used github for this before and I'm
> having difficulty finding this feature. Can you maybe post a link to
> this feature for one of the repos, say merb_cucumber?
explicitly turn this on in the admin panel for each project.
Martin Gamsjaeger
Nov 12, 2009, 9:53:54 AM11/12/09
to me...@googlegroups.com
Mark,
Good catch! I enabled the Issues feature in the repos that still needed it.
cheers
snusnu
Good catch! I enabled the Issues feature in the repos that still needed it.
cheers
snusnu
MarkMT
Nov 12, 2009, 10:00:27 AM11/12/09
to merb
Thank you!
Dylan Clendenin
Nov 12, 2009, 3:22:04 PM11/12/09
to me...@googlegroups.com
I would love to help with documentation materials in any way I can. I'm planning on spending as much of my RubyConf time as possible on Merb stuff. Maybe I should just sell my ticket?--
Dylan Clendenin
831.331.1484
Dylan Clendenin
831.331.1484
Jacques Crocker
Nov 12, 2009, 4:24:51 PM11/12/09
to me...@googlegroups.com
Cool, would love your help with some merb hacking and docs update at RubyConf. I also sold my ticket and will just be hanging around the area, focusing on Merb dev. I'll send out details about where people can meet up (will be either in the hotel or walking distance from it). Free food and drinks to anyone willing to join up to watch and/or code!
Jeff Pollard
Nov 13, 2009, 2:17:00 PM11/13/09
to me...@googlegroups.com
I won't be at Rubyconf, but would be interested in helping with documentation too.
-J
-J
Dylan Clendenin
Nov 13, 2009, 2:25:31 PM11/13/09
to me...@googlegroups.com
I'm sure we'll find some creative ways to facilitate collaboration over that time. Wow, food and drinks? Right on Jacques.
Ashley Moran
Nov 16, 2009, 7:27:05 AM11/16/09
to me...@googlegroups.com
On Nov 12, 2009, at 3:24 am, Jan wrote:
> It's so exciting that merb is resurrecting, we have one more reason not to rewrite our merb project in rails now. Good job :-)
I'll second that. It's a shame that the Rails 3 "merge" announcement almost killed stone-dead one of the best pieces of software I've ever used. I've been looking into Ramaze as a backup plan, but it's just not as polished as Merb. I'm hoping to get a lot more mileage out of Merb yet...
Ashley
--
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
刘松
Nov 16, 2009, 10:21:59 PM11/16/09
to me...@googlegroups.com
I agree.
If rails3's default stack is prototype, activerecord, unit test, though its dividable ability, I don't think it's open enough.
If merb is to reorg, I vote YES.
If rails3's default stack is prototype, activerecord, unit test, though its dividable ability, I don't think it's open enough.
If merb is to reorg, I vote YES.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
cult hero
Nov 20, 2009, 6:28:17 PM11/20/09
to merb
Oh hell yes.
I shifted one of my projects from Merb to Ramaze when it felt like
things died and have been playing with that for a few months. (1.9
support is the main reason since we're using 1.9 in production for a
few necessary reasons.)
I would love to be using Merb again and frankly, I think I've learned
enough about Ruby in the past months that I can do more than be a
spectator! (Now I just need to learn to use Git properly. Heh.)
On Nov 16, 7:21 pm, 刘松 <liusong1...@gmail.com> wrote:
> I agree.
> If rails3's default stack is prototype, activerecord, unit test, though its
> dividable ability, I don't think it's open enough.
> If merb is to reorg, I vote YES.
>
> On Mon, Nov 16, 2009 at 8:27 PM, Ashley Moran <ashley.mo...@patchspace.co.uk
I shifted one of my projects from Merb to Ramaze when it felt like
things died and have been playing with that for a few months. (1.9
support is the main reason since we're using 1.9 in production for a
few necessary reasons.)
I would love to be using Merb again and frankly, I think I've learned
enough about Ruby in the past months that I can do more than be a
spectator! (Now I just need to learn to use Git properly. Heh.)
On Nov 16, 7:21 pm, 刘松 <liusong1...@gmail.com> wrote:
> I agree.
> If rails3's default stack is prototype, activerecord, unit test, though its
> dividable ability, I don't think it's open enough.
> If merb is to reorg, I vote YES.
>
>
>
>
> > wrote:
>
> > On Nov 12, 2009, at 3:24 am, Jan wrote:
>
> > > It's so exciting that merb is resurrecting, we have one more reason not
> > to rewrite our merb project in rails now. Good job :-)
>
> > I'll second that. It's a shame that the Rails 3 "merge" announcement
> > almost killed stone-dead one of the best pieces of software I've ever used.
> > I've been looking into Ramaze as a backup plan, but it's just not as
> > polished as Merb. I'm hoping to get a lot more mileage out of Merb yet...
>
> > Ashley
>
> > --
> >http://www.patchspace.co.uk/
> >http://www.linkedin.com/in/ashleymoran
>
> > --~--~---------~--~----~------------~-------~--~----~
> > 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>
>
>
> > wrote:
>
> > On Nov 12, 2009, at 3:24 am, Jan wrote:
>
> > > It's so exciting that merb is resurrecting, we have one more reason not
> > to rewrite our merb project in rails now. Good job :-)
>
> > I'll second that. It's a shame that the Rails 3 "merge" announcement
> > almost killed stone-dead one of the best pieces of software I've ever used.
> > I've been looking into Ramaze as a backup plan, but it's just not as
> > polished as Merb. I'm hoping to get a lot more mileage out of Merb yet...
>
> > Ashley
>
> > --
> >http://www.patchspace.co.uk/
> >http://www.linkedin.com/in/ashleymoran
>
> > --~--~---------~--~----~------------~-------~--~----~
> > 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
Chris Scott
Nov 21, 2009, 3:30:53 AM11/21/09
to me...@googlegroups.com
ExtJS digs and continues to support Merb
Our extjs-mvc Gem auto-renders Stores for three ORMs now: DataMapper, ActiveRecord and MongoMapper.
--
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.For more options, visit this group at http://groups.google.com/group/merb?hl=.
To unsubscribe from this group, send email to merb+uns...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages