On Monday 30 July 2007 17:59, Mark Pictor wrote: > For the record, Paul was given the opportunity to get access to the > new repository -- the same way anyone else gets access.
No Mark - You miss the point entirely. The move was made without consultation or due process. As a result, the project admins no longer have any control. In addition, the repository is on an untrusted server reliant on a single person maintaining the hardware and system security. As I predicted when this move was foisted on us, RCSlib development has reverted to an in house project by NIST - Valuable contributions in both directions have been lost. Elsewhere, others have been making noises about an emc3 fork.. Sourceforge provide a web interface to manage my own ssh keys along with a number of other services should I wish to use them. So why the hell should I submit keys to an untrusted third party when I can use the SF web interface. Bottom line - I do NOT trust the system that currently hosts the repository. --- Paul. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
