I see it laid out as such:
iRex will provide source code releases for internal software when/where they see fit. That code will be organized by software release version.
From there, we can add new application sources and releases (community ipdf, fbreader, dillo, etc). This way the modified sources are available to all. New trunks can be created with modifications and enhancements.
It will all make sense when we get the ball rolling on this.
|