Free workgroups software for linux

DokuWiki is a simple, clean and easy to use wiki system that allows collaborative editing of a web site. Its focused on creating documentation for developer teams, workgroups and small companies. DokuWiki Wiki JumpBox bundles DokuWiki version 2007.05.24

WHY USE A JUMPBOX

Its Simple

Open Source applications are great. The applications are powerful, inexpensive and get the job done. But installing and configuring those applications can be a pain. A JumpBox delivers Open Source applications in a way that makes them simple to try, run and operate.

Its Quick

Actually downloading a JumpBox will take the most time. Once thats done, youre just a few minutes from having a working application that can serve multiple users.

Its Portable

A JumpBox collects the application, application dependancies and all application data into a single bundle that can easily be moved from one computer to another. This allows you to start running the application on your desktop and then as usage grows move it to a server without needing to reinstall or reconfigure. Plus with support for Mac OS X, Windows and Linux you can even move the application between platforms with little effort.

Its Safe

Manually installing Open Source applications not only takes a lot of time and effort, but when youre done its still left to you to figure out how to protect the data the application manages. With a JumpBox its easy to add automatic backups of the entire state of the application.

Its Virtual

A JumpBox application is a virtual appliance that bundles the open source application and all its runtime dependancies into a single package that runs on top of virtualization software from VMWare, Parallels or Xen. This means all JumpBox applications automatically gain the benefits of traditional server virtualization and can be dropped into existing virtualization infrastructure when available.

Its Comfortable

JumpBox provides a consistent runtime environment for all applications that we bundle. The applications may differ considerably, but their installation and operation will be familiar no matter which JumpBox you choose.

ELOG is part of a family of applications known as weblogs. ELOG Electronic Web Logbook general purpose is :
1. to make it easy for people to put information online in a chronological fashion, in the form of short, time-stamped text messages ("entries") with optional HTML markup for presentation, and optional file attachments (images, archives, etc.)
2. to make it easy for other people to access this information through a Web interface, browse entries, search, download files, and optionally add, update, delete or comment on entries.
ELOG is a remarkable implementation of a weblog in at least two respects :
- its simplicity of use : you dont need to be a seasoned server operator and/or an experimented database administrator to run ELOG ; one executable file (under Unix or Windows), a simple configuration text file, and it works. No Web server or relational database required. It is also easy to translate the interface to the appropriate language for your users.
- its versatility : through its single configuration file, ELOG can be made to display an infinity of variants of the weblog concept. There are options for what to display, how to display it, what commands are available and to whom, access control, etc. Moreover, a single server can host several weblogs, and each weblog can be totally different from the rest.
Several logbooks can be served though a single ELOG server. Each logbook can use different attributes for its entries. The logbook can then be searched using these attributes. The right pane on the left image shows a search for all entries with attribute "Type" equal to "Configuration ", and the lower pane shows the search result. It is also possible to use full-text search in attributes and the entry body.
While logbook entries are usually displayed one entry per page, they can also be listed consecutively which makes it easy to produce a paper printout of a logbook.
Logbook pages can be edited or deleted. This feature can be turned off in the configuration file so that a logbook entries cannot be changed after being submitted.
An additional feature is the automatic generation of a notification email messages based on a certain type or category of a logbook entry.
Main features:
- Personal Logbooks. Personal notes can be written into ELOG and can then be retrieved from anywhere with a Web browser. This makes it handy for PC supporters who have to go around in companies or laboratories and dont want to carry their paper logbook with them. The same holds true for people traveling around a lot. The logbook database consists of plain ASCII files which can copied easily between different computers to have local access, for example on a notebook with no network connection.
- Shared Logbooks. Logbooks can be shared by several people, for reading and optionally for writing. This way workgroups can share and exchange information like in a (simplified) news group. This is supported by the Reply command in ELOG which creates "threads" of entries. Users can be notified by email when new entries are added to the logbook. Compared to that of a news server, the installation of ELOG is much simpler.
- Small Databases. Since arbitrary attributes can be defined for a logbook, it can be used as a small database with search facilities.
- Problem collections. A system can consist of two logbooks, in one of which users enter bugs or problems. If someone adds a problem, an email is automatically sent to the administrator, who can then copy the entry to the second logbook and add the solution to the problem. Users can then look up all fixed problems.
- Shift Logbooks. If the Allow delete and Allow edit flags are off, an entry cannot be modified once its been entered. This can be useful for shift logbooks for example in accelerator control rooms where each entry becomes a "document" with a time and author stamp. ELOG was originally developed as a shift logbook for the PiBeta and Muegamma particle experiments at PSI.
- File collections. Since files can be attached to ELOG entries, the system can be used to store and retrieve files. This can be used to store configuration files, which need to be accessible by several people over the web, or to store images. Since ELOG features an elaborate query facility, entries can be searched for by specifying several categories.
Enhancements:
- ELCode tags were improved with keyboard shortcuts, tables, and a date/time tag.
- Several small bugs were fixed.

