| !How did bitweaver come about?
|
|
|
| -In the beginning, back in late 2003, [/spider|spider] created a branch of TikiWiki that mose (TikiWiki lead developer dubbed "spidercore". In the spidercore experiment, spiderr got phpBB to embed naturally inside of TikiWiki 1.8.
|
| +In the beginning, back in late 2003, [/spider|spider] created a branch of TikiWiki that mose (TikiWiki lead developer) dubbed "spidercore". In the spidercore experiment, spiderr got phpBB to embed naturally inside of TikiWiki 1.8. The entire structure of bitweaver has been changed and all of the original TikiWiki libraries have been broken up. This means that bitweaver is leaner, faster, and makes far fewer database calls than ever. |
|
|
| !bitweaver Construction
|
| Projects that are underway with bitweaver. If you are interested in contributing to any of these project please contact the person listed, or drop by IRC.
|
|
|
| -||-=What=-|-=Who=-|-=Last Updated=-|-=Status=-|-=Description=-
|
| -bitcommercePackage | spiderr | 26-JUL-2005 | ~~#090:Development Started~~ | full-featured, tightly integrated eCommerce system for bitweaver
|
| -LibertyXMLRPC | bigwasp, wolffy | 25-JUL-2005 | Planning | thinking about the spec for xml-rpc
|
| +||__::What::__|__::Who::__|__::Last Updated::__|__::Status::__|__::Description::__ |
| +YellowpagesPackage | wjames5, lugie | 22-FEB-2007 | ~~#090:In Development~~ | A rich listings and web directory package. |
| +GmapPackage | wjames5 | 09-DEC-2005 | ~~#090:In Development~~ | Google maps for bitweaver. Almost usable but some schema changes still happening. |
| +bitcommercePackage | [/spider] | 28-FEB-2007 | ~~#090:Beta~~ | full-featured, tightly integrated eCommerce system for bitweaver |
| +TreasuryPackage | [/xing] | 01-MAR-2007 | ~~#090:Beta~~ | flexible and pluggable file gallery. |
| +LibertyForms - SDLC | lsces, wolffy, jht, xing | 16-JUL-2005 | Planning | A developers tool for Rapid Application Development of forms based packages |
| ||
|
| + |
| +You can download one of our latest weekly builds from [/builds/|weekly build] or the release version from [http://sourceforge.net/project/showfiles.php?group_id=141358|SourceForge]. |
| + |
|
|
| !So where is bitweaver going and how are we going to get there?
|
|
|
| These are the current major release plans. They are not set is stone and we welcome your comments, ideas, or requests. We are very open to new feaures here at bitweaver.
|
| See ((ReleaseProcess)) for how releases are handled and which branch is currently in which state.
|
|
|
| -__{img src=http://skins.hotbar.com/skins/mailskins/em/042502/042502_2178_1220_prv.gif}ReleaseAl: Code name "((ReleaseAl|Al))"__
|
| -~~#090:Released April 2, 2004~~
|
| -The "AL" release, named after Al Capone, was the first release of bitweaver. In many ways, Al Capone was released as a Proof Of Concept release. It allowed us to show that the ideas behind bitweaver were worthwhile and worth doing. The real Al Capone was always in a hurry - and this release was accomplished in a hurry. The only major advance made in Al Capone was ((DatabasePrefixing|database prefixing)). This feature, which happens during installation, allows a site to host multiple bitweaver sites in a single database. This brief release was only used for the bitweaver.org website and not much else.
|
| +!!((bitweaverThree)): Code name "Earp" |
| +Planning stages. |
| + |
| +!!((bitweaverTwo)): Code name "Dillinger" ''~~#039:Active Version~~'' |
| +~~#090:Released May 3, 2008~~ |
| +A huge step forward, the entire database and CSS schemas were cleansed and made consistent withing packages and across packages. ((LibertyServices)) were added to greatly enhance the power of packages to interact with each other. See also ((New for R2)) |
|
|
| -__{img src=http://skins.hotbar.com/skins/mailskins/em/042502/042502_2178_1220_prv.gif}ReleaseZero: Code name "((ReleaseZero|Bonnie))"__
|
| +!!((bitweaverOne)): Code name "Clyde" |
| +~~#090:Released July 6, 2005~~ |
| +At this point the modular structure of bitweaver has been established an we are focused on even more speed and performance. The database schema has significantly diverged from Tiki 1.8 with two important criteria - immutable foreign keys ( `user` column -> `user_id` ). Also interfaces to the bitweaver core are in inplace, and we greatly encourage the development of drop in bitweaverPackages. We also worked on gutting the html templates to make the XHTML 1.0 strict. |
| + |
| +!!((bitweaverZero)): Code name "Bonnie" |
| ~~#090:Released July 19, 2004~~
|
| Bonnie Parker may have been deadly but she could also be a sweetheart. In a few months, came along the "BONNIE" release in May of 2004. We put a lot of effort into Bonnie and she was sweet. The key architectural changes were to simply move the tikiwiki code from its single-directory organization (300+ files in the root) to a more natural grouping of files by their feature type.The code will be adapted to support a more modular architecture. This will be based on the spidercore developed by spiderr.
|
|
|
| The combination of modularity and accessibility will be the major features for the second release.
|
|
|
| -__{img src=http://skins.hotbar.com/skins/mailskins/em/042502/042502_2178_1220_prv.gif}ReleaseOne: Code name "((ReleaseOne|Clyde))"__
|
| -~~#090:Released July 6, 2005~~
|
| -At this point the modular structure of bitweaver has been established an we are focused on even more speed and performance. The database schema has significantly divergee from Tiki 1.8 with two important criteria - immutable foreign keys ( `user` column -> `user_id` ). Also interfaces to the bitweaver core are in inplace, and we greatly encourage the development of drop in bitweaverPackages. We also worked on gutting the html templates to make the XHTML 1.0 strict.
|
| -
|
| -The entire structure of bitweaver has been changed and all of the original TikiWiki libraries have been broken up. This means that bitweaver is leaner, faster, and makes far fewer database calls than ever.
|
| -
|
| -You can download one of our latest weekly builds from [/builds/|weekly build] or the release version from [http://sourceforge.net/project/showfiles.php?group_id=141358|SourceForge].
|
| -
|
| -__ReleaseTwo: Code name "Dillinger"__
|
| -To be decided....
|
| -
|
| -__ReleaseThree: Code name "Earp"__
|
| -To be decided....
|
| -
|
| -__ReleaseFour: Code name "Floyd"__
|
| -To be decided....
|
| -
|
| -__ReleaseFive: Code name "Gambino"__
|
| -To be decided....
|
| -
|
| -__ReleaseSix: Code name "Henry"__
|
| -To be decided....
|
| -
|
| -__ReleaseSeven: Code name "Ice-T"__
|
| -To be decided....
|
| -
|
| -__ReleaseEight: Code name "Jesse"__
|
| -To be decided....
|
| -
|
| -__ReleaseNight: Code name "Kelly"__
|
| -To be decided....
|
| -
|
| +!!bitweaverNull: Code name "((ReleaseAl|Al))"__ |
| +~~#090:Released April 2, 2004~~ |
| +The "AL" release, named after Al Capone, was the first release of bitweaver. In many ways, Al Capone was released as a Proof Of Concept release. It allowed us to show that the ideas behind bitweaver were worthwhile and worth doing. The real Al Capone was always in a hurry - and this release was accomplished in a hurry. The only major advance made in Al Capone was ((DatabasePrefixing|database prefixing)). This feature, which happens during installation, allows a site to host multiple bitweaver sites in a single database. This brief release was only used for the bitweaver.org website and not much else. |
|
|
| -(Obviously our code naming convention follows [http://www.crimelibrary.com/gangsters_outlaws/|famous outlaws and criminals]) |
| +Obviously our code naming convention follows [http://www.crimelibrary.com/gangsters_outlaws/|famous outlaws and criminals]: |
| +*ReleaseFour: Code name "Floyd" |
| +*ReleaseFive: Code name "Gambino" |
| +*ReleaseSix: Code name "Henry" |
| +*ReleaseSeven: Code name "Ice-T" |
| +*ReleaseEight: Code name "Jesse" |
| +*ReleaseNight: Code name "Kelly" |