Norm Jacobs wrote: > > FWIW, > > In the not to distant future, we will be integrating some templates for > projects to follow when integrating into the SFW build environment. > There are a few components that already use something close to the > approach we are looking at for these templates. If you take this > approach and use a couple of tools already in the gate, it should help > reduce some of the work involved in integrating into the build, make > things more consistent and hopefully eliminate some common errors that > we see. We are also looking at putting together some guidelines to help > developers and code reviewers identify and address problems earlier. > Anyway, templates, tools, and guidelines are meant as an aid, they are > not a replacement for common sense. If you are interested in getting > involved, please let me know.
Templates sounds like a good idea to me. As at the moment people seem to be using any random package as their templates which are not always that good as templates. Paul > > Paul Cunningham wrote: >> Vladimir, >> >> Note: I have changed the 'subject:' line. >> >> Vladimir Marek wrote: >> >>> I'm wondering, most of the comments that regularly show here could be >>> checked automatically. Wasn't there some thought about a tool which >>> would try to inspect package for correctness? I would be interested in >>> participating in such thing in order to learn more about current sfwnv >>> status. >>> >> >> I don't know about any suggested 'tool', but yes there should be >> something; >> either that or a "Pre Code Review" 'check-list' that must be completed >> prior to sending out a 'code-review request'. It does get a bit boring >> writing the same 'old' comments for the majority of the latest reviews >> I have done. >> >> Anyway I think that is really something for the sfwnv c-team to push >> forward. -- ---------------------------------------------------------------------- Paul Cunningham Software Engineer Tadpole Computer Products