BuddySpace is an instant messenger with four novel twists: (1) it allows optional maps for geographical & office-plan visualizations in addition to standard buddy lists; (2) it is built on open source Jabber, which makes it interoperable with ICQ, MSN, Yahoo and others; (3) it is implemented in Java, so it is cross-platform; (4) it is built by a UK research lab, so it is 100% free with full sources readiily available. But BuddySpace is about more than just messaging, as we explain below.

One of the key factors that led to the widespread popularity of Instant Messaging applications from 1997 onwards (including ICQ, AOL, Yahoo!, MSN, Odigo, and Jabber messengers) was the concept of pushed presence: the automatic notification of the appearance of friends and colleagues online.

However, Instant Messaging (IM) is just one of many possible presence-related and presence-dependent applications. For example, presence-enabled applications can facilitate safety-tracking of children by mobile phone, support for emergency services, blind-date radar, group teleconference management, multiplayer games, and anything involving the collaboration of individuals separated in space and time.

Why phone a contact only to receive an engaged tone or pre-recorded message, when the telephone network already knows what state your contact is in, and could indicate this directly on your contact list? All of these concepts embody varying degrees of what we refer to as enhanced presence management.

The concept of presence has matured in recent years to move away from the simple notion of online/offline/away, towards a rich blend of attributes that can be used to characterise an individuals physical and/or spatial location, work trajectory, time frame of reference, mental mood, goals, and even intentions! Our challenge is how best to characterise presence, how to make it easy to manage and easy to visualise, and how to remain consistent with the users own expectations, work habits, and existing patterns of Instant Messaging and other communication tool usage.

BuddySpace generalizes the concept of Buddy List (popularised by Instant Messaging tools such as AOL Instant Messenger, ICQ, MSN Messenger, and Yahoo Messenger) to provide multiple views of collaborative workgroups according to users needs and tastes. Our aim has been to provide a personal dashboard or radar screen so that one can observe the availability and interaction state of colleagues worldwide in a manner that exhibits the following desirable properties:

* immediate: real-time updates need to be pushed instantly to users rather than pulled in by request -- the push approach helps keep updates more palpable and informative
* peripheral and therefore non-intrusive: users lead busy lives, and dislike being bombarded with yet more information, so we aim to keep awareness of colleagues available in a compact manner that can be noticed peripherally
* customisable: some people prefer simple or hierarchical lists, some prefer visual maps, some prefer status lights, and so on; some prefer a Windows look-and-feel, some a Mac-- we need to cater for diverse user preferences and capabilities
* scaleable: we have to provide ways to indicate the presence of potentially enormous numbers of people, even given that these numbers will be filtered down for personal use -- researchers inhabit workspaces with many hundreds of colleagues around the globe; the Open University has well over 150,000 students online; large peer-spaces like music swapping communities have many millions of users connected simultaneously
* interoperable: with several hundred million users of the Big Four (AIM/ICQ/MSN/Yahoo!), it is crucial that any approach allow interopebility with systems to which our users already subscribe; this is one of the many reasons we built BuddySpace entirely on top of Jabber (www.jabber.org), which provides gateways to the Big Four products.
* cross-platform: we need to service a community not only on Windows, Unix/Linux, and Mac desktop and notebook configurations, but also on PDAs and mobile phones -- we therefore develop entirely in Java
* XML-literate: for future intelligent applications, communication transport needs to be about more than just string-transmission; another we adopted Jabber is that it is based entirely on a generic XML transport architecture, ideally suited for this purpose.
* open source: for the research community to join us and to gain leverage via our research output, we have ensured that BuddySpace is open source, available on SourceForge.
* clean: BuddySpace adheres rigorously to the Jabber specification, which means that it interoperates with other Jabber clients and servers without danger of the rogue behaviour that non-standard implementations inadvertently allow (e.g. the semantics of users inhabiting multiple groups is undefined in some clients, and can cause crashes).
* extendable: BuddySpace deploys a plug-in architecture which means that additions, such as new visualizations, and new concepts such as gaming interfaces, are readily achievable

