Comparing versions
Version 7Current version

This is a page for Bitweaver Roadmap planning

Please add to, and comment on this page.

Proposed Features

Native Forums

testing aaa

Improved Comment Retrieval Performance

The current storage method for comments does not allow easy retrieval of a range of comments if a tree structure (i.e. replies to indiv comments) has been used.
Drupal has a scheme for creating comment keys such that comments can be tree structured, but easily retrieved in chunks with a single query.
Not difficult to implement, but requires a schema change.

Gateway between email and Content creation, Forums, comments, etc.

Universal Discussion

We have many possible ways for discussions:
  • mailing lists
  • forums
  • blogs
  • wiki-pages
  • IRC

Seems like it should be possible with central content management to make a discussion appear in all of these formats simultaneously. Each just being a different way of viewing the same information. email gateways to blogs and forums are pretty common, Zwiki has email to wiki, Drupal has email to content functions, comments are pretty much equivalent to to forums replies in concept.
IRC is a little harder, but while content -> IRC might not be practical except as summary, IRC -> content shouldn't be too hard.

Interfacing content with forums would probably be more practical with some kind of native forum implementation.

Edit Sections of Pages

The ability to edit sections of pages rather than always having to edit the entire page. Mediawiki supports this feature.


Allows reuse of content without making mulitple copies. See:

This page is for developers. Please add to, and comment on this page if you would like to help develop the core of bitweaver. If you are NOT a developer, please do not edit this page. You may leave suggestions in the comments.

In Development

Centralize Network Communication Handling

SwitchboardPackage is being completed to deal with the various complexities of network communications.

project owner: wjames5
contact: wjames5 on IRC freenode #bitweaver
development code: cvs co -r tekimaki _bit_switchboard
sponsor: tekimaki

Goal: develop Switchboard to be universal transport gateway for all messaging, such as email, sms, aim. Any kind of transaction can be facilitated through switchboard. Such as enabling two way email interaction with BoardsPackage posts (e.g. sending and receiving posts like a mail list), to posting photos, videos, audio files etc, to TreasuryPackage from a phone. Also see Drupal Mailhandler and

State: Switchboard is now distributed with Bitweaver and LibertyCommments makes use of it for notification events.

Todo: Migrate more core communication components onto Switchboard.

Ideas for Release 3 of bitweaver

Remove distinctions between modules and "central" modules so any module can be located in any area.

Register module profiles during layout editing so we can know details, such as optional parameters the module takes.

Continue cleanup of BoardsPackage to bring it to level of phpbb

We should build out a list of specific todos - perhaps on the Boards package page. and we can point there for what needs doing.

Key missing features:
  • Nested boards - the schema exists, logic and template support is needed.
  • Nice pagination
  • Ability to add lots and lots of custom smilies. forum people are smiley insane (smileys package, quicktags?)
  • Signatures (easy, there's already an unused on partially coded, should be part of users package though)
  • Integration with MessagesPackage (go through switchboard) (WHY? messages is already there integrated into bw, a module can show numbers of read/unread msgs, AND that can already be done with a customized template in the header/topbar)
  • Configurable cute little user level based on number of posts, eg "Noob" 0 < 10 posts, "Getting Aquantned" 10->100, "I'm a Regular", 100 -> 1000 "Old timer" > 1000 posts

Port Drupal Project Module to Manage Package Pages

We should endeavor to make package release easier and friendlier. Look at which I believe drives the project pages on

Add History to Translations

this would allow sites to open translating to far more people. Each string would have a history.

Edit Sections of Pages

The ability to edit sections of pages rather than always having to edit the entire page. Mediawiki supports this feature.


Allows reuse of content without making mulitple copies. See:


  • Remote API (Atom, RSS2, etc) to interact with other sites or desktop apps /spider
Page History
26 Apr 2010 (11:51 UTC)
vandalized the page
Benjamin Couhe86.20.144.4621
Current • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
James Thompson64.65.89.2277
View • Compare • Difference • Source
James Thompson64.65.89.2276
View • Compare • Difference • Source
James Thompson64.65.89.2275
View • Compare • Difference • Source
James Thompson64.65.89.2274
View • Compare • Difference • Source
James Thompson64.65.89.2273
View • Compare • Difference • Source
James Thompson64.65.89.2272
View • Compare • Difference • Source
James Thompson64.65.89.2271
View • Compare • Difference • Source