Anyone got any ideas about how we can run a semi informal review process on any major new additions. When a page has been up for a while just going in and making them change is reasonable, but if the person is in the process of still putting it together what is the best way of providing feedback. Is it just a matter of ensuring that a page isn't linked to in the wiki until people have had a chance to look over it and comment? Do we discuss it on the mailing list when there are issues, or put comments direct into pages?
Graham Martin Stoufer wrote .. > Everyone, > I just got around to reading the email from the list regarding the > session/class pages I put up. I think it's best that I take them down > for the time being until I have a better handle on things. Aside from > the few typos I made, the content up there isn't what it should be. > > I'm still motivated to post a simple and direct 'hello world' example > that introduces beginners to the core functionality and issues to > address when using sessions with classes. From the valuable feedback > I've gotten so far, I wonder if this is even possible. > > And yes, I agree that all the documentation on the wiki should be > addressing the current release (3.3) and let others augment with > notes/sub pages functionality in older releases. > > -- > * Martin C. Stoufer * > * DST/DIDC/ITG * > * Lawrence Berkeley National Lab * > * MS 50B-2239 510-486-8662 *