BuddySpace fulfills all the above criteria, and provides a compelling user interface that can be highly compact, yet provide users with an important feel-good factor, akin to seeing nearby office lights turned on when entering ones office building at night. By studying the semantics of presence, we can also augment the existing impoverished presence states in a principles manner, providing capabilities that are more representative of the way real users work. Forthcoming capabilities will include automatic location updates via mobile devices, and the use of semantic matchmaking via intelligent profile handling, in order to help users quickly find and filter colleagues of particular interest.

Smb4K is a SMB and CIFS (Windows) share browser for KDE.
Smb4k uses the Samba software suite to access the SMB and CIFS shares of the local network neighborhood.
Its purpose is to provide a program thats easy to use and has as many features as possible.
Main features:
- Scanning for (active) workgroups, hosts, and shares
- Mounting and unmounting of SMB and CIFS shares, including unmounting all shares at once
- Access to the files of a mounted SMB or CIFS share using Konqueror
- Auto-detection of external mounts/unmounts
- Remounting of recently used shares on program start
- Miscellaneous infos about the mounted SMB and CIFS shares
- Network search
- WINS server support
- Preview of shares
- Selectable look-up and search methods
- Default login
- Ability to execute mount and umount SUID root (using super or sudo)
- Special handling of homes shares
- Ability to bookmark favorite shares
- System tray icon
- Support of advanced Samba options
- Support of printer shares
Enhancements:
- Reintroduced Polish translation provided by Jerzy Trzeciak.
- Updated Turkish translation and improved smb4k_add.desktop file.
- Fixed missing functionality of the --ignore-existing argument of rsync.
- Fixed net rap server domain command that is incompatible with Samba 3.0.25 (and later?).
- Fixed Smb4KPasswordHandler::readAuth() that returned a pointer that was freed when the function exited.
- Fixed broken Smb4KPrint::print() function.
- Fixed a bug in the preview dialog.
- Fixed DCOP-related hanging of Smb4K during KDE start-up.
- Fixed a potential memory leak in the bookmark editor.

filofant project is a mail archiving and document indexing software intended for using in companies or workgroups which wants to share the knowledge embedded in their documents and emails.
Installation:
Currently there is no installscript, so you have to do all at your own...
1) Binaries
configure && make & make install
in the src directory.
It is recommended to provide an prefix for the installation like --prefix=/opt/filofant
2) CGIs
The CGIs will be installed in $PREFIX/bin/cgi-bin. If this is not the cgi-directory of your webserver, you should move them there.
3) Environment
filofant needs the variable FILOFANT_HOME to declared, to find its config and binary files. It this variable is not defined, the base config has to be stored at /etc/filofant.rc
This variable has to be set for the CGI also, eg in Apache you could set it with the SetEnv directive.
4) System
Create a systemuser for the filofant (eg. filofant). The user has to be access to the base directory ($FILOFANT_HOME) of the installation.
5) Database
PostgreSQL: Create a database with the createdb command, create an user of the same name as the system user with the createuser command (This user has to be database administrator).
su to the filofant user. Insert database schema from the file filofant.sql (in directory sql) If you have nonstandard system user for the webserver or the filofant, please correct the grants in the sql file before inserting it.
6) Base configuration
The file filofant.rc has to be located in the directory $FILOFANT_HOME/etc. Edit (or create) this file and enter the following lines:
BaseDir=/opt/filofant
User=filofant
DBUser=filofant
DBName=filofant
Fill in the appropriate data. I you have password protection at the database or the database is not at the same machine, add the following lines:
DBPwd=
DBPort=
DBHost=
Enhancements:
- A new binary for resolving system variables without password query changes access to system settings in scripts for cronjobs.
- This allows a tighter security setting for the database.
- Internal references in HTML previews will now be translated correctly to the filofant preview page.
- A bug regarding the embedding of images in HTML previews has been fixed.
- When using the fulltext search engine with more than one stopword, only the first was detected.
- This has been fixed.