My name is Mike Culbertson, I have been a sysadmin for about 10 years, and I've been coding for about 12. I currently work for a software company in New York City.

My interest in bitweaver derives from my desire to implement improvements to ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and ((bitweaver and bitweaver and TikiWiki so as to make it a truly viable replacement for other CMSs that I see in use commercially.

I am currently working on:


In order for Tiki to compete with the likes of Plone, a robust, fully featured DMS must be implemented. Companies seeking out a new CMS will almost certainly need to migrate large amounts of data, in a variety of formats. Providing a means with which to seamlessly integrate this existing data into Tiki will be a very attractive feature.


I am a strong believer in standardizing the presentation format of data from any type of application. Moving to modern, standardized XHTML compliant output using CSS for formatting will make strides to "evening out" the user interface.


Some of the methods Tiki uses to manage, write and access files and data are IMHO, quite insecure and arguably dangerous. In conjunction with creating a debian package,I am compiling a list of proposed changes to inprove the overall security of the application. Luckily most of these require little code change. I'll add a link to the list when I post it.


A .deb is underway. I'd love to see 1.8 in unstable :)