My own thoughts on this:

While I am not sure I would be able to maintain any modules directly, I would be MORE than happy to serve as a "Mac OS X" consultant for those who maintain modules and do not have access to OS X equipment.

I agree that some sort of consistency among all the modules is needed. Consistent APIs help keep developer productivity high and the amount of "surprises" to a minimum. When and how to aline the modules to a consistent state is another whole debate. My thought is sooner rather than later or do it at a major CMake release number, like 3.0, or have the new modules that break current CMakeLists.txt files as an Optional install for cmake, that way those of us working on projects can use the newer versions.. Just some suggestions..

I think Kitware should layout the "rules" for writing a module including naming conventions, formatting of the module, various options, and all that stuff. THEN a DEMO Module needs to be written that follows ALL the guidelines and shows lots of different scenarios that can be used: Windows specific stuff, OS X Frameworks stuff, Unix/ Linux specific stuff.

Like I said, just my thoughts.

--
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services


On Jul 25, 2007, at 10:11 AM, Bill Hoffman wrote:

CMake has been steadily growing in popularity over the past years. The
bug tracker has many bugs in it related to CMake FindXXX modules.
Since the CMake developers often do not have access to machines with
the software installed, or experience with finding/using many of the
packages found in the Modules directory of CMake, applying the patches
has not been happening at a reasonable pace. I would like to move to a
system where each FindXXX module in CMake has a dedicated volunteer
maintainer.

The maintainer would be responsible for tracking bugs and applying
patches to the FindXXX modules being maintained.   This could be done
via CVS write access to the Modules directory of CMake, or by sending a
patch via email, it would be up to the maintainer how they wanted to
manage the process.

I would like each module in CMake to have a maintainer listed in the
Module with contact information.  That information would be used in
the documentation generation, so that users would know who to contact
with problems or suggestions.  The maintainer would be expected to
have an account on the bug tracker and watch the bugs/patches for that
module.

For contribution of new modules to CMake, a proposal should be sent to
the CMake mailing list [EMAIL PROTECTED], and if the proposal is
accepted, and a maintainer is found, the module would be added to CMake.
Proposals for new modules should have [New Module] in the subject.
Patches for existing modules should be sent to the maintainer, or put
in the bug tracker.

If you are interested in maintaining an existing module in CMake, please
respond to the list.

Thanks.


-Bill





_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to