Roman: >> Also, to what degree do you intend to get involved with the >> project, in addition to whatever is needed to maintain the >> OpenSolaris spec file. > > All what it needs to offer actual spec files of a given > project.
Yes, I think that (strictly speaking) the OpenSolaris spec file maintainer is really only responsible for the actual OpenSoalris spec file. However, I think I'm trying to encourage that such maintainers should really consider being involved with the module community directly. For example, I own a number of spec files and common community tasks I do include: - Fixing bugs as they are noticed. Often these are Solaris specific build or runtime issues, but its also good to get involved with fixing bugs in general, if you have the time. - Familiarize yourself with the bugs for the module on whatever bug tracking tool is used by the module. It's good to be involved with adding comments if you notice any new information that might help resolve any bug (like perhaps letting them know that you can replicate the problem using OpenSolaris). - When we patch a module, I try to make sure that we file a bug in bugzilla (or whatever bug tracking tool/mail list/etc.) so that the fix gets upstream. This sometimes involves some interaction with the maintainer if they want additional changes made to get the patch upstream. - Review documentation and file bugs when issues are noticed, or otherwise help to improve manpages, gtk-docs, etc. so that they are as accurate as possible. I think that people considering to be a OpenSolaris spec file maintainer should consider getting involved in these ways, even if it isn't strictly required. Brian
