Hi all, For those of you at the meeting this week that were interested in the full Node Version Module that I talked about, My old boss put it up on GitHub at
http://github.com/casefoundation/drupal-full_node_version/tree/master
I was going to set up a site with it so people could see it in action. At that point if anyone is interested maybe we could get togeather and hammer out any major issues.
For those of you who do not know what I am talking about, this is the abstract of the talk we were going to give about Full Node Version
Often we need to see a site to know when it's right. While preview is great for single pages, it falls short when publishing a bunch of linked content. What to do when preview isn't enough?
Code, of course. We tweaked Drupal's permissions system to provide multipage preview and a distinct view of test content. This code also enables batch moves to production -- without backing up and restoring the database.
With a couple of our modules, you can do the same thing.
Comments
Release on d.o?
e2thex: Do you have plans to release this on d.o? Is there anything holding you back that we can help you with -- the CVS learning curve, packaging a module for public release, etc.?
Todd Ross Nienkerk
Co-founder, Four Kitchens
Todd Ross Nienkerk
Digital Strategist and Partner
Four Kitchens: Big ideas for the web
IRC: toddross
Yeah I will need some help
Yeah I will need some help packaging for public release but it would also be good to have some other eyes on the code before it goes up there. Or is that what why we have dev release?
Dev versions
e2thex: Generally speaking, a module should be hammered at for awhile before it receives a 1.0 release. There are many conventions for signaling a "beta" or use-at-your-own-risk version: 0.x releases, 1.0-beta, 1.0-rc1 (as in "release candidate #1"), and so on. You can also set up your module page to display a nightly development snapshot, which isn't really a true release at all; rather, it's a packaged version of the latest commits to CVS that have not been tagged anything at all. (These take names like "6.x-1.0-dev.")
There are some basic things you should do before committing a new module -- namely, making sure your .info file is complete and properly formatted. Apart from that -- and the steep CVS learning curve that we're all frustrated with -- there's no reason to be shy about committing your work! :)
Todd Ross Nienkerk
Co-founder, Four Kitchens
Todd Ross Nienkerk
Digital Strategist and Partner
Four Kitchens: Big ideas for the web
IRC: toddross
After Reading up on CVS contributing
After reviewing http://drupal.org/cvs-application/requirements. I am going to review the code before I put it up, but I am still hoping to do this by the end of the week. Also as most of this work was done while working for the Case Foundation, my old boss is going to be the one that post it. I will let you all know when I get it up there.
Code is now on drupal.org
Full Node Version is now a Drupal.org project. Yay! With code, issue queue, etc --
http://drupal.org/project/full_node_version