|
|
|
|
The current contact for contributed-code questions is Gary Pavlis, pavlis@indiana.edu.
There is now web-based access to the CVS Repository. This allows users to browse examples of Antelope contributed source code and download just the pieces they want. You can access this by clicking here.
There is now a mirror, available for anonymous read-only access, of the Antelope contributed-code repository in the
Git Distributed Version Control System. This is the initial foray for the User-group
community into git-based collaborative development. The mirror is updated once per hour, and is available with the
following command:
% git clone git://antelopeusersgroup.org/contrib.git contrib
Binaries are currently compiled and available on the Antelope CD-ROM distributions from Boulder Real-Time Technologies, Inc. (BRTT)
Source code is currently available under the terms specified here.
To download source code from different releases or the latest and greatest version click here.
Contributions to the Antelope software base are currently through arrangement with Gary Pavlis. All contributed software is managed with the Concurrent Version System (CVS), housed at the University of Indiana. For more information on contributing software of general interest to be used with Antelope, contact pavlis@indiana.edu.
Recent discussions at the December, 2000 Antelope Users-group meetings have shown the desire for an Antelope Wish-list, i.e. a list a things the collective community would like to see included in the upcoming versions of Antelope. This list has been assembled not by BRTT but by the user community, thus it truly is a wish-list rather than an official reflection of the BRTT Development agenda (i.e. the author of the list is not in a position to make promises about what BRTT will produce next). Nevertheless, BRTT representatives have expressed a willingness to take into consideration what appears here. This list shows programs and capabilities that the community would like to see BRTT or some community member provide. Requests for additions or changes to this list should be directed to Kent Lindquist.
Recent discussions have revealed a number of software programs and packages that have been developed by individual institutions to meet particular needs. In some cases these utilities are of general interest. Often they have not been contributed either because they have been written in a manner that is somewhat parochial, and they need to be tweaked a bit to be of general utility; or they are useful at their host institution but not yet up to appropriate quality levels for the authors to be comfortable releasing them. In a few cases there are utilities that are probably ready for contribution but have not yet been contributed. This list attempts to sketch the known software utilities that have been written at individual networks but not contributed for one reason or another. Hopefully, feedback based on this list will inspire prioritized attempts by the authors to make these programs generally useful and to contribute them. For additions or corrections to this admittedly incomplete list, please contact Kent Lindquist.