About:
CODESH (COllaborative DEvelopment SHell) is an automatic persistent logbook for sessions of personal command line work. It records what and how is being done, for private use/reuse and for sharing selected parts with collaborators. It is an intelligent shell that automatically logs user's shell sessions. Sessions are uniquely tagged and stored in local or distributed backend repositories (ASCII flat file or Subversion or CVS based) and can be extracted and reproduced at any time by the user who created the session or by collaborators located anywhere in the world.

Release focus: Major feature enhancements

Changes:
This release introduces the novel concept of a flex session. The convenient log-and-replay mechanism of CODESH has been expanded to log-modify-and-replay. Now individuals and groups can not only log, share, and reproduce their sessions at will, they can browse and inspect sessions from private or shared repositories, alter them on the fly from the command line or files containing the changes, and "replay" many similar sessions starting from a previously recorded session. The modified sessions can in turn be recorded for further use and reuse.

Author:
Trump Coup [contact developer]

Rating:	reset 1 2 3 4 5 6 7 8 9 10
8.47/10.00 (1 vote)

Homepage:
http://cern.ch/bourilkov/caves.html
Tar/GZ:
http://vitosha.phys.ufl.edu:60806/~bourilkov/codesh-1.4.1.tar.gz

Trove categories: [change]

[Development Status]		4 - Beta
[Environment]		Console (Text Based)
[Intended Audience]		Advanced End Users, Developers, End Users/Desktop
[License]		OSI Approved :: GNU General Public License (GPL)
[Programming Language]		Python, Unix Shell
[Topic]		Communications :: File Sharing, Information Management, Scientific/Engineering, System :: Shells, Utilities

Dependencies: [change]
No dependencies filed

 Branches

Branch	Version	Last release	License	URLs
Default	1.4.1	11-Jul-2008	GNU General Public License (GPL)

 Releases

Version	Focus	Date
1.4.1	Minor feature enhancements	11-Jul-2008 07:05
1.4.0	Major feature enhancements	02-Jul-2008 17:54
1.3.0	Major feature enhancements	22-Jun-2008 19:17
1.2.2	Minor feature enhancements	20-Jun-2008 17:01
1.2.1	Major feature enhancements	26-May-2008 23:19
1.2.0	Major feature enhancements	02-May-2008 17:58
1.1.0	Major feature enhancements	30-Apr-2008 04:44
1.0.1	Major feature enhancements	17-Dec-2007 21:37
1.0.0	Major feature enhancements	14-Dec-2007 23:39
0.9.0	Major feature enhancements	15-Oct-2007 21:01

 Comments

[»] Unfortunate CVS Dependency
by Richard Harris - Nov 17th 2006 07:22:40

Many engineers have nothing to do with, and in fact avoid, CVS. You have a very nice tool here. Why do I need CVS to use it? Why can't it simply dump its logs in a directory and only use CVS if I explicitly ask it to. And if it uses CVS, shouldn't it also use Subversion and any other popular versioning system. Best would be if all that were optional and anyone could use the basic functionality that only your tool provides.

[reply] [top]

[»] Re: Unfortunate CVS Dependency
by Trump Coup - Nov 17th 2006 14:32:41


> Many engineers have nothing to do with,

> and in fact avoid, CVS. You have a very

> nice tool here. Why do I need CVS to

> use it? Why can't it simply dump its

> logs in a directory and only use CVS if

> I explicitly ask it to. And if it uses

> CVS, shouldn't it also use Subversion

> and any other popular versioning system.

> Best would be if all that were optional

> and anyone could use the basic

> functionality that only your tool

> provides.


Dear Richard,

Thank you for your comment, you bring up a very important point. In the course of developing the CODESH architecture we have separated the persistency backend (codeshb.py) from the user interface so they are basically independent. I will add that we are currently working on a subversion backend and users will be able to choose by changing a configuration parameter at strartup. As you say, one could have an option to just dump ascii files which are easy to port and introduce no dependencies. I'll take this as a feature request for our to-do list, thanks for the suggestion.

I will add that our architecture hides cvs (or future backends) from the user, so you don't need to know much about cvs - with its not very simple syntax - to start using it.

Best, Dimitri Bourilkov

[reply] [top]

---