Hi Brian, On Wed, 2007-12-12 at 19:05 -0600, Brian Cameron wrote:
> Questions include: > - Briefly describe the functionality provided by the open > source technology? It would be a good idea to fill the %description field with this information. > - Is the open source technology an implementation of an industry > standard? > > Note that code that supports any proprietary software or > hardware should be mentioned. For example, device support > or support of a particular format, or a codec. This is a bit more work. > - Without doing any research, are you aware of any patent or > copyright lawsuits or claims relating to the open source > technology? > > - What is the license? Provide the full text. Instead of providing the full text, perhaps we could just fill in the License field in all spec files and maybe add a URL to the license where it's not one of the widely used ones. > - What is the abstraction layer between the code and the rest > of the system? How is the code segregated from the rest of > the system? For example, it is inappropriate to link non-GPL > code into a GPL program. Explain any such issues. Grr... I was always unsure what to write in this box (: > - Pointers to any documentation, websites, project home pages > that should be used to reference the project. We already have the URL field filled in for most modules. > That doesn't seem like a burdensome amount of work to expect > someone to do if they wish to be an OpenSolaris module maintainer. Well, it's not very exciting to do this paperwork, the good news is that it's usually only needed once. > Perhaps we could set aside a spot on the OpenSolaris Wiki to store > this information so it can be referenced and easy to put together. > Helping with this work would be of great assistance to getting > any modules into Nevada. I think the spec file itself is the best place for this information. > Another process that is useful is the ARC (Architecture Review > Committee) process, where we document and review module interfaces. Right. We could possibly also include a list of imported and exported interfaces in the spec file. Laca
