Free change channel software for linux

Channel is a generic/simple facility with the purpose of making event dispatching and message passing as straightforward to use as data structures:
Channel is a template library, with its major components configurable as template parameters:
template
<
class Id_Type,
class Id_Trait = IdTrait ,
class SynchPolicy = ACE_MT_SYNCH,
class AllocPolicy,
class Router = MapRouter
>
class Channel
By replacing Id_Type, Id_Trait and Router with various concrete classes, Channel can support table/linear message routing, hierarchical routing and associative routing (Linda style) at the demand of user. The same way, we can use integer, string, POD structs or any class as message ids (provided that proper operations are defined with Id_Trait)
Channel provides complete publish/subscribe interface for channel members (peer threads in message passing and objects in event dispatching) to pub/sub message/event ids/types and send/receive messages/events
Channels are process local entities which can be "connected" to allow transparent distributed communication between members in different channels (Connectors based on tcp socket and unix domain socket are provided as samples)
Namespace control:
The ids published/subscribed by channel members constitute channels namespace.
Channel provides publish/subscribe scope control; When ids are published/subscribed, peers can specify desired scope (LOCAL, REMOTE, GLOBAL)
When 2 channels are connected, their namespaces are automatically "merged", which is transparent to both channel members and programmers. Members can communicate with members in remote channels the same way as with local members (by pub/sub ids).
Namespace merge/integration is controlled by:
Id scope specification
filters and translators defined at channel connections
Channel communication are peer-2-peer; there are no central daemons required for message passing.
Channel support both asynchronous message passing and synchronous event dispatching models.
Channel is built on top of
ACE (Adaptive Communication Environment) to gain platform independence.
Enhancements:
- The framework was ported to Windows XP with VC8.
- Dispatching policy was added as a Channel template parameter to support various dispatching algorithms.
- Broadcast and simple RoundRobin dispatching policies were implemented for testing.
- Callback was changed to functor style so that normal functions and functors can be directly used as callbacks.

Change Control Request Manager is an online system for managing change requests for businesses. Change Control Request Manager project can be customized to fit the needs of a particular business.
Main features:
- Abillity to customize data entry fields. Field type include test, dropdown list, boolean, date, and integer.
- Search for existing CCR records.
- Custom logo. You can place your companys logo at the top.
- Custom Disclaimer message.
- User administration.
- Install script.
Enhancements:
- A reporting system was added.
- Similar to the browse order screen, you can customize the report and display a date range to print.

DBD::ODBC::Changes is a Perl module with logs of significant changes to the DBD::ODBC.

Gnome Desktop Change is a daemon that changes randomly your GNOME desktop background.

Gnome Desktop Change is a daemon that changes randomly your GNOME desktop background. Its totally written in C++, it uses FAM (File Alteration Monitor) to detect changes into directory that contains picture files, and its multithread.

TopicEngine is an advanced topic management script for eggdrop bots. Its features are: fine-grained access permissions, multiple channels, shortcuts to commands, intelligent topic handling, learning, locking, and more.

Commands can be executed via public message (using !topic in a channel), query (/msg botnick topic #channel, or on the partyline (.topic #channel).

Wont change the topic if it would make it go over the maximum topic length for the network
Access can be limit by bot flags per channel or globally, and by IRC status (+o,+v). Users can be blocked if needed.

Supports prefixes and postfixes to ensure something is always at the start/end of the topic (e.g. channel homepage URL).

If a user changes the topic with /topic, will try to learn the new one so that future !topic commands work smoothly. If a topic is set without a pre- or postfix, the bot resets the topic with them.

Topic locking, so that it cannot be changed. If the topic is changed with /topic, the bot will change it back. TopicEngine uses the botnet to try to avoid a botfight with two locked topics.
he topic is reset after a netsplit to make sure all servers across the network have the topic.
Intelligent trimming of the topic to try to fit as much as possible into the available space.

Can learn a new topic if its set with /topic instead of through the bot. Automatically learns all the topics on active channels when joining them, and will update them to have pre- and postfixes if needed.

VCS::CMSynergy::Changes is a list of changes to VCS::CMSynergy.

This module is a Perl interface to CM Synergy (formerly known as Continuus CM), a change and configuration management system from Telelogic AB (http://www.telelogic.com). It is implemented on top of the CM Synergy CLI, hence you must have the command client ("ccm")
installed to use it.