We updated the book site today with versions of all of the cheatsheets to bring them in line with Ruport 1.2. All of the existing content has been revised as necessary to make sure that it's current.
In addition, the new features introduced in Ruport 1.2 have been added to the relevant cheatsheets. In some cases there were placeholders for them in the previous versions, and these have all been replaced with the real content.
This brings us fully up to date with the current version of the progress matrix. We'll be working on the main section shortly.
Friday, September 7, 2007
Tuesday, September 4, 2007
Book Coverage Matrix Now Available
Mike and I have talked for a while about putting together a matrix which lets people see at a glance what features we plan to cover in the Ruport book, along with their current status. Tonight, we've finally gotten around to putting one together.
This coverage matrix will serve as an important part of the project, because it lets users know what we're trying to accomplish with the Ruport Book and gives them a chance to challenge our sense of 'finished' when it comes to covering various features.
We invite folks to keep an eye on this matrix, make suggestions for new features to be covered, complain when you think we're covering something that's not important, complain when the documentation is marked complete when it's not, give us the heads up when things are out of date, etc...
Basically, when all the rows in all the tables are green, the book will be ready to enter the typesetting / general editing phase and be complete content wise. So in addition to using this as a road map, you can look at it as a progress bar, and harangue us when things seem to be moving too slowly :)
In other news, we also got all of the cheatsheets up to date with Ruport 1.2 tonight, we'll have them up on the web within a couple days.
This coverage matrix will serve as an important part of the project, because it lets users know what we're trying to accomplish with the Ruport Book and gives them a chance to challenge our sense of 'finished' when it comes to covering various features.
We invite folks to keep an eye on this matrix, make suggestions for new features to be covered, complain when you think we're covering something that's not important, complain when the documentation is marked complete when it's not, give us the heads up when things are out of date, etc...
Basically, when all the rows in all the tables are green, the book will be ready to enter the typesetting / general editing phase and be complete content wise. So in addition to using this as a road map, you can look at it as a progress bar, and harangue us when things seem to be moving too slowly :)
In other news, we also got all of the cheatsheets up to date with Ruport 1.2 tonight, we'll have them up on the web within a couple days.
Monday, September 3, 2007
PayR 0.0.1 released : Developer Preview
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.
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.
Subscribe to:
Posts (Atom)
