G
To whom does one apply for a cvs login? Alternatively, to whom might one submit contributed code? I've written a loadable Tcl extension for interacting with the LPLC, along with a couple of scripts (including a Tk interface to the chaser demo). I also have a question about the proper handling of bug reports and change requests. That is, I have some complaints and suggestions regarding the implementation of plc_init() and the resolution of config files, but do not think it appropriate to change the system spec or code unilaterally. Does control.com have a bug tracking system that PuffinPLC plans to use for numbering bugs and tracking their states? And if the mailing list is the only forum for reporting and tracking bugs, do we have a "Subject:" header convention for distinguishing bug reports from other discussions? Other than perusing the comments in the source code, is there a published "to do list" of things that have already been identified as needing attention? By this, I do not necessarily mean new features, but areas where cleanup or improved robustness are needed. Greg Goodman Chiron Consulting [email protected] _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc