We've been talking about how the Ruport Book is going to be based on a real world application, but until today, that's largely been vaporware aside from a screenshot or two from me.
PayR 0.0.1 has been released, officially dispelling the myth that we're over here coding up Duke Nukem Forever. However, there is still a ton to be done. This initial snapshot, available on RubyForge, is really just to get the code out there and let interested developers and potential Ruport Book readers take a look at it.
The code is a straight yank from the application that's currently in a late prototype stage at my work, and will likely undergo major cleanup and changes within the next couple weeks. We also need to add a bunch of reports to it, some of which I've started but aren't included in the package.
I do have some tests, but since they're currently broken, I've not included them. My hope is that getting the code out into a public place will shame me into cleaning it up, and also let us drive the book forward and get back on track with producing new content. Keep in mind, we won't be doing weekly releases of the main discussion, but that you can always keep an eye on the book's subversion repository for our latest source documents.
We are currently about 3-4 weeks behind schedule, which means that we'll need to make up some time if we want to get the book in print before November. Mike and I have both freed up our schedules a little more, but we can use your help editing, reviewing, and testing the code examples, so if you're interested, be sure to let us know.
Back with more news soon, until then, enjoy the sneak peek at PayR, which will hopefully quickly get the polish it deserves.
Showing posts with label news. Show all posts
Showing posts with label news. Show all posts
Monday, September 3, 2007
Tuesday, August 28, 2007
Ruport 1.2 released, now to get things up to date
We've been working off of trunk as we write the Ruport book, so it means that some of the features from the new 1.2 release have already been covered.
However, there are at least a few places where things are out of date, and probably broken now. If you'd like to help out, have a look at the Ruport 1.2 release notes, download the gem, and start playing with the book content. When you run into problems, let us know.
We'll be working to get everything back up to speed in the next few days, but we appreciate any problem reports between now and then. For now, enjoy 1.2!
However, there are at least a few places where things are out of date, and probably broken now. If you'd like to help out, have a look at the Ruport 1.2 release notes, download the gem, and start playing with the book content. When you run into problems, let us know.
We'll be working to get everything back up to speed in the next few days, but we appreciate any problem reports between now and then. For now, enjoy 1.2!
Thursday, August 9, 2007
Come Get Up In Our Grill
Though we've been calling this effort "The Most Open Publishing Project Ever", we've clearly been missing a key part of that, a blog. Now we've decided to change that and join the mass of mixed signals and noise that is the blogosphere.
We'll be using this blog to announce new content whenever it is available, as well as give people progress reports on the administrative side of things, such as starting up the company that we'll be printing the book through Lulu with.
We hope this serves a few purposes, the first of which is of course giving the book more exposure and inviting our users to participate or at least stay in the loop. The other thing we hope to do, which is perhaps more generally useful, is document our experience of writing and producing a work basically on our own, without a publisher to handle all the details for us. With any luck, we'll be able to do this successfully and share our experiences for the benefit of other folks who want to write free documentation.
For now, here's an update on where we stand, on various fronts:
We'll be using this blog to announce new content whenever it is available, as well as give people progress reports on the administrative side of things, such as starting up the company that we'll be printing the book through Lulu with.
We hope this serves a few purposes, the first of which is of course giving the book more exposure and inviting our users to participate or at least stay in the loop. The other thing we hope to do, which is perhaps more generally useful, is document our experience of writing and producing a work basically on our own, without a publisher to handle all the details for us. With any luck, we'll be able to do this successfully and share our experiences for the benefit of other folks who want to write free documentation.
For now, here's an update on where we stand, on various fronts:
- We're in talks with BTree to get some initial funding to start up an LLC or other kind of company with. This company will likely consist of only two partners, Michael and myself, with a very reasonable profit sharing model worked out with BTree.
- We're looking for some incentives for folks to buy the printed book or typeset PDF when it becomes available. Because we intend to make the HTML version of the book available free of charge forever, we won't be using traditional product-centric profit models. Instead, we plan to donate a sizeable amount of our proceeds to charity. We have a couple of organizations in mind, and will announce our final selection and the amount of profits we plan to share with them soon.
- We are also considering doing pre-orders of the printed book at a much lower cost than the final retail price. Please let us know if you're interested in this, as a decent amount of interest will help make sure we do this. We'd likely begin taking pre-orders in mid-September for an early November release date.
- We are about two weeks *behind* on writing, but have worked enough wiggle room into the schedule where this should not effect our goal of having the book in print before RubyConf. We'll let you know if things change.
- An alpha release of PayR, the application which the Ruport Book will be based on will be out soon, within the next couple weeks.
- The editorial support, review commentary, and feedback for the book have been less than what we hoped for. We notice that our users are learning a lot from the materials based on the kinds of questions that are being asked on the mailing list, but we are really counting on honest opinions from our users on whether or not the work we've done so far is helpful to them. Feel free to chime in any time. :)
- What has been lacking in discussion has not been lacking in financial support. Donations have covered our hosting costs for 1 year for the various project resources. All further donations will be used to help offset business costs, allow us to borrow less money, and generally make things go more smoothly. To those who have contributed so far, thank you!
Subscribe to:
Posts (Atom)