[CMake] Call for Module maintainer volunteers

[Pau Garcia i Quiles]

Quoting "Miguel A. Figueroa-Villanueva" <miguelf at ieee.org>:

+1 to both


> Hello,
>
> As co-author (with Jan Woetzel) of the FindwxWidgets I'd be happy to
> maintain it.
>
> I also recently made changes to the FindLATEX and FindImageMagick in
> my local repository. I'd be happy to apply the changes if accepted by
> the list and maintain the modules.
>
> I like this idea, but I have a couple of suggestions/questions:
>
> 1. Given the cross-platform nature of these modules, in many cases a
> recruiter for at least the Unix, Win32, and MacOS platforms should be
> maintaining the module... Of course, this will be hard to find so what
> would be the process for a maintainer to apply patches to platforms he
> doesn't know or have access to? Ask in the list or just blindly apply
> patches submitted to those platforms?
>
> I for one have no idea how things are setup in the APPLE platforms...
> I do have access to Win32 and unix-like platforms.
>
> 2. Now that more people are likely to be applying changes to different
> modules, more effort should be put to standardizing the naming
> conventions and interface. Also, I would vote for a coordinated
> deprecation system so that the modules can all evolve to this
> standard.
>
> This is related to my previous posting
> (http://www.cmake.org/pipermail/cmake/2007-July/015168.html).
>
> My two cents,
>
> --Miguel
>
> On 7/25/07, 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 cmake at www.cmake.org, 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 at cmake.org
> http://www.cmake.org/mailman/listinfo/cmake



-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to the amount of work, I usually need 10 days to answer)