2010/10/21 Karsten Wade <[email protected]> > > > > The first question that will come up is when we expect to do the next rev > of > > the textbook. Thoughts? I can imagine another sprint would be most useful > to > > make this happen. > > How about the week after GOSCON? :) > > That would give us some time to line up content sources for remixing, > and get writers, editors, and reviewers prepared. >
While that sounds technically feasible, that's about a week and a half from today. I think we'd need more time to get new volunteers up to speed. > > I've had my head in various places so haven't been driving this hard, > it's all a bit behind where I'd hope it would be by now, but I think I > can clear the way to give a good chunk of time to this project > until the next rev. For example, getting the foundation built up a > bit more so a writing sprint is more successful. > > Next question -- is the release feature-based or time-based? > > Due to feature requests being the major work right now (new content > chapters), I'm tempted to break the mold and do feature-based. But I > can also see a value in releasing the next rev sooner even if all our > content hopes aren't fulfilled. We have a lot of momentum brewing in > some focused locations, and I'm sure we'd all like to see the work > published and in use ASAP. Thus, why some of us prefer time-based > releases when it comes to keeping the community rhythm dancing ... > > I'm all for feature based releases. -- Leslie Hawthorn Open Source Outreach Manager Oregon State University Open Source Lab http://identi.ca/lh http://twitter.com/lhawthorn
_______________________________________________ tos mailing list [email protected] http://teachingopensource.org/mailman/listinfo/tos
