On 8/20/07, Jochen Mader <[EMAIL PROTECTED]> wrote: > It is getting a little hard to follow the whole thing. > I think LLRP is reaching a critical mass (codewise and knowledgewise) > and we should probably start taking a look into gathering things. > Right now a lot of information is being scattered around in the mailing > list and it is hard for someone from the outside to really get hold of > everything that is needed and provided by the current project. > I suggest to put a description of the files and their purposes on a > wiki, by that providing a facility for everybody to collaborate on it > and also to provide the starting point for documentation. > Cheers > Jochen > >
Jochen -- A great idea. I think Paul's document is a step in the right direction of getting the design decisions down on paper. But a wiki would certainly lower the bar on collaboratively generating "first cut" engineering documentation. Eventually this stuff needs to be gathered into released documentation though, one way or another. But as a "living document" with a low bar to community changes/improvements wikis have some utility. Also you mention that it is not obvious what files are what. It looks like Gordon did put a README in the Definitions directory. I also have one in LTK-Perl. Is this the wrong place? Anyway, any volunteers for setting up and maintaining a wiki? -- John. ------------------------------------------------------------------------- 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/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
