I'm learning about Pylons and I've read a few tutorials, but none of them have addressed collaboration practices.  Starting on a practice project. I'd like to keep my code in a revision-control system (Git, specifically) as if it were an open-source project with multiple developers, in order to practice that aspect of Pylons development as well.
I'm wondering what I should do with the development.ini file that was generated by Paster as part of my new application.  On one hand, it contains lots of settings that other develpers wouldn't want to have to recreate by hand, so it seems like it ought to be stored in my Git repository so that other developers can access it.  On the other hand, some of the settings, such as the database connection URL, are specific to one person's development environment and wouldn't make sense to share with others.
What do real-world Pylons applications do with this file?
You should check in development.ini. Most developers are smart enough to realize that if they want to run your application they need to make some tweaks. The development.ini will serve as a template. A file that has the database configured incorrectly is still useful since I can see that the system is trying to connect to the database and failing.
Later on you will be making files such as development.ini, staging.ini, and production.ini. This will help when you move environments.
Should Pylons' development.ini be checked in?