On Wed, Nov 11, 2009 at 6:28 PM, Jacques Crocker <[email protected]> wrote:
> > > 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 > 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 > > > On Nov 11, 6:24 pm, Matt Aimonetti <[email protected]> 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 <[email protected]> > 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. > > > > > We've separated out some gems into top level github.com/merbrepositories. > > > 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 > > > > > *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. > > > > > 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. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
