Projects

DiMo

Directory Monitor Application by WEBNETSOFT http://www.webnetsoft.gr

ChronicleDroid

ChronicleDroid assist in creating ETL mappings for tracicking changes on a existing OLTP Schema. ChronicleDroid implements The Data Vault architecture. Currently in early development stage

Sqitch

Sane database change management

SysFink

The unix based guard for checking consistency of system files. Sysfink server periodically scan basic information in the client's file systems and reports changes to administrator.

paradoxsmod

A mod developed by paradox for the game tremulous (http://tremulous.net). It features many simple client side changes that will make the game look even better (hopefully)

vcchanges

Right now, LinuxLive just mounts x.file or x/ to /, and it's a simple implementation, but it's not the best. My idea is for LinuxLive to only record certain directories based on a text file (say in slax/changes.conf), but that's still not perfect, if line a in /root/Desktop/file.sh is ... [More] removed and /root/Desktop/file.sh is stored in a module, the whole file gets copied, so what if git is used? Have LinuxLive store all changes in ram, but mark all of the folders provided in changes.conf as git repos, then autodetect new files/folders and mark them as version controlled, periodically git diff the all of the repos, and store them in matching directories, when it happens again, the previous one is overwritten till the day ends, then that is committed so the previous day's diffs aren't duplicated. So if I have /root marked, and slax/changes is the changes dir, then /root will be turned into a git repository before modules are inserted, then after the modules are inserted, ll of my previous changes are applied and after five minutes slax git diffs them into slax/changes/root/diff-date.slaxdiff, overwriting the previous diff, then once the day changes, it git commits, so every day is stored, and minimal junk stays. And it doesn't have to be git, it only that cvs is waaaaaaaaaaaaaaay outdated, and it stores its info in nonhidden folders, bzr's main advantage is merging and branching, but it is slow, svn, I think git supersedes it. This will only apply to text files, for binaries, they will be copied over, mainly for 2 reasons: Most binaries aren't touched, they are left alone Deltaing/Diffing them won't be very efficient [Less]

wikkawiki-plugin-actions

While working with WikkaWiki, we have developed several add-on actions or have added various functionality. Whether or not any of these additions are appropriate for inclusion in the release code is yet to be seen. Either way, they have been documented on the WikkaWiki site and shared here for ... [More] anyone who may consider them a worthy addition to their WikkaWiki installation. Instructions for installation are included in each tarball or in the online documentation as linked in their corresponding wiki page. [Less]

websitechangeuploader

Certain website creation tools, such as iWeb in local mode, publish a completely new version of your site rather than just the changes. For large sites, this is an unreasonable maintenance burden. This tool will keep hash information from previous uploads to be able to identify and upload only those files which have changed.

WebTrack

WebTrack is a set of tools used to track changes in Web Pages and to inform the user if anything relevant has changed. The main purpose is to check a lecture pages at ETH Zurich and inform students about changes.

NeoKiller

NeoKiller is a project that aims to duplicate the .NET framework Huggle program in C++ to provide extensive cross-operating-system compatibility. See our wiki at http://neokiller.sf.net/