[pgrouting-dev] New website for review

pgRouting pgrouting-dev
1

Hi list,

It has started many months ago, but I’m glad to say there is some visible output now.
I created a new pgRouting website, built with Sphinx, and I copied the relevant content from current TRAC wiki.

If you have a time, please take a look at the current version and tell me, if something is missing.
Let me know if you have ideas what could be done better: http://update.pgrouting.org/
(on the first page the “news” block and the “callout” to add some banners like the one for FOSS4G 2011 for example are still missing)

If everything looks OK, I would propose to change to the new website in about a week or so.

Next steps would be then:

If someone wants to help with the website, fix typos or add/edit content, I’m happy to add you as a committer to the repository on Github.
There is a cron job running on the server that checks the Git repository every hour and updates the website if there are changes.

Aside the website, a few other things have changed, mostly related to GitHub hosting:

It has been a long way.

Daniel

–
Georepublic UG & Georepublic Japan
eMail: daniel.kastl@georepublic.de
Web: http://georepublic.de

2

Daniel,

Wow! two big thumbs up! Thank you for all this effort and the results are very fine.

One problem on the Download -> Code Respository section:

woodbri@mappy:~/work/pgrouting-git$ git clone git@github.com:pgRouting/pgrouting.git
Initialized empty Git repository in /u/work/pgrouting-git/pgrouting/.git/
The authenticity of host 'github.com (207.97.227.239)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

A couple of small suggestions for the Development page.

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:
o where to add documentation
o How to use RFCs
o coding standards if any (might just say to not reformat existing pages and to you style similar to existing).
o test cases
o examples
o whatever you guys think would be appropriate and desirable for contributors to provide.

2. I think it would be helpful to add a link to 1-2 GitHub Tutorials out on the web.

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.

Great job on this.
   -Steve

On 11/14/2010 8:13 AM, Daniel Kastl wrote:

Hi list,

It has started many months ago, but I'm glad to say there is some
visible output now.
I created a new pgRouting website, built with Sphinx, and I copied the
relevant content from current TRAC wiki.

If you have a time, please take a look at the current version and tell
me, if something is missing.
Let me know if you have ideas what could be done better:
http://update.pgrouting.org/
(on the first page the "news" block and the "callout" to add some
banners like the one for FOSS4G 2011 for example are still missing)

If everything looks OK, I would propose to change to the new website in
about a week or so.

Next steps would be then:

    * Copy relevant tickets from TRAC to GitHub (-> Anton)
    * Cache the discussion forum as HTML and upload it to
      http://download.osgeo.org/pgrouting/forum/
    * Prepare redirect from current http://pgrouting.postlbs.org to
      http://www.pgrouting.org (also try to redirect missing links as
      good as possible) (-> Orkney)
    * Change DNS record of pgrouting.org <http://pgrouting.org> (Daniel)
    * Make the change final and announce it.

If someone wants to help with the website, fix typos or add/edit
content, I'm happy to add you as a committer to the repository on Github.
There is a cron job running on the server that checks the Git repository
every hour and updates the website if there are changes.

Aside the website, a few other things have changed, mostly related to
GitHub hosting:

    * All pgRouting related repositories will be in
      https://github.com/pgRouting
          o pgrouting (library): https://github.com/pgRouting/pgrouting
          o website: https://github.com/pgRouting/website
          o workshop (FOSS4G 2010): https://github.com/pgRouting/workshop
          o osm2pgrouting: https://github.com/pgRouting/osm2pgrouting
          o pgrouting-contrib:
            https://github.com/pgRouting/pgrouting-contrib (place to
            collect wrapper functions, examples, etc.)

Especially to "pgrouting-contrib" and "website" I want to add anyone as
committer, who would like to contribute, without restrictions.
For all other repositories I hope that Git will make it easier to
propose changes and patches by creating your own fork and sending "pull
requests" to apply changes to the pgRouting repository.

It has been a long way.

Daniel

--
Georepublic UG & Georepublic Japan
eMail: daniel.kastl@georepublic.de <mailto:daniel.kastl@georepublic.de>
Web: http://georepublic.de

_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev

3

Hi Steve,

Thank you for the comments!

2010/11/15 Stephen Woodbridge <woodbri@swoodbridge.com>

Daniel,

Wow! two big thumbs up! Thank you for all this effort and the results are very fine.

One problem on the Download → Code Respository section:

woodbri@mappy:~/work/pgrouting-git$ git clone git@github.com:pgRouting/pgrouting.git
Initialized empty Git repository in /u/work/pgrouting-git/pgrouting/.git/
The authenticity of host ‘github.com (207.97.227.239)’ can’t be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘github.com,207.97.227.239’ (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

Oh maybe this problem happened, because I have never tried to clone a repository recently, that I didn’t create myself :wink:
It seems that there are several ways to access a repository:

A couple of small suggestions for the Development page.

  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:
    o where to add documentation
    o How to use RFCs
    o coding standards if any (might just say to not reformat existing pages and to you style similar to existing).
    o test cases
    o examples
    o whatever you guys think would be appropriate and desirable for contributors to provide.

Good ideas … some points I don’t know well about either, but maybe we can steal from other projects a bit.

  1. I think it would be helpful to add a link to 1-2 GitHub Tutorials out on the web.

Yes, true. That’s not so difficult.

  1. 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.

I don’t really know.
When you create a new project with the wizard, it also creates this block on the index.html page in root:

Indices and tables

==================

  • :ref:genindex
  • :ref:modindex
  • :ref:search

I don’t know one of them could be useful. Only search worked from beginning, so I disabled the other two.
Sitemap is only mentioned in the documentation at toctree: http://sphinx.pocoo.org/markup/toctree.html?highlight=sitemap

Daniel

Great job on this.
-Steve

On 11/14/2010 8:13 AM, Daniel Kastl wrote:

Hi list,

It has started many months ago, but I’m glad to say there is some
visible output now.
I created a new pgRouting website, built with Sphinx, and I copied the
relevant content from current TRAC wiki.

If you have a time, please take a look at the current version and tell
me, if something is missing.
Let me know if you have ideas what could be done better:
http://update.pgrouting.org/
(on the first page the “news” block and the “callout” to add some
banners like the one for FOSS4G 2011 for example are still missing)

If everything looks OK, I would propose to change to the new website in
about a week or so.

Next steps would be then:

If someone wants to help with the website, fix typos or add/edit
content, I’m happy to add you as a committer to the repository on Github.
There is a cron job running on the server that checks the Git repository
every hour and updates the website if there are changes.

Aside the website, a few other things have changed, mostly related to
GitHub hosting:

o pgrouting (library): https://github.com/pgRouting/pgrouting
o website: https://github.com/pgRouting/website
o workshop (FOSS4G 2010): https://github.com/pgRouting/workshop
o osm2pgrouting: https://github.com/pgRouting/osm2pgrouting
o pgrouting-contrib:

https://github.com/pgRouting/pgrouting-contrib (place to
collect wrapper functions, examples, etc.)

Especially to “pgrouting-contrib” and “website” I want to add anyone as
committer, who would like to contribute, without restrictions.
For all other repositories I hope that Git will make it easier to
propose changes and patches by creating your own fork and sending “pull
requests” to apply changes to the pgRouting repository.

It has been a long way.

Daniel

–
Georepublic UG & Georepublic Japan

eMail: daniel.kastl@georepublic.de mailto:[daniel.kastl@georepublic.de](mailto:daniel.kastl@georepublic.de)
Web: http://georepublic.de

pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev

pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev