Hi Steve,<div><br></div><div>Thank you for the comments!<br><br><div class="gmail_quote">2010/11/15 Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Daniel,<br>
<br>
Wow! two big thumbs up! Thank you for all this effort and the results are very fine.<br>
<br>
One problem on the Download -> Code Respository section:<br>
<br>
woodbri@mappy:~/work/pgrouting-git$ git clone git@github.com:pgRouting/pgrouting.git<br>
Initialized empty Git repository in /u/work/pgrouting-git/pgrouting/.git/<br>
The authenticity of host '<a href="http://github.com" target="_blank">github.com</a> (207.97.227.239)' can't be established.<br>
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.<br>
Are you sure you want to continue connecting (yes/no)? yes<br>
Warning: Permanently added '<a href="http://github.com" target="_blank">github.com</a>,207.97.227.239' (RSA) to the list of known hosts.<br>
Permission denied (publickey).<br>
fatal: The remote end hung up unexpectedly<br></blockquote><div><br></div><div><br></div><div>Oh maybe this problem happened, because I have never tried to clone a repository recently, that I didn't create myself ;-)</div>
<div>It seems that there are several ways to access a repository:</div><div><ul><li>SSH read and write: git@github.com:pgRouting/pgrouting.git</li><li>Git read only: git://<a href="http://github.com/pgRouting/pgrouting.git">github.com/pgRouting/pgrouting.git</a></li>
</ul><div>I everywhere wrote the command with read and write access and didn't think about it. That might be the problem.</div></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
A couple of small suggestions for the Development page.<br>
<br>
1. I think it would be a good idea to have a "How To Contribute" page the has a short paragraph covering things that we think are important. Ideas like:<br>
o where to add documentation<br>
o How to use RFCs<br>
o coding standards if any (might just say to not reformat existing pages and to you style similar to existing).<br>
o test cases<br>
o examples<br>
o whatever you guys think would be appropriate and desirable for contributors to provide.<br></blockquote><div><br></div><div>Good ideas ... some points I don't know well about either, but maybe we can steal from other projects a bit.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
2. I think it would be helpful to add a link to 1-2 GitHub Tutorials out on the web.<br></blockquote><div><br></div><div>Yes, true. That's not so difficult.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
3. Does sphinx have the ability to automatically create a site map page? If so I think it might be useful to generate that and link it in somewhere. If not I'm not sure if it is worth the effort to generate and update manually.<br>
</blockquote><div><br></div><div>I don't really know. </div><div>When you create a new project with the wizard, it also creates this block on the index.html page in root:</div><div><br></div></div></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;">
<blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div class="gmail_quote"><div><div>Indices and tables</div></div></div></div></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;">
<div><div class="gmail_quote"><div><div>==================</div></div></div></div></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div class="gmail_quote">
<div><div><br></div></div></div></div></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div class="gmail_quote"><div><div>* :ref:`genindex`</div></div>
</div></div></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div class="gmail_quote"><div><div>* :ref:`modindex`</div></div></div></div></blockquote>
<blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;">
<div><div class="gmail_quote"><div><div>* :ref:`search`</div></div></div></div></blockquote></blockquote><div><div class="gmail_quote"><div><br></div><div>I don't know one of them could be useful. Only search worked from beginning, so I disabled the other two.</div>
<div>Sitemap is only mentioned in the documentation at toctree: <a href="http://sphinx.pocoo.org/markup/toctree.html?highlight=sitemap">http://sphinx.pocoo.org/markup/toctree.html?highlight=sitemap</a></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
<br></div><div>Daniel</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Great job on this.<br>
-Steve<div class="im"><br>
<br>
<br>
On 11/14/2010 8:13 AM, Daniel Kastl wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Hi list,<br>
<br>
It has started many months ago, but I'm glad to say there is some<br>
visible output now.<br>
I created a new pgRouting website, built with Sphinx, and I copied the<br>
relevant content from current TRAC wiki.<br>
<br>
If you have a time, please take a look at the current version and tell<br>
me, if something is missing.<br>
Let me know if you have ideas what could be done better:<br>
<a href="http://update.pgrouting.org/" target="_blank">http://update.pgrouting.org/</a><br>
(on the first page the "news" block and the "callout" to add some<br>
banners like the one for FOSS4G 2011 for example are still missing)<br>
<br>
If everything looks OK, I would propose to change to the new website in<br>
about a week or so.<br>
<br>
Next steps would be then:<br>
<br>
* Copy relevant tickets from TRAC to GitHub (-> Anton)<br>
* Cache the discussion forum as HTML and upload it to<br>
<a href="http://download.osgeo.org/pgrouting/forum/" target="_blank">http://download.osgeo.org/pgrouting/forum/</a><br>
* Prepare redirect from current <a href="http://pgrouting.postlbs.org" target="_blank">http://pgrouting.postlbs.org</a> to<br>
<a href="http://www.pgrouting.org" target="_blank">http://www.pgrouting.org</a> (also try to redirect missing links as<br>
good as possible) (-> Orkney)<br></div>
* Change DNS record of <a href="http://pgrouting.org" target="_blank">pgrouting.org</a> <<a href="http://pgrouting.org" target="_blank">http://pgrouting.org</a>> (Daniel)<div class="im"><br>
* Make the change final and announce it.<br>
<br>
If someone wants to help with the website, fix typos or add/edit<br>
content, I'm happy to add you as a committer to the repository on Github.<br>
There is a cron job running on the server that checks the Git repository<br>
every hour and updates the website if there are changes.<br>
<br>
Aside the website, a few other things have changed, mostly related to<br>
GitHub hosting:<br>
<br>
* All pgRouting related repositories will be in<br>
<a href="https://github.com/pgRouting" target="_blank">https://github.com/pgRouting</a><br></div>
o pgrouting (library): <a href="https://github.com/pgRouting/pgrouting" target="_blank">https://github.com/pgRouting/pgrouting</a><br>
o website: <a href="https://github.com/pgRouting/website" target="_blank">https://github.com/pgRouting/website</a><br>
o workshop (FOSS4G 2010): <a href="https://github.com/pgRouting/workshop" target="_blank">https://github.com/pgRouting/workshop</a><br>
o osm2pgrouting: <a href="https://github.com/pgRouting/osm2pgrouting" target="_blank">https://github.com/pgRouting/osm2pgrouting</a><br>
o pgrouting-contrib:<div class="im"><br>
<a href="https://github.com/pgRouting/pgrouting-contrib" target="_blank">https://github.com/pgRouting/pgrouting-contrib</a> (place to<br>
collect wrapper functions, examples, etc.)<br>
<br>
Especially to "pgrouting-contrib" and "website" I want to add anyone as<br>
committer, who would like to contribute, without restrictions.<br>
For all other repositories I hope that Git will make it easier to<br>
propose changes and patches by creating your own fork and sending "pull<br>
requests" to apply changes to the pgRouting repository.<br>
<br>
It has been a long way.<br>
<br>
Daniel<br>
<br>
<br>
<br>
<br>
--<br>
Georepublic UG & Georepublic Japan<br></div>
eMail: <a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@georepublic.de</a> <mailto:<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>
<br>
<br>
<br>
_______________________________________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a><br>
</blockquote>
<br>
_______________________________________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a><br>
</blockquote></div><br></div>