Hi pgRouting list members,<br><br>Exactly two weeks have passed since my previous email and I got positive feedback from the following people:<br><ul><li>Frederic Junod (Camptocamp)</li><li>Stephen Woodbridge (Imaptools)</li>
<li>Venkatesh Raghavan (Osaka City University)</li><li>Kai Behncke (FOSSGIS e.V) ... who was crazy busy with FOSSGIS, but I hope I understood you right, didn't I?</li></ul>I also would like to add Christian Gonzales, who was very interested in joining pgRouting last year and then started pgRoute project. We had some discussion about collaboration the last days, because there is a lot of overlapping between the two projects. <br>
<br>I added a Project Steering Committee Guideline to the wiki as a proposal:<br><a href="http://pgrouting.postlbs.org/wiki/PSC">http://pgrouting.postlbs.org/wiki/PSC</a><br><br>Jeff McKenna pointed me to the Mapserver RFC, which seemed to be more compact and understandable than the referenced GRASS document of the last email. (Also GEOS project uses the same PSC template btw.)<br>
I made very small changes like replacing project names and links and extended the voting period to four days for example. I also added the possible list of initial PSC members and I would propose Anton Patrushev as the initial Chair of the PSC.<br>
<br>If you have any comments, objections or questions, please ask!<br>If you changed your mind and don't feel like you want to join the PSC (anymore), or if you want to join now or want to propose someone else, you're welcome.<br>
Please speak up, if you haven't done so yet!<br><br>I think the PSC document in the wiki explains quite well, what a PSC is for and why it makes sense to have one. <br>IMO there is one very urgent task for a new PSC, which is to decide a new release based on the current SVN trunk version. Because the current pgRouting version 1.03 doesn't work anymore with the next GIS LiveDVD (with new PostgreSQL/PostGIS) and they don't like to checkout certain revision numbers ;-)<br>
I think, there is a lot more to discuss and to decide, but it should be done more open and transparent and by the community instead of informal decisions from desk to desk.<br><br>Best regards,<br>Daniel<br><br><br><br><div class="gmail_quote">
2010/2/21 Daniel Kastl <span dir="ltr"><<a href="mailto:daniel@georepublic.de">daniel@georepublic.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi pgRouting list members,<br><br>For some time already there hasn't been much activity in source code commits and new releases. The last release has been quite long time ago.<br><br>We (Anton Patrushev and Daniel Kastl) want to boost project activity and make it easier for others to join and influence pgRouting development. <br>
Looking at successful OSGeo projects we think that it should become easier to participate for everyone, and decisions should be made more transparent. <br><br>To get started Anton and I are in favor of establishing a PSC (Project Steering Committee) for pgRouting. <br>
A good description of the role of a PSC can be found in the GRASS project wiki: <a href="http://grass.osgeo.org/wiki/RFC1" target="_blank">http://grass.osgeo.org/wiki/RFC1</a><br><br>We believe that having a PSC would be the initial step for pgRouting to become more "open", to handle project management properly, to improve code quality, to hopefully extend functionality and of course to attract more developers and users.<br>
<br>To start an initial Project Steering Committee we're now looking for candidates. <br>Since the number of people who have been involved so far is rather small, we welcome anyone who has strong interest and/or motivation to participate.<br>
<br>Especially I would like to to invite the following people to participate in the pgRouting PSC:<br> - Frederic Junod (Camptocamp)<br> - Ema Miyawaki (Orkney)<br> - Stephen Woodbridge (Imaptools)<br> - Kai Behncke (FOSSGIS e.V)<br>
- Venkatesh Raghavan (Osaka City University)<br><br>If any other individuals/companies are interested, please raise your voice now!<br><br>Looking forward to hear some feedback,<br><br>Daniel<br> <br><br clear="all"><br>
-- <br>Georepublic UG (haftungsbeschränkt)<br>Salzmannstraße 44,<br>81739 München, Germany<br><br>eMail: <a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@georepublic.de</a><br>Web: <a href="http://georepublic.de" target="_blank">http://georepublic.de</a><br>
<br>Tel: +49 (089) 4161 7698-1<br>Fax: +49 (089) 4161 7698-9<br><br>Commercial register: Amtsgericht München, HRB 181428<br>CEO: Daniel Kastl<br><br><br>
</blockquote></div><br><br clear="all"><br>-- <br>Georepublic UG (haftungsbeschränkt)<br>Salzmannstraße 44,<br>81739 München, Germany<br><br>eMail: <a href="mailto:daniel.kastl@georepublic.de">daniel.kastl@georepublic.de</a><br>
Web: <a href="http://georepublic.de">http://georepublic.de</a><br><br>Tel: +49 (089) 4161 7698-1<br>Fax: +49 (089) 4161 7698-9<br><br>Commercial register: Amtsgericht München, HRB 181428<br>CEO: Daniel Kastl<br><br><br>