Yes, I think I can do that. I assume this would cover everything in /app/composer, but not anything else at the moment?<br>Steven<br><br><div><span class="gmail_quote">On 8/21/07, <b class="gmail_sendername">Marco Hugentobler
</b> <<a href="mailto:marco.hugentobler@karto.baug.ethz.ch">marco.hugentobler@karto.baug.ethz.ch</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Martin and Tim,<br><br>Thanks for your feedback and for the willingness to maintain the code. I will<br>adapt the draft organigram accordingly.<br><br>Gary and Steven,<br><br>Is it ok for you to be code maintainer for the code parts mentioned in my
<br>previous e-mail?<br><br>Best regards,<br>Marco<br><br><br>On Wednesday 15 August 2007 16:20:20 Marco Hugentobler wrote:<br>> Dear qgis devs,<br>><br>> In the psc, we recently talked about having more formalised processes and
<br>> clearer responsibilities in the qgis team.<br>><br>> From the development side, I'd like to have code maintainers for different<br>> parts of the code, e.g. for the different plugins and providers and parts
<br>> of the qgis libs. A code maintainer would review patches for the<br>> corresponding part, coordinate the efforts of interested developers, answer<br>> questions and make sure the code is in a clean and up-to-date state. I hope
<br>> that such an organisation will help us to better coordinate our efforts and<br>> make it clearer for new developers where to ask for guidance. It would also<br>> be visible which modules currently lack a maintainer (
e.g. in my opinion<br>> GRASS module).<br>><br>> The code maintainers would add one or more lines to their e-mail signature<br>> such to make it clear for everyone, e.g.<br>><br>> Tim Sutton<br>> .....
<br>> Maintainer QGIS raster module<br>> ...<br>><br>><br>> I could imagine the following parts of code:<br>><br>> - raster: Tim<br>> - python bindings: Martin<br>> - core lib: Martin<br>> - gui lib: Martin
<br>> - app (dialogs): Tim<br>> - mapserver export: Gary<br>> - delimited text: Gary<br>> - print composer: Steven<br>> - wfs, wms: Marco<br>> - renderers: Marco<br>><br>> and other parts that need maintainers:
<br>> - GRASS plugin/provider<br>> - postgres provider<br>> - ogr provider<br>> - gps plugin/provider<br>> - georeferencer plugin<br>> - project file<br>><br>><br>> What are your opinions about this this in general? Do you like it too or is
<br>> it just unnecessary complication?<br>><br>> For the areas of code, I'm sure I missed a lot of things. And probably<br>> there are even volounteers for the second part of the list...<br>><br>><br>
> Regards,<br>> Marco<br><br><br><br>--<br>Dr. Marco Hugentobler<br>Institute of Cartography<br>ETH Zurich<br>Technical Advisor QGIS Project Steering Committee<br><a href="mailto:marco.hugentobler@karto.baug.ethz.ch">
marco.hugentobler@karto.baug.ethz.ch</a><br></blockquote></div><br>