Publication Plan, Dependency Questions, License Model

I spent some time back in late February / March working to revive the prototype code from 2004 (the last time I actually looked at the source code) but stopped short of a total bring-up thinking that the time would be better spent on refactoring routines that I now feel are poorly implemented (who wrote this crap?) and porting sections dependent on the Windows OS (see Welcome post).

The prototype codebase has the following dependencies currently:

Obviously quite a lot has changed since 2004. Notwithstanding, investment in STL and Boost in particular seem to have withstood the test of time.

As I’m super busy currently, getting the source code published is going to take some time because I do not want to release the currently busted and out-of-date source as a baseline. It will simply be too confusing and chaotic. What’s likely is that as I tackle the various subsystems of the platform (there are ~six major subsystems) that I’ll package them as libraries and release them one at a time. The first will likely be the base parsers that read and deserialize the XML-encoded data flow graphs upon which the entire platform is based.

Source code will eventually appear on GitHub where I’ve a created the Encapsule-Project organization (no repositories currently so don’t even bother looking).

License model: I intend to publish under the Boost Software License because it is simple, permissive, and non-controversial. I could say more but the explanation would then exceed the number of words in the actual license text.

I would appreciate hearing from anyone willing to offer suggestions about the list items above marked ‘under investigation’ and more broadly from people who have practical ideas for applying this work to the problems they’re facing. Or, if you think the whole effort is a total waste of time I would like to hear that too :)

Thanks, Chris

  1. No comments yet.

  1. No trackbacks yet.

You must be logged in to post a comment.